Two known caveats of the score-driven regen loop, called out in README §"Score-driven regen loop":
- No max-iteration cap. If a doc consistently scores below
TIER1_THRESHOLD = 0.85 (e.g. source is genuinely malformed or has unparseable generate blocks), the loop runs indefinitely. Fix: hard cap at ~5 iterations, log+park.
- No best-so-far retention. Each regen overwrites the previous doc on disk. If round-2 produces a worse doc than round-1, the better one is lost. Fix: keep the highest-scoring version per element across all regen rounds and only commit-to-disk when the new score beats the stored max.
Both are documented but not fixed yet. Low priority — current corpus converges in 2-4 iterations in practice.
Two known caveats of the score-driven regen loop, called out in README §"Score-driven regen loop":
TIER1_THRESHOLD = 0.85(e.g. source is genuinely malformed or has unparseable generate blocks), the loop runs indefinitely. Fix: hard cap at ~5 iterations, log+park.Both are documented but not fixed yet. Low priority — current corpus converges in 2-4 iterations in practice.