System view
Corpus map
This page maps the public corpus by role rather than chronology.
Corpus structure
Layer map
| Layer | Object | Role | Primary page | Primary repository / anchor |
|---|---|---|---|---|
| Architecture | Advanced Global Intelligence | ecosystem frame | /advanced-global-intelligence/ | GitHub AGI |
| Formula | c = a + b |
canonical formula | /c-a-plus-b/ | site page |
| State / conceptual model | Qubit-State c (c[q]) |
controlled non-collapse under uncertainty for c |
/qubit-state-c/ | MD / PDF / DOI |
| Boundary | L4 |
feasibility boundary | /l4/ | ester-reality-bound |
| Principle / L4-bound experience | Kotov Principle of L4-Bound Experience | scarcity inversion thesis for L4-bound temporal continuity | /kotov-principle-l4-bound-experience/ | GitHub release |
| Grounding | Actor Grounding Layer | source-state qualification / runtime reliance | /actor-grounding-layer/ | AGL document set |
| Continuity / sovereignty | SER |
entity continuity / governance | /ser/ | SER repo |
| Development timeline | Beyond Agents | dated public lineage; navigation / provenance surface, not evidence authority | /beyond-agents/ | original question / JSON timeline |
| Implementation | ester-clean-code |
executable operational layer | /publications/ | ester-clean-code |
| Narrative | Qubit of Hope — Volume I | public narrative entry | /qubit-of-hope/ | Volume I repo |
| Narrative continuation | Qubit of Hope — Volume II | second-volume continuation of the book layer | /qubit-of-hope-volume-ii/ | Volume II repo |
| Editorial / future-facing | Vision | living authorial vision; not evidence/status authority | /vision/ | site page |
| Evidence / review | Releases / Evidence | reviewable contour | /releases/ / /evidence/ | site pages |
| Identity / entry | About / Publications | public author surface | /about/ / /publications/ | site pages |
Negative frame
What this map is not
- Not a product stack.
- Not a commercialization funnel.
- Not a replacement for reading the actual materials.
Links onward
Next surfaces
Use Distinctions as the semantic hygiene layer when terms start flattening into each other.
Use Beyond Agents when the question is not the current stack but how the public argument developed over time.