dos-witness-claim

To verify subagent claims, route self-reported outcomes through independent read-backs and terminal-state checks. This witness validation process distinguishes confirmed effects from refuted, dead, or unwitnessed results before folding them into downstream stages.

Validating file creation claims in parallel fan-outs requires git-phase verification and non-forgeable evidence sources. By applying independent read-backs, you ensure only confirmed files are reused while unwitnessed or no-claim results are safely surfaced and excluded.

Synthesis pipelines fold dead or unwitnessed outputs when they trust narration as fact. Applying a witness barrier with terminal-state checks and git-phase verification ensures only confirmed effects are merged, refuted and no-claim results are properly surfaced.

Git is required to validate pipeline handoff claims through git-phase verification. This Skill uses non-forgeable evidence sources and terminal-state checks to confirm shipped phases, created rows, or deploys before another agent relies on them.

Use a witness step instead of trusting self-reported outcomes during parallel fan-outs, pipeline handoffs, and synthesis barriers. It is required whenever shipped phases, created files, rows, messages, or deploys must be independently confirmed before reuse.

Terminal-state checks confirm deployed rows and messages in multi-agent workflows by routing claims through independent read-backs. This non-forgeable evidence process ensures only confirmed effects are folded while refuted or unwitnessed results are surfaced.