Evidence Submission to I-CIL

Evidence Envelope & Verification Standard

Version

1.0

Status

Locked

Applies To

I-CIL v1.x

Last Updated

2026-02-01

1. Purpose of Evidence Submission

Evidence is required to support score-affecting signals. I-CIL does not accept raw files as evidence; instead, evidence is submitted as a structured Evidence Envelope.

  • Evidence is auditable
  • Evidence is tamper-evident
  • Evidence is reproducible
  • I-CIL does not store raw artifacts
  • Disputes are resolved deterministically

Evidence is a declaration of facts, not a document upload.

2. Evidence Principles

  1. Evidence ≠ File – Evidence is structured context, not raw data.
  2. Hash the Context – What, why, when, and by whom are hashed.
  3. Platform Accountability – Platforms attest under license.
  4. Replayability – Evidence must be reproducible byte-for-byte.

3. Evidence Lifecycle

1

Collect

Platform collects raw artifacts.

2

Construct

Platform constructs Evidence Envelope.

3

Canonicalize

Envelope is canonicalized.

4

Hash

Canonical envelope is hashed.

5

Submit

Hash is submitted with signal.

6

Sign

Platform signs the submission.

Hash mismatch during dispute invalidates the evidence.

4. Evidence Envelope Declaration

Envelope Metadata

Version
1.0
Evidence ID
platform-generated reference

Submitted By (Platform Attestation)

Platform ID
UUID
Legal Entity Name
Entity Name

This identifies the legally accountable submitting entity.


Related Entities

I-CIL ID
0x...
Platform Influencer ID
Internal ID
Campaign ID
Optional

Signal Context

Signal Code
CODE
Severity
LOW / MEDIUM / HIGH
Reported At
ISO-8601 UTC

Evidence Artifact (Repeatable)

Artifact Type
DOCUMENT / SYSTEM_LOG / MEDIA
Description
Brief description
Content Hash
SHA-256 of raw artifact
Content Format
PDF / CSV / MP4

Attestation

Statement
"I certify this evidence is accurate..."
Attested By
Authorized Representative

False attestation may impact platform credibility and license status.

5. Canonicalization Requirements

  • UTF-8 encoding only
  • JSON keys sorted lexicographically
  • No insignificant whitespace
  • ISO-8601 timestamps with Z suffix
  • Explicit null for unused optional fields
  • Version field required
  • Arrays preserve order
  • No additional fields allowed

Canonicalization rules are versioned and immutable.

6. Evidence Hashing Rule

The entire canonical Evidence Envelope JSON is hashed. Raw artifacts are never hashed alone.

SHA-256(canonical_evidence_envelope_json)

7. Dispute Verification

During a dispute, the platform must reproduce:

  1. Identical Evidence Envelope
  2. Identical artifact hashes

Hash Match

Evidence Valid

Hash Mismatch

Evidence Invalid

Invalid evidence affects platform credibility automatically.

8. Security & Privacy Commitments

  • No PII stored in envelope
  • No raw artifacts stored by I-CIL
  • Evidence retention is platform responsibility
  • Hashes are irreversible but auditable

9. Non-Compliance Consequences

  • Signal rejection
  • Platform confidence reduction
  • License suspension for repeated violations

“The Evidence Envelope standard ensures that all score-affecting claims in I-CIL are context-aware, tamper-evident, replayable, and platform-accountable.”