Mode
Internal controls

Account Closure Control Center

Controlled account deactivation with obligation checks, maker-checker evidence, case timeline, outbox records, and a no-Ledger mutation boundary.

SafetyOperationsLedger Safety
Closure requests00 open
Blocked checks00 warnings
Guard health0 / 00 legacy issues

Control State

Closure readinessreview required
Permission gaps0
Ledger references0

Request Evidence

Every closure request carries status, checker evidence, account state, timeline, outbox, and check counts.

No records yetRecords will appear here after the first live or test activity.

Subject Obligations

Open money or operational obligations stay visible before a Consumer or Merchant can be safely closed.

No records yetRecords will appear here after the first live or test activity.

Permission Evidence

Request, approval, cancellation, and reopen decisions must point to allowed Permission Checks for the same subject.

No records yetRecords will appear here after the first live or test activity.

Closure Checks

Checks explain the balances, holds, disputes, provider work, or warnings that can block closure.

No records yetRecords will appear here after the first live or test activity.

Database Guards

PostgreSQL guards enforce lifecycle shape, Permission Check evidence, one open request per subject, and commit evidence.

No records yetRecords will appear here after the first live or test activity.

Control Evidence

Closure changes access state only; corrections or payouts must remain in their own Ledger-safe modules.

No records yetRecords will appear here after the first live or test activity.

Timeline Evidence

Case Timeline gives Auditors an append-style lifecycle view of request, blocked, close, cancel, and reopen events.

No records yetRecords will appear here after the first live or test activity.

Outbox Evidence

Lifecycle events are emitted through Outbox after the authoritative transaction commits.

No records yetRecords will appear here after the first live or test activity.

Ledger Boundary

This table should stay empty; Account Closure is an access-state workflow and must not create Ledger movement.

No records yetRecords will appear here after the first live or test activity.

Legacy Guard Issues

Historical issue counters must remain zero before new closure writes are considered healthy.

No records yetRecords will appear here after the first live or test activity.