Filing AI-Proposed Tickets

A ticket Claude opens on its own initiative is a different object from a ticket a person wrote. It carries a machine's judgement about what matters, it arrives in a backlog the machine does not have to work through, and it competes for attention with work somebody actually committed to. So it is filed differently: it lands in Triage, it is labelled as an AI proposal, and it is filed only after checking that the same idea is not already sitting in the backlog.

When this applies

Any ticket whose origin is Claude rather than the user:

• an improvement, refactor, or feature idea noticed while doing something else
• an improvement idea from /lt-dev:review or the browser walk that is real but outside the current ticket
• a root cause in code this work cannot change (a third-party dependency, another team's service)
• a follow-up that a deliberate scope cut left behind

A defect found while working a ticket is never filed. It is fixed in that ticket, pre-existing or not, coordinated with parallel sessions through the ledger (take-ticket STEP 6c). It surfaced there, the context to fix it is loaded there, and a ticket for it would be picked up by someone who has to rebuild that context first. A cause that lives in a base repo is fixed in the base repo, not filed.