Canon Incident

• incident context and scope when the user wants a more precise handoff; otherwise none required for support-state guidance

Preflight Profile

• Optional taxonomy confirmation: canon inspect modes
• If incident context is provided, use it only to choose the nearest honest alternative.
• Do not start a Canon run.

Canon Command Contract

• Support-state only.
• Explain that Canon models incident as a typed mode and keeps it discoverable.
• Explain that Canon does not yet deliver incident-specific execution, escalation, and evidence end to end.
• If the request has stabilized into bounded live-codebase change work, direct the user to $canon-brownfield.
• If the incident is still too ambiguous to bound safely, direct the user to $canon-requirements.

Expected Output Shape

• explicit modeled-only notice
• what Canon knows today about incident mode
• what is missing before incident becomes runnable end to end
• nearest honest alternative

Failure Handling Guidance

• If canon is missing, show the supported install path from README.
• Never emit fabricated Canon run output, approval state, or evidence bundle.

Next-Step Guidance

• Use $canon-brownfield when the incident requires bounded live-codebase change planning.
• Use $canon-requirements when the incident first needs bounded problem framing.

Related Skills

• $canon-brownfield
• $canon-requirements