Northstar Mutual · Customer charterWork stays in this browser.
Scope the problem
Listen to the customer, inspect the intake problem, and agree a first delivery you can defend.
Step 1: Brief
YOUR FIRST CUSTOMER ENGAGEMENT
Find out why one delivery creates two tasks.
Northstar’s adjusters report duplicate tasks. Leadership has asked for an AI claims agent, but the first job is to understand the failure and agree a useful, measurable delivery.
Your deliverableA short customer agreement: what you will fix, how you will check it, and who owns it.Practice estimate25–35 minutes · synthetic case
MR
Maya RaoClaims director · Northstar Mutual
D1 / CUSTOMER REQUEST
“I promised leadership a demonstration in two weeks. They asked for an AI claims agent.”
Five stakeholders see different parts of the problem. Read their accounts, inspect the delivery trace, and write a first agreement. A new constraint will test whether it still holds.
INVESTIGATE BEFORE YOU COMMIT
Whose account changes your decision?
0 / 3 minimum accounts cited
LC
Luis Chen
Adjuster lead · D2
Interview account
I sometimes see two tasks for the same delivery. I think a duplicate takes about four minutes to untangle, but that is my estimate. We have not timed it consistently. The team worries that an automation project will be used to justify staffing cuts. Adjusters must retain claim decisions.
Read this carefully
An attributed account. Four minutes is an estimate, not a measured baseline.
A useful follow-up
Can you show a duplicate and observe how it is resolved, rather than estimate the whole cost from memory?
These are authored accounts. Keep requests, estimates, measurements, and constraints distinct.
02 · LOG-01 · INSPECTABLE EVIDENCE
Twelve deliveries. How many operations?
The old service created a new task for every delivery in this synthetic convenience sample. An event ID belongs to its customer namespace. A new event can legitimately update a claim you have already seen.
Selected trace: 2 deliveries for one customer/event operation. Inspect the highlighted task rows below.
12deliveries
9tenant + event operations
3extra tasks
LOG-01: one task row for every delivery, including retries
Row
Time
Tenant
Event
Claim
Created task
L1
09:00
harbor
evt-01
H-101
T-01
L2
09:01
harbor
evt-02
H-102
T-02
L3
09:02
cedar
evt-01
C-201
T-03
L4
09:03
harbor
evt-01
H-101
T-04
L5
09:04
harbor
evt-03
H-103
T-05
L6
09:05
cedar
evt-02
C-202
T-06
L7
09:06
harbor
evt-04
H-104
T-07
L8
09:07
harbor
evt-02
H-102
T-08
L9
09:08
cedar
evt-03
C-203
T-09
L10
09:09
harbor
evt-05
H-105
T-10
L11
09:10
cedar
evt-02
C-202
T-11
L12
09:11
harbor
evt-06
H-101
T-12
Trace the repeated operations
harbor / evt-01: rows L1, L4 created tasks T-01, T-04.
harbor / evt-02: rows L2, L8 created tasks T-02, T-08.
cedar / evt-02: rows L6, L11 created tasks T-06, T-11.
L12 updates H-101 under a fresh event ID. Deduplicating every occurrence of that claim would drop a legitimate operation.
Name the denominator
3 / 12 = 25% extra tasks per delivery.
3 / 9 = 33.3% extra tasks per distinct operation.
Both describe this sample. Neither establishes a weekly claims rate, model accuracy, live adoption, or savings.
YOUR CUSTOMER AGREEMENT
Make the first delivery defensible.
0 / 7 areas written · 0 accounts cited
What will change for the customer?
NORTHSTAR MUTUAL / WORKING AGREEMENT
Customer delivery charter
Working draft · 0 of 7 areas written
User and problem
This decision is still unwritten.
First delivery
This decision is still unwritten.
Success measure and baseline
This decision is still unwritten.
Safety and operating guardrails
This decision is still unwritten.
Out of scope
This decision is still unwritten.
Owner and acceptance task
This decision is still unwritten.
Assumptions and next questions
This decision is still unwritten.
Before you save
Still needed: User and problem; First delivery; Success measure and baseline; Safety and operating guardrails; Out of scope; Owner and acceptance task; Assumptions and next questions; Citations from at least three stakeholders
A CUSTOMER CONSTRAINT CHANGES
Your first decision is about to be tested.
Keep the initial agreement intact. Then see what happens when the delivery conditions change.
Save your first charter to unlock this part of the exercise.
05 · CHECK THE REASONING
What does the evidence support?
These authored cases check specific decisions. A matching answer does not grade your charter or certify customer-delivery skill.
06 · TAKE THE DECISION INTO THE BUILD
Keep the promise beside the code.
The intake mission can attach your latest saved charter to its selected experiment. That attachment stays fixed if you revise discovery later. A browser model or synthetic test run does not establish live customer outcomes.
northstar-discovery-2026-11-18.1. Every source and log row is synthetic. The illustrative worked engagement is separate from these exercise observations.
Your charter and checked cases save in this browser.