Ideas · Builder Notes
Closing Tier 0 defects, and ticking boxes only when the code agrees
How I closed the Kognita alpha Tier 0 defect list for 0.3: real fixes where needed, proof tests where the note had drifted, and one checkbox per pull request.
Before
The 0.3 definition of done had a list of Tier 0 defects. Some were real, some had already been fixed in code but not in the notes.
After
Each item got its own pull request. Real fixes: foreign keys on evidence payload references, and keeping the vector index in step on the embedding write path. Stale items, such as entitlements failing open and engages missing from the protocol, got a test proving the current behaviour and a note marking the drift. The classifier replay, injection relabel and conformance kit lines were ticked only after the tests held.
The rollup line 'All Tier 0 defects closed' was ticked only after every box under it was re-checked against the code.
Why it matters
Drift is a finding in itself. Writing down 'the note was wrong' was more useful than quietly tidying the roadmap.
One drift stayed open on purpose: a typed classification could still replace the classifier's label, including a lower one. That was fixed later in 0.5.
One checkbox, one pull request, one test. It makes a definition of done auditable.
Sources
Kognita is an open-source alpha. This note comes from Kognita PR #19, Kognita PR #20, Kognita PR #21, Kognita PR #22, Kognita PR #23, Kognita PR #24, Kognita PR #25, Kognita PR #27 in the Kognita repository.