akarachen Eric Grill
- Ask one question at a time, include your recommended answer, and wait. Inspect the code when it can answer the question.
- Resolve domain terms and boundaries before API, persistence, UI, rollout, or test details.
- Challenge ambiguous terms and contradictions with the actual code. Propose a precise canonical term.
- Probe the plan with concrete cases: duplicate events, partial failure, retries, cancellation, missing state, permission denial, out-of-order updates, and cross-context ownership.