Reliability model
Coherent reads, safe fallbacks and failure behavior across the public product.
BizHedge prefers a truthful unavailable state over a partial or internally inconsistent result.
Reliability invariants
| Invariant | Failure response |
|---|---|
| One market generation per analysis | Keep the prior verified generation or stop before candidate construction. |
| One public generation per partner view | Restart the full snapshot after a conflict. |
| One construction behind every dollar | Reject arithmetic drift and rebuild from the vetted position. |
| One exposure reference per owner answer | Do not apply the answer to a sibling exposure. |
| One idempotency identity per receipt payload | Return the existing receipt or a conflict. |
| Complete customer cohort before publication | Keep the cell, dimensions and dates private. |
Partner snapshots carry both a checkpoint and public generation. Clients page to the end, then verify that summary and taxonomy identify that same generation; a change triggers a clean restart.
Safe fallback order
Fallback retains known evidence; it does not relabel older evidence as freshly published. Public health preserves the generation identity, reports the actual publication age and exposes the failure state.
Idempotency and resumability
Long market refreshes checkpoint completed work and publish only after full verification. Partner changes can be replayed from an opaque checkpoint. Receipt creation uses a stable idempotency identity. These mechanisms let clients repeat an interrupted action without creating a second public fact.
Bounded failures
Public errors use stable classes and omit raw dependency messages. A live analysis failure closes its stream with a calm stage error; a no-fit result remains distinct because its search completed. Failure to persist an already completed analysis does not retroactively invalidate the owner result.
Private surfaces fail closed. Missing or invalid authorization does not expose response details that help distinguish private records, and repeated partner-generation instability returns a conflict response so clients reset instead of merging incompatible data.
Verification layers
Schemas validate object shape. Unit and contract tests verify financial, privacy, generation and method behavior. Static builds validate the public artifact tree and documentation boundary. External acceptance must still identify the exact deployment and backend state being reviewed; a passing local build is not production evidence.