メニュー
Use when routing a verification target to status-qualified owner lanes and joining native evidence receipts into a VERIFICATION-WEAVE parent receipt without promoting owner outputs.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Use when deciding whether work merits a governed multi-agent dispatch and, when it does, proposing, tension-checking, confirming, registering, running, closing, and observing that dispatch through repository-local bindings.
Use when deciding whether work merits a governed multi-agent dispatch and, when it does, proposing, tension-checking, confirming, registering, running, closing, and observing that dispatch through repository-local bindings.
The design principle behind Principle 5 (pairwise tension) of the subagents-strategy constitution. Use when designing the angle set for an n≥2 subject group (role investigate or evaluate) so the agents' micro-vectors are structurally opposed and their correlated bias cancels under composition — not merely non-overlapping. This is the design/theory layer; check-tension is the executable gate that enforces it before the human confirm.
Use when: building a compact, task-ready context pack from selector-level evidence and obligation-linked excerpts.
Route repository work through installed Arcanum capabilities and execute validated capability-bound dispatches through host-native operations.
Route repository work through installed Arcanum capabilities and execute validated capability-bound dispatches through host-native operations.
| name | verification-weaver |
| description | Use when routing a verification target to status-qualified owner lanes and joining native evidence receipts into a VERIFICATION-WEAVE parent receipt without promoting owner outputs. |
| argument-hint | <target-or-receipt> [--mode route|validate-receipt|fixture-plan|report] |
| tier | arcana |
| domain | verification-evidence-routing |
| version | 0.1.0-candidate |
| origin | created from SWU-VW-001 on 2026-06-21 |
| allowed-tools | Read, Write, Glob, Grep, Bash |
Use verification-weaver when a target needs evidence routing across testing,
UX, execution, architecture, or research lanes and the output must remain a
parent receipt instead of an owner-level promotion.
Core verb: route.
Receipt type: VERIFICATION-WEAVE.
The capability:
verification-weaver may route to these lanes:
test-derivationux-evidence-validatorexperiment-harnessarchitecture-pattern-inventoryresearch-evidence-harnessIt must not perform the owner work itself. Owner outputs stay status-qualified,
and parent receipts may use only promotion_action: none or
promotion_action: candidate-request.
Accept one bounded target or one existing receipt. A target can be:
Emit or update a VERIFICATION-WEAVE parent receipt with:
target_kind;status;promotion_action;Pass only when the target is classified, required owner evidence or explicit gaps exist, public-safety checks pass, and no parent promotion is attempted.
Flag when the route is useful but still has soft residue, such as UX human comprehension risk, architecture source incompleteness, mixed-target split needs, or research dry-run limits.
Block unsupported targets, missing oracles, hard public-safety failures, flaky evidence, adapter failures, and parent promotion attempts.
Run:
bash arcanum/arcana/verification-weaver/development/run-validation-fixtures.sh
The runner validates synthetic fixtures and runnable negative controls. Treat the runner output as candidate package evidence, not as registry promotion.