ViewSpec Proof Bundle

Read the first proof before trusting the artifact.

Run viewspec prove --out .viewspec-proof for the starter proof, then open .viewspec-proof/PROOF.md. To prove an authored brief, run viewspec prove --intent viewspec.intent.json --target react-tailwind-tsx --install --out .viewspec-proof --json. Use proof_report.json for automation and support_bundle.json for redacted failure triage.

ViewSpec proof bundles are local source artifact and provenance proof by default. For react-tailwind-tsx, they become a bounded React/Vite/Tailwind reference-host proof only when host verification actually passes.

PROOF.md PASSED

Status: PASSED
Target: html-tailwind
Proof level: source_artifact
Claim: Source artifact integrity and provenance proof

Inputs And Outputs
- Intent path: .viewspec-proof/viewspec.intent.json
- Artifact path: .viewspec-proof/artifact/index.html
- JSON report path: .viewspec-proof/proof_report.json
- Support bundle path: .viewspec-proof/support_bundle.json

Hashes
- Artifact SHA-256: 64 hex chars
- Manifest SHA-256: 64 hex chars

Manifest Summary
- Emitter: html_tailwind
- Aesthetic style delta: changed_tokens 13, categories 8, declarations 28

Checks
- compile: passed
- artifact_check: passed
- proof_summary: written

What To Check

1. Status

Start with pass or fail.

A failed proof is still useful because it records stable error codes, fixes, and the path that was safe to write.

2. Level

Read the proof level.

source_artifact means checked files and hashes. react_tailwind_reference_host means the bounded host verifier passed.

3. Hashes

Compare what was checked.

Artifact, manifest, diagnostics, and report hashes let a reviewer detect stale files or unreviewed generated output.

4. Summary

Read compact manifest facts.

The manifest summary records emitter, node count, root aesthetic profile, compact style-delta counts, and checked layout columns/spans when present.

5. Errors

Fix the first code.

Use the validation repair_checklist, regenerate the full IntentBundle, and rerun viewspec prove. Share support_bundle.json before full local reports.

Human entrypoint

`PROOF.md`

Use this file for review. It summarizes status, proof level, target, inputs, outputs, hashes, manifest summary, compact style-delta counts, checks, host verification status, network policy, timings, and fixes.

cat .viewspec-proof/PROOF.md

Machine contract

`proof_report.json`

Use this file for CI and agents. It is the stable JSON contract with schema version, checks, paths, hashes, host report, assertion_requirements such as style_assertion_count, errors, metadata, and timings.

jq .ok .viewspec-proof/proof_report.json

Support triage

`support_bundle.json`

Use this file first when debugging a failed proof. It is capped at 16KB and omits raw intent, design, artifact, diagnostics, absolute paths, environment variables, credentials, and telemetry.

jq .errors .viewspec-proof/support_bundle.json

What It Does Not Claim

ViewSpec prove is not pixel-perfect visual regression, accessibility certification, arbitrary host-app certification, or hosted compiler publish automation.

For arbitrary React applications, routers, state managers, Tailwind customizations, browser matrices, zoom behavior, and accessibility audits, add host-specific tests outside the proof bundle.

Repo guide LLM summary