#1431 removed the agent-completion/truth-gate machinery but left four documents pointing at it as though it were live. The machinery is gone from main as of 8cd4a10; the instructions to use it are not.
One of these is a standing operating procedure, not a retrospective, which is what makes this worth a ticket rather than a drive-by edit.
Current state on main (8cd4a10)
| File |
Line |
Problem |
.jules/agent_orchestration_sop.md |
65 |
Lists "the truth gate reports the real remaining blockers" as a verification gate every agent must satisfy before advancing any PR. Standing instruction to wait on a signal that no longer exists. |
MERGE_POLICY.md |
164 |
Cites .github/workflows/agent-completion-enforcement.yml in the present tense as a file that "documents" its own failure mode. That file was deleted by #1431. |
docs/runbook/pr-remediation-report-2026-08-04.md |
124–127 |
Tells maintainers to "Either restore the publishing App or drop the gate from required checks." Neither is actionable; there is no gate left to drop and no trust path to restore (all three allowlists were empty by construction). |
docs/pr-remediation/2026-07-31-run.md |
74–79, 90–95 |
Staged next-command asks a human to "provide the truth-gate's historical provenance disposition"; a maintainer note recommends investigating the faulting workflow. |
Why the SOP one matters most
The two dated reports are retrospectives — a reader discounts them by filename. .jules/agent_orchestration_sop.md is a standing SOP consulted before advancing work, so it would tell every future agent to block on a check that cannot report. That is the same class of defect MERGE_POLICY.md's own demotion rule exists to catch: guidance that looks like enforcement but cannot be satisfied.
Acceptance criteria
.jules/agent_orchestration_sop.md no longer instructs agents to wait on the truth gate; the bullet points at the checks that actually validate (PR Governance / Canonical issue and evidence).MERGE_POLICY.md:164 no longer refers to a deleted file in the present tense.- Both dated reports carry a "historical as of <date>" marker, and their imperative recommendations about the gate are past-tensed or struck. Their observations are left intact — they are an accurate record of the queue on their run dates and should not be rewritten.
- A repo-wide
grep over *.md for truth.gate, Agent completion enforcement, and agent-lock surfaces no remaining present-tense operational guidance.
Out of scope
#1431 removed the
agent-completion/truth-gatemachinery but left four documents pointing at it as though it were live. The machinery is gone frommainas of8cd4a10; the instructions to use it are not.One of these is a standing operating procedure, not a retrospective, which is what makes this worth a ticket rather than a drive-by edit.
Current state on
main(8cd4a10).jules/agent_orchestration_sop.mdMERGE_POLICY.md.github/workflows/agent-completion-enforcement.ymlin the present tense as a file that "documents" its own failure mode. That file was deleted by #1431.docs/runbook/pr-remediation-report-2026-08-04.mddocs/pr-remediation/2026-07-31-run.mdWhy the SOP one matters most
The two dated reports are retrospectives — a reader discounts them by filename.
.jules/agent_orchestration_sop.mdis a standing SOP consulted before advancing work, so it would tell every future agent to block on a check that cannot report. That is the same class of defectMERGE_POLICY.md's own demotion rule exists to catch: guidance that looks like enforcement but cannot be satisfied.Acceptance criteria
.jules/agent_orchestration_sop.mdno longer instructs agents to wait on the truth gate; the bullet points at the checks that actually validate (PR Governance/Canonical issue and evidence).MERGE_POLICY.md:164no longer refers to a deleted file in the present tense.grepover*.mdfortruth.gate,Agent completion enforcement, andagent-locksurfaces no remaining present-tense operational guidance.Out of scope
PR Governance, which is distinct frompr-governance.yml's validating job (Canonical issue and evidence). Whether branch protection binds the intended one is a separate configuration question needing admin scope — see the discussion on docs: stop directing agents to the truth gate #1431 retired #1434.