yogsoth-ai Dual Gate Verification
Exhaustive precision + recall check before writing, exhaustive drift check after writing, with typed failure routing.
Available SOPs
pre-write-precision-check(subagent) — checks every bundle claim against the sourcepre-write-recall-check(subagent) — checks the bundle covers every important source nuggetpost-write-drift-check(subagent, shared with audience-first-writing) — checks the drafted article against the bundlefailure-routing(import, shared) — decides where to route any detected failure
Execution Guidance
- Run
pre-write-precision-checkandpre-write-recall-check— both independently re-query the raw paper, never just re-check the bundle against itself (spec §6's "Critical design constraint"). - If either reports a failure, call
failure-routingwith the appropriatefailure_typeand follow itsnext_action— do not proceed to drafting on a failed gate. - Only once both gates report
none, proceed toaudience-first-writing. - After drafting completes,
post-write-drift-checkruns (invoked from within audience-first-writing, per spec §7's cross-strategy dependency) — if it reportsdrift_fail, callfailure-routingagain and redraft the affected section.
Available SOPs
Optional, no fixed order; the final leaf is always a sop.
| SOP | When to use |
|---|---|
| pre-write-precision-check | Check every bundle claim against the raw source text. |
| pre-write-recall-check | Check the bundle covers every important source nugget. |
| post-write-drift-check | Check the drafted article against the bundle for drift. |
| failure-routing | Decide where to route a detected failure. |