OpenChainGraph Suite · Audit & Assurance

Consent-Order / MRA Remediation Closure Cycle

Single-stage register cycle over an institution's own consent-order Articles or MRA findings and its own remediation-status records. The register computes, per issue, milestone completeness (every committed milestone closed with evidence attached), evidence validity (delivered evidence type matches what the milestone itself declares it calls for), and overdue or on-track timing against each issue's own committed date, reusing the RO remediation-closure cycle's cutoff arithmetic unchanged. The rollup emits the closed decision: auto_pass, review_required, escalate, or hold. hold and escalate route the register to an exception step naming the issue owner as reviewer; review_required routes to the compliance officer; and a fully closed register that reaches auto_pass still requires a named-human approval record rather than an automatic pass, because whether remediation was appropriate, timely, and sustainable is exactly the judgment the approval record exists to evidence, not to automate. The approver is bound to the institution's own MRA or consent-order response-owner role, named exactly as the order itself names it. The bundle evidences the institution's own basis for asserting closure; it does not itself satisfy a supervisor's own closure determination.

OpenChainGraph · 1 Step attestation mandate Hash-Anchored §4 chain_depth:1 Client-Side · Zero PII
Chain Topology: MRA Remediation Closure Register
§4 Execution Hash · Chain Definition Anchor
execution_hash:computing…
Chain Stages · 1 Step
1 ROOT / TERMINAL node dual_control(1, approver)
Consent-Order / MRA Remediation Closure Register art-533-mra-remediation-closure-register
Per-issue milestone completeness, evidence validity and overdue/on-track determinations, plus the rollup closed decision enum, close the closure-evidence bundle. Single stage.
§27 Human Accountability gate: the rollup decision (auto_pass / review_required / escalate / hold) routes hold and escalate to an exception step naming the issue owner as reviewer, and review_required to the compliance officer. Reaching the closure-evidence bundle at all requires at least one named approver's signed approval record over this run's subject_hash (dual_control, threshold 1, role approver), bound to the institution's own MRA or consent-order response-owner role, named exactly as the order itself names it, so no outcome, including a fully closed register, closes without a human accountable act.
MCP Call · register_mra_remediation_closure
{
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "name": "register_mra_remediation_closure",
    "arguments": {}
  },
  "id": 1
}
Export Artifacts
Download the §4 chain definition artifact (hash-anchored composite JSON) or the §13.11 W3C Verifiable Credentials view. Both derive from the chain definition; no new hash is minted. Available after hash computation.