Name the input and the decision separately
Record the exact revision, repository, attendance input, and policy reference. The attendance input should identify its authority—for example, a named check-in record or event—rather than a vague Boolean. Then record the proposed capacity effect explicitly: unchanged, hold, release, or reassign under the named policy.
PostgreSQL's transaction-isolation documentation describes serialization failures and retrying a transaction. That applies to PostgreSQL's documented behavior; it does not show that this change, another database, or a scheduling system handles capacity correctly.
Make the repeat-event and rollback paths inspectable
Run the local receipt validator before asking a maintainer to inspect an actual repository. It requires a dry-run outcome, a declared duplicate-event result of unchanged, a named reviewer, rollback owner, rollback procedure, and a post-rollback check.
node --test sites/odexing.com/evidence/P147/no-show-recovery-change-receipt.test.mjs
The fixture does not start a database, observe a dedupe key, classify a customer, release capacity, or authorize a merge. It checks only that the proposed review record refuses hidden policy and recovery decisions. A repository-specific exercise must still observe the first and repeated events.
Stop when a repeated report can create a new outcome
Pause the change when a repeated attendance report could produce another recovery action, when the policy is unnamed, or when rollback lacks an owner. A maintainer should also require a safe environment-specific exercise before relying on a local receipt.
For a separate retry-policy gate, see Gate an Agent-Generated Retry-Policy Change Before Merge. For a time-context change, see Gate an Agent-Generated Time-Zone Change Before Merge. For incoming-event verification, see Gate an Agent-Generated Payment-Webhook Change Before Merge.
Does this receipt choose a database isolation level or prove concurrency safety?
No. It identifies the questions that a repository-specific test and maintainer review must answer. Database choice, locking, retry policy, and production behavior remain environment-specific.