Sample · Not a real insured
Insurance · Underwriting evidence pack
Open the pack. Check it yourself.
What an underwriter receives from an insured that runs Regulayer™: the insured workflow, one bind allowed, one bind held, and a signed record you verify in your own browser, without us.
Your insured runs Regulayer™. You review the evidence they choose to share.
No Regulayer™ engine for the carrier to install.
1 · The insured workflow
Who may let the AI do what.
| Insured | A coverholder that binds commercial property on a carrier’s paper. |
|---|---|
| Workflow | An AI agent issues binders under a binding authority. |
| Named person | The carrier’s underwriting manager, by role. |
| Authority | Commercial property, one territory, up to $2,000,000 per risk, until the end of the year. |
| Where it runs | Inside the insured’s own environment. The insured chooses what evidence to share. |
| What the carrier installs | No Regulayer™ engine. The carrier reviews the evidence it is given. |
2 · One bind allowed, one bind held
Illustrative example · Delegated authority
The carrier withdraws the binding authority. The next bind is held.
The authority. The carrier’s underwriting manager lets a coverholder’s AI agent bind commercial property on the carrier’s paper: one territory, up to $2,000,000 per risk, until the end of the year.
Bind 1 · 9:14 AMBound
A $1,400,000 warehouse risk.- Inside the class
- Inside the territory
- Inside the limit
- Authority current. Bound, and recorded.
Bind 2 · 2:07 PMHeld
A $1,400,000 warehouse risk.- Inside the class
- Inside the territory
- Inside the limit
- Authority withdrawn at 1:40 PM. Held for an authorized person, and recorded.
Same class, same territory, same limit. Only the authority changed, and the bind waited for a person.
Illustrative example. Sample carrier, sample coverholder, sample binds. Regulayer™ supplies the evidence; the carrier makes the determination.
3 · Verify a record
A signed record. Change it, and it fails.
Every decision, allowed or held, is sealed as a signed record when it happens. Take two of the engine’s own signed records and drop each into the open verifier. No account, no call to Regulayer™.
Download a file below.
Open the open verifier and drop the file in.
Compare what it says with the expected result.
The engine’s signed records, untouched.
Expected: the sequence is complete, and all 23 records verify.
The same records, with one stopped action rewritten as allowed.
Expected: 22 verify. Record 3 fails: the signature does not match this record.
These two files come from the engine’s recorded demonstration run with sample people, not from an insurance workflow. They show how a record is checked. All seven files are on the verifier test set.
4 · At three commercial moments
A driving record for AI, in practice.
| Moment | What the insurer receives | From the records |
|---|---|---|
| Underwriting | Evidence of the controls operating on the connected workflow | This pack: the workflow, the authority, an allowed bind, a held bind |
| Renewal | A comparable history of actions, interventions and gaps | The same records, for the whole period |
| Claim | A timeline of authority, attempted actions and observed outcomes | The records around the loss, in order |
Next
Your insured’s own workflow, in a pilot.
Sample. Illustrative workflow, sample carrier, sample coverholder, sample binds. Regulayer™ supplies the evidence; the carrier makes the determination. Patent pending.
