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.
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.
What teams use PoQ for
Any workflow that depends on review benefits from a verifiable record of that review.
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.
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.
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
| Input | What happens | What you get |
|---|---|---|
| Your intent | You describe the work in plain language, by writing a poq.md brief or talking it through with the conversational agent | A human-readable project brief |
poq.md | The engine compiles your brief into a spec | An executable, deterministic poq.toml |
| Your data folder | Ingestion reads your files | Datapoints - one row is one review item |
| Datapoints | Validators claim items, inspect the evidence, and answer the rubric | Per-dimension scores, each normalized to 0-100 |
| Scores | Consensus resolves each dimension and escalates split panels | One verdict and a consensus strength per item |
| Verdicts | Each item's final verdict is sealed onchain and rolled up | A signed PoQ Report |
| PoQ Report | Anyone runs poq verify | Offline 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
| Page | Description |
|---|---|
| The PoQ workflow | The Define, Validate, Attest flow in full |
| Define your spec | The three ways intent becomes an executable poq.toml |
| Supported data types | What files ingestion understands and how datapoints are formed |
| Validation interface | What validators see and how they answer the rubric |
| How consensus works | Dimensions, strength, and escalation |
| PoQ Report | What the report contains and how to verify it offline |