# CAIN-42 Independent Verification Center — Outside Auditor Guide
## Step-by-Step Runbook for Independent Evaluation, Offline Verification, and Claim Validation

**Audience:** Independent Security Researchers, External Safety Auditors, Regulatory Evaluators  
**Canonical Front Door:** `https://cainstudio.online/verification-center/`  
**Current Release Kit:** Auditor Kit 8.3.1 (`7a42d69055a059207fbdc0f0f39c713507662cf707c737e6ad578694b0f222d6`)  
**Overall Release Gate:** **BLOCKED**  

---

### 1. The Auditor's Entry Path

A visitor to `https://cainstudio.online` can find the Verification Center directly from the homepage:
1. Via the top banner link: `Auditors: verify CAIN-42 →`.
2. Via the primary announcement section: **`VERIFICATION CENTER →`** button.
3. Via the main navigation dropdown under **Proof** → **Verification Center**.

---

### 2. What Can Be Independently Verified (3-Minute Quick Run)

An auditor can verify the following on their own machine, with standard Python only, requiring **no credentials** and **no network access** after downloading:

#### Step 1: Download & Verify the Release Package
```bash
curl -fsSLO https://cainstudio.online/evidence/auditor-kit/8.3.1/cain42_verify.py
curl -fsSLO https://cainstudio.online/evidence/auditor-kit/8.3.1/cain42-auditor-kit-8.3.1.zip

python3 -I cain42_verify.py cain42-auditor-kit-8.3.1.zip \
  --trust-anchor XhK+pwJlsTymjoA8rnJBiGP344rTKK1qD5xTtbkbZlY= \
  --expect-sha256 7a42d69055a059207fbdc0f0f39c713507662cf707c737e6ad578694b0f222d6 \
  --expect-version 8.3.1 \
  --human
```
**Expected Outcome:** `VERDICT: PASS_INTEGRITY (exit 0)`.

#### Step 2: Test Tamper Detection
Modify any byte inside `cain42-auditor-kit-8.3.1.zip` or omit `--trust-anchor`:
- With tampered byte: `VERDICT: FAIL_INTEGRITY`.
- With wrong trust anchor: `VERDICT: UNTRUSTED_SIGNING_KEY`.

#### Step 3: Check Public Transparency Log (Sigstore Rekor)
```bash
curl -fsSLO https://cainstudio.online/evidence/auditor-kit/8.3.1/cain42_rekor_check.py
python3 -I cain42_rekor_check.py cain42-auditor-kit-8.3.1.zip \
  --trust-anchor XhK+pwJlsTymjoA8rnJBiGP344rTKK1qD5xTtbkbZlY=
```
**Expected Outcome:** Queries Sigstore Rekor logIndex 3220737978 directly and confirms `LOGGED_AND_CONSISTENT`.

#### Step 4: Run the Standalone IHVRK Verifier
Extract the IHVRK bundle and run zero-import verification:
```bash
cd ihvrk/evidence && python3 verify_ihvrk_evidence.py
```
**Expected Outcome:** `RESULT: PASS (9 checks, 0 failed)` across all 68 registered evidence files.

---

### 3. What CANNOT Be Verified Yet (Explicit Limitations)

Auditors must note that integrity of published evidence does **not** equal production assurance:
1. **Source Code is Private:** Outside auditors without repository access cannot inspect full implementation source.
2. **Gateway Hosted Tool Bodies are Unconfined:** Tools running inside the hosted gateway process lack Landlock/seccomp process boundaries (addressed in Evolution 4 worker design).
3. **No Hosted CI:** Because the repository has no Git remote, test passes are local host passes, not third-party CI attestations.
4. **Single Server Infrastructure:** All three domains run on one hosting provider; independent multi-region failure domains are not active.
5. **No Third-Party Audit:** All existing results were generated by CAIN development sessions; no external audit firm has reviewed the system.

---

### 4. Submitting Findings & Challenging Claims

If an auditor identifies a discrepancy, broken claim, or security flaw:
- Submit findings via `https://cainstudio.online/evidence/auditor-kit/latest/#report-finding`.
- Include exact command, environment details, hash mismatch, or stack trace.
- Findings are tracked under the public threat register.
