Listen: Deep Dive podcast on this topic — play below (~20 min English; Spanish follows).
Open almost any operational review. Velocity is up. The board is green. Standups happen. Tickets close.
And yet something still feels stuck — not because people are lazy, but because activity is being mistaken for health.
This post names what that stuck feeling often is: not one vague “technical debt” number, but two independent tensions that can accumulate while the surface looks calm.
Two debts, not one bucket
Compendium `04_HARMONY_AND_METRICS` splits tension into:
Coherence debt — unresolved structure tension: conflicting patterns, unstable commitments, forms that do not fit together, schema mismatch in the shared pattern library.
Flux debt — unresolved continuity tension: unhandled offers, unfinished runs, events not yet integrated back into identity, queues that shuffle without clearing.
Collapsing both into a single backlog score hides the diagnosis. You can be structurally coherent while continuity stalls — or busy clearing events while patterns fight each other.
Total tension and harmony
Total tension is written H = coherence debt + flux debt.
Harmony means H reaches zero: both components cleared, not traded off on a spreadsheet.
That is a stronger claim than “we hit sprint goals.” It means lawful organisational steps are actually reducing tension off-equilibrium — and the formal project proves constitutional convergence to H=0 for systems that satisfy the seam discipline.
Two loops, two reduction paths
The dual-triangle map (see Accountability Without Architecture Is Just a Promise) is not repeated here. What matters for harmony:
- Class-side refinement — Accept, Run, Publish — mainly addresses coherence debt by returning execution evidence to public pattern-space.
- Instance-side processing — Fit, Offer, Integrate — mainly addresses flux debt by folding returned continuity meaning back into private identity.
Same equilibrium, two jobs. Confusing which debt you are carrying sends fixes to the wrong loop.
What zero feels like (without mysticism)
At H = 0, further lawful steps change nothing useful. The system has reached maximal availability: stable enough to rest, responsive enough to act.
In plain terms: repetition does not keep rewriting state. Idempotence is earned through tension resolution, not declared by policy.
Keep this operational. Harmony is not a vibe; it is a measurable equilibrium the formal layer treats as proven when the constitutional interface holds.
Load-bearing boundary: residue is not backlog
Epic 29 adds a quantity that looks like debt but is not H:
Allocation residue — the exact mismatch when a continuous ideal is rendered into finitely many discrete quanta under a finite budget (think rounding remainders in a fair split).
Residue can exist even when H = 0, because discrete rendering always carries a bounded remainder. Treating residue as backlog tension produces false alarms and wrong fixes.
H measures disharmony and strictly decreases under lawful traversal. Residue measures rendering arithmetic. Do not merge them on one dashboard.
A Monday-morning diagnostic
Before you add process, ask:
Which debt am I actually carrying — structure, continuity, or neither (just residue)?
If you cannot answer, the next standup will measure activity again instead of health.
Compact summary
Green dashboards can hide two independent debts — structure and continuity — whose sum must reach zero for harmony. Lawful work reduces H off-equilibrium; Class and Instance address different components. At H=0, maximal availability means stable and responsive without endless rewrites. Allocation residue from discrete rendering is not H-debt.
Read next
- Accountability Without Architecture Is Just a Promise — the seam map this post assumes
- 04_HARMONY_AND_METRICS.md — Compendium anchor for H, convergence, and the residue caution
Listen to understand more
When tension actually clears (EN) · Deuda de coherencia y flujo sistémico (es-419)
Co-writers
Cursor: Composer 2.5 (body and metadata wrap).