What is PoQ

Proof of Quality (PoQ) is a verification layer for AI work. You define quality as a rubric, a panel of independent validators scores each item against it, consensus resolves one verdict per item, and PoQ seals the rubric, outcome, and level of agreement as a permanent onchain attestation. Instead of asking anyone to trust an internal review process, PoQ records how the decision was reached — and anyone can verify that record.

PoQ sits on top of the evaluation, audit, and review workflows you already run. It doesn't replace your tools or experts; it preserves how quality was judged so the claim can travel with the work.

How PoQ works

You bring data and a quality bar. PoQ compiles it into a rubric every validator applies the same way.

Why verification matters

A score tells you what was decided, not why. As AI work moves between teams and organizations, customers, partners, auditors, and regulators inherit the conclusion — but rarely the standard, the evidence, or the level of agreement behind it. PoQ attaches that record to the claim itself, so a quality claim no longer depends on the credibility of whoever made it.

A bare score must be taken on faith. A PoQ-backed score carries its rubric, evidence, agreement, and signature — and anyone can check it.

What teams use PoQ for

Any workflow that depends on review benefits from a verifiable record of that review.

The work differs; the problem is the same. Once a review ends, its reasoning usually disappears — PoQ keeps it.

Experts, agents, and scale

Having experts review every item is the gold standard — and it is slow and expensive. PoQ makes the fast path trustworthy instead: panels mix human experts with AI agent validators, consensus resolves each item, and only split panels escalate to experts. Both kinds of validators see the same rubric and evidence and are scored the same way. The attestation is what makes this automation viable — you don't have to trust the automated review, because you can verify it.

Expert review of everything doesn't scale. Consensus panels with agent validators do — and the signed attestation is why the fast path can be trusted.

What you get

You bring intent and a folder of data. PoQ returns a signed PoQ Report: one verifiable record of what was reviewed, by whom, against what rubric, and with how much agreement.

You bring intent and data; PoQ compiles a spec, builds review items, scores them by consensus, and returns a signed PoQ Report.

That signed report is a real artifact — open the example PoQ Report to browse one now, or run poq verify against it offline.

The pipeline, step by step
InputWhat happensWhat you get
Your intentYou describe the work in plain language, by writing a poq.md brief or talking it through with the conversational agentA human-readable project brief
poq.mdThe engine compiles your brief into a specAn executable, deterministic poq.toml
Your data folderIngestion reads your filesDatapoints - one row is one review item
DatapointsValidators claim items, inspect the evidence, and answer the rubricPer-dimension scores, each normalized to 0-100
ScoresConsensus resolves each dimension and escalates split panelsOne verdict and a consensus strength per item
VerdictsEach item's final verdict is sealed onchain and rolled upA signed PoQ Report
PoQ ReportAnyone runs poq verifyOffline confirmation the report is authentic and unaltered

Quickstart

Ready to try it? The Quickstart creates your first project in the UI or via the API in a few minutes.

See also

PageDescription
The PoQ workflowThe Define, Validate, Attest flow in full
Define your specThe three ways intent becomes an executable poq.toml
Supported data typesWhat files ingestion understands and how datapoints are formed
Validation interfaceWhat validators see and how they answer the rubric
How consensus worksDimensions, strength, and escalation
PoQ ReportWhat the report contains and how to verify it offline