# Bestie Check

Quality assurance for knowledge-work deliverables: governed packs, quote-bound approval, findings, coverage, and receipts.

Bestie Check verifies a knowledge-work deliverable against admitted principle packs. It records what it checked, what it found, and what it did not engage. It does not rewrite the deliverable, invent approval, or treat silence as clearance.

## One contract, several surfaces

Web, REST, MCP, CLI, and Office all call the same Check contract. No surface reimplements judgment. Plugins and hooks never manufacture spend approval.

- Custody first: the deliverable is uploaded or referenced as an `artifactRef`. Agents should not paste raw document bytes into transcripts.
- Quote, then quote-bound approval: a run names the pack stack, budget ceiling, tenant, and expiry. Approval binds that quote — not a bare “approve” flag.
- Run, then read: findings, a coverage register (including not-engaged), and a receipt. Authorized follow-up uses the durable `checkId`.

## What Check is for

- Governed principles: which criteria were applied, and which were not.
- Evidence and warrant: whether cited sources actually support the claims they are asked to carry.
- Assumptions: what the recommendation depends on, and whether those claims still hold.
- Argument structure: whether the deliverable’s conclusion follows from admitted material.

## What Check is not

- It is not a second editor. It does not silently rewrite the document.
- It is not a guarantee that a reader will agree. A receipt is useful only if the verification boundary is explicit.
- It is not an installer for every agent product. Public knowledge lives here; operational artifacts stay in Check custody.

## Current public boundary

Managed Check is an operator-provisioned pilot. Public routing currently uses the admitted V01 principles verifier. The accepted fourteen-verifier production graph is not registered for customer traffic. Built, accepted, and customer-reachable are different claims — we do not round them up.

> Private findings, receipts, and deliverable bytes are not published on this site. Authorized agents retrieve them through the Check API or MCP after a governed run. See [coverage and receipts](/docs/coverage-and-receipts).

## Read next

- [Principle packs](/docs/principle-packs)
- [Coverage and receipts](/docs/coverage-and-receipts)
- [Getting started for agents](/docs/agents/getting-started)