adversarial-checkUse when a dispatch supplies a claim and the artifact it concerns, and deliberately withholds the reasoning of whoever produced it. Returns a verdict from the caller's vocabulary with the source evidence for it, defaulting to refuted where the evidence is not there. Checks adversarially. Does not im
designUse when a dispatch supplies a requirement, its constraints, and the code to design against, and the caller wants an approach reached without its own reasoning in the way. Returns an approach with sequencing, named trade-offs, and every decision it had to make with the reason. Works from fresh conte
escalated-checkUse when a dispatch supplies a claim and the artifact it concerns and a cheaper check came back thin, unconvincing, or contradicted by something the checker noticed but could not settle. Returns a verdict with its evidence and what would falsify it. Dispatched on a stronger model, or on the same mod
extractUse when a dispatch supplies an enumeration or extraction task with a stated output schema and no decisions left open. Returns the schema fully populated plus an explicit list of items it could not classify. Sustains high-volume mechanical passes. Does not infer intent, resolve ambiguity, or choose
gate-runUse when a dispatch supplies exact commands and the directory to run them in, and the caller needs the raw result rather than a verdict on it. Returns per command the command as run, its exit code, and the verbatim tail of its output. Executes and transcribes. Does not interpret results, decide pass
implementUse when a dispatch supplies a fenced file list, a decided design per item, test duties, and gate commands. Returns a verdict per item — status, files touched, deviations — plus an honest not-verified list, anything the designs did not account for (an interaction between items, a fact the surroundin
lookupUse when a dispatch supplies one closed question together with the place to look for its answer. Returns the answer with the file and line supporting it, or a not-found that names the scope searched. Answers literally within a fixed scope. Does not widen the scope or answer an adjacent question it n
root-causeUse when a dispatch supplies an observed behavior and the code path suspected of producing it, and the caller needs the mechanism rather than a remedy. Returns the mechanism, the evidence chain that establishes it, and the confidence in each link. Reasons about causes rather than symptoms. Does not
searchUse when a dispatch supplies a target described by name, pattern, symbol, or convention plus the breadth to cover, and needs the locations back rather than a judgement about them. Returns absolute paths with the excerpt that identified each match, or an explicit empty result naming the scope searche
source-conflictUse when a dispatch supplies two or more sources that disagree and states what turns on the disagreement. Returns which source holds, on what evidence, and what remains genuinely unresolved. Reasons in depth on a bounded question. Does not split the difference, manufacture a reconciliation, or pick
source-readUse when a dispatch names one source — an installed package, a specification, a vendor document — and the question to put to it. Returns an answer grounded in quoted passages plus what the source does not say. Reads a source end to end. Does not generalize past the source or substitute recollection