Commitment, Disclosure, Exception, and Outcome Log¶
Method — instantiates Evidence-Bounded Trust Governance
Keeps a running ledger that links each material promise and disclosure to the deviations, reasons, harms, responses, and remedies that followed it, and shows whether the loop actually closed.
The Commitment, Disclosure, Exception, and Outcome Log is a running ledger of promises against reality. Where the other mechanisms decide or test how much reliance is warranted before the fact, the log is the durable record that runs alongside the relationship: every material commitment and disclosure the trustee makes is written down, and then each deviation from it is linked back to its cause, the parties it affected, the response taken, and the remedy — with an explicit open/closed status. Its defining idea is the closed loop: a promise is not a data point, it is the head of a chain that is only resolved when the exception it spawned has been owned and remedied. The log neither grades evidence nor grants reliance; it makes accountability legible over time by ensuring that no material promise, and no broken one, silently disappears.
Example¶
An enterprise SaaS vendor signs a service-level agreement: 99.95% monthly uptime, 24-hour breach notification, no subprocessors added without notice. The customer's vendor-management lead opens a log. Each of those is a commitment row. Over the year, entries accumulate. A March outage breaches the uptime promise — the log links it to a disclosure (the vendor's root-cause writeup: a botched database failover), the impact (four hours of degraded service for 200 seats), the response (a fix to the failover automation), and the remedy (a service credit) — and the row is marked closed once the credit lands and the fix ships.
A second entry is more telling. In June the vendor quietly adds a new analytics subprocessor. There is no disclosure row to match the commitment "no subprocessors without notice" — the log surfaces a silent exception, an unmatched promise. That gap is the finding: not that an outage happened, but that a commitment was broken with no disclosure, no impact assessment, and no remedy. At renewal, the customer does not argue from memory or goodwill; they read the ledger — which promises held, which broke, which breaks were owned and closed, and which simply vanished.
How it works¶
- Record the commitment at its source. Every material promise or disclosure becomes a dated row in the trustee's own words, so later deviations have something concrete to be measured against.
- Link, don't just list. Each exception is chained to the commitment it violated, its cause, the parties harmed, the response, and the remedy — the entries are a graph, not a pile.
- Track open/closed status. A deviation stays open until its remedy is complete; the log's headline number is how many loops remain unclosed, and for how long.
- Surface the silent exception. A commitment with no matching disclosure or outcome is itself flagged — the absence of an entry is treated as a finding, not as compliance.
Tuning parameters¶
- Materiality threshold — which promises are worth logging. A low threshold captures everything but buries signal; a high one keeps the ledger readable but can miss a small broken promise that presaged a pattern.
- Attribution depth — how far each exception's causes and impacts are traced. Deeper links support real accountability but cost time and can turn adversarial.
- Closure definition — what counts as a remedy that closes a loop. A strict bar (harm actually repaired) prevents paper-closure; a loose one clears the queue but hides unremedied harm.
- Access and transparency — who may read and append. Shared visibility supports challenge; over-exposure can leak confidential evidence or chill candid disclosure.
- Retention window — how long closed entries persist. Long retention reveals slow patterns; short retention protects privacy and prevents stale evidence from haunting a repaired relationship.
When it helps, and when it misleads¶
Its strength is memory that resists both selective forgetting and selective remembering: at renewal, breach, or dispute, the ledger replaces "my sense is they've been reliable" with a chain of promises, breaks, and closures anyone can inspect. It is what makes accountability structural rather than personal, and it is the substrate a later audit or breach investigation reads from.
Its failure mode is that a log records but does not itself repair — and a well-kept ledger can create moral hazard, quietly relaxing the pressure to perform because "at least it was documented."[n1] The classic misuse is defensive documentation: the log becomes a compliance artifact, its loops marked closed on paper while the harm sits unremedied, or it is wielded as a weapon of accumulated grievance rather than a tool for correction. The guarding discipline is to define closure as harm actually remedied, to make the count of open loops the number that matters, and to remember the log's job is to prompt remedy and challenge — not to substitute a paper trail for either.
How it implements the components¶
commitment_exception_accountability_and_remedy_structure— the ledger is this structure: it links each promise and disclosure to its deviations, causes, impacts, ownership, and remedy, and tracks whether the accountability loop closed.
It does not detect breach, contain harm, or run the repair path — that is the Trust-Breach Triage, Containment, and Repair Protocol, which consumes this log's evidence trail; the log records and flags, but the protocol acts. It also does not grade or authenticate evidence (proportional_evidence_signal_verification_and_privacy_plan), stage reliance (domain_specific_trust_tier_and_reliance_envelope), or calibrate tiers against outcomes (trust_calibration_outcome_dependency_and_drift_review).
Related¶
- Instantiates: Evidence-Bounded Trust Governance — the log is the accountability memory the lifecycle writes to and reads from.
- Sibling mechanisms: Domain-Specific Trust Evidence and Exposure Matrix · Graduated Reliance and Bounded-Exposure Trial · Independent Reference, Claim, and Conflict Verification · Trust-Breach Triage, Containment, and Repair Protocol · Trust-Calibration and Dependency Audit
Editorial Notes¶
Form Classification¶
Form family: Record, Log & Register
Rationale: Keeps a running ledger that links each material promise and disclosure to the deviations, reasons, harms, responses, and remedies that followed it, and shows whether the loop actually closed, 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, Disclosure, Exception, and Outcome Log as 'Keeps a running ledger that links each material promise and disclosure to the deviations, reasons, harms, responses, and remedies that followed it, and shows whether the loop actually closed', so its operative form is Record, Log & Register.
Review outcome: Independent reviewer agreement; high confidence.
Origin Attribution¶
Primary origin: Accounting & Auditing
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Multi-domain
Rationale: Audit and control practice cohered attributable ledgers that link commitments, exceptions, corrective action, evidence, and closure status.
Related originating lineages:
- Law & Governance — Compliance and remedy regimes contribute disclosure duties, breach reasons, harms, and accountable redress.
- Organizational & Management Science — Issue and action tracking contributes ownership, lifecycle state, and closure follow-through.
Review resolution: Both reviewers agree on accounting_auditing as primary. Reading the source mechanism confirms that its defining operation belongs to that lineage; the final record retains law_governance, organizational_management 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¶
[n1] Moral hazard is the tendency to take less care when the consequences of a lapse are borne, absorbed, or merely documented elsewhere. A log that records deviations without ensuring remedy can inadvertently produce it — "it's in the log" becoming a substitute for "it won't happen again" — which is why closure must be defined as harm remedied, not harm recorded. ↩