Notes

Schema rules that survive three tool migrations

Hands typing on a laptop during a workshop

Rename pressure shows up after a platform rebrand or a new orchestrator. Without a version rule, every rename forks historical reliability reports.

Prefer additive properties with a deprecation window. Keep the old key emitting for one release cycle while boards migrate, then remove it on a dated ticket.

Run identity keys need the same discipline. Mixing pipeline IDs with agent hostnames mid-funnel is a common way to invent phantom drop-offs.

A one-page schema charter beats a forty-page wiki nobody opens. Owners, naming pattern, and change process — that is enough to start.