Task manifest (cwi.task-verdict/1.0)
Build a manifest without hand-writing JSON
Fill the claim, add checks row by row, then ship the manifest into the Run tab — or straight to the CLI.
Checks
What a verdict proves — and what it doesn't
- PASS proves the listed checks passed at run time. It does not prove the task was good, complete, or honest — only that its receipts checked out.
- FAIL means at least one check's observed evidence contradicted the claim. The evidence is in the record — argue with the evidence, not the badge.
- PARTIAL means something could not be verified (network error, timeout, CORS block). Unverifiable is reported as unverifiable — never rounded up to a pass.
- URL checks in the browser are subject to CORS: a site that blocks cross-origin reads will ERROR here and PASS in the CLI. The CLI is the authority for URL checks.
- File checks are sandboxed to one base directory. Paths that escape it are rejected and reported as ERROR — never silently read.
- This is heuristic triage for orchestration claims, in the spirit of the Trust Fabric: receipts over assertions, evidence over adjectives.
Check types
| type | proves |
|---|---|
url_status | a URL answers with the expected HTTP status |
url_contains | a fetched page body matches a pattern |
file_exists | a file exists under the base dir (CLI) |
file_sha256 | a file's bytes match an expected hash (CLI) |
file_regex | a file's content matches a pattern (CLI) |
json_field | a JSON field equals an expected value (CLI) |
count_match | a pattern occurs at least N times in a file (CLI) |
Schemas: cwi.task-verdict/1.0 ·
cwi.task-verdict-record/1.0 ·
engine verdict.js (zero-dependency UMD) ·
repo