# Evidence Graph

**Author:** Ciprian Ștefan Pleșca  
**Status:** Academic assurance case for CIGP v0.1

The CIGP Evidence Graph connects each technical claim to its supporting artifact, the independent check that can be performed, and the limit that remains after a successful check.

```mermaid
flowchart TB
    C[Evidence-consistency claim] --> S[Commit-reveal seed]
    C --> H[Canonical hash]
    C --> G[Ed25519 signature]
    C --> L[Hash-linked ledger]
    C --> M[Merkle inclusion]
    S --> V[Independent verifier]
    H --> V
    G --> V
    L --> V
    M --> V
    V --> R[Bounded result]
```

| Claim | Check | Important limit |
| --- | --- | --- |
| A revealed server seed matches its declaration. | Recompute SHA-256 commitment. | It does not prove when the commitment was published. |
| A proof was not edited after signing. | Recompute canonical hash and verify Ed25519 signature. | A compromised key remains a residual risk. |
| Rounds preserve their stated predecessor relationship. | Verify `previous_round_hash` across the ledger. | Withheld or externally unanchored history may remain possible. |
| A batch includes a round. | Verify the Merkle path against its root. | The root must be independently published to carry external weight. |

Read the full, version-controlled [Evidence Graph](https://github.com/Ciprian-LocalPulse/CIGP-Protocol/blob/main/docs/academic/evidence-graph.md) and the [security threat model](https://github.com/Ciprian-LocalPulse/CIGP-Protocol/blob/main/docs/security/threat-model.md).