- Kind
- model, built in house
- typed
- Owner
- Actuary
- typed
- Accountable executive
- CRO
- produced
- Monitoring status
- none yet: not deployed
- produced
- Boundary
- none
- produced
- Re-assertion interval
- 90 days, the tenant interval
- typed
- Last asserted
- asserted 2026-10-09
- produced
The prototype switches the signed-in role. Only the named role sees a decision's trigger.
Inventory / nebula-mutual/
Pricing model v3
- Approval recorded
- G3 draftdrafted 2026-10-09 by the actuary; approver the CRO
- Run status
- Held by a conditionG3 cannot pass: a self-declared conformance self-test failed; nothing is 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-02 migrated at onboarding, 2026-05-04, from the prior register | Data lead | a0c4e18caeb2… show full hasha0c4e18caeb24f560878e38ae058091ec35fefc9499deb1855ced68c86b4b4be | G1 record |
| G2 | Validation | passed 2026-06-05 | Validator | c19be28551b8… show full hashc19be28551b8e6980dee4b81f3abb4810181362241bc00f99d09b8eb95a22ff7 | G2 record |
| G3 | Approval | draft | CRO | none yet | G3 draft |
| G4 | Deployment | not started | CRO | none yet | none yet |
| G5 | Operation | not started | Actuary | none yet | none yet |
Gate records
- Gate
- G1 data and design, passed 2026-03-02
- produced
- Approver
- Data lead, signed 2026-03-02 14:45 CT with key dl-nm-01, Ed25519; token GT-2026-0042
- produced
- Provenance
- Migrated at onboarding, 2026-05-04, from the prior register
- produced
- Evidence at passage
a0c4e18caeb2… show full hash
a0c4e18caeb24f560878e38ae058091ec35fefc9499deb1855ced68c86b4b4be- produced
- Gate
- G2 validation, passed 2026-06-05
- produced
- Approver
- Validator, signed 2026-06-05 11:42 CT with key val-nm-01, Ed25519; token GT-2026-0152
- produced
- Evidence at passage
c19be28551b8… show full hash
c19be28551b8e6980dee4b81f3abb4810181362241bc00f99d09b8eb95a22ff7- 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, the tenant interval. Tier 3 allows at most 365 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.