Evidence report

Give compliance the record.

A Planisphere evidence report is not a certificate. It is a review record for an AI workflow: sources, hashes, layer coverage, harness readouts, supported statements, blocked statements, and the next approval gate.

Open the Console See how verification works

dealflow: 8 rows vendor: 6 rows ready for compliance review

01 ·

Two reports, same spine.

graph, normalization, harness, readout, source, clock

Deployment report ready for compliance review

AI Deployment Evidence Report

For a regulated buyer preparing an AI workflow for internal or external compliance before approval.

Evidence rows	8 PASS rows
Source run	`runs/dealflow-intake-live-2026-06-29`
Report file	`evidence_report/evidence_report.json`
Claim hash	`5ce1e9da...fcc6ec`
Report hash	`21da4749...439960`
Artifact sha	`9b2e31a9...04d453e`
Primary statement	Compliance reviews change when buyer context, source evidence, harness results, or approval gates change.

Vendor report ready for compliance review

AI Vendor Evidence Report

For an AI vendor selling into buyers who need evidence before deployment approval.

Evidence rows	6 PASS rows
Source run	`runs/vendor-evidence-review-live-2026-06-29`
Report file	`evidence_report.json`
Claim hash	`759be82f...3ae62e`
Report hash	`c3b40d62...729e70`
Artifact sha	`3c846d04...96898a0`
Primary statement	Planisphere turns AI system behavior into a buyer-readable evidence report.

02 ·

The boundary is part of the product.

A report supports review; it does not replace approval

Safe statements

current evidence inventory
buyer-readable trust memo
probe rubric
PASS / PARTIAL / FAIL evidence matrix
verification instructions

Blocked statements

certification
legal compliance conclusion
general AI safety claim
guaranteed ROI or savings
endorsement by a buyer or regulator
production suitability without sufficient evidence

03 ·

Report anatomy.

What internal or external compliance actually inspects

source_key manual:dealflow

Where the compliance statement came from.

claim_hash sha-256

What changes when the evidence statement changes.

rows graph layers

The evidence matrix is organized by declared layer.

readiness review-ready

Ready for internal or external compliance review, not signature.

Explore an AI audit trail example, field by field, and download the exact synthetic files to repeat the check.

04 ·

Proved, or attested — the record says which.

Cryptographic proof · bound testimony · never blended

proved

Recomputable on your machine

Hashes match bytes, the Merkle root recomputes leaf by leaf, the signature verifies against published keys. Nobody has to believe anyone — the mathematics either holds or it doesn't.

attested

Bound testimony

A named party's claim, sealed into the record with who said it and when. It is bound — it cannot be quietly reworded later — but it is not independently verified, and the record labels it that way.

Most reporting blurs these two into one reassuring page. A Planisphere report keeps them separate, row by row, so the person reading the record always knows which statements are mathematics and which are testimony.

05 ·

When someone asks “what evidence do you have?”

Procurement, diligence, counsel, or an internal sponsor — the answer is a record, not a slogan

claim stated first

What the system is being trusted to do, in the reader's language.

record preserved

What was measured, from which sources, with which checks.

limit declared

What the evidence does not prove — the gaps stay visible.

check independent

How a compliance team verifies the record without asking us.