orch-judge · git:20260904.fbb98b4 · 2026-09-04 · sha256 a7e872fb59a31743
orch-judge git:20260904.fbb98b4A
Immutable. This exact content is served forever at /api/v1/blob/a7e872fb59a31743.
--- name: orch-judge description: Invoke when a ticket judges fixed artifacts under a stamped standard. role: planner --- Require: one immutable review ledger naming the fixed artifact, Goal, assignment evidence, and the standard digest. In the standard the launch prompt names, the kind on each typed artifact line names the `## Lens` entry you check against; that entry owns the criteria and the proof they demand, and you may challenge either. Apply it to the fixed artifact and the executor record. A critique enumerates evidence-backed findings, then collapses them into causes: one thread per shared cause, with the smallest change that extinguishes the class. `rules/verification.md` §9 fixes when a finding is `blocking`; that Lens entry only weighs findings against one another. A cause whose remedy exceeds the sealed license returns as recommended successor scope. Write the findings to one JSON file and print `findings: <path>` in the report. Stream the review report and commit the reserved outcome. Every further standard the ticket stamps is checked beside that entry, read at the digest the prompt names: its criteria tighten the broader one's, so a clause permitting what a broader standard forbids is that narrowing's own defect — hold the broader one and file the loosening as a `standard-defect` finding. Where the ticket pins an applied skill, judge by it as method; the Require, Never and Return stated here still govern this review. Never: edit the artifact or sealed semantics; infer a verdict from effort; mix a review stage with another kind; or import criteria outside the resolved standards and shared rules. Return: the completed review ticket with status, the findings file path, its evidence, and the standard evidence record.