- Request
- Underwriting notes summary
- typed
- Requested by
- Business line head, Group benefits
- typed
- Purpose
- summarize an applicant's underwriting file into a one-page brief for the underwriter; suggest only, the underwriter decides
- typed
- Proposed owner
- Actuary
- typed
- Data and its class
- applicant medical disclosures: sensitive-personal; underwriter case notes: personal
- typed
- Generative or agentic
- yes, on Meridian Language Systems
- typed
- Proposed tier
- 2, the requester's proposal
- typed
- Ticket
- NM-REQ-2291 in Nebula Mutual's ticketing
- typed
- Triage
- awaiting triage by the Data lead, due 2026-10-22, from the ticket
- produced
The prototype switches the signed-in role. Only the named role sees a decision's trigger.
Intake, as of 2026-10-16
Intake
Requests to use AI, before G1: what is asked, by whom, with what data, and the triage decision. Routing stays in your ticketing.
Prototype states
One request waits for your triage: underwriting notes summary, due 2026-10-22.Two of your requests are open: one waits for triage and one was returned to you for information.Nothing here waits for you. The Data lead triages requests.
| Request | Requested by | Personal data | Proposed tier | Triage | Ticket |
|---|---|---|---|---|---|
| Underwriting notes summary int-0011 | Business line head, Group benefits | personal; sensitive-personal | 2 | awaiting triage by the Data lead, due 2026-10-22, from the ticket | NM-REQ-2291 |
| Broker question assistant int-0010 | Business line head, Individual life | undetermined | 3 | returned for information 2026-10-15 by the Data lead, token GT-2026-0401 | NM-REQ-2287 |
| Policy lapse prediction int-0009 | Business line head, Individual life | personal | 2 | proceeds to G1 at tier 2 2026-10-14 by the Data lead, token GT-2026-0398 | NM-REQ-2264 |
| Group claims routing int-0008 | Business line head, Group benefits | personal | 2 | merged into Claims routing 2026-10-02 by the Data lead, token GT-2026-0384 | NM-REQ-2240 |
Learn more about intake
Intake is a record, not a workflow. It keeps what was asked, by whom, for what purpose, with what data, and what was decided. Assigning, chasing and due dates stay in your ticketing: each request carries its ticket, and the triage decision is posted back to it. A request that proceeds becomes an inventory entry with G1 open; one that is returned, merged or declined stays here with its reason.
typed entered by a personproduced written by the system
What the proposed tier would require
| Gate | Tier 2 in Nebula Mutual's profile |
|---|---|
| Entry | Entry, owner, classification, intended use |
| G1 Data and design | Data sources and design record; signed by the Data lead |
| G2 Validation | Validation report, narrower scope allowed; the same independence |
| G3 Approval | Approved by the CRO's delegate, with conditions and an expiry |
| G4 Deployment | Signed deployment record and rollback plan |
| G5 Operation | Re-assertion at least every 90 days |
From Nebula Mutual's own tier profile. The Data lead sets the tier at triage.
Triage
Named: the Data lead, as register owner. Due 2026-10-22, from the ticket. A signed decision with a reason, never one click.
Only the Data lead triages a request. Chasing it stays in your ticketing, on ticket NM-REQ-2291.
Shown as a request looks once it proceeds: the request for policy lapse prediction.
- Request
- Policy lapse prediction
- typed
- Requested by
- Business line head, Individual life
- typed
- Purpose
- flag policies likely to lapse in 90 days, for a retention call; suggest only
- typed
- Proposed owner
- Actuary
- typed
- Data and its class
- policyholder payment history, 2019 to 2026: personal
- typed
- Generative or agentic
- no
- typed
- Proposed tier
- 2, the requester's proposal
- typed
- Ticket
- NM-REQ-2264 in Nebula Mutual's ticketing
- typed
- Triage
- proceeds to G1 at tier 2 2026-10-14 by the Data lead, token GT-2026-0398
- produced
- Became
- nebula-mutual/lapse-prediction, submitted by the Actuary 2026-10-16 14:05 CT; G1 draft awaiting the Data lead
- produced
The Actuary or the Data lead submits the system; the entry carries this request.
- Request
- Broker question assistant
- typed
- Requested by
- Business line head, Individual life
- typed
- Purpose
- answer brokers' product questions from the product guides
- typed
- Proposed owner
- not named
- typed
- Data and its class
- broker questions: undetermined
- typed
- Generative or agentic
- yes; vendor not named
- typed
- Proposed tier
- 3, the requester's proposal
- typed
- Ticket
- NM-REQ-2287 in Nebula Mutual's ticketing
- typed
- Triage
- returned for information 2026-10-15 by the Data lead, token GT-2026-0401
- produced
- Why undetermined, and by when
- not given
- typed
Undetermined data is allowed at intake with a reason and a date. It cannot be admitted at release.
The requester edits a returned request and sends it back; the Data lead triages it again.
Shown to the requester after the Data lead returns int-0010: the request opens with its answers, and the fields it was returned for are marked.
Only the requester edits a returned request. You can read it on the Returned tab.
Learn more about returned requests
Editing keeps the request's number, int-0010, and its ticket. Each send writes a new version; version 1, with the Data lead's return, stays on the record, so the triage sees what changed.
Shown as a merged request looks: handled as a change to an existing entry, not a new system.
- Request
- Group claims routing
- typed
- Requested by
- Business line head, Group benefits
- typed
- Purpose
- route group benefit claims to the right adjudicator queue
- typed
- Proposed owner
- Actuary
- typed
- Data and its class
- group claim forms: personal
- typed
- Generative or agentic
- no
- typed
- Proposed tier
- 2, the requester's proposal
- typed
- Ticket
- NM-REQ-2240 in Nebula Mutual's ticketing
- typed
- Triage
- merged into Claims routing 2026-10-02 by the Data lead, token GT-2026-0384
- produced
- Merged into
- nebula-mutual/claims-routing, as a change to its intended use; the Actuary re-asserts the entry
- produced
What happens next
- Triage
The Data lead sets the tier and decides: proceed to G1, return, merge or decline.
- Submit
If it proceeds, the model owner submits the system and G1 opens.
- Track
The ticket carries the routing; this record carries the decision.