Skip to content
PROTOTYPE — MOCK DATAFigures are generated fixtures derived from the registry. Not ACF actuals.
Menu (13)

Collections — Nexusti roll rates

HEALTHY
Collections / Debt Recovery · production · 1 dataset
FOUR CLASSES, FOUR POLICIES — “HANDLE FAILED” IS NOT ONE SETTING
Transport — the push never arrived
client retries ×5, backoff to 15 min

We answer 503 with Retry-After. The idempotency key is what makes a retry safe rather than a double count.

Schema — the payload is the wrong shape
Reject the whole batch

Default. 365 valid rows out of 412 produce a figure nobody can reconcile against the source count.

Content — shape fine, values implausible
Quarantine + alert the data owner

Default. Same plausibility range the manual entry form already enforces.

Absence — nothing arrived
Mark not reported + alert

The only answer that does not invent a number. The tile goes to not_reported, which is a state, not a value.

NOT ON THE MENU

Zero-fill. It is not an unchosen option, it is an absent one. A silent zero on a board screen is the exact failure this platform exists to prevent.

ESCALATION LADDER, AND THE BREAKER AT THE END OF IT
  1. 1st failure or miss→ data_owner
  2. 2nd consecutive→ data_owner, metric_owner
  3. 3rd consecutive→ data_owner, metric_owner, division GM

Circuit breaker: 5 consecutive rejected pushes, or 3 consecutive missed windows, suspends the project. A feed that is failing repeatedly is producing noise — the failure state has to be louder than the data. Resuming requires a human and a note.

No rejected batch on this project. The inspector is demonstrated on Appraisal — daily decision report, which is currently refusing its file.