Overview
GRID-GUIDE-001 is the platform's founding written record. Charles authored it from the design conversations, handoff packages, and decision records produced through October 4, 2026. It runs top-down: the company and doctrine first, then infrastructure, then every Surface area, then extensions, products, and sister businesses.
The guide was written from the design record, not from the running system. That distinction is intentional. The Grid has been building from these designs and knows what actually shipped. The role of the assimilation process (Rev B) is to reconcile the two: verify every capability row, overwrite anything that changed, fill the gaps, and produce the authoritative reference.
Precedence rule: The running system wins over this guide for facts about what exists and how it behaves. A ratified decision in the handoff registry wins over this guide for questions of intent. This guide wins over unratified drafts only where it records a later decision by Charles.
Chapter structure
Every chapter follows the same skeleton so the Grid can parse and update it mechanically. Section 9 is the verification block - the Grid fills in what is actually true today with evidence.
- 1. What it is
- 2. Why it exists (the business reason)
- 3. What makes it up (components and sub-parts)
- 4. How team members use it
- 5. How the agentic infrastructure shows up in it
- 6. Technical underpinnings
- 7. Governing packages and records
- 8. Open decisions
- 9. Live in the UI vs. not live (the verification block - Grid completes this)
Chapters
Status ledger summary
The full ledger is in docs/guide/GRID-GUIDE-001/03-STATUS-LEDGER.md (210 rows). Rev A.3 last-known status is shown here. The Verified Status column is blank until the GUIDE.1 verification pass runs against the actual system.
The UNKNOWN count is high by design. These are capabilities Charles named in conversation where the design record does not say what shipped. GUIDE.1 closes that gap by inspecting the running system.
Open decisions
20 questions for Charles (only he can answer) and 30+ gating ratification items across packages. Full list in docs/guide/GRID-GUIDE-001/06-OPEN-DECISIONS.md. Key items:
| ID | Question | Chapter |
|---|---|---|
| Q-01 | Gray Trace: which entity is its parent, what does it do, and how does it relate to the platform? | 34 |
| Q-02 | Name the seven layers of ArcBrain. | 8 |
| Q-03 | Swift's contractual role in Brain licensing: affiliate, reseller, or both? | 1, 8 |
| Q-04 | Is Atlas a customer-facing brand, and what is its final name? | 1 |
| Q-05 | Final name and boundary for Audience vs. Clients. | 18 |
| Q-06 | Native Surface mobile app: now, later, or never? | 10 |
| Q-10 | Should guests ever have Chat channels in Surface? | 13 |
| Q-14 | ArcPet vs. Roar: one pet vertical or two? | 31 |
| Q-17 | Code area: CI server budget and merge queue choice. | 22 |
| Q-18 | Self-hosted workspace (mail, docs, meetings): pursue as a package or park? | 6 |
Assimilation plan (GUIDE phases)
The Assimilation Directive (01-ASSIMILATION-DIRECTIVE.md) defines the full procedure. Roadmap phases below follow it.
docs/guide/GRID-GUIDE-001/. Register GRID-GUIDE-001 Rev A.3 in the seeding registry with status draft and provenance authored-from-design-record. Add this page to the internal hub. (Complete with this PR.)draft pending Charles's ratification.File index
All files live in docs/guide/GRID-GUIDE-001/ in the repo.
00-README.md- Orientation, status vocabulary, standing conventions01-ASSIMILATION-DIRECTIVE.md- Full procedure for Rev B02-REVISION-PROTOCOL.md- How to produce and version later revisions03-STATUS-LEDGER.md- 210+ capability rows with last-known and verified status04-CHAPTER-MANIFEST.yaml- Machine-readable chapter index with source packages05-GLOSSARY.md- Every proper noun and package ID06-OPEN-DECISIONS.md- Consolidated ratification and decision queue07-build-docx.js- Script to regenerate the Word edition from COMPLETE.mdchapters/ch00-ch40.md- The 40 chapter files (canonical source)diagrams/- SVG sources and PNG renders (stack, ownership, surface-areas, lifecycle, memory)GRID-GUIDE-001-RevA3-COMPLETE.md- All chapters concatenated for single-file ingestionGRID-GUIDE-001-RevA3.docx- Human-readable Word editionCHANGELOG-RevA1.md / RevA2.md / RevA3.md- What changed each revision