Document baseline and source ownership
Two commits, two roles
The supplied PDF is a migration source snapshot generated from nereusstream/nereus main@894fc4e4. The current implementation checkout is main@c820391d, verified on 2026-08-07. The website records both because a source snapshot is not automatically current merely because it is detailed.
When a page contains a claim that can drift, it must use the current implementation commit or explicitly label the claim as historical PDF baseline. A test-only source advance can leave architecture text unchanged, but the distinction remains visible in the status page and coverage map.
Ownership model
| Content | Maintained in |
|---|---|
| Public architecture, concepts, flows, and operations | This website repository (Markdown/MDX) |
| Class-level contracts and implementation plans | nereus source repository |
| Architecture PDF | A release snapshot generated from website Markdown/MDX after migration completes |
| Current status and verification facts | src/data/projectStatus.ts and the project-status page |
| Source anchors | Exact commit links in each page |
The supplied PDF remains an input snapshot during migration. It is not treated as a second hand-maintained website source.
Machine-readable page contract
Every Nereus and Nereus Delay page records its product, source repository, full source commit, verification date, status, and authority in frontmatter. The DocBaseline banner renders the product, short commit, verification date, and authority while linking the short commit to the full source SHA. yarn docs:check verifies those fields against migration/product-source-locks.yml, so a page cannot silently drift to a different product baseline.
Coverage contract
The migration map records every PDF chapter, appendix, figure, and table. A section can be migrated, in-progress, or pending; a pending item must not be silently omitted. Completion requires the map to have no unmapped sections or figures and the generated site to pass broken-link checks.
Non-goals for this stage
- No multi-version Docusaurus tree before
v0.1.0is released. - No locale dropdown before the Chinese route is complete enough to be useful.
- No temporary search plugin before the documentation corpus reaches the planned size.
- No new Quickstart promise derived only from an architecture PDF.