Reference

This section holds standing reference material that doesn't fit elsewhere in the docs taxonomy:

• Time Machine — canonical session opener (lives at the top of the docs source tree, not under Reference)
• Trust Industry Linkages — government bodies, regulatory frameworks, data sources we monitor or align to
• Design Decision Records (DDRs) — architectural decisions worth preserving
• Policy & Legal — accessibility, AI transparency, cookie, copyright, privacy

Briefs

Implementation briefs are archived by default in briefs/archive/. They are session-scoped task documents — once the work has shipped, the canonical state lives in the appropriate reference doc (architecture, infrastructure, operations, workers, workspace), not in the brief that proposed the work.

Going forwards: any new brief is filed directly into briefs/archive/ and is never added to the mkdocs nav. The brief is a working artefact for the session that produces it; it's preserved as historical context (via git log and the archive folder), not as living reference. If a brief introduces a concept or pattern worth keeping, that concept goes into the appropriate reference doc.

Why: a sprawling brief tree was the failure mode that prompted this consolidation (session 58 morning). Search returned shipped-and-superseded briefs as if they were current reference, which made it harder to find the actual current state.

To search archived briefs, browse the briefs/archive/ folder directly on disk or run git log docs/docs/briefs/archive/.