role-manager-execution

Ticket-first governance requires creating or linking a GitHub issue and drafting a formal handoff document with objectives, constraints, and acceptance criteria before any commits begin. This ensures scope is defined up front to prevent misalignment and rework.

Binary acceptance criteria are defined as testable conditions that result in a deterministic pass or fail verification. You must capture these measurable criteria alongside objectives and non-objectives in a formal handoff document before work starts.

Document a formal handoff by drafting a MANAGER_HANDOFF that explicitly captures the objective, non-objectives, repository policy constraints, and binary acceptance criteria. This validates required fields and ensures the process is documented before any commits.

Scope definition should include the objective, non-objectives, policy constraints, and binary acceptance criteria. Capturing these elements up front establishes verification gates and reduces misalignment and rework during implementation.

Yes, the governance process applies to both creating new and linking existing GitHub issues. You must reference the linked issue in all changes and ensure the formal handoff document captures required fields before implementation begins.

Verification gates are applied after defining binary acceptance criteria and before implementation begins. You select and apply the required tests and checks to enforce quality and ensure deterministic verification of the defined scope.