Name: truth-verify
Author: zowskyy

Prompt file imported from zowskyy/frontier-syntax (.cursor/commands/truth-verify.md). Copyright stays with the author.

/truth-verify

Run the Frontier verification pipeline (engine v3.0).

Usage

/truth-verify [--quick] [--ci] [--full] [--phases=phase1,phase2]

What it does

Python engine — unified orchestration instead of shell phases
Property-based tests — parser never panics, deterministic parse/hash
Incremental cache — .verification_cache/ skips unchanged phases
Parallel execution — independent phases run concurrently
Optional Docker sandbox — host vs container hash comparison when Docker is available
Mandatory Coq in CI — --ci fails if coqc or proofs are missing
Differential checks — fuzzing, sample hash parity, WASM artifact presence

Examples

/truth-verify --quick
/truth-verify --ci
/truth-verify --phases=fuzz,compare

Equivalent command

./build_truth.sh --quick
python3 -m verification.engine --quick

Outputs

verification/reports/ — environment, emulation, comparison, final report
proof/certificates/ — signed JSON certificate + SHA-256 sidecar
truth_certificate_*.txt — human-readable certificate
.verification_cache/ — incremental phase cache

Troubleshooting

Re-run a single phase:

python3 -m verification.engine --phases=fuzz --no-cache

Install truth-verify and it becomes one more candidate the router can pick - when it fits.

A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.

{ "prompt": "# /truth-verify\n\nRun the Frontier verification pipeline (engine v3.0).\n\n## Usage\n\n```\n/truth-verify [--quick] [--ci] [--full] [--phases=phase1,phase2]\n```\n\n## What it does\n\n1. **Python engine** — unified orchestration instead of shell phases\n2. **Property-based tests** — parser never panics, deterministic parse/hash\n3. **Incremental cache** — `.verification_cache/` skips unchanged phases\n4. **Parallel execution** — independent phases run concurrently\n5. **Optional Docker sandbox** — host vs container hash comparison when Docker is available\n6. **Mandatory Coq in CI** — `--ci` fails if `coqc` or proofs are missing\n7. **Differential checks** — fuzzing, sample hash parity, WASM artifact presence\n\n## Examples\n\n```\n/truth-verify --quick\n/truth-verify --ci\n/truth-verify --phases=fuzz,compare\n```\n\n## Equivalent command\n\n```bash\n./build_truth.sh --quick\npython3 -m verification.engine --quick\n```\n\n## Outputs\n\n- `verification/reports/` — environment, emulation, comparison, final report\n- `proof/certificates/` — signed JSON certificate + SHA-256 sidecar\n- `truth_certificate_*.txt` — human-readable certificate\n- `.verification_cache/` — incremental phase cache\n\n## Troubleshooting\n\nRe-run a single phase:\n\n```bash\npython3 -m verification.engine --phases=fuzz --no-cache\n```", "variables": [], "notes": "Run the Frontier verification pipeline (engine v3.0).", "metadata": { "source": { "provider": "github-cursor-commands", "repository": "https://github.com/zowskyy/frontier-syntax", "path": ".cursor/commands/truth-verify.md", "ref": "bebd75ddbb95515e807e45e83e8eceabba25365b", "url": "https://github.com/zowskyy/frontier-syntax/blob/bebd75ddbb95515e807e45e83e8eceabba25365b/.cursor/commands/truth-verify.md", "key": "zowskyy/frontier-syntax/.cursor/commands/truth-verify.md" } } }

truth-verify

About

/truth-verify

Usage

What it does

Examples

Equivalent command

Outputs

Troubleshooting

Install truth-verify and it becomes one more candidate the router can pick - when it fits.

Use it

Manifest

Reviews