Section 6 of 440

How to Use This Book

TWO ROUTES: CORE/PROGRAM AND CAPABILITY

Titan has two connected routes. The Core/Program route uses a non-scoring current-state profile and human-selected route. The Capability route records bounded task performance. Their records and claims remain separate.

Table 2 — TWO ROUTES: CORE/PROGRAM AND CAPABILITY

Route

Use it for

What the result means

Core / Program route

Broad non-scoring current-state profile and user-selected Program route.

A bounded planning record; not Capability L1–L5, diagnosis, population rank or causal proof. Produces no composite, rank, bottleneck or automatic recommendation.

Capability Standard route

One declared task with direct, burden, retention and transfer tests.

Evidence only for the declared task and conditions; never a Core score or judgement of identity, worth or potential. Selection remains a human decision under the declared evidence, safety, support and authority boundaries.

Choose one route before starting. A Program may contain useful practice, but completing a Program does not award a capability level. A capability assessment may identify useful support for a Program, but it does not alter the frozen twenty-four-domain Core profile or an operational Capability record.

Begin with the architecture (Part 1). It introduces HCE’s central idea: capability is neither a fixed essence nor an unlimited act of self-construction. It is a bounded relationship among a person or human-in-system configuration, a task, an outcome, the surrounding conditions and constraints, the supports used, the evidence collected and the time over which the claim remains current. Part 1 then presents Titan’s three planning layers - Hardware, Operating System and Applications - inside the Context Envelope.

Declare one real outcome, review the relevant Core domains and compare available routes. Titan may show relevant evidence and constraints; the person or properly authorised decision-maker chooses the route.

Work the system in order, but not all at once. Part 2 catalogues the narrative capability systems; Part 2B defines the separately assessed Capability Standard. Part 3 contains twelve integrated Programs A-L: implementation schedules, not registry modules. Part 4 covers implementation in real life and Part 5 covers resources and safety. Appendix AA holds unscored candidates and research-only topics; Appendix AB is the Cockpit and Engine operator guide. Build one capability to reliable use before stacking the next—serial progress beats scattered effort.

Read the signals on every protocol:

  • Evidence grades—Strong, Moderate, Emerging, or Speculative—tell you how much confidence each recommendation deserves. Not every claim rests on equal ground; the full evidence base is in §5.2.
  • Safety Gates—the boxed panels route higher-risk health, temperature, breath, exercise, substance and combat questions to stop rules or qualified care. A gate is not clearance and does not convert an excluded progression into a general-use protocol.
  • Profile fields preserve current observations, supports, uncertainty and reason-coded non-assessment.

Use the appendices selectively as supporting material. Their menus, schedules, worksheets and examples are adaptable aids rather than universal requirements; the governing safety and claim boundaries still apply.

One principle governs all of it: observe before you conclude. The lower-risk protocols offer educational starting points; apply them conservatively, measure honestly, and stay inside the stated safety and professional boundaries.

THREE WAYS TO RUN THIS: LITE, STANDARD, ADVANCED

This book is large, but you do not have to run all of it at once. Choose the depth that matches your life right now—you can always move up a tier later.

Lite. Use the lowest-burden foundations that fit your situation: protect adequate sleep opportunity, include feasible regular movement, meet ordinary nutrition and hydration needs, record a simple daily observation only if it is useful, and review once a week. No laboratory testing, deliberate temperature exposure or breath-hold work is required. Adapt the route to health, disability, medication, caring responsibilities and local guidance. (R7D-S01; R7D-S02; R7D-S03)

Standard. Run one bounded Program cycle: declare the outcome, preserve a baseline, compare routes, select one deliberately, track result and burden, then review and retest at the appropriate interval. The sixteen operational capability modules remain separate and use task-specific declarations and evidence.

Advanced. Use independently assessed capability work, formal low-risk N-of-1 methods and qualified professional routes where the task requires them. Bloodwork, medication, clinical treatment, temperature exposure and other material-risk decisions stay with appropriate care; the Safety Screen cannot clear them. Depth means stronger evidence and verification, not greater physiological risk.

You are not behind if you stay on Lite for a year. Consistency on a small system beats ambition on a large one. The worst version of this book is the one abandoned in week three because it asked for more than your life could give.

WHAT TO EXPECT IN YOUR FIRST 90 DAYS

Honesty is part of the method, so here is what ninety days realistically buys—and what it does not.

What may move first. A consistent routine can make sleep opportunity, daily movement and other observable behaviours easier to track within the first weeks. Strength, work capacity, mood and perceived energy vary with the person, context and task; measure your own trend without treating a suggested timeline as a promise.

What changes slowly. Body composition is a matter of seasons, not weeks. Deep skill—physical, cognitive, or financial—compounds over years. Identity-level change, becoming the kind of person for whom all this is simply normal, is the slowest and most valuable shift of all. If a protocol promises any of these fast, distrust it.

What should never be forced. Do not cut sleep to make room for the protocol; sleep is the protocol. Do not push through sharp pain, dizziness, or a body asking you to stop—those are signals, not weakness. Do not chase restriction, extremity, or numbers for their own sake. And never override the safety screen because you feel impatient. The system is built to compound quietly over years; forcing it is the one reliable way to break it.

YOUR DAY 0 CHECKLIST

Reading this book changes nothing. Acting on it changes everything—and the gap between the two is where most people stall. So before you go any further, complete Day 0. It takes about twenty minutes and turns you from a reader into a participant. This is your first protocol.

  1. Open the Titan Cockpit or companion Engine. It holds your current-state profile, dated observations, declarations, direct results, separate unaided and supported records, and the retest/currency queue.
  2. Complete the Safety Screen first. Work through the screen at the front of this book, which also lives in the Cockpit. If anything applies to you, use the relevant qualified route before starting those protocols. This step is not optional.
  3. Complete the Minimum Viable Profile. State one real outcome and review only the Core domains that may bear on it. Record legitimate non-assessment with a reason code.
  4. Compare plausible constraints and available routes. A lower domain entry does not prove causation, and Titan does not rank the routes.
  5. Choose deliberately. Open Part 2 only after the outcome, safety boundary, evidence limits, burden, support and fallback are visible. Holding or declining every route is valid.

Use Day 0 only if it is the most useful entry point. You may read, pause, seek support or choose a different route before beginning. The system reduces some planning burden; it does not replace judgement, access, support or motivation.