| name | sustainable-cadence |
| description | Treat the operator's capacity, pace, and rhythm as first-class design inputs — not afterthoughts to optimize away. Use when planning workload or cadence, deciding whether to push hard or pace deliberately, judging whether carried/slow/deferred work is genuine avoidance vs. a legitimate quality gate or rhythm, designing rituals and routines, sequencing a heavy week, or guarding against burnout-by-velocity. The generative complement to the system's defensive anti-values: it says what conditions let work (and the person doing it) sustain, not just what to never become. |
Sustainable Cadence — capacity as a design input
The system's anti-values are all defensive — what it must never become. This is the generative counterpart: the conditions under which work, and the person doing it, actually sustain. A system that optimizes only throughput and trust will run faster and still grind the operator down. Pace is not a constraint on the work; it is part of the design of the work.
The core principle
The operator's capacity is a design input, not an afterthought. Don't optimize the human off a cliff to ship faster. Paced work through a real quality gate is not avoidance.
This is care-as-infrastructure stated as a mechanism, not an ideology: the question "what conditions let this person and this work sustain?" is a legitimate design question, the same kind as "what conditions let this system scale?" Background on the ethics-of-care and sustainable-pace lineage (in neutral management terms): references/care-as-infrastructure.md.
The decision it most often settles: paced vs. avoidant
Carried, slow, or deferred work triggers a real question — is this drift, or is it healthy pacing? Don't pathologize by default. Run the test:
| Signal | Leans paced (legitimate) | Leans avoidant (real drift) |
|---|
| Is there a stated reason for the pace? | Yes — a quality gate, a window/cadence, a dependency, capacity | No reason given; just slipping |
| Is it moving, even slowly? | Yes — gated progress, sequenced steps | Untouched across many days, no sequencing |
| Would shipping now lower quality below a real bar? | Yes — the gate is protecting the output | No — it's ready; the delay is friction-avoidance |
| Is the target genuinely future-anchored? | Yes — waiting-on-date, window cadence | No — it could be done now and isn't |
If it leans paced → display it neutrally, don't nag. If it leans avoidant → name it directly (Radical Candor). The skill is telling them apart, not defaulting to either.
How to apply (the workflow)
- Read the capacity, not just the calendar. Before loading more on, check what's already in flight (active projects, carries, calendar fullness). A "yes" to new work is a "no" to something — surface the trade.
- Sequence, don't pile. Deferral-by-sequencing (doing things in a deliberate order) is not avoidance. Distinguish a real backlog from a manufactured-urgency list.
- Honor rhythm. Rest, recovery, and cyclical pace are inputs to sustained output, not lost time. A slower lane through a quality gate beats a fast lane that ships low-quality work that boomerangs.
- Protect the gate, not the speed. When something is paced for quality, the pace is the feature. Don't treat "carried through a real bar" as a failure to ship.
- Still name true avoidance. Sustainable ≠ permissive. When the test says avoidant, this skill makes you more direct, not less — care personally AND challenge directly.
Worked example
A draft has been carried for several days. Naive read: drift — push to ship. Cadence read: there's a stated three-gate publish bar, the draft moved through two of them, and shipping now would publish below the bar. → Paced, not avoidant. Display neutrally, nudge gently, don't pathologize. (Contrast: a task with no reason, untouched for a week, doable now → name it as drift.)
Relationship to the rest of the system
This complements the Anti-values (defensive) and the Growth Mindset (the person grows). It's the lens behind "what are you saying no to?", horizon-hiding for far-dated carries, and window-cadence carry display. When /aios:drift, /aios:today, or /aios:close-day weigh whether carried work is avoidance, this is the test to run.
