Commitment Register¶
Tracking register — instantiates Commitment Lifecycle Governance
Holds every commitment and its current lifecycle state — proposed, active, amended, satisfied, breached, released — in one owned, queryable record, so no promise is silently forgotten and none lingers past its basis.
A Commitment Register is the archetype's memory — the single place where each commitment lives as a durable row carrying its current state, its accountable owner, and its priority, from the moment it is proposed until it is satisfied or released. Its distinguishing move among its siblings is authoritative state and ownership over the whole life: where a speech-act clause makes a commitment and a verification mechanism checks one, the register answers, at any moment, the one question the others can't — which commitments exist right now, who owns each, and what state is each in. It does not create commitments, and it does not enforce them; it keeps them from becoming invisible, unowned, or quietly stale.
Example¶
A bank operating under a regulatory consent order carries dozens of remediation commitments — stand up independent model validation, clear the transaction-monitoring alert backlog, re-paper high-risk accounts. A Commitment Register gives each one a row: the commitment, its accountable executive, its current state (active, at risk, satisfied), a priority class (regulator-facing vs. internal), a due-or-renewal date, and the date it last moved. Each quarter, the register is the artifact the board and the regulator both read from. When one commitment slips from active to at risk, it is visible and it is owned — nobody has to remember it was made. When another is marked satisfied, the row points at the evidence that closed it (evidence a verification mechanism produced, not the register). Nothing falls through the cracks, and status can be answered without a scramble.
How it works¶
Every commitment gets exactly one authoritative row, and that row's state is maintained across the lifecycle from a defined vocabulary — proposed, active, amended, satisfied, breached, released — so "what's the status of X" always has a single answer rather than several conflicting ones held in different heads. Each row names one accountable owner and a priority class that routes attention. The whole register is re-groomed on a cadence: satisfied and released rows retire, new commitments enter, and priority re-sorts what gets looked at first. Crucially, the register records state; it does not itself verify performance or fire consequences — a state change points at evidence held elsewhere.
Tuning parameters¶
- State vocabulary — how many lifecycle states the register distinguishes, from a crude open/closed to the full proposed→released set. Finer states show exactly where each commitment sits but demand more upkeep to stay accurate.
- Granularity — one row per headline commitment, or decomposed sub-commitments. Decomposition tracks partial progress but bloats the register until nobody reads it.
- Owner cardinality — strictly one accountable owner per row, or shared ownership. One owner removes the diffusion of responsibility; shared ownership reflects reality but blurs who answers for a slip.
- Priority class — how commitments are ranked for attention (regulator-facing, customer-facing, internal). Set well it surfaces the critical few; set badly it buries a serious slip under routine ones.
- Review cadence — how often rows are re-stated and pruned. Too rare and the register rots into a graveyard; too frequent and grooming becomes theatre.
When it helps, and when it misleads¶
Its strength is memory and single-answer status: a commitment that has been logged, owned, and state-tracked cannot be quietly forgotten, double-counted, or left ownerless. It is what lets a large body of promises be governed as a portfolio rather than as whatever each person happens to remember.
Its failure modes are equally real. The register holds only what someone chose to enter, so off-register side promises stay invisible while the tidy list lulls everyone into thinking it is complete. It decays into a write-only artifact groomed for audits rather than consulted for decisions. And its state field is easily run backwards — a row marked satisfied as a status game, without the performance evidence to back it, launders an unmet commitment into a closed one. The discipline that guards against this is to keep the register the single source of truth everyone actually consults,[n1] to require every state change to point at real evidence held elsewhere, and to prune retired rows as aggressively as new ones are added.
How it implements the components¶
Commitment Register fills the tracking-and-state side of the archetype's machinery — the components that keep commitments visible and owned over time:
commitment_ledger— it is the ledger: the enumerated, persistent record in which every commitment appears as one distinct, durable entry.standing_condition— each row carries the commitment's current lifecycle state, so whether a commitment still stands is an explicit, maintained field rather than something inferred.commitment_priority_class— it classifies commitments by criticality and audience, routing attention to what matters first.commitment_owner— each row names the single accountable owner-of-record, and the register maintains that field as ownership transfers across the lifecycle.
It does not create or word the commitments it lists (commitment_object, commitment_terms, authority_or_standing) — the Contract Speech-Act Clause does — nor does it verify that a commitment was kept or record its consequences (performance_evidence_set, consequence_record, accountability_and_consequence_path), which the Performance Contract, Warranty or Guarantee, and Performance Bond or Deposit own. The register tracks state; other mechanisms produce the evidence a state change points to.
Related¶
- Instantiates: Commitment Lifecycle Governance — the register is the lifecycle's memory, making every commitment's current state visible, owned, and single-answered.
- Consumes: entries generated at formation, e.g. a Contract Speech-Act Clause; state changes from revision, e.g. an If-Then Revision Contract, post to it.
- Sibling mechanisms: Contract Speech-Act Clause · If-Then Revision Contract · Readback Confirmation · Performance Bond or Deposit · Escrowed or Conditional Commitment · Performance Contract · Precommitment Device · Public Commitment · Renegotiation Notice Protocol · Service-Level Commitment · Warranty or Guarantee
Editorial Notes¶
Form Classification¶
Form family: Record, Log & Register
Rationale: Holds every commitment and its current lifecycle state — proposed, active, amended, satisfied, breached, released — in one owned, queryable record, so no promise is silently forgotten and none lingers past its basis, making its operative form a durable record, ledger, register, or trace whose value depends on preserving actual state or history.
Independent corroboration: The frozen evidence defines Commitment Register as 'Holds every commitment and its current lifecycle state — proposed, active, amended, satisfied, breached, released — in one owned, queryable record, so no promise is silently forgotten and none lingers past its basis', so its operative form is Record, Log & Register.
Review outcome: Independent reviewer agreement; high confidence.
Origin Attribution¶
Primary origin: Organizational & Management Science
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Multi-domain
Rationale: Project and governance practice cohered authoritative registers with owners and lifecycle states for obligations from proposal through release or breach.
Related originating lineages:
- Accounting & Auditing — Control registers contribute authoritative status, evidence, and exception accountability.
Review resolution: Both reviewers agree on organizational_management as primary. Reading the source mechanism confirms that its defining operation belongs to that lineage; the final record retains accounting_auditing only where it materially formed the mechanism and keeps present-day application breadth separate from provenance.
Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.
Review outcome: Reconciled after independent review; high confidence.
Notes¶
The register is deliberately not the enforcer. Keeping the record of state separate from the verification of performance and from the consequence path is what keeps the state field trustworthy: if the same body both marks a commitment satisfied and is judged on its rate of satisfaction, the state field is corrupted at the source. The register should be able to point at independently produced evidence for a closure, never be the sole author of it.
[n1] Single source of truth — the principle that a given fact should be recorded and edited in exactly one authoritative place, with every other view derived from it. A commitment register only works as governance if it is that place; the moment people keep parallel private lists of "real" status, the register stops being consulted and the whole mechanism hollows out. ↩