standards.sgit.ai / documents
The documents
The eleven source documents behind this site, captured verbatim under briefs/ and readable here. The raw markdown is the source of truth; the page is presentation. That raw-plus-curated split is the provenance discipline this site argues for, applied to itself — and it is why every document is fetchable at a constructed URL, /briefs/<filename>.md, which agents may rely on.
| Document | Type · date | In one line |
|---|---|---|
| The brief pack — overview | Pack overview · 23 Aug 2026 | The commission in summary: four corrections to the premise, the naming argument, the three architectural decisions to make first, and the one question that needs answering before the next vault publishes. |
| The commission | Brief · 23 Aug 2026 | The memo, the four corrections, the LAW/STANDARD/FRAMEWORK argument for keeping the site's name, the thesis, the honesty constraint, and the build order — published unresolved. |
| Standard by standard | Inventory · 23 Aug 2026 | Instrument by instrument with LAW/STANDARD/FRAMEWORK labels, depth ratings, republishable yes/no, the ranked build order, and the eleven worked examples this site's proof pages come from. |
| Vaults are the substrate | Architecture · 23 Aug 2026 | The load-bearing document. The vault/repo fork and its resolution, the per-standard vault layout, the two-hash scheme, the taxonomy/ontology split, zip distribution, and the publishing discipline. |
| The keys vault | Architecture · 23 Aug 2026 | The private vault over the vaults: why escrow is a precondition of publishing, what goes in the register, the threat model, rotation, and the recursion that must be answered before the vault is created. |
| Tools outside the vault | Architecture · 23 Aug 2026 | Three working precedents, the contract between a tool and a vault, and five tools ranked by value over effort — with what must be true before the crosswalk browser can ship. |
| The cross-standard layer | Method · 23 Aug 2026 | Why the meta layer ships before any instrument: the node and edge grammar, bridges-not-merges, authority anchoring, the subset method, the grounding ladder, and the named prior art. |
| Site architecture | Design · 23 Aug 2026 | Page by page, what is a page and what is a vault and what is both, the naming conventions, and the house pattern this site is built on. |
| Boundaries and licensing | Legal · 23 Aug 2026 | The ISO blocker, the readiness trap, the citation problem, network boundaries, and house style. §4 is redacted in this edition — the reason is on the page. |
| Gaps and open questions | Status · 23 Aug 2026 | Nine things that must be built fresh, nine open questions published unresolved, eight honest tensions, and the loose ends worth an hour each. |
| Licence | Licence · 23 Aug 2026 | CC BY 4.0 for this site's own writing, and the republishability table that governs every instrument folder — including the one instrument family that cannot be republished at all. |
What was removed, and why the removal is published
Two things from the original pack are not here.
- §4 of Boundaries and licensing is redacted. It indexes twelve source paths that must not be published, and several of the reasons are themselves the disclosure — one names a company and enumerates its unfulfilled statutory obligations, one names a third party and its alleged breaches (and flags defamation risk in doing so), two name private individuals with signature blocks, one describes a live unremediated vulnerability. Reproducing the index would reproduce a usable summary of every one of them. The classes are published; the entries are not.
- The 50-row source manifest is not published at all. It maps every source document to an internal repository path, and six of its rows are marked do-not-publish for the reasons above. A path index to material that must not be published is itself a finding aid for it.
Publishing the redaction rather than removing the sections silently is the same judgement those sections ask for, applied to them. Where we lose →
Reading order
- The commission — the four corrections to the premise. Each one changed what got built.
- Vaults are the substrate — the load-bearing document, and the one architectural fork this site publishes rather than settles.
- The cross-standard layer — why the method ships before any instrument.
- Gaps and open questions — read this before believing anything on the rest of the site.
Licence. The pack and this site are CC BY 4.0, attributed to Dinis Cruz with AI co-authorship. The instruments themselves keep their own licences — and one of them cannot be republished at all.