- Kind
- agent (LLM on Meridian Language Systems)
- typed
- Owner
- Actuary
- typed
- Accountable executive
- CRO
- produced
- Monitoring status
- declarations streaming; the boundary is watching and flagging, so it records and cannot block
- produced
- Re-assertion interval
- 30 days
- typed
- Last asserted
- asserted 2026-10-14
- produced
The prototype switches the signed-in role. Only the named role sees a decision's trigger.
Inventory / nebula-mutual/
Customer assistant
- Approval recorded
- G4 passed, condition duesigned by the CRO 2026-09-02; condition fired 2026-10-15: re-validate on vendor model change
- Run status
- Outside approvalapproval no longer covers what runs; the boundary is watching and flagging, and cannot block
- Configuration approved at G4
- recorded
- Configuration on live calls
- recordedno longer matches the one approved at G4 since 2026-10-15 09:41 CT
typed entered by a personproduced written by the system
Gate chain
| Gate | Name | Approval | Named approver | Evidence | Record |
|---|---|---|---|---|---|
| G1 | Data and design | passed 2026-04-14 migrated at onboarding, 2026-05-04, from the prior register | Data lead | 556f723c5505… show full hash556f723c5505f1a772d04e833c5f1222372c07e11799d0432ea07376fbf6d200 | G1 record |
| G2 | Validation | passed 2026-06-11 | Validator, independent of G3 | 37246b63cd96… show full hash37246b63cd96184177dbcd842b20282301b0d7f653cbce5b1984ecf79ec177dd | G2 record |
| G3 | Approval | passed 2026-07-19 | CRO | 61720fdd6369… show full hash61720fdd63693af61b5003e8fbed5416b6e112c4cad42b559668f04ab8c9ba81 | G3 record |
| G4 | Deployment | passed 2026-09-02, condition due | CRO | 52e4b24fa803… show full hash52e4b24fa803b96452f12e54b51de3a8d7916e8d105cdf0a53033c235ebd7927 | G4 record |
| G5 | Operation | in operation; declarations streaming | Actuary | 1172f042b67f… show full hash1172f042b67f2fe441787ae8bdde39c9acab44c7c5e32483076b975aa6301709 | G5 record |
| G2 | Re-validation after chg-0014 | not started | Validator | none yet | G2 re-validation |
Gate records
- Gate
- G1 data and design, passed 2026-04-14
- produced
- Approver
- Data lead, signed 2026-04-14 10:04 CT with key dl-nm-01, Ed25519; token GT-2026-0089
- produced
- Provenance
- Migrated at onboarding, 2026-05-04, from the prior register
- produced
- Evidence at passage
556f723c5505… show full hash
556f723c5505f1a772d04e833c5f1222372c07e11799d0432ea07376fbf6d200- produced
- Gate
- G2 validation, passed 2026-06-11
- produced
- Approver
- Validator, signed 2026-06-11 16:05 CT with key val-nm-01, Ed25519; token GT-2026-0160
- produced
- Evidence at passage
37246b63cd96… show full hash
37246b63cd96184177dbcd842b20282301b0d7f653cbce5b1984ecf79ec177dd- produced
- Gate
- G3 approval, passed 2026-07-19
- produced
- Approver
- CRO, signed 2026-07-19 12:14 CT with key cro-nm-01, Ed25519; token GT-2026-0318
- produced
- Evidence at passage
61720fdd6369… show full hash
61720fdd63693af61b5003e8fbed5416b6e112c4cad42b559668f04ab8c9ba81- produced
- Configuration approved
- recorded
- produced
- Gate
- G4 deployment, passed 2026-09-02; condition due
- produced
- Approver
- CRO, signed 2026-09-02 14:12 CT with key cro-nm-01, Ed25519; token GT-2026-0362
- produced
- Conditions
- re-validate on vendor model change (fired 2026-10-15)
- typed
- Configuration approved at G3
- recorded
- produced
- Evidence at passage
52e4b24fa803… show full hash
52e4b24fa803b96452f12e54b51de3a8d7916e8d105cdf0a53033c235ebd7927- produced
- Gate
- G5 operation, in operation since 2026-09-02
- produced
- Approver
- Actuary, signed 2026-09-02 14:24 CT with key act-nm-01, Ed25519; token GT-2026-0363
- produced
- Evidence at passage
1172f042b67f… show full hash
1172f042b67f2fe441787ae8bdde39c9acab44c7c5e32483076b975aa6301709- produced
Re-assertion
The model owner confirms the entry is still true, and says what that rests on.
Waits until chg-0014 closes: what runs no longer matches what G4 approved.Open the change chg-0014
Re-assertion waits until chg-0014 closes. The actuary, as model owner, re-asserts it then.
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: 30 days. Tier 1 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.
Retirement
Retiring at G5 removes the boundary and revokes keys. The records stay readable and exportable.
The actuary, as G5 approver, signs a retirement.