Capacity-Safe Design Standard

Every system built for humans was designed at full capacity. None of them work when the human operating them doesn't.

Preamble

This standard exists because of a design failure so universal it became invisible. For generations, every system humans interact with — schools, workplaces, productivity tools, medical environments, digital products, parenting frameworks, government services, AI interfaces — was architected around one assumption: the human using it is available. Regulated. Resourced. At capacity.

That assumption has never been true. The Capacity-Safe Design 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.

Capacity cannot be demanded. It can only be restored.

Part I · Foundations

1.1 The Problem This Standard Solves

Most humans interact with systems every day that were designed for a version of themselves that rarely exists — rested, regulated, resourced, untraumatized, and operating at full cognitive and emotional capacity.

When real humans encounter these systems, one of three things happens: they force themselves through at great personal cost; they fail at tasks the system makes unnecessarily difficult; or they abandon the system and call it their own fault.

This standard names that assumption as a design error — not a personal one — and provides the framework to correct it.

1.2 What Capacity Means

Capacity refers to the available bandwidth of the human nervous system at any given moment — its ability to perceive, process, decide, respond, connect, and act. Capacity is not a character trait. It is a biological reality that changes throughout every day and in response to every experience a human has.

Part II · The Capacity Map

The Capacity Map describes five states of human nervous system capacity. These are not diagnostic categories. They are operational positions. A person may move between states multiple times in a single day. No state is a failure.

Every Capacity-Safe system must identify which state a user may be in and respond differently to each. A system that treats a Flooded person the same as a Grounded person has failed at the infrastructure layer.

Part III · The Infrastructure Stack

You cannot repair the roof while the foundation is underwater.

Four layers must be addressed in order: Somatic (body, safety, regulation) → Cognitive (clarity, load, memory) → Relational (connection, trust, co-regulation) → Operational (tasks, goals, execution). Most systems address only one layer incorrectly.

Part IV · The Recovery Spine

Five-phase delivery protocol for any Capacity-Safe interaction:

1. Safety — establish perceived safety before any demand
2. Offload — remove unnecessary cognitive and emotional burden
3. Simplification — reduce choices, steps, and language complexity
4. Gentle Movement — one small forward action, never forced pace
5. Recovery Protection — prevent shame, comparison, and catch-up demands

Part V · The Twelve Capacity-Safe Design Principles

All twelve must be met for Foundation certification. Principles include: State Before Task; Capacity Is Assumed Variable; Shame Is a Design Bug; Exit Is Always Available; Recovery Is the Goal; and others defined in the full document.

Read complete principle definitions in the full standard →

Part IX · Capacity-Safe Certification

9.1 Certification Levels

• Foundation — twelve core principles, Recovery Spine, basic Capacity Map response
• Full Standard — complete Infrastructure Stack, full state-based UI adaptation
• Advanced — measurable capacity return outcomes, consent-based state detection
• Institutional — organization-wide implementation across all human-facing systems

9.2 Certification Requirements

Annual review. Self-assessment with evidence, third-party NSIF Practitioner review, user-reported capacity safety data, zero prohibited patterns in UX audit, public commitment to the Capacity Return Principle.

Certification paths

Closing · Why This Standard Exists

I am regulated, therefore I can.

Every person who has ever abandoned a planner, quit an app, or called themselves broken for not being able to keep up — was not failing. They were in a capacity state that the system was not designed for. The failure was the design.

Every system built for humans should work for humans as they actually are — not as the system wishes they were.