docs(space): rewrite README — audit-first CEP Terminal

README.md

@@ -1,56 +1,185 @@
+# CROVIA · CEP Terminal
+Public Evidence Inspector for AI Training Datasets
+
+Crovia CEP Terminal is a public, audit-first interface to inspect AI evidence capsules
+(crovia_cep_capsule.v1) published as open datasets.
+
+This Space does not simulate compliance.
+It shows exactly what exists — and what does not.
+
+---
+
+## What this Space is
+
+This is not a demo with fabricated green checks.
+
+This Space is a live evidence terminal that:
+
+- loads real CEP capsules from Hugging Face datasets
+- performs lightweight but real structural checks
+- exposes missing provenance, signatures, and hashchain anchors
+- visualizes the actual audit surface of a dataset
+
+If something is missing, Crovia shows it.
+
 ---
-title: Cep Terminal
-emoji: 💻
-colorFrom: purple
-colorTo: indigo
-sdk: gradio
-sdk_version: 6.0.2
-app_file: app.py
-pinned: false
-license: apache-2.0
-short_description: Verify Crovia CEP capsules
+
+## What this Space is NOT
+
+- Not a marketing dashboard
+- Not a compliance simulator
+- Not a “trust me” interface
+- Not a blockchain demo
+
+There are no fake receipts and no cosmetic green lights.
+
 ---
 
-# CROVIA · CEP Terminal
+## How to read the results
+
+### Trust Signal
+
+The Trust Signal (GREEN / AMBER / RED) is derived, not declared.
+
+A RED signal means:
+- missing cryptographic anchors
+- incomplete provenance
+- unverifiable payouts or receipts
+
+This is not an error.
+It is the correct audit outcome.
+
+---
+
+### Evidence Graph
+
+The graph shows what is actually bound to the capsule:
+
+- receipts
+- payouts
+- signatures
+- hashchain roots
+
+Unbound elements are shown explicitly.
+
+Nothing is hidden.
+
+---
+
+### Inspector Panel
+
+The Inspector explains why a dataset fails or passes:
 
-This Space is an **open demo Evidence Inspector** for Crovia CEP capsules (`crovia_cep_capsule.v1`).
+- missing schema
+- missing model metadata
+- missing period
+- missing signature
+- missing hashchain
 
-It does **real, lightweight verification** inside the Space:
-- parses the capsule JSON
-- runs structural checks (schema / period / required fields)
-- recomputes a **canonical SHA256 fingerprint** of the capsule
-- displays evidence nodes + anchors (hashchain / signature fields if present)
+This is meant to be readable by:
+- engineers
+- legal teams
+- auditors
+- journalists
 
-### Open Demo Mode (important)
-This Space does **not** attempt to replicate the full Crovia Core Engine.
-Deep cryptographic verification and end-to-end auditability are delegated to the **Crovia CLI**.
+---
+
+## Open Demo Mode (Important)
+
+This Hugging Face Space runs in OPEN DEMO MODE:
+
+- structural parsing
+- canonical fingerprint computation
+- evidence surface inspection
 
-**Why this matters:** Crovia is designed so anyone can verify evidence **offline** with a CLI — not inside a UI.
+Deep cryptographic verification (DSSE, full hashchain replay, payout proofs)
+is intentionally delegated to the Crovia CLI / Core Engine.
+
+This keeps the Space:
+- fast
+- transparent
+- non-deceptive
 
 ---
 
-## Try it
+## Why Crovia exists
+
+For years, the AI industry has said:
+
+“Your data was used to train the model.”
+
+Without receipts.
+Without numbers.
+Without proof.
 
-Type a CEP fingerprint (example):
-- `CEP-2511-K4I7X2`
+Crovia exists to enforce one rule:
 
-The Space fetches the capsule from:
-- dataset: `Crovia/cep-capsules`
+If an AI system makes value from data, there must be evidence.
+
+And that evidence must be:
+- inspectable
+- auditable
+- verifiable by anyone
 
 ---
 
-## Crovia CLI (canonical)
+## The uncomfortable truth
+
+Most open datasets used to train modern AI models:
 
-Use the CLI to verify bundles, hashchains, and payouts end-to-end.
+- do not expose provenance
+- do not bind payouts
+- do not anchor receipts
+- do not provide hashchains
 
-Example flow:
-- `crovia check <receipts.ndjson>`
-- `crovia pay <receipts.ndjson> --period 2025-11 --budget 1000`
-- `crovia bundle --receipts ... --payouts ...`
-- `crovia sign <bundle.json>`
-- `crovia trace <receipts.ndjson> --out proofs/hashchain.txt`
+Crovia does not hide this.
+
+Crovia makes it visible.
 
 ---
 
+## Why this Space matters
+
+This is likely the first public terminal that:
+
+- inspects real training datasets
+- shows compliance gaps in public
+- does not normalize missing evidence
+
+This Space is not here to look good.
+It is here to be correct.
+
+---
+
+## Next steps (outside this Space)
+
+To perform full verification:
+
+pip install crovia
+
+crovia explain capsule.json
+crovia trace receipts.ndjson --out proofs/hashchain.txt
+crovia verify bundle.json
+
+This Space shows what exists.
+The CLI proves what holds.
+
+---
+
+## Final note
+
+If a dataset fails here,
+it does not mean it is “bad”.
+
+It means:
+
+Evidence is missing.
+
+And missing evidence is exactly what Crovia was built to expose.
+
+Crovia.
+Evidence, not promises.
+
+
 ## License
 Apache-2.0