dos-witness-claim

Route subagent claims through independent read-backs with terminal-state checks.

18|4|Updated Jun 10, 2026

Search Tags:#git #verification #subagents #pipeline #evidence #claim validation #witness

Ready to run

npx skills add https://github.com/anthony-chaudhary/dos-kernel --skill dos-witness-claim

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: dos-witness-claim
Source: https://github.com/anthony-chaudhary/dos-kernel/tree/main/claude-plugin/skills/dos-witness-claim
Command: npx skills add https://github.com/anthony-chaudhary/dos-kernel --skill dos-witness-claim

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When multiple agents or pipeline stages report results, this Skill prevents you from treating narration as fact. It helps you verify claims against an independent read-back before folding them into a synthesis or downstream decision.

Core Features & Use Cases

Routes subagent claims through a witness step instead of trusting self-reported success.
Distinguishes confirmed, refuted, unwitnessed, and no-claim outcomes.
Fits parallel fan-outs, pipeline handoffs, and synthesis barriers where one agent’s output must be validated before another agent relies on it.

Quick Start

Use the dos-witness-claim skill to verify the subagent results from this batch and return only confirmed claims for the next stage.

Frequently Asked Questions about dos-witness-claim

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I verify subagent claims before trusting self-reported pipeline results?▼

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.

What is the best way to validate file creation claims in parallel agent fan-outs?▼

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.

Why does my synthesis pipeline fold in dead or unwitnessed agent outputs?▼

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.

Do I need git to validate pipeline handoff claims between agents?▼

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.

When should I use a witness step instead of trusting self-reported agent outcomes?▼

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.

Can I use terminal-state checks to confirm deployed rows in a multi-agent workflow?▼

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.