0020 — Human Capability System and The Ascent

• Date: 2026-09-20
• State: accepted for public explanatory release
• Authority: Codex 1 Arts. II–VII; Codex 0 §§04–07, 11, 20–21; Codices 3, 4, 5, 6, 10, 11; STD-A, STD-D, STD-S, STD-X, STD-Q
• System / owner: SYS-02 Learning / DIV-01 Academy; data covenant SYS-01 Identity / DIV-05 Technology

Nine-field record

1. 1Decision: The Human Capability System is the public expression of CapabilityOS and Anabasis's core operating method, not a thirteenth institutional system. The Ascent is its individual experience. Institutional Programmes apply the same method to populations within an agreed mandate. Public pages may explain the intended loop — Assess, Prioritize, Learn, Act, Prove, Reflect, Adapt, Internalize, Self-direct, Autonomy — but must label reserved capabilities as planned.
2. 2Reasoning: The person is the primary unit. Education, technology, research, missions, and institutional delivery are instruments serving capability and eventual autonomy. One public hierarchy corrects the impression that the Academy, Accelerator, or any single division is the institution's core.
3. 3Alternatives considered: A thirteenth SYS-* was rejected because Codex 11 closes the system set at twelve. Treating The Ascent as a new course product was rejected because it would subordinate the person to Academy architecture. Building a diagnostic before the governed data and engine layers exist was rejected as premature and misleading.
4. 4Evidence reviewed: Codex 1; Codex 0 Chapters 04–07, 09, 11, 20, 21; the Registry states of ENG-01/03–07, ENT-06/07/17, DASH-01, TOOL-04; current homepage, Academy, Apply, Institutional, About, Privacy, Scholar, and navigation surfaces; Decisions 0011, 0014, 0015, 0018, and 0019.
5. 5Expected outcomes: A visitor can name the core method, distinguish The Ascent from the Academy and Accelerator, understand the path toward autonomy, and understand that planned systems are not yet live. No private signal is exposed or newly collected.
6. 6Owner: DIV-01 owns the individual learning method; DIV-05 owns CapabilityOS and the data boundary; the Executive Office owns public institutional framing.
7. 7Date: 2026-09-20.
8. 8Review schedule: first review 2026-12-20, then annually; review owner Executive Office with Stewardship Office for member trust.
9. 9Result: public explanatory integration approved. Operational results remain unwritten until the review date. Personalized Diagnostic, adaptive prioritization, AI guidance, Life Event adaptation, automated Weekly Review, automated Personal Operating System, Independence Check, and new member-data records remain reserved.

Relationship to prior decisions

• Extends Decision 0011 by placing the Five Pillars and Seven Schools beneath the Academy as instructional architecture within the wider method.
• Extends Decision 0014 by adding an individual system entry without changing the five public commercial pathways or ecosystem definitions.
• Preserves Decision 0015's single-source and non-implied-governance rules; no ecosystem relationship is restated here.
• Narrowly supersedes Decision 0018 only to add a compact Human Capability System / Ascent introduction to the homepage. The homepage remains a gateway and does not regain the removed explanatory depth.
• Extends Decision 0019's responsive contract to SURF-27 and SURF-28 without a separate mobile implementation.

Privacy and truth boundary

The public release creates no capability-profile, assessment, goal, mission, reflection, life-event, or personal-operating-system record. Personal conversations, private drafts, notes, reflections, and meeting content never enter the capability graph or institutional memory. Enterprise clients, employers, sponsors, partners, and investors receive no automatic access to an individual's record. Any future consequential recommendation remains advisory, explainable, auditable, and accepted or rejected by a person.

Institutional Critic

1. 1100× scale: one canonical Ascent explanation and one member-data covenant prevent page-local forks; operational scale awaits governed engines and entities.
2. 2Unverified assumptions: demand for the method, diagnostic validity, intervention efficacy, cadence, and independence criteria are unverified; the site makes no outcome claim.
3. 3Simpler solution: editorial explanation plus the existing protected intake is simpler and more truthful than a simulated product.
4. 4Duplication: The Ascent reuses CapabilityOS, SYS-01, SYS-02, ENG-02, and reserved ENG-03–07; it creates no engine or system duplicate.
5. 5Enterprise view: Institutional Programmes explain agreed populations, measures, aggregates, and strict private-record separation.
6. 6First-time view: one route introduces the method in sequence, defines no more than three terms at a time, and ends with one action.
7. 7Legal, operational, security: no new data collection or permissions; conservative status language; the data covenant does not claim unbuilt self-service controls.
8. 8Debt and repayment: the operational Diagnostic, adaptive engines, personal dashboard, and self-service data controls remain reserved. Their Registry entries, ethics review, validation evidence, and security model repay the gap before implementation.
9. 9Constitutional consistency: the release strengthens people, knowledge, and trust; rejects engagement optimization; keeps AI advisory and people decisive; and aims at autonomy.

Codex 8 evaluation

• Revenue potential: indirect; clearer individual and institutional entry may support existing education and programme revenue.
• Implementation cost: moderate editorial, governance, discovery, and verification work.
• Maintenance cost: low while one canonical route and covenant remain authoritative.
• Operational complexity: unchanged; no new workflow, data entity, permission, or automation.
• Customer value: high clarity about what Anabasis develops and how a person begins.
• Enterprise value: clearer population-level method and reporting boundary.
• Long-term strategic value: high; preserves the person-centred hierarchy beneath future CapabilityOS development.

The change increases human, intellectual, technological, and reputational capital. It does not alter the Codex 8 allocation sequence.

Rollback

Remove SURF-27 and SURF-28 from public navigation and revert only the Decision 0020 framing if review finds public confusion or an unsupported claim. Preserve the privacy constraints, existing routes, and Decisions 0011, 0014, 0015, 0018, and 0019.