Every system built for humans was designed at full capacity. None of them work when the human operating them doesn't. The failure was never human. It was always architectural.
A Promise Before the Standard
If you have ever abandoned a planner, quit an app, failed to show up, disappeared from a system, or called yourself broken for not being able to keep up — this document is for you. You were not failing. You were in a capacity state that the system was not designed for. The failure was the design.
I am regulated, therefore I can.
A Warning Before the Standard Begins
This framework can be misused. Gentle colors and warm language do not make a distress-extraction system Capacity-Safe. The mark certifies structure, not aesthetics. It certifies demand architecture, not tone.
If distress drives your conversions, fear drives retention, or shame drives re-engagement — the Capacity-Safe mark is not for you.
Preamble
This standard exists because of a design failure so universal it became invisible. For generations, every system humans interact with was architected around one assumption: the human using it is available, regulated, resourced, and at capacity.
That assumption has never been true. The Capacity-Safe Systems Standard does not ask humans to adapt to broken systems. It asks systems to be designed around the actual range of human capacity — including its lowest points and its highest ones.
This is not accommodation. It is not therapy. It is not wellness culture. It is infrastructure.
Capacity cannot be demanded. It can only be restored.
Part I · Foundations
Capacity is the available bandwidth of the human nervous system — not a character trait, not willpower. Version 3.0 introduces the Capacity Alignment Principle: the system works for the human it is serving right now. Valid goals include return, stabilization, expansion, and sovereignty — not only “return to baseline.”
The standard applies to products, AI, workplaces, schools, hospitals, communities, and policy. It is an operational systems standard — not a clinical instrument.
Part II · The Capacity Map v3.0
Eight operational states (plus the Disconnected Function overlay). Fluid, bidirectional. No state is a failure.
| State | System response priority |
|---|---|
| Flowing | Get out of the way. Protect flow from unnecessary interruption. |
| Grounded | Full experience available. Respect preferences. No forced modification. |
| Recovering | Protect the return. Gentle pacing. Do not rush toward full capacity. |
| Stretched | Streamline. Fewer steps. Clear language. Low friction. |
| Flooded | One thing. No pressure. Shame-free. Clear path to stop. |
| Frozen | Warmth. Breath. Presence. One physical prompt. No agenda. |
| Fractured | Consistency. Predictability. Zero shame. Human support pathway. |
| Zero Demand | Hold space only. No tasks. No goals. System holds indefinitely. |
Disconnected Function is an overlay — high performance without integration. The system must not exploit it.
Part III · The Infrastructure Stack
Four layers in order: Somatic → Cognitive → Relational → Operational. Most systems address only one layer incorrectly.
Part IV · The Recovery Spine
Session-level protocol: Safety → Offload → Simplification → Gentle Movement → Recovery Protection. The Spine may stop at any phase. Safety alone is enough.
Part V · The Recovery Arc
Longitudinal capacity path over days, weeks, and years — distinct from the session-level Recovery Spine.
Part VI · The Eighteen Capacity-Safe Principles
Version 3.0 expands from twelve to eighteen principles. Principle 1: Capacity Alignment Is the Goal. All eighteen must be met for Foundation certification under v3.0. Read complete definitions in the full PDF.
Part XIV · Capacity-Safe Certification
- Foundation — eighteen principles, Recovery Spine, basic Capacity Map response across all eight states
- Full Standard — complete Infrastructure Stack, Recovery Arc, Capacity Privacy, AI guardrails if applicable
- Advanced — measurable capacity alignment outcomes, consent-based detection, verified impact data
- Institutional — organization-wide implementation
Certification requires evidence, practitioner review, user-reported alignment data, and public commitment to the Capacity Alignment Principle — not the old “capacity return only” framing.
Certification paths · AI Agents practitioner credential
Closing · Why This Standard Exists
I am regulated, therefore I can.
Every person who abandoned a planner, quit an app, or called themselves broken was not failing. They were in a capacity state the system was not designed for. The failure was the design.
Human capacity is not a bug in the system. It is the system. Everything built for humans must be built around it.