NFRs — non-functional requirements — is this project's own operative term for version control, reliability, resilience, security, backups, consistency, explainability, and documentation. That sentence was written a month before this site was conceived, and it is the site's table of contents. Other sites in this network sell the argument that somebody has to be the villagers. This one is the same sentence from the inside: how the NFRs actually get done here, including where they do not.
“What I call the non-functional requirements, which fundamentally is the whole version control, reliability, resilience, security, backups, consistency, explainability, and documentation.”
Quoted verbatim wherever this site states its scope, because the scope is the quote. Eight items. This site owns the disciplines among them that have no other home, links the ones that do, and publishes the fact that the eighth — backups — has no doctrine written anywhere.
Most of the topics on that list already have an owner somewhere in the network. A hub that restates what its spokes measured is worse than no hub, so this one has a rule it enforces in CI rather than in prose.
| The rule | What it means here |
|---|---|
| Link the measurement, never restate it | When a sibling site has measured something, this site links that page. It does not re-measure and does not paraphrase the number. |
| Generate or date every number | Every figure on this site carries an as-of date or is generated at build time. The pre-release gate rejects a page that carries figures without one. |
| Every discipline page ends with its counter-evidence | A page teaching a practice closes with the measured places that practice failed here. |
The stakes are raised by the memory thesis: if these sites are memory an agent reads, a stale page is not an inconvenience, it is a false memory. The freshness discipline and the thesis arrive together or not at all.
The disciplines with no other home in the network, each with its position, its verbatim material, and the measured places it did not hold.
Every NFR topic: what it means here in one line, where the canonical material lives, and which site owns it. One page an agent reads to know where everything else is.
Read → OwnedNo mocks. No patches. Assert on contracts, not implementation. Deploy via pytest. Affordable because the type system and the testing philosophy were one decision.
Read → OwnedThe pipeline is a verifier, not a runner: build once, verify before naming. Push by digest, test the pre-tag image, only then assemble a manifest.
Read → OwnedIf the reality document doesn't list it, it does not exist. Briefs are aspirations, not facts. The best NFR idea in the estate, and manually enforced.
Read → Never publishedThe named methodology, in versioned guides written explicitly for LLMs, centred on preserving developer flow state. Nobody outside this estate has seen it written up.
Read → Owned patternDesign for the failure you had, not the one you imagine. Every mechanism here traces to a named incident — which is the doctrine, and it was nowhere written down.
Read → Discipline onlyProfitability-first · pre-approve the ladder · budget-on-the-step. The discipline is published; this estate's own figures are not, and that boundary is stated on the page.
Read → OwnedThe project manager is where the register becomes work — plus how a brief becomes work here, a system demonstrated across roughly 4,000 documents and described as a system nowhere.
Read →A site teaching NFRs from an estate whose scorecard is mixed is credible in a way no clean-room guide is. A clean column would be dishonest. Every lapse below is already published in a sibling pack with its evidence — this site adds assembly, not exposure.
| NFR | The estate, measured as of 24 Aug 2026 |
|---|---|
| Version control | ✅ auto-increment tags, the version file convention, a hundred days of dense history |
| Reliability / resilience | ✅ watchdog, health poller, bake-and-verify — and a dead workflow invoking a binary defined nowhere, sixteen times, that nobody noticed |
| Security | ✅ key discipline, deny-by-default allowlists — and one disclosed key-in-history incident, handled well |
| Backups | ⚠️ the thinnest topic in the corpus: mentioned constantly, no doctrine anywhere |
| Consistency | 🟡 total banner compliance beside partial import alignment; four stale sources of truth |
| Explainability | ✅ reality docs, provenance — and no evals anywhere |
| Documentation | ✅ a governing rule and a corpus over a million words — and a README describing a repository that does not exist |
Seven rows for eight NFRs: reliability and resilience are one row because the corpus uses them interchangeably. The full table, with every cell linked to the sibling pack holding its evidence and the numbers left where they were measured, is on the scorecard.
The clearest statement of what this whole network is for was made in a chat message, and it belongs on a page.
“The idea of these sites is to provide good briefs for agents to learn about how we work and think — these sites are a more evolved and focused version of what is usually called LLM memory.”
Conventional memory is accumulated transcripts, retrieved by similarity, private to one vendor, unversioned and invisible to the person it describes. This is the same function built as publishing: memory you can read, cite, version, license and hand to any agent, because it is a website. The thesis, the evidence that it was already the design, and its honest limits →
The same distinction this estate's own documentation rule insists on, applied to the site making the argument.
Which claims here are backed by a measurement in a sibling pack, which are positions, and which are proposals nobody has built. Kept as a table, not a tone.
Read → The gapThe eighth item on the list, in an estate with irreversible publishing and frozen vaults, with no written backup or recovery discipline. The stub is published so the gap is visible.
Read → EngineeringValidate → tag → deploy, with the hub's own rules as CI checks: every discipline page must cite a sibling, every page carrying figures must carry a date.
Read → The sourcesThe seven documents this site was built from, published whole and readable in-page. The raw markdown stays the source of truth.
Read →