Source-of-truth map

AIOS is a context monorepo, not one build monorepo. Each product has its own source, tests, release cadence, and documentation. Public website prose is a projection of those sources, not the authority over them.

Product ownership

Question	Authoritative source
Individual workspace behavior	aios-workspace source, especially scaffold/, scripts/, and validation/
Workspace architecture	aios-workspace/docs/architecture.md
Workspace feature inventory	aios-workspace/docs/feature-set.md, checked against executable source
CLI command surface	aios-workspace/scripts/cli/registry.mjs and scripts/cli/usage.mjs
Team Brain data and flows	aios-team-brain/docs/ARCHITECTURE.md plus route and library source
Workspace ↔ Brain wire contract	aios-workspace/docs/brain-api.md
Brain implementation version	aios-team-brain/lib/api/version.ts
Workspace GUI (cockpit) + desktop shell	aios-workspace/gui + src-tauri (authoritative until their deferred deletion); the cut standalone repo is aiosbrain/aios-workspace-gui, seam contract in aios-workspace/docs/gui-toolkit-contract.md
Shared hub modules	@aiosbrain/foundation on npm, source aios-workspace/packages/foundation/; the old scripts/ paths are re-export shims
Devtools command set	@aiosbrain/aios-devtools@0.2.0, sourced from aiosbrain/aios-devtools; five Workspace commands delegate through aios-workspace/scripts/cli/devtools-commands.mjs
Public documentation	aios-website/src/content/docs/
Shared design system	aios-design/DESIGN.md and published @aios-alpha/* packages
Agentic Engineering Maturity	root agentic-engineering-maturity/

Do not infer absence from a missing context file

Before concluding a feature does not exist, search the defining repository’s code and tests. A missing, renamed, or stale summary document is evidence about the document—not proof that implementation is missing. aios-workspace/docs/feature-set.md exists, but executable source still wins when the two disagree.

Verification order for agents

1. Identify which product owns the behavior.
2. Search the owning repository’s code graph or source.
3. Trace callers, routes, and tests.
4. Read the product’s authoritative document.
5. Compare the website projection.
6. Report discrepancies in both directions: documented-but-missing and shipped-but-undocumented.

Automated checks and their limits

Check	What it proves	What it does not prove
Workspace npm run check:docs	Operator-loop inventories match source/spec files	All workspace prose is current
Team Brain npm run check:docs	Routes, tables, and ingestion sources match ARCHITECTURE.md inventories	The pinned member API document matches every handler
Website npm run check:docs	Generated workspace facts and product-boundary rules match public docs	Unmarked prose is semantically complete
Workspace/Brain contract conformance tests	Shared fixture, tiers, SSE, payloads, provisioning tools, and version anchors agree	Every documented endpoint has a handler and every handler is documented

That last limitation is why launch reviews must also run the cross-repository Brain API conformance audit.

Compact agent context

Use /llms.txt when you need a copy-pasteable ecosystem briefing. It contains boundaries, source hierarchy, safety invariants, setup flows, and verification commands without duplicating the full guides.