SIGNAL · CLEAR
LAT 37.1°NLON 93.0°WVOL XVII · 2026
DISPATCH 042 — STRUCTURE OVER STACK·FIELD NOTE — AUDITABLE BY DESIGN·DOCTRINE — DEFENSIBLE UNDER SCRUTINY·NEW SPRINT WINDOW OPEN · Q3·DISPATCH 042 — STRUCTURE OVER STACK·FIELD NOTE — AUDITABLE BY DESIGN·DOCTRINE — DEFENSIBLE UNDER SCRUTINY·NEW SPRINT WINDOW OPEN · Q3·
N · 04
90 · S
GAD · Documentation

The Documentation Set

Explanatory and non-normative. Where any of these and the specification differ, the specification governs.

Release status· Documentation release docs-2026.07-r3, candidate. Specification sealed at v1.3 (succession-7). Checksums ship unsigned; the findings register is published and open, and the documentation package’s exact evidence references are still pending before it calls itself the public distribution. Independent formal and cryptographic review has not begun; results are Propositions and Claims until it does.

Text © 2026 Atlas North Institute LLC · CC BY-ND 4.0 · name and marks reserved · implementing the methodology requires no permission.

Reading paths

  • An executive or buyer: the Executive Guide, then the Manifesto.
  • A practitioner: the Manifesto, the Glossary, then the Guide's ladder chapter.
  • An implementer or standards reviewer: the specification is the only normative document; the Glossary maps practice language onto it; the register tracks every open finding.
  • A verifier: the specification's Section 9, then GAD Protocol.

The four documents

Manifesto. The argument. Why trust technology built for human developers failed when the labor changed, and what discipline replaces it. The six principles stated in full.

Executive Guide. For the person who will be asked, when the work is done, what they actually hold. Today the honest answer is testimony: a vendor's assurance, a screenshot, a log curated by the system in question. The Guide explains what a conforming governed run produces instead, and walks the maturity ladder from Recorded to Defensible.

Glossary. The vocabulary of the discipline, defined once, tool-agnostically. A term here names a concept, not a product feature. Where a reference implementation exists, it implements these definitions; it does not own them.

Standardization Track. A provisional working document, dated July 17, 2026, on what a standard would address and where GAD would sit among neighboring work. Venue selections and intellectual-property terms are candidates pending a counsel-supported IP workstream.

Release integrity

RELEASE-MANIFEST.json identifies every governed content artifact in the release with role, status, and SHA-256. SHA256SUMS covers all content artifacts and the manifest and verifies with sha256sum -c SHA256SUMS. The checksum file cannot cover itself; its authentication is the operator's detached signature, expected beside it as SHA256SUMS.sig. This build ships unsigned and says so. Prior releases r1 and r2 are preserved exactly and never overwritten; successors carry their own manifests and explicit deltas.

Downloads