sustainable-cadencelisted

# 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`](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? | Y