PUBLIC DOCS / MVP

Proof Foundry Docs

The first public docs match the private beta product: guided setup, governed launches, scoped connectors, Proof Credits, TaskSpecs, approvals, and ProofCards.

Concepts

A lab owns members, budgets, provider access, projects, TaskSpecs, approvals, runtime evidence, and ProofCards.

Setup

Accept a private beta invite, confirm plan and caps, choose connector posture, create the first project, then run preflight before launch.

Connectors

GitHub is app-scoped and repo-selected. Hugging Face can be connected for account-owned deployment and artifacts. Stripe handles plan and credit checkout.

BYOK

BYOK provider credentials are stored server-side with redacted hints and audit events. Hosted OpenAI and Anthropic BYOK are not part of the current default path.

Proof Credits

Proof Credits cap managed OpenRouter model calls and managed Hugging Face compute. Spend is reserved before provider calls and reconciled after usage evidence.

TaskSpecs

A TaskSpec records question, sources, repository, datasets, role plan, budgets, approvals, and verifier criteria before runtime starts.

Approvals

Risky actions wait for human approval receipts. Missing approval, budget, connector scope, or provider state blocks launch instead of pretending work is ready.

ProofCards

A ProofCard summarizes the claim, evidence support, metrics, artifacts, costs, and verifier outcome. No raw secrets or hidden reasoning belong in ProofCards.

No raw secrets

Docs, support, exports, and examples should use redacted ids and status evidence. Do not paste provider keys, invite tokens, database URLs, webhook payloads, hidden reasoning, or private dataset rows.