Learning tools
PROJECT · MISSION 2 OF 7
WHEN YOU NEED THEM
Make intake reliable
Reproduce a duplicate delivery, repair the Python service, and preserve the result of an independent check.
Your saved customer charter
01 · UNDERSTAND THE CUSTOMER
A retry is a delivery, not a new decision.
Northstar’s intake integration serves several fictional customer tenants. Harbor and Cedar can both call their first event evt-01. The payload’s tenant field is a claim; the authenticated caller establishes which tenant may write.
Your repair must create one task for a new event, return that task on an identical retry, and reject a changed payload under the same key. JSON field order must not create a false conflict.
Before running anything, predict what happens if you deduplicate on the event ID alone. Then consider two workers receiving the same event at once.
one atomic commit→Adjuster work
02 · PREDICT, RUN, INSPECT
Which repair survives a different customer?
This browser model compares four policies on the same authored events. It does not run your downloaded Python code. The local checker additionally tests restart and concurrent delivery.
FIXED STARTER BASELINE · practice · starter
| Case | Delivery | Expected | Observed | Task | Result |
|---|---|---|---|---|---|
| p1 | First Harbor deliveryCreated one task and recorded its event identity. | 202 | 202 | 1 | Pass |
| p2 | Sender retries after its connection dropsCreated one task and recorded its event identity. | 200 | 202 | 2 | Needs repair |
| p3 | Another Harbor claimCreated one task and recorded its event identity. | 202 | 202 | 3 | Pass |
| p4 | Cedar independently uses evt-01Created one task and recorded its event identity. | 202 | 202 | 4 | Pass |
| p5 | Negative amountInvalid claim identity or amount; no state was written. | 400 | 400 | None | Pass |
| p6 | Missing claim identityInvalid claim identity or amount; no state was written. | 400 | 400 | None | Pass |
| p7 | Harbor credentials try to write Cedar dataThe authenticated tenant cannot write this payload. | 403 | 403 | None | Pass |
| p8 | Same event key with a changed amountCreated one task and recorded its event identity. | 409 | 202 | 5 | Needs repair |
| p9 | Cedar creates a second taskCreated one task and recorded its event identity. | 202 | 202 | 6 | Pass |
| p10 | Harbor creates a third taskCreated one task and recorded its event identity. | 202 | 202 | 7 | Pass |
| p11 | Cedar retries its second taskCreated one task and recorded its event identity. | 200 | 202 | 8 | Needs repair |
Inspect the exact event inputs and resulting tasks
p1: authenticated harbor, event evt-01, payload tenant harbor, claim H-101, amount 1200.
p2: authenticated harbor, event evt-01, payload tenant harbor, claim H-101, amount 1200.
p3: authenticated harbor, event evt-02, payload tenant harbor, claim H-102, amount 980.
p4: authenticated cedar, event evt-01, payload tenant cedar, claim C-201, amount 540.
p5: authenticated harbor, event evt-03, payload tenant harbor, claim H-103, amount -2.
p6: authenticated harbor, event evt-04, payload tenant harbor, claim missing, amount 250.
p7: authenticated harbor, event evt-05, payload tenant cedar, claim C-999, amount 90.
p8: authenticated harbor, event evt-01, payload tenant harbor, claim H-101, amount 1300.
p9: authenticated cedar, event evt-06, payload tenant cedar, claim C-202, amount 180.
p10: authenticated harbor, event evt-07, payload tenant harbor, claim H-104, amount 760.
p11: authenticated cedar, event evt-06, payload tenant cedar, claim C-202, amount 180.
Tasks that actually exist in this run
Task 1 · harbor · H-101 · amount 1200
Task 2 · harbor · H-101 · amount 1200
Task 3 · harbor · H-102 · amount 980
Task 4 · cedar · C-201 · amount 540
Task 5 · harbor · H-101 · amount 1300
Task 6 · cedar · C-202 · amount 180
Task 7 · harbor · H-104 · amount 760
Task 8 · cedar · C-202 · amount 180
Why the strongest policy still needs a transaction
Tenant-scoped keys prevent unrelated customers from colliding. Comparing a canonical payload detects a changed request under an old key. Persisting the key survives restart. The local reference creates the task and event record in one SQLite transaction, with a unique tenant/event constraint, so competing deliveries cannot both create work.
Those properties hold inside this exercise’s single SQLite database. External side effects, event retention, distributed transactions, and a production signature replay policy need separate designs.
03 · REPAIR REAL CODE
Take the failure into your terminal.
Unzip the project, open its folder, and run the starter checks. The first command is meant to fail: it writes a report of the duplicate-delivery bug.
python3 check.py --candidate starter.py --report before.json Repair starter.py, then run the same checks against your own implementation.
python3 check.py --candidate starter.py --report evidence.jsonThe kit includes a loopback HTTP server, signed fixture deliveries, SQLite persistence, independent changed cases, and a reference solution to inspect after your attempt. Read its README before running the server.
Download project + README ↓04 · DEFEND THE DELIVERY
What changed, and what proves it?
Run an experiment and attach the result that supports your decision. You can export an unfinished draft too.
Draft: attach a browser run and complete the three writing fields when ready for review.
Work saves in this browser after your first change.
Return to the full customer engagement
Use this mission’s code and report as evidence for the integration artifact. Discovery, AI evaluation, adoption, and handoff remain separate capstone work.
Open the nine-artifact capstone →Read the fictional worked engagement →Return to your FDE route →Back up your browser progress →Fixture version northstar-intake-2026-11-18.1. All customer records are synthetic. Browser runs are deterministic policy models; local reports are unsigned learner submissions. No mastery or hiring claim is made.