Recommended order
This page defines the recommended public reading order.
Orientation
Before or after the canonical term stack, use About and Corpus map to orient identity and corpus structure.
New reader? Use /start-here/ as the soft entry.
Sequence
Step 1
What this page does: sets the architectural frame and naming discipline for the public corpus.
Why it comes here: it defines the overall map before individual terms narrow.
Who should read it: anyone entering the corpus from outside.
Open pageStep 2
What this page does: fixes the canonical formula and the roles of a, b, and c.
Why it comes here: the formula should be read after the frame, not before it.
Who should read it: readers trying to understand the entity layer itself.
Open pageStep 3
What this page does: defines the feasibility boundary under power, heat, latency, maintenance, scarcity, and irreversibility.
Why it comes here: it prevents the formula from drifting into cost-free metaphor.
Who should read it: readers checking whether claims survive real constraints.
Open pageStep 4
What this page does: inserts source-state qualification and runtime-reliance discipline before ordinary progression or review.
Why it comes here: it belongs after L4 feasibility and before continuity/governance logic is allowed to move forward.
Who should read it: readers checking grounding, initiation, degradation, and fail-closed conditions.
Open pageStep 5
What this page does: specifies continuity, sovereignty, arbitration, and bounded governance for the long-lived entity.
Why it comes here: governance only makes sense after the frame, formula, boundary, and grounding conditions are clear.
Who should read it: readers focused on continuity and sovereignty structure.
Open pageStep 6
What this page does: offers the original narrative/public entry into the world of c.
Why it comes here: it complements the architecture layer rather than replacing it.
Who should read it: readers who want the public narrative layer after the canonical stack is fixed.
Open book hubStep 7
What this page does: continues the narrative layer as a second-volume companion node.
Why it comes here: it extends the book layer after the original narrative entry has already been situated.
Who should read it: readers continuing the narrative layer after Volume I.
Open pageStep 8
What this page does: continues the trilogy as a third-volume companion node.
Why it comes here: it belongs after Volume II so the narrative sequence remains explicit.
Who should read it: readers following the complete public trilogy layer.
Open pageAdvanced branch
optional state model
c (c[q])Use this after c = a + b and L4 when the reader needs the technical note on controlled non-collapse under uncertainty.
This branch does not replace the main sequence; it clarifies one derived state of c.
Optional extension
Child-facing protocol path
CCDP v0.1 — Child-c Development Protocol is a draft research protocol pack for child-facing persistent AI entities under the c = a + b / SER / L4 corpus, with v0.1.1 hygiene guidance.
It is not legal advice, clinical guidance, product certification, or implementation approval.
The public website links the public package surface and selected review materials; sensitive-controlled technical artifacts remain in the GitHub package for specialist review and are not presented as public UX guidance.
After glossary
After glossary, use /distinctions/ to avoid common flattening of terms.
Next step
After canonical terms, continue with the public works surface, the confirmed release timeline, and the compact evidence contour.
Final note
The architecture layer and the narrative layer are complementary, not interchangeable.
If the corpus is being read too loosely, check /misreadings/.