cep-capsules / README.md
CroviaTrust
Update README.md
f482149 verified
# CROVIA – CEP Capsules (`crovia_cep_capsule.v1`)
This dataset contains **CROVIA CEP Capsules**: compact, hash-addressable
evidence blocks produced by the **C-Line** (Crovia Core Line) for each
training/attribution period.
A CEP capsule links together:
- royalty receipts (`royalty_receipt.v1`)
- payouts (`payouts.v1`)
- hash-chain proofs
- C-Line configuration
- trust & concentration metrics
- AI Act Annex IV evidence pointers
Each capsule is **independent**, **offline-verifiable**, and uniquely identified
by a fingerprint such as:
CEP-YYYYMM-XXXXXX
yaml
Copia codice
---
## 📦 Current capsules
- **`CEP-2511-K4I7X2`** – demo run for period **2025-11**
(4 providers, 200 receipts, €1M budget, Gini ≈ 0.16, data health = A)
---
## 🔍 Verify locally with `cep`
You can verify any capsule with the Crovia CEP CLI:
```bash
# local dev mode (inside crovia-cep repo)
pip install -e .
cep CEP-2511-K4I7X2
Expected output:
```
```bash
arduino
Copia codice
cep crovia CEP-2511-K4I7X2 VERIFIED
model crovia-llm-demo
period 2025-11
providers 4 receipts 200 gini 0.16
health A AI Act Annex IV ready
This confirms:
```
the capsule file was successfully fetched
its structure matches crovia_cep_capsule.v1
all referenced hashes and metrics are consistent
🧬 How to publish a new capsule (for future periods)
For any period YYYY-MM, generate:
Receipts NDJSON (royalty_receipt.v1)
Payout NDJSON (payouts.v1)
Hash-chain proof file
C-Line summary metrics
A capsule file in this dataset:
pgsql
Copia codice
CEP-YYYYMM-XXXXXX.json
After pushing it here, verification becomes universal:
```bash
Copia codice
cep CEP-YYYYMM-XXXXXX
```
📄 License
Apache-2.0
---
license: apache-2.0
---