Glossary
| Term | Meaning |
|---|---|
| Acceptance | A decision that the specified criteria are met; human criteria remain with the operator. |
| Advisory review | Independent evidence and findings that inform the primary's acceptance decision. |
| Brief | The written intent, design context, rationale and scope. |
| Candidate | The exact implementation or full-tree bytes to which evidence is bound. |
| Delivery | A verified commit and fast-forward push after the required executable checks. |
| Gate | An executable check that must pass before the governed transition. |
| Handoff gate | The full check on the tree after all tracked close bookkeeping. |
| Methodology work | Changes to the development method, policies, skills or supporting machinery. |
| Operator | The person who owns decisions and product judgment for this checkout. |
| Park | A truthful hold stating the blocker and the evidence or decision needed to resume. |
| Phase | A coherent outcome with explicit dependencies, scope and acceptance. |
| Pin | An exact version or dated external reference deliberately selected for use. |
| Policy | A binding repository rule. |
| Primary | The instance accountable for orchestration and decisions in its selected authority mode. |
| Proof estate | The recipient-local inventory of executable checks and their governance evidence. |
| Skill | A discoverable procedure with instructions and any supporting resources. |
The methodology brief in the source repository owns the complete canonical glossary. Use its terms when editing plans and policies.