Layer 7 — Data, Evidence, and Publishing
Runtime stores, metrics generation, drift guard, proof cards, reviewer mirror, NotebookLM Drive sync, OneDrive package, wiki build, and hosted deploy.
The base of the seven-layer code architecture: the pipeline that converts live engineering state into auditable, reviewer-accessible evidence. Metrics are generated from real test and coverage runs (never hand-authored) and drift guards fail CI when documentation claims diverge from measured code state — the discipline behind Production Proof and Canonical Metrics and Wording. Publishing targets include the per-component proof cards, the public reviewer mirror snapshot, the NotebookLM Drive-synced source pack, the offline executive package, and this wiki’s own build-and-deploy pipeline.
Questions this layer answers
- How does documentation evidence get published?
- Which artifacts feed NotebookLM and the wiki?
Ask them live on the Code Architecture Dashboard — click the bottom layer of the infographic.
Documentation & evidence
- Documentation index — the full docs tree this layer publishes from
- Proof card: Strategic positioning
Related layers
- Layer 1 — User & Operator Surfaces — serves the wiki and evidence surfaces this layer builds
- Layer 6 — Connector & Integration Layer — whose status claims this layer audits and publishes
Last refreshed: 2026-07-06