Structured output lab
Ship and explain the ticket triage schema gate
Page 8 packages proved vs unproved evidence so another engineer can run, trust, or reject the ticket triage JSON endpoint.
1Learn the idea
Read
Assemble the ship record
A shippable lab artifact includes: how to run it, the metric result (schema pass rate; repair attempts; final reject count), the failure you can still reproduce (accepting extra fields that change routing, or string priority 'high' vs enum), the security gate for logging full ticket PII in triage debug dumps, and a rollback note. The user decision it supports remains: return validated category, priority, summary, and confidence for a support ticket.
Read
Freeze the evidence
npm run typecheck
npm test
Read
Run the credentialed smoke test only in an approved environment:
RUN_LIVE_EVALS=1 npm run test:live
Expected evidence: **“Charged twice” becomes billing/high with a short summary; extra keys are rejected.**. Store this beside the fixture version so scores remain meaningful after content changes in `structured-output-lab`.
Read
Explain limits without apology
State operating limits for the ticket triage schema gate in plain language: fixture size, offline vs live dependencies, and what would require a new eval set. Shipping structured-output-lab is honest scoping, not maximal confidence language.
Read
Lab notebook: proved vs unproved
Fill this table in your notes for the ticket triage schema gate:
- Proved on
sample ticket + triage schema: … - Unproved beyond the fixture: …
- Metric that blocks release: schema pass rate; repair attempts; final reject count
- Failure still reproducible: accepting extra fields that change routing, or string priority 'high' vs enum
- Security gate: logging full ticket PII in triage debug dumps
- Rollback: …
Ship the narrative only when the unproved list is honest. Reviewers trust narrow claims that support return validated category, priority, summary, and confidence for a support ticket more than maximal language that collapses under the first production oddity.
Read
Worked judgment
Hand your ship note to a peer and ask them to recreate a proved/unproved ship note with rollback without watching you type. If they cannot, your evidence is still tribal knowledge. Tighten the run command and the metric line until a stranger can validate the ticket triage schema gate against sample ticket + triage schema.
Read
Why this stage matters for the ticket triage schema gate
At the mastery and shipping stage for structured-output-lab, the job is narrower than finishing a product demo. You are creating one progressive evidence piece about sample ticket + triage schema that later pages inherit without redefining success. Keep that fixture small enough to inspect by hand, keep outputs copy-pasteable as text, and refuse to narrate this baseline as if it were a production SLA: free-text model reply without schema validation.
For this page specifically, success looks like a proved/unproved ship note with rollback while still centering the user decision to return validated category, priority, summary, and confidence for a support ticket. If you cannot point to a file, command, or assertion that proves that for the ticket triage schema gate, stay on this page instead of advancing.
Glossary: tool · Glossary: structured output · Cheatsheet: production ops signals
Go deeper
Before you start
Why this matters
List two things this chapter proved on the fixture and two things it did not prove about the ticket triage schema gate. If you cannot name the gaps, you are not ready to ship the narrative—even if the code runs.
In the wild
See how this idea shows up as a product and a company — then come back to the lesson. Skills transfer across vendors.
Related lessons
Check your understanding
Page assessment
Answer from memory. Completion is saved from this evidence, not from opening the next page.
All responses are required.