Generated reference
The inventory behind the architecture story
These figures are derived from the pinned schema set and Swift package manifest. The source guide below points from the curated diagrams into the detailed documents that carry implementation and operating nuance.
Current closure
Contract and implementation scale
- 10
- schema packages
- 358
- portable descriptors
- 101
- Swift targets
- 524
- declared target edges
- 14
- curated diagrams
- 11
- architecture invariants
Schema inventory
Descriptors by pinned package
Width represents descriptor count, not importance. Package versions and digests come from the checked schema-set closure.
Swift package inventory
Dependency-heavy composition points
A wider bar means a target deliberately composes more modules. It is a review prompt, not a quality score.
- 48
- regular targets
- 32
- test targets
- 21
- executable targets
Deep source guide
The documents behind the diagrams
Start here
Product vocabulary, system landscape, and the trust model.
- Platform primer
The portable graph contract, stores, authority, media, processing, and native clients in one source document.
README.mdProduct · Engineering - Customer journeys and MCP prompt playbook
Birdwatching and Field Notebook storyboards, actual tool boundaries, local demos and the hosted follow-up.
docs/customer-agent-journeys.mdCustomers · Product builders
Contracts and data
Schema authority, generated projections, local persistence, and synchronization.
- Package architecture
The target dependency rules and composition-root responsibilities that keep Core domain neutral.
docs/package-architecture.mdEngineering · Partners - Cross-platform synchronization
The local outbox, authority checkpoint, conflict, and accepted-history contracts.
docs/cross-platform-sync.mdEngineering · Operations
Core flows
Identity and the signature evidence-to-play product journey.
- Access scopes
How principals, ownership, grants, visibility, and blob authorization remain explicit.
docs/access-scopes.mdEngineering · Operations - Login and identity decisions
The hosted identity, derived-principal, device credential, and deployment-isolation decisions.
docs/login-owner-decisions-2026-09-02.mdProduct · Engineering · Operations
Engines
Durable processing and deterministic game execution.
- Processing graph foundation
How immutable graph revisions, capabilities, runs, artifacts, and provenance compose.
docs/processing-graph-foundation.mdProduct · Engineering - Swift processing runtime
The native compiler, dispatcher, durable queue, and capability boundary.
docs/swift-processing-runtime.mdEngineering - Measured evidence workbench
The separation between machine observations, review state, and accepted semantic truth.
docs/v3-measurement-workbench.mdProduct · Engineering - Game kernel contract
The pure deterministic interpretation boundary and canonical transcript contract.
docs/game-kernel-g0.mdProduct · Engineering - Game authority
Admission, atomic command resolution, append-only events, and replayed projections.
docs/game-authority-wave2.mdEngineering · Operations
Platform boundaries
Contracts, modules, domains, composition roots, and extension rules.
- Domain extension contract
The folder shape, schema allocation, registration, and test seams for additional domains.
domains/README.mdEngineering · Partners - Forking and reuse
How another product or company inherits platform gates without importing first-party domain policy.
docs/forking.mdEngineering · Partners - Design identity and tokens
The normative rules for colour, type, the mark and layering (L0 shared library through L3 fork), and the one token source — design/tokens/ — that generate.mjs projects into the Explorer's CSS, the NeoStoryDesign Swift module and colorsets, and each domain's own web and native overlay.
docs/design/README.mdProduct · Engineering · Partners - Customer delivery, deployment choices and MCP
M1 groundwork, dedicated and shared-infrastructure business cases, evidence levels and the smallest deployment MCP extension.
docs/platform-business-cases.mdBusiness · Partners · Engineering · Operations
Operations
Artifact-pinned promotion, deployment isolation, telemetry, and public-edge proof.
- Deployment and promotion
The environment ladder, immutable image tags, rollback, and public-edge smoke contract.
docs/deployment.mdEngineering · Operations - Operability contract
Structured events, metrics, trace vocabulary, and the distinction between proof and live observation.
docs/operability-g0.mdEngineering · Operations
Interpretation boundary
Generated structure is evidence, not explanation
Counts and dependency edges reveal scale and composition pressure. They do not determine architecture quality on their own. Return to the curated Atlas for the responsibilities, trust boundaries, and decisions those structures support.