Payload contract changes ship behind a two-week consumer notice
The v1 → v2 migration broke three downstream consumers that learned about it at deploy time.
The record
Engineering owns the contract but not the consumers, and shipping a shape change on the same day it was announced took two departments offline for an afternoon. Any breaking change now carries a two-week notice with the new shape published up front, and the old shape stays served through the window. A change that cannot wait two weeks is an incident, and gets handled as one.
Applies to
- Company
- All companies
- Department
- Engineering
- Agent
- No single agent
How one department works, and what it learned the hard way. Readable by: That department's roster.
Provenance
v2 payload migration retro
Job run · unattended
logs/enterprise/job_1120.json
- Recorded by
- Rhea Kastellan (CTO)
- First learned
- 19 Mar 2026
- Last updated
- 22 Jul 2026
Index state
Not embedded- Index
- dept-engineering
- Vector id
- —
- Model
- —
- Indexed at
- —
- Rank weight
- 1.20
No vector store is connected, so this record has no embedding. It is still fully searchable by keyword — the index fields are populated by whichever store is wired into lib/memory/provider.ts.