- Gate
- G1 draft
- typed
- Approver
- Data lead (one named person)
- typed
- Intended use
- flag policies likely to lapse in 90 days, for a retention call; suggest only
- typed
- Data
- policyholder payment history, 2019 to 2026; personal data
- typed
- Tier
- 2
- typed
The prototype switches the signed-in role. Only the named role sees a decision's trigger.
Gates / Policy lapse prediction / G1
Gate record: policy lapse prediction, G1
Prototype states
- Approval recorded
- G1 draft
- Run status
- Not yet approvedG1 not passed; nothing should be running
typed entered by a personproduced written by the system
Evidence artifacts
| Artifact | SHA-256 | Captured | Source |
|---|---|---|---|
Data sheetOpen the artifact record
| 2b7e900c85f3… show full hash2b7e900c85f34c74f6cbe28122cfae7a98f7d5eff643e03bf6fb9944d1eac281 | 2026-10-16 14:02 CT | uploaded |
Design noteOpen the artifact record
| 8d14c34842af… show full hash8d14c34842af0b72c6197f6077c22235ebf5ef15f62c3712ed48b3adff4b8dc2 | 2026-10-16 14:04 CT | uploaded |
Decision
Named approver: the Data lead. Due 2026-10-30. Each option is a signed decision with a reason; none is one click.
Only the Data lead can sign, return or reject this gate. You can read the record and every artifact above.
No evidence attached
G1 needs the data sheet and the design note before the Data lead can sign. Attach them here; each is hashed and timed when it is attached.
Shown as it would be after the Data lead signs.
- Approval recorded
- G1 passed
- Run status
- Not yet approvedG2 to G4 not passed; nothing should be running
Token GT-2026-0418. Next: the Validator's G2.
Shown as it would be after the Data lead returns it.
- Approval recorded
- G1 draft, returned
- Run status
- Not yet approvednothing is running
Returned to the actuary with the Data lead's reason.