- Kind
- model (vendor model from Corvane)
- typed
- Owner
- Actuary
- typed
- Accountable executive
- CRO
- produced
- Monitoring status
- declarations streaming; the boundary is watching only, beside the institution's own gateway, so it records and cannot block
- produced
- Re-assertion interval
- 90 days
- typed
- Last asserted
- asserted 2026-10-01
- produced
- Supplier record
- Corvane, on file since 2026-03-12 checked 16 Oct 2026
- typed
The prototype switches the signed-in role. Only the named role sees a decision's trigger.
Inventory / nebula-mutual/
Underwriting triage
- Approval recorded
- G4 draftdrafted 2026-10-15 by the actuary in Claude; awaiting the CRO, due 2026-10-22
- Run status
- Not yet approvedG4 not passed; nothing should be running
typed entered by a personproduced written by the system
Gate chain
| Gate | Name | Approval | Named approver | Evidence | Record |
|---|---|---|---|---|---|
| G1 | Data and design | passed 2026-03-20 migrated at onboarding, 2026-05-04, from the prior register | Data lead | 91d4e7ed0e34… show full hash91d4e7ed0e34e4c8f777f15acd2da836f4fd1ca467f930e55c02542288bb33dd | G1 record |
| G2 | Validation | passed 2026-08-21 | Validator | a2c6f01dbf61… show full hasha2c6f01dbf6161db26baadfd4fb1b33365c90ab9039bc306f3ce3be218a51725 | G2 record |
| G3 | Approval | passed 2026-09-12 | CRO | b3e801a0c541… show full hashb3e801a0c54134edfd58c0786de66e97dbb54b68a330e3aae6f7dc55a140b43a | G3 record |
| G4 | Deployment | draft | CRO | none yet | G4 draft |
| G5 | Operation | not started | Actuary | none yet | none yet |
Gate records
- Gate
- G1 data and design, passed 2026-03-20
- produced
- Approver
- Data lead, signed 2026-03-20 16:14 CT with key dl-nm-01, Ed25519; token GT-2026-0057
- produced
- Provenance
- Migrated at onboarding, 2026-05-04, from the prior register
- produced
- Evidence at passage
91d4e7ed0e34… show full hash
91d4e7ed0e34e4c8f777f15acd2da836f4fd1ca467f930e55c02542288bb33dd- produced
- Gate
- G2 validation, passed 2026-08-21
- produced
- Approver
- Validator, signed 2026-08-21 13:04 CT with key val-nm-01, Ed25519; token GT-2026-0344
- produced
- Evidence at passage
a2c6f01dbf61… show full hash
a2c6f01dbf6161db26baadfd4fb1b33365c90ab9039bc306f3ce3be218a51725- produced
- Gate
- G3 approval, passed 2026-09-12
- produced
- Approver
- CRO, signed 2026-09-12 15:20 CT with key cro-nm-01, Ed25519; token GT-2026-0371
- produced
- Conditions
- Attach the vendor model card from Corvane before G4. Owner: Actuary (model owner).
- typed
- Evidence at passage
b3e801a0c541… show full hash
b3e801a0c54134edfd58c0786de66e97dbb54b68a330e3aae6f7dc55a140b43a- produced
Re-assertion
The model owner confirms the entry is still true, and says what that rests on.
The actuary, as model owner, re-asserts this entry.
Learn more about re-assertion
Each re-assertion is a signed record and resets the interval. It names its evidence: what the chain already holds, a file you attach, or your word only, said as such.
A late re-assertion says why it lapsed. If you cannot confirm the entry, escalate it: the CRO, as accountable executive, decides, and nothing is re-asserted meanwhile.
Re-assertion interval
Now: 90 days. Tier 2 allows at most 90 days.
The Data lead, as register owner, sets the interval.
Learn more about intervals
One interval control, in days, everywhere. Every entry without its own interval follows the tenant interval, 90 days, never above its tier's maximum, including entries that existed before the tenant interval was set. The register owner sets an entry's own interval; a practitioner may only draft it.
An interval longer than the tier allows is flagged here, on Records home and on the control center, and the control refuses it.