# CAIN-42 Verification Package — Intellectual Property & Licensing

**Goal: let an outside reviewer independently verify CAIN-42's claims without disclosing proprietary implementation
source.**

## Published (for verification)
- Sanitized quorum-certificate samples, replica public keys, membership.
- The standalone offline verifier source (`offline_verifier/verify_qc.py`) and negative fixtures.
- Manifests, reconciliations, formal-model figures, soak results, and documentation.

## Withheld (proprietary / sensitive)
- The CAIN-42 implementation source (`cain/*`, `cain45/*`, `cain_microservices/*`) is **not published**. The QC bundle
  records the source as a commit-hash commitment, not source.
- Private signing keys, cluster shared secrets, tenant data, and internal infrastructure credentials.

## What a reviewer CAN reproduce without source
- Verify every Ed25519 signature over the exact canonical signed bytes.
- Enforce the quorum rule (2f+1 of n) and reject every negative fixture.
- Recompute Merkle inclusion/consistency proofs from published log data.
- Reconcile published test and model-checking counts against the raw artifacts.
- Re-run TLC against the bounded specifications.

## What a reviewer CANNOT reproduce without source (and why it matters)
- Running the proprietary PBFT engine itself, re-deriving private keys, or executing the hosted enforcement path.
- Therefore this package supports **verification of published claims and evidence**, not independent re-execution of the
  closed-source engine. Claims that would require source access are marked accordingly.

## Licensing
- The offline verifier is published for verification use; redistribution requires operator permission.
- Evidence artifacts are operator-published evidence, copyright CAIN-42 / FIRME AI.
- Contact the operator for source access, additional evidence, or a live status probe.