nfrs.sgit.ai / admin / versions

Release history

Every push to the release branch is a minor release, tagged automatically from one version file that has to agree with the release commit's subject before the tag exists. How the pipeline does it.

VersionDateWhat shipped
v0.1.2 25 Aug 2026 The hub checks its own spokes. check_siblings.py reports whether every sibling host this site links actually answers, and it found the one defect worth finding: the network line said sentinel. where the site is sg-sentinel. — a wrong hostname carried straight over from the house pattern and repeated on four pages. It is deliberately a report and not a gate. This site links twelve hosts it does not control, so wiring their availability into CI would mean a sibling's outage turns this repository's build red for a reason nobody here can fix; a gate should fail for defects its own repository can correct, and everything else is a report a human reads before a release. The first run is published on the comms board with its date: twelve of fourteen answering, with coding. and skills. linked, correctly named, and not yet shipped. Those links stay — removing a correct link to an unshipped sibling would hide a fact about the network rather than fix one.
v0.1.1 25 Aug 2026 The gate could not find itself. v0.1.0 shipped with the whole of admin/build/ untracked: the repository was created from the stock Python .gitignore, whose build/ line silently swallowed the site's own build tooling, so CI checked out a tree with no validate.js in it and the pipeline stopped at its first step. The sibling repositories all carry the negation line for exactly this reason; this one now does too, with the incident named beside it. Worth recording rather than quietly fixing, because it is this site's own recurring finding arriving on day one and from an unexpected direction: the gate was written, tested, and shown to fail correctly on three seeded defects — and none of that mattered, because the file was never in the commit. A check that is not present is indistinguishable from a check that passes, which is the same defect as the structural guard that has never worked, one layer further out. The fix ships as a release rather than an amend: every push to the release branch is a release, and the first thing this pipeline should be able to show is that it recovers in the ordinary way.
v0.1.0 25 Aug 2026 The site, first release — the hub, its rules, and the pipeline that enforces them. Built from the v0.33.62 brief pack, in the build order the brief specifies. The topic map first, because it is the hub's reason to exist: every non-functional-requirement topic with its position in a line, its canonical source, and its owning site, plus the owns-versus-links contract that keeps a hub from restating its spokes. Then the memory thesis — these sites as a more evolved form of what is usually called LLM memory, with the evidence that it was already the design and the four staleness failures that are its honest limit. Seven owned disciplines, each closing with its counter-evidence rather than a summary: testing and why no-mocks is affordable here and not elsewhere, CI as build-once-verify-before-naming, documentation as a truth system, the methodology published outside the estate for the first time, resilience as design-for-the-failure-you-had, budgets as discipline with every figure deliberately absent, and how a brief becomes work here — the system demonstrated across thousands of documents and described as a system nowhere until now. The honest column ships with the rest rather than later: the scorecard with no plain tick in it, the backups stub published as an absence with the question that has to be answered first, and what this site asserts versus what it can show, including its own unbuilt generators. The two rules the site teaches are enforced on it by CI: a discipline page citing no sibling fails the build, and a page carrying figures without an as-of date fails the build. Plus the agent surface the brief asks for — llms.txt, llms-full.txt, a markdown twin, and the brief pack fetchable at constructed URLs — and the eight source documents published whole, minus the manifest that indexes withheld material.