How it is built and kept

A system built and run by one person survives by refusing scope. Every practice system drifts toward more: more coverage, more copies, more tooling. Here each refusal is deliberate, and each is enforced by structure or a check rather than by intention.

Four things this is not

Four neighbor systems sit one step away, and the practice refuses each:

not an encyclopediacoverage is not the goal, and a gap is not a defect. The entry check refuses material that only restates what a model produces on demand.

not an archivewhat is kept cold is detached from the working system. Nothing reads it and nothing depends on it, so it cannot rot the working store.

not a sync platformcontent moves between machines through version control only. One auditable path. A second path would be an unaudited second write history.

not groupwarebuilt for one working mind. Multi-user features are out of scope by construction, which is what keeps the rest this simple.

The keeping decision

Material that enters the practice meets one decision: is it worth keeping, and at which grade?

One class of full documents is kept: the owned source originals, held beside the knowledge base because the byte comparison on the trust page needs them. Everything else in the working store is processed material with a grade.

Kept by review

The machinery is maintained the way it was built. Reviews on a schedule read the logs the checks keep: what was caught, what was refused, what went quiet. Machinery whose record goes quiet is removed, as the rules page describes. The reviews exist so the system stays the size one person can hold.