The tag-readme trace read as a self-improving loop
Type: kb/types/note.md
The observed trace discharges causal connection. Read against self-improving system, the same change also discharges that definition, which asks for two things the reflective obligations do not: a change to the system's own organization, and a response to evidence about an objective it could have failed. Commonplace improves in the proposal-selection shape — draft a candidate, review it with a real chance of rejection, merge selectively — so that loop is the grid to lay over the trace. This note does the full mapping; the classification draws the human, joint, and computational allocation profile from it.
| Requirement | In the trace | Runs in |
|---|---|---|
| Change to the system itself | The edit landed on kb/types/tag-readme.md, a self-representing artifact rather than ordinary content. |
— |
| Search | Splits: a maintainer noticed the index type was doing two jobs and that the learning-theory head had outgrown its completeness claim. Formulating that into ADR 026's specific candidate ran through an agent retrieving stale indexes are worse than no indexes as self-representation and drafting the split around it. |
Human, then computational; the candidate path is joint overall |
| Improvement objective | The bar the change could have missed: a marked head must not mislead a thorough reader, per stale indexes are worse than no indexes. ADR 026 makes it testable — complete is a mark the validator can falsify. |
Human frames it; code checks it |
| Evaluation | Tests and the validator mechanically check that the marks are consistent; the judgment that the split was the right shape was the maintainer's. | Split |
| Operative retention | The three consumers — enforcement, routing, advice — keep acting on the change after merge. | Code (after human merge) |
What the mapping settles, and what it does not
Naming the objective is the step the reflective reading never had to take, and it is what makes the loop improvement-directed rather than merely change-directed. A change loop with no objective can only report that something moved; this one can report that a specific bar — do not mislead a thorough reader — is being held, and can fail against it.
The honesty check lives here too: the validator passing means the marks are consistent, not that the type split actually made the KB better. Evaluating the objective is mechanical; evaluating whether the objective was worth adopting is not, and that judgment stays the maintainer's. The pass is a result; the improvement is still a claim.
The allocation the mapping exposes
Search and evaluation are joint: the maintainer chooses the target and judges the design's shape, while the agent formulates the candidate and the validator checks the codified objective. Retention becomes computational after human adoption. The whole pathway is reflective because the accepted change is mediated through operative self-representation, but that does not determine actor allocation. Human gates remain where no adequate automatic check reaches, since warranted autonomy is bounded by oracle domain.
Relevant Notes:
- Commonplace as a reflective self-improving system — part-of: the classification and allocation profile this reading supports
- The tag-readme change as an observed causal-connection trace — part-of: the trace this reading interprets
- Where change candidates come from in Commonplace — part-of: surveys the wider set of candidate-forming mechanisms the agent's role in Search is one instance of
- Methodological and computational closure track different changes — rests-on: why actor allocation is reported separately from the pathway's reflectivity
- Self-improving system — rests-on: the definition this trace is read against
- A proposal-selection improvement loop requires search, evaluation, and operative retention — rests-on: the search/evaluation/retention grid used here
- warranted autonomy is bounded by oracle domain — rests-on: why the human gates sit where the oracle runs out
- stale indexes are worse than no indexes — rests-on: the improvement objective the loop aims at