Knowledge check

Check your knowledge

Choose an answer to see why it is right or wrong.

JavaScript is off, so every explanation is shown at once.

1. 01A Request always carries exactly one stage. What moves it from one stage to the next?

   • Each stage produces an artifact and passes a gate; the stage auto-advances when its automated checks are green, and a human is pulled in only on an exception.Correct. Stages auto-advance on green checks - schema and typed validation, policy-as-code, security clear, and a green eval gate for behavior changes. The human is an exception handler, not a checkpoint at every boundary.
   • A human must sign off at every one of the seven stage boundaries before it can advance.Incorrect. The human gate is an exception handler, not a routine checkpoint. Stages auto-advance when their gate checks pass; a human is summoned only on a failure, a novel or low-confidence case, detected drift, or an always-human transition.
   • The agent decides on its own authority and writes the new stage directly to the protected Request record.Incorrect. No agent mutates protected state. A transition is proposed through advance_stage and only happens when the stage's gate is satisfied; a failed gate returns the Request to the prior stage.

2. 02The lifecycle exposes exactly two write tools, request_intake and advance_stage. What does propose-only mean for them?

   • They open a GitHub issue or PR and stage a draft Request node; they never mutate protected state, merge, apply, or release.Correct. Both write tools only open an issue/PR and stage a draft node. The consequential action - merge, apply, release - is always held for a human gate.
   • They apply the change directly once the agent is confident enough, skipping review.Incorrect. Propose-only means the opposite: they never apply, and confidence does not authorize mutation. Every consequential action waits for a human.
   • advance_stage may merge a PR to a protected branch as soon as the DoD score reaches 100%.Incorrect. A green DoD is the machine gate, but merging is a human CODEOWNER action. An agent proposes; a human enacts.

3. 03A Request advances from review to done only when which condition holds?

   • DoD == 100% (no failing item, every applicable item passing or validly waived) AND a CODEOWNER approves.Correct. The DoD is the machine gate and the CODEOWNER approval is a separate human gate; both are required, which is separation of duties in action.
   • All twelve Core checklist items are waived with a recorded reason and approver.Incorrect. Core items cannot be waived at all - only conditional items can, and even then a waiver needs both an approver and a reason.
   • The automated DoD score reaches 100%, which by itself moves the Request to done.Incorrect. A 100% DoD is necessary but not sufficient. The separate CODEOWNER human approval - and the recorded completion evidence - are also required.

4. 04You pushed a branch, the tests are green, and get_dod reports every applicable item passing. Is the Request done?

   • Not yet. Done also requires the CODEOWNER's approval and the completion evidence recorded; until then it is worked on, not done.Correct. get_dod returns done only when no item fails, every applicable item passes or is validly waived, and codeownerApproval.approved is true - with the completion-evidence token written to Core.
   • Yes - a green automated DoD score is the definition of done.Incorrect. The machine gate is only half. The human CODEOWNER gate and the recorded evidence are also required before a Request reaches done.
   • Yes, as long as the agent marks it done with advance_stage.Incorrect. advance_stage is propose-only; it cannot enact the final transition on its own authority. The human gate still holds.