Claims manifest
Evidence map for high-stakes Veto documentation claims.
This manifest is the review gate for hosted documentation claims. Any claim about SDK/API behavior, receipts, security, dependency boundaries, release provenance, or performance must map to code, tests, release state, and an owner before the docs present it as generally available.
The machine-readable source for CI is apps/docs/claims-manifest.json. The repository hygiene check fails when implemented/scoped claims do not point at local code and tests, or when hosted docs reintroduce stale receipt fields, unshipped CLI/Python receipt helpers, unsupported Merkle anchoring claims, or overbroad financial-grade language.
Status meanings:
Implemented: code and tests exist on the released branch.Pending PR: code exists in review but the docs must not imply general availability.Planned: strategy only; do not present as product behavior.Scoped: true only within the explicit limits in the Evidence column.
| Claim | Docs surfaces | Status | Evidence | Owner |
|---|---|---|---|---|
POST /v1/validate records a decision and returns a receipt summary. | API reference: Validate, Receipts | Implemented | apps/server/src/routes/validate.ts; apps/server/src/services/receipts.ts; apps/server/src/routes/__tests__/validate.test.ts; apps/server/src/routes/__tests__/validate-sqlite-selfhost.test.ts | Platform |
GET /v1/decisions/:id/receipt returns the canonical veto.receipt/1 payload for authorized callers. | API reference: Decisions, Receipts | Implemented | apps/server/src/routes/decisions.ts; apps/server/src/routes/__tests__/decisions.test.ts; OpenAPI receipt tests | Platform |
GET /v1/receipts/export streams receipt payloads as NDJSON with pagination. | API reference: Receipts; guide: Verify decision receipts | Implemented | apps/server/src/routes/receipts.ts; apps/server/src/routes/__tests__/receipts.test.ts; SQLite self-host export tests | Platform |
| Offline receipt verification detects malformed payloads, broken hash links, timestamp regressions, and invalid protocol shape. | API reference: Receipts; guide: Verify decision receipts | Scoped | packages/receipt-protocol/src/receipt.ts; packages/receipt-protocol/src/validate.ts; packages/receipt-protocol/test/receipt.test.ts. Current verifier checks root continuity; full block-root recomputation is not yet a hosted-docs claim. | SDK |
| Platform receipt appends are serialized per org/project chain and reject forks under concurrency. | Receipts API, Decision receipts concept | Pending PR | Storage append hardening must include Postgres transaction lock, SQLite transaction, Convex CAS mutation, and concurrency tests before this becomes an Implemented claim. | Platform |
| Python SDK exposes validation outcomes and receipt verification helpers. | SDK: Python, CLI | Pending PR | SDK helper work is in review and must not be presented as generally available in hosted docs until the SDK PR lands and package docs are updated. | SDK |
| The Python base package has dependency-zero local enforcement. | SDK: Python, Security/dependency pages | Planned | Not implemented. Do not claim until local enforcement routes through the Rust trust kernel and optional extras split YAML/HTTP/Pydantic/CLI deps out of the base path. | SDK |
| The TypeScript local enforcement path executes no third-party runtime code. | SDK: TypeScript, Security/dependency pages | Planned | Not implemented. Do not claim until dependency-zone gates and kernel wrapper PRs land. | SDK |
| Release artifacts use trusted publishing/OIDC provenance and no long-lived publish tokens. | Security, installation, release notes, DPA template notes | Planned | Not implemented. Do not claim until npm/PyPI trusted publishing or equivalent attestation checks are enforced in CI. | Release |
| Veto Cloud is the enterprise control plane, not the local trust root. | Architecture, local evaluation, financial-agent trust model | Scoped | Local/self-host flows must remain usable without Veto Cloud. Docs may describe cloud rollout/audit/retention features, but not as required for local enforcement. | Platform |
When a docs PR adds a new high-stakes claim, update this table in the same PR. When a code PR graduates a Pending PR or Planned row, update the status only after the linked tests pass on the target branch.