sgit newsroom v0.1.29 · snapshot 2026-09-24

Reading room · nfrs.sgit.ai · llms-full

On this page

Reading room / nfrs.sgit.ai / llms-full.txt · section 4 of 12

nfrs.sgit.ai — brief pack

For: the agent commissioned to build nfrs.sgit.ai From: Dinis Cruz, via the SG/Send Librarian Version: v0.33.62 · 24 August 2026 Licence: CC BY 4.0 — see LICENSE.md


What this is

The home for the non-functional-requirements topics — CI, testing, security, scalability, resilience, explainability, serverless, architecture, documentation, budgets, project management — built as the network's hub: it owns the disciplines that have no other home, and the topic map that shows an agent where everything else lives.

The name is right. nfrs.sgit.ai is the corpus's own operative term — the villagers brief defines it verbatim: "the whole version control, reliability, resilience, security, backups, consistency, explainability, and documentation." That sentence is the site's table of contents. Expand the acronym in sentence one; otherwise ship it.

And the commissioning message contains the network's purpose statement:

"these sites are a more evolved and focused version of what is usually called LLM memory."

02__ develops that into a page — memory you can read, cite, version, license and hand to any agent, because it is a website — and recommends it for the sgit.ai hub too.


Read in this order

FileWordsWhat it does
00__BRIEF.md1.1kStart here. The naming verdict, the hub shape, the owns/links split, the scorecard
01__the-topic-map.md0.8kThe hub's core artefact — every NFR topic: position in one line, canonical source, owner site
02__the-memory-thesis.md0.7kThe sites-as-agent-memory page, with the evidence it was already the design (for_llms filenames, the markdown twin, the agent-access report)
03__the-owned-disciplines.md0.8kTesting, CI, documentation/reality, budgets, PM — position, verbatim material, counter-evidence
04__site-architecture.md0.3kPage by page; the generate-or-date rule
05__boundaries-and-licensing.md0.3kThe hub's contract: owns vs links-and-never-restates
06__gaps-and-open-questions.md0.7k6 build-fresh items, 5 open questions, 4 tensions
09__source-manifest.csv23 rowsEvery source, tiered 0–3, every path verified on disk

The four things worth your attention

1. The scorecard is the credibility move. The estate measured against its own eight-NFR list: version control ✅, resilience ✅-with-a-dead-workflow, security ✅-with-one-disclosed-incident, backups ⚠️ no doctrine at all, consistency 🟡, explainability ✅-with-no-evals, documentation ✅-with-a-fictional-README. Every lapse is already published in a sibling pack — this site adds assembly, not exposure. A clean column would be dishonest; the mixed table is the teaching.

2. IFD is the most original owned asset. Iterative Flow Development — the estate's named methodology, versioned guides at v1.2.x, written explicitly "for LLMs assisting with IFD-based development… preserving developer flow state." Nobody outside the estate has ever seen it. Publishing it is also a test of the open-source position ("the moat is a rate, not a wall") — 06__ Q3 says decide that explicitly rather than assume it.

3. The most original PM page is a description of what already happens. "How a brief becomes work here" — acceptance criteria, same-day cross-team reviews, day-indexes, numbered asks, good-failure/bad-failure debriefs, ~4,000 documents of demonstrated practice, described nowhere as a system. It doubles as onboarding for every new agent session, which is the memory thesis in action.

4. Backups is the honest gap. The eighth item on the corpus's own list, 151 mentions, no doctrine — in the estate with irreversible publishing and frozen vaults. 06__ Q5 asks the right first question: is the vault model (versioning + escrow) already the doctrine, unnamed? An hour of thinking, then either the page or the dated stub.


The hub's one rule

Link the measurement, never restate it; generate or date every number. This site quotes more sibling measurements than any other — it has the most to lose from drift, and the memory thesis raises the stakes: a stale page in an agent-memory network is a false memory.


This file is released under the Creative Commons Attribution 4.0 International licence (CC BY 4.0).


== briefs/v0.33.62__nfrs-brief-pack__00__BRIEF.md