Tickets — issues (I-NNN, I = Issue)

A lightweight queue for technical issues spotted in the app / real transaction data, kept separate from the T-NNN task board. The convention + escalation rule live in AGENTS.md → "Tickets".

• One file per ticket: I-NNN.md. Frontmatter: tid, title, status, source (the tx / place it was found), area, created, updated, and task: T-NNN once escalated.
• status: open · investigating · escalated · fixed · closed · wontfix.
• A structural / infra ticket also gets a T-NNN task (deliberate work); cross-link both ways. A one-off data fix can stay ticket-only.

Next free ticket UID

I-038

Why this exists (decision)

• ✅ Attestation (EOP Local Assistance): read AGENTS.md before adding this board structure.
• Proposed + approved by: the owner, 2026-06-21.
• Rationale: tx / app issues are reactive, symptom-level observations — a different animal from planned T-NNN work — so they get a lightweight ticket queue (I-NNN, I = Issue); when one turns out to be structural, a T-NNN task is created on top so the task board stays the canonical record for deliberate work.
• Evidence — owner, 2026-06-21 (verbatim):

  "treat tx issues as some sort of ticket system, while if the tx issue gets into some sort of structural issue (infrastructure), then on top of the tx issue and it's UID, a T-xxx task should also be created."

"I-xxx was strictly referred to naming transaction related issue (as a ticket created, cos I stands for issue)."