Configure the postmortems contract

Implement types or schemas around summarization service so illegal states are unrepresentable at the boundary. For blameless postmortem for tokenizer-induced summarization outage, trusted inputs come from sessions, signatures, pinned digests, or workload identity — not from free-form model text. EM facilitating review of INC-SUM-TOK-87 should be able to read the contract and know which fields are optional, which are enumerated, and which abort the request. Constructors and boot paths must not perform provider side effects; injection points keep tests honest.

Document required env vars in .env.example with placeholders only. Rotation story belongs later, but the contract already forbids printing secrets and forbids defaulting to fail-open when a dependency is missing. Invariant to encode in types/tests: actions are owned, dated, verifiable; contributing factors include process not only code. If a config number lacks units, fix the name (timeout_ms, rpm_hard) before writing logic.

14:02 deploy summarizer 14:11 error rate climb 14:20 page 15:22 pin digest + rollback

Create fixtures for the golden path and for INC-SUM-TOK-87. Name files after the behavior (429-retry-after.json, cross-tenant.json, empty-citation.json) rather than test1. Each fixture carries expected status/code. This kit is the shared language for validation and failure pages.

Compatibility promise: additive fields may appear only if readers ignore unknowns safely; breaking changes bump a version visible on the wire. For AI payloads, size limits arrive before JSON parse when hostile blobs are a risk. Document how clock skew, idempotency keys, and tracing headers travel through blameless postmortem for tokenizer-induced summarization outage. If you use feature flags later, the contract already states that flags are not authorization. Link each config knob to a unit and a failure mode (“0 means disabled” vs “0 means divide-by-zero”). A peer reviewing the PR should find INC-SUM-TOK-87 named in a comment on the adversarial fixture.

Generate OpenAPI or a typed client only after the hand schema is stable for one fixture round-trip. Record how errors look on the wire — problem+json, envelope, or bare status — and stick to one. Clock sources must be injectable for skew tests. If webhooks appear later, document signature header names now even as TODOs. Keep sample payloads UTF-8 and free of real emails. Add a makefile or npm script that validates schemas without network. In this chapter the product is blameless postmortem for tokenizer-induced summarization outage, the human stakeholder is EM facilitating review of INC-SUM-TOK-87, and the incident id you design against is INC-SUM-TOK-87. Re-state the oracle in your notes — postmortem published with 3 actions; action A1 verified by test that fails on old tokenizer pin — and keep the invariant visible: actions are owned, dated, verifiable; contributing factors include process not only code. Track actions_closed_on_time and recurrence_90d as the scoreboard. Surface under change control: summarization service. If you only have forty minutes, finish the fixture for action 'be more careful' with no owner — recurrence in 6 weeks before polishing UI. Promotion language stays ternary: promote, hold, or roll back based on evidence, not hope.