Decide where the work belongs
Map semantic consequence
For each changed field, record event type, consumer, parser result, stored state, side effect, and recovery. Separate unknown-field tolerance from missing required data. Use a bounded fixture or observed event shape behind each impact claim.
Compare compatibility paths
Assess accepting additive fields, versioned parsing, migration, quarantining unknown shapes, or requesting contract evidence. Record owners and rollback. Do not ignore a renamed field because the payload still parses. Test the selected route.
Set schema order
Queue identity, authorization, and state-changing fields first, then shared decoders and display fields. Set owner, fixture, review date, and evidence threshold. Keep one isolated event version below a broad contract rewrite when reach is unknown.
What to carry forward
Return a schema queue with field change, semantic effect, handler reach, safe containment, owner, and proof needed to reprioritize. Escalate effect-bearing changes. Keep rank provisional when version or consumer use is incomplete. Attach the affected consumer.
Technical background: GitHub documentation.
Keep the decision with the work.
Use a Work Item in Aglet to record the problem, the evidence you have, and the next decision. Add an owner and priority, then keep updates in the discussion so the next person can follow the reasoning.
Create an account See the product workflow