[abewheel]

Operating guidance could turn historical changes, unused proposals, and open risks into work that users could not truthfully finish. This release separates dormant planning and historical assurance context from current assignments while preserving actual approval, source continuity, access, deadline, and period-coverage checks.

• Add an owner-authorized impact decision bound to meaningful source history, current facts, procedures and exact materiality questions. Reuse already accepted design reviews and data-use decisions with matching retained source snapshots. Real change-and-revert cycles stale the binding; unrelated commits and committing reviewed work do not. Required approvals and Policy Events remain separate.
• Allow withdrawal of a never-effective Obligation Rule without invented activation or approval facts, preserving existing independent schedule decisions and immutable history.
• Keep unused inventory proposals dormant after setup, reconcile real setup logins without activating a service or rewriting prior frozen review populations, schedule continuing risks by their actual checkpoints, and recognize exact validated successor proof without rewriting historical records.
• Retain historical reporting gaps as disclosed limitations and keep gaps overlapping the candidate period actionable.
• Export target mutation payloads without calculating unrelated workflow/history, retaining stale-write protection for JSON and every companion slot.

Validation: independent combined correctness/security review loop; focused positive/negative regressions; actual Playwright review/withdrawal/risk paths, source and API checks; full uncached Node 24 validation; fresh local-package consumer validation; package inspection, zero-dependency audit, and private-source/secret scans.

Shared actions, generic writes and validation require a consistent declared and locked reader of 0.21.6 or newer before adopting the optional model 13 shapes. A truthful forward dependency repair restores current validity while disclosing an earlier format limitation; business dates and approvals are preserved. Installing the package does not change customer records. Both packages are coordinated at 0.21.6.