← Frame 21 — HO3 6mo

FRAME 22 / 24

Edge: commit-gate re-validation failed

Frame 23 — Bind void →

ALTHEA

Schneider Insurance · Richard ▾

What changed

At Set A generation · 14:18 CDT

Baldwin Coastal · OPEN for bind

→

At commit · 14:54 CDT

Baldwin Coastal · CAT suspension activated 14:42

Accumulation snapshot

unchanged · OK

·

Eligibility re-check

unchanged · OK

What this means & what's next②

No policy was issued, no money moved, no docs were delivered to the HO. The bind never committed — we caught the conflict at the gate. The HO does not know anything happened; they just signed a packet that won't be used.

To resume: wait for the CAT suspension to lift (typically 48–72 hours), then re-quote and re-collect signatures. The new packet will reflect any rate changes between now and then.

To tell the HO: "We caught a system-side change just before final lock — coverage hasn't started, and we'll regenerate the paperwork once a weather-related hold is lifted in a few days. No action needed from you yet."

Submission status = "commit failed, re-quote required" · audit logged

Back to dashboard Re-quote now

Stories covered

As Althea compliance, I want re-validation at the commit gate — accumulation, CAT suspension, eligibility — re-checked against current state, not the §1-pinned snapshot.
As an agent whose commit fails at the gate, I want a clear remediation message ("submission re-validation failed because [reason]. Set A is voided. Re-quote required.") — don't strand me.

Interactions

Diff card — explicitly compares §1-entry snapshot vs current state at §5 commit. Most useful for the hurricane-watch gaming scenario where suspension activates mid-bind. Agent sees exactly what changed.
HO-facing language — pre-written script so agent can communicate without speculation. "No policy was issued" is the load-bearing fact for the HO.

Design notes

This is the rarest path — sigs are usually collected within minutes; CAT activation mid-flow is the only realistic trigger.
Set A is voided (not re-used) because anything that changed at the gate may have changed in the packet's underlying assumptions (rates, eligibility, accumulation).
No HO-facing delivery happens — Pattern 1 (bind = in-force) only fires after commit, which never happened here.
Audit log captures the full state diff for compliance reproducibility.

Edge cases not shown

Accumulation re-validation fail (rare — zone hit capacity mid-bind)
Eligibility re-check fail (e.g., HO3 expired during sig window)
OFAC re-screen fail (TBD — re-screen is Phase-2 at launch)
Rate table version updated mid-bind (handled by version-pin TTL, not re-validation fail)
Multiple gate fails at once