Tristan-Hauber Input: issue, P#, answered Q#, optional approved M#, authority, and optional verified issue-review receipt. The main thread owns evidence state and remote mutation.
- Verify issue/comment/parent/linked/docs fingerprints; retrieve only changed or missing material, falling back to full affected context when freshness is unknown. Revalidate findings; mark stale/already-resolved items.
- Convert answered decisions into explicit wording; never infer an unanswered semantic choice. Preserve remaining
Please answer:questions and stop before mutation. - Without exact authority, show the smallest proposal: separate
Already established:from stableM#rules and allow natural Approve/Revise/Reject/Recheck, partial approval, and replacement wording. Revalidate revisions; show material changes once more. - Record original state and create a local draft. Apply only approved rules and the smallest complete change; preserve unrelated human context and do not alter metadata fields outside authority.
- Run
$adversarial-review-loop artifact_kind=issue-draft checkpoint=save, then$issue-reviewagainst the draft using verified unchanged linked evidence. Absorb newP#; surface newQ#; stop on oscillation. - Require
CLEAN, verify/reconcile remote revision, update intended fields, verify remotely, refresh the receipt, then delete the draft.
Return UPDATED/BLOCKED | issue | resolved/stale IDs | approved M#/- | verification | review receipt | blocker/draft/-, followed by exact questions. For an orchestrator, UPDATED is an internal hand-off: re-fetch and rerun $issue-review from scratch using verified unchanged evidence, then continue. A standalone invocation may end after verification.