Docs
03Structured writing
The docs surface collects public design and implementation records. It stays readable, sourced, and bounded.
This is the first public docs surface. It links to repo artifacts but does not replace the full content model.
Contract
03.1Design contract
The repo-level contract translates Radium into rules future implementation work can follow.
The design contract defines how pages consume the read-only Radium source, which components to use, how proof posture is shown, and how public visibility is enforced.
Inspect the integration recordReports
03.2Implementation reports
Every Codex run creates or updates a report under docs.
-
Content model report
Implementation report for the typed public content model and register data layer.
Read docs surface entry -
Design contract
Repo-level design contract for Radium component use, public boundaries, proof posture, and voice.
Read docs surface entry -
Foundation report
Implementation report for the Astro, React, and Radium foundation.
Read docs surface entry
Boundary
03.3What is not built yet
The docs route is a surface, not a final documentation system.
Record hardening, search indexing, and full quality gates are still future prompts. This page keeps that absence visible rather than implying finished documentation.

