Investigate bug

Own the evidence between a bug report and a workable ticket. Ordinary matching requests and authorized bounded handoffs use this procedure. A complete current investigation is reused, not repeated because delivery starts. Investigation-only ends at the ticket outcome; a separate explicit investigation-and-fix request may authorize a later delivery handoff, never a fix inside this procedure.

Authority and dependencies

Read target instructions and relevant context, workflow, tracker and domain pointers. Inspection and a conversation return are the default. Confirm authority for diagnostic execution, local probes, retained artifacts and tracker effects separately; source access grants no installation, external disclosure, service startup, model calls or delegation. Protect unrelated work, partial changes, modes and links. Product repair, PRs, closure, merge and release are outside this owner.

Discover companions from the runtime/project catalog or an explicit approved location, not sibling paths. Read complete entries and conditional references; record source/revision or digest and check semantic capabilities. Ambiguous or incompatible candidates block the affected route; recheck changed source, task or authority. Missing helpers permit supported findings/drafts, not installation or a legacy diagnosis fallback.

• write-tickets is required for ticket preparation and publication/reconciliation: current bounded bug input, duplicate/partial-write handling, exact publication approval, native relationship/role read-back and no automatic readiness/scheduling. It owns the exact proposal, all tracker writes and graph procedure discovery. Continue through its procedure in the current context without asking the user to invoke it; publication approval is separate from following the drafting procedure. An unresolved case supplies an explicitly investigation-only draft, never a ready fix claim.
• analyze is conditional for material technical-readiness/method/check gaps; require current code/caller evidence, targeted reuse and recommendations without implementation. Direct cause inspection and a supported method recommendation need no automatic Analyze run.
• research is conditional for unresolved authoritative source/version questions; require cited findings and freshness/disclosure bounds. Reading unchanged domain definitions needs no modeling run; actual meaning/decision work uses discovered domain-modeling with its plan-only/approved gate.
• Optional delegation requires separate authorization and the discovered work-on read-only execution contract, not delivery invocation. The root reserves shared capacity, exclusive scopes, finite bounds and lineage; workers request work from the root rather than recursively spawning. Missing authority/contract blocks delegation, not direct diagnosis. No model assessment is required.

For changes or validation read validation.

1. Bound the report and reuse current evidence