cyberneticlibrary

Verify docs match changed source code

docaudit-impact-verifyworkflowsetup L30
akira993/doc-audit-harness
What it does

Verify findings adversarially across multiple agents

Best for

Checking whether docs still match source after changes without re-reading entire files.

Inputs
  • · workflow args object
Outputs
  • · verdict object
Requires
  • · agent MCP
  • · parallel execution
  • · workflow phases
  • · mdq indexer
  • · grep
  • · Read tool
Preconditions

Workflow runtime available; agents ready; input schema valid; args provided

Failure modes

Agent timeout or refusal; schema validation fails; empty result set; dedup collision on key

Trust signals
  • · Schema validation enforced
  • · Structured phase logging
  • · Parallel agent orchestration
  • · Adversarial verification
  • · Strict schema requirements
  • · Enumerated field constraints