nfrs.sgit.ai / documentation

Documentation is a truth system, not prose

Every project has documentation and most of it is wrong, because documentation defaults to describing what somebody intended. This estate's governing rule attacks that directly, and it is the single best non-functional-requirement idea in the corpus.

“If the reality document doesn't list it, it does not exist. … Briefs are aspirations, not facts.”

Why this is a truth system rather than a style guide

The rule creates a single privileged document per domain whose job is not to explain anything but to enumerate what is actually there. Everything else in the corpus — briefs, designs, proposals, debriefs — is explicitly demoted to aspiration. That demotion is the load-bearing half. A corpus in which every document has equal standing has no way to answer does this exist?, and an agent reading it will confidently describe a feature somebody once proposed.

The rule does not make documents accurate. It makes the corpus answerable: there is exactly one place to look, and everything else is marked as not that place.

The supporting disciplines

DisciplineWhat it doesWhat it costs
PROPOSED labelsUnbuilt features are labelled in place, so a reader who never sees the reality document still gets the warning.Someone has to remove the label when it ships, and nothing checks.
The markdown twinEvery page is fetchable as markdown at a constructed URL, so a traversing agent never has to parse HTML.Two artefacts per page, which is a drift surface unless generated.
Day-indexesEvery working day gets an index of what was produced, which turns a corpus into a timeline.Discipline, daily.
Good-failure / bad-failure debriefsFailures are classified rather than just recorded: a good failure is one that taught something for its cost.Requires writing the debrief while the failure still stings.
Licence footer as a corpus ruleEvery document carries its licence, so any fragment stays attributable when it travels.Trivially automatable, and therefore the one that holds.
Handover guidesA session that ends writes down how the next one starts. Don't improvise.The value is invisible until the handover happens.

Note the pattern in the cost column: the disciplines that hold are the ones a machine enforces, and the ones that drift are the ones that need a person to remember. That is not a criticism of the people. It is the finding.

Counter-evidence

The system exists, at scale, and it failed twice in exactly the way the cost column predicts. Published as found as of 24 August 2026:

Both are documented with their evidence at sgit.ai, which owns the corpus and the repository the fictional README described; the conventions half of the finding belongs to coding.sgit.ai. This site links rather than re-measures, per the hub contract.

The fix this estate would recognise

The corpus already has a precedent for turning a manual rule into a machine one: the licence footer holds because an audit script checks it. The same move applies here.

A reality-document freshness check in CI, exactly like the licence audit: a reality document older than the code it describes fails the build.

This site runs the small version of that idea on itself. The pre-release gate rejects a page carrying figures without an as-of date, and rejects a discipline page that cites no sibling — both of which are freshness checks wearing different clothes. It is a much easier problem on a sixteen-page site than on a corpus, and that difference is stated rather than glossed: this is a demonstration of the shape, not a solution to the hard case. The hard version is listed as proposed, not built.