The source documents
Everything on this site is written from these 12 documents — 15,244 words commissioning it, and the measurements behind them. They are published in full, because a site that audits a platform should be checkable against the audit it was given.
The raw markdown is the source of truth. Each reader page renders its document from the raw file in briefs/ at load time; if that fails, the page falls back to a link to the raw file. Nothing is transcribed by hand, so a reader page cannot say something the document does not.
Every file is fetchable at a stable constructed URL: /briefs/<filename>. That is a promise, not an accident.
Read them
The brief
The commission, the rename verdict with the number that settles it, the one-character bug, what “very mature” measures out at, the honesty constraint, and the build order this site was written against.
Read it →What it actually is
The two ephemeral layers the site must not conflate, sessions and the thread-affinity bug behind them, the watchdog, both API surfaces, the auth-model correction, the isolation table, and how artefacts come back.
Read it →The rename
Nine acceptance criteria scored against the tree, the guard that could not match what it guarded, the full breakage list, the recommended sequencing, and the domain collision.
Read it →The maturity audit
Where the maturity is real — tests, history, CI/CD, documentation, operational hardening — and the four specific places the claim is overstated. Ends with the paragraph this site publishes verbatim.
Read it →The spec system
One abstraction, sixteen implementations, three generalisation mechanisms, the entry-point path for third-party specs, and why the family view carries the argument the alphabetical list does not.
Read it →The serverless argument
“We are competing for the agent-deployment market.” The positioning, the trade stated honestly, the cold-start ladder against the measured benchmarks, the 50-second number, the recursion, and what can and cannot be said about cost.
Read it →The site architecture
The house pattern, the one rule no sibling site needs, the page-by-page plan, what is generated versus written, and the naming conventions. This document is the specification this site was built to.
Read it →Boundaries, redaction and the disclosure
What was checked and is clean, what must be redacted, what must not be published at all, how to publish the one security note, and the network boundaries. Published redacted under its own rule.
Read it →Gaps and open questions
The five-day fix list that changes what this site can honestly say, eight build-fresh items, eight open questions published unresolved, seven honest tensions, and the loose ends worth an hour each.
Read it →The pack README
The reading order, the one-character bug as the opening move, the four things to know before writing, what /shipped/ has to say, and the house pattern.
Read it →Licence and redaction rules
CC BY 4.0 for the site, Apache-2.0 for the code it quotes, the redaction list that is not advisory, what was verified clean, and the accuracy rule: code wins. Published redacted under its own rule.
Read it →All 12, with their raw files
| Document | Raw file | Words | Published |
|---|---|---|---|
| The brief | 00__brief.md | 1,702 | verbatim |
| What it actually is | 01__what-it-is.md | 1,542 | verbatim |
| The rename | 02__the-rename.md | 1,298 | verbatim |
| The maturity audit | 03__maturity-audit.md | 1,381 | verbatim |
| The spec system | 04__the-spec-system.md | 1,364 | verbatim |
| The serverless argument | 05__the-serverless-argument.md | 1,473 | verbatim |
| The site architecture | 06__site-architecture.md | 875 | verbatim |
| Boundaries, redaction and the disclosure | 07__boundaries-and-security.md | 1,179 | redacted |
| Gaps and open questions | 08__gaps-and-open-questions.md | 1,438 | verbatim |
| The pack README | 09__pack-readme.md | 1,109 | verbatim |
| Licence and redaction rules | 10__licence-and-redaction.md | 796 | redacted |
| The source manifest | 11__source-manifest.csv | 1,087 | verbatim |
Two are redacted, and here is why
The platform this site documents is live infrastructure. Two of the documents are the redaction list itself, so between them they named every live address the site was told to strip: an AWS account id, ten internal hostnames, five named stack FQDNs, and sixteen real EC2 instance ids with three AMI ids. Publishing them verbatim would publish exactly what they exist to prevent.
They are published under their own rule — shapes, not addresses. <stack-name>.sg-compute.<zone> is documentation; a live FQDN is a target. Each address was replaced by the shape it is an instance of, nothing else was changed, and the site's release gate encodes the same list so no future page can reintroduce one.
One thing is not redacted, deliberately: the zone sg-compute.sgraph.ai. This site's own label collides with it, and the stated decision is to claim the distinction rather than hide it.
Licence
All 12 documents, and every page of this site, are released under CC BY 4.0. Attribution: Dinis Cruz, via the SG/Send Librarian, with AI co-authorship (Claude, Anthropic). Where the site quotes the platform's own source code, it is quoting Apache-2.0 code — that notice is retained and the snippets do not carry this site's licence.