Five-ledger architecture / Structural Value Units (SVUc)
Capacity is the structure's ability to carry the work—not a morale score.
The IVA Capacity Ledger recognizes labor, time, attention, role load, infrastructure, resilience, redundancy, concentration risk, and the ability to sustain work.
Capacity explains why an approved and funded plan can remain infeasible. It preserves the cost of carrying the system even when the immediate output still arrives.
What the ledger recognizes
Independent standing inside the domain.
Capacity explains why an approved and funded plan can remain infeasible. It preserves the cost of carrying the system even when the immediate output still arrives.
- Role load, leadership bandwidth, timing burden, and implementation demand
- Coverage, redundancy, infrastructure, systems, data readiness, and resilience
- Concentration risk, hidden labor, dependency on informal knowledge, and carrying limits
Common structural signals
Conditions that formal reporting can miss.
One person repeatedly absorbs execution and cleanup
The condition requires evidence and recognition inside its native ledger rather than informal acknowledgment alone.
A plan assumes labor or timing that does not exist
The condition requires evidence and recognition inside its native ledger rather than informal acknowledgment alone.
Knowledge and authority are concentrated in an irreplaceable role
The condition requires evidence and recognition inside its native ledger rather than informal acknowledgment alone.
Reporting consumes the capacity required to improve performance
The condition requires evidence and recognition inside its native ledger rather than informal acknowledgment alone.
Evidence and governance
Recognition requires more than a plausible story.
A structural position must satisfy documentation, persistence, materiality, cross-functional impact, and verifiability. Once recognized, the register identifies classification, valuation, evidence reference, responsible owner, review date, and event history.
The public page explains the domain and its requirements. Detailed calibration, scoring interpretation, templates, diagnostic sequencing, and audit instruments remain protected.