Supersession Audit Trail?

Every logical row whose append-only entry column has more than one version. Each rewrite carries a supersedes reason from L1's v1 vocabulary (Inflight / BundleAssignment / TechnicalCorrection). Reads from the BASE tables, not Current — by definition Current hides the prior entries we want to audit here. Use the supersedes filter to slice by reason: high TechnicalCorrection volume signals a feed problem; high Inflight is normal in a busy bundling cadence.

Logical Keys (Transactions) with Supersession

Count of distinct transaction_id values (logical keys) whose append-only entry column has more than one row. Unit: distinct keys. The 'no-reason' KPI to the right counts ROWS, not keys — a key may have multiple no-reason rows. Healthy demos may be 0; production workloads typically have a small steady trickle of TechnicalCorrection / BundleAssignment events.

Supersession $ Exposure

Sum of |amount| across superseded transaction entries — the dollar magnitude of the audit surface. Counts alone leave the size question open; this is the answer to "how much money do these revisions move?"

Supersession Rows with No Reason

Count of higher-Entry rows whose supersedes reason is blank. Unit: rows, not distinct keys — one logical key may have multiple no-reason rows. Target value = 0; every supersession SHOULD declare its cause (Inflight / BundleAssignment / TechnicalCorrection) per the L1 SPEC. Drill into the detail table below to see which rows lack a reason.

Transactions Audit

Every entry of every logical transaction with >1 entry. The supersedes column on the higher-entry row tells you why it exists. Use the supersedes filter (Inflight / BundleAssignment / TechnicalCorrection) to narrow the audit to one cause class. Left-click a transaction_id cell to focus this sheet on that transaction's full trail (or pick one from the Transaction ID dropdown; clear that dropdown to return to all). Right-click the transfer_id cell to view every leg of this transfer on the Transactions sheet.

Daily Balances Audit

Every entry of every (account, business_day) cell with more than one stored value. The money column changing across entries is the audit trail for an end-of-day re-statement. Right-click the account_id cell to view the Daily Statement for that account-day.



Supersession Audit

_supersession_* is not a SHOULD-constraint — it's a diagnostic view that surfaces logical keys with multiple entry versions (the audit trail for TechnicalCorrection / BundleAssignment / Inflight rewrites). Reads from BASE tables (not Current*) since Current* hides superseded entries by construction. See the dashboard for the visualization.

Action. Diagnostic only — supersession is expected for normal corrections. Investigate when entry_count is unusually high for the row's age, or when the rewrite reason is missing. Diff the entries to see what actually changed across versions.