AND Triage

Close, wait, or send one authoritative GitHub work record to Pack. Ground the route, apply it when authorized, and leave executable package creation to and-pack.

Workflow Contract

Use and-workflow-contract before reading or writing workflow state. Read deployment-handoff.md only when the route turns on whether reviewed implementation has an authoritative Deployment disposition and, for custom, a complete Deployment Manifest. If repository setup or the contract is unavailable, route to setup-and or report the missing skill.

The workflow contract owns stage, State Reason, lifecycle, relationship, and receipt representation.

When GitHub is inaccessible, report the exact read or write blocker and identify any route that could not be written as unapplied.

Act Or Ask

Apply a clear needs-info or needs-pack route directly. Ask one focused question before mutation only when the target is ambiguous, the route itself would encode unrecorded human judgment, closure lacks authority, the duplicate or rejection target is unclear, or the write would overwrite a maintainer conclusion or create an unauthorized side effect.

When human judgment is the missing input rather than the route decision, write needs-info and ask the exact State Reason question; the route itself needs no approval.

Treat ownership, linked PRs, containment, dependencies, and prior State Reasons as route evidence, not automatic confirmation gates.