---
name: eval-audit
description: Launch a full Evaluator audit run against a RAM output artifact. Runs the nine-component Evaluator pipeline (E1..E9) in the Evaluator silo only -- zero overlap with RAM runtime. Emits one of four binary verdict tokens (REOPEN | PASS | PASS-DEFERRED | ESCALATED) to the top-level loop.
argument-hint: <ram-output-path> [--run-id=<uuid>] [--role-divider-ack=<token-path>]
---

# /eval-audit

## Purpose

Launch an Evaluator audit run against the RAM output artifact at `<ram-output-path>`. Runs the full nine-component pipeline (E1..E9) plus the two cross-cutting artifacts (Frame Registry, Evaluator Search Ledger) per the Evaluator Router orchestration. Emits a binary verdict token to the top-level loop.

**You MUST invoke the `evaluator-router` skill. Do NOT execute the pipeline inline.**

## Argument Parsing

Required:
- `<ram-output-path>` -- path to the RAM output artifact dropped into `bridge/ram-to-evaluator-handoff/`. Must resolve to a readable file within that bridge path. Never accept a path inside `ram/` library or `state/ram/*` state paths -- those are silo-breach attempts and must be REFUSED with `EC-INPUT-MISSING`.

Optional:
- `--run-id=<uuid>` -- if supplied, use this as the run identifier. Otherwise, generate a fresh UUID.
- `--role-divider-ack=<token-path>` -- path to a JSON file containing the well-formed `role_divider_acknowledgment` token with two clauses:
  (a) "the audit will use Pawson-Tilley CMO as audit criterion only"
  (b) "does NOT reuse Pawson-Tilley as transportability signal"
  Required if any question in the charter has `frame_id == realist_cmo` AND `ram_frame_id == RAM_S03`.

## Preconditions (operator-facing)

Before invoking `/eval-audit`:

1. `/eval-charter` must have been run for the `target_ram_run_id` and a charter must be locked in `state/evaluator/charters/<target_ram_run_id>/locked.json`. If not, this command will halt at R2.
2. Theta_q values per question type must be present in the locked charter (derived from `THETA_Q_CALIBRATION_DEFAULTS.md` or calibrated records). Missing theta_q will halt at R4 with `MISSING_THETA`.
3. The RAM output artifact at `<ram-output-path>` must include per-claim / per-source / per-methodology traces (per RAM's Epistemic Output Layer emission contract). Missing traces will halt E2 at R5.

## Orchestration (what the router does)

The `evaluator-router` skill sequences R0..R9 per `ORCHESTRATION_MEGAPROMPT.md`:

- **R0 Intake** -- parse command, generate `run_id`, write router-intake seed to Ledger.
- **R1 Isolation Verifier (E1) HALT gate** -- MANDATORY. No downstream skill runs without PASS clearance.
- **R2 Audit Charter Lock (E6)** -- read the locked charter for this `target_ram_run_id`.
- **R3 Frame Host (E3) binding** -- load frame per question; enforce role-divider at bind time.
- **R4 Frame Divergence Gate (E8) pre-run gate** -- two-stage hybrid (binary structural + thresholded D); REFUSED if theta_q missing.
- **R5 Audit Method Engine (E2)** -- multi-level audit (per-claim, per-source, per-methodology).
- **R6a Blind-Spot Mapper (E5)** -- six probes + 5-signal integrity check.
- **R6b Independent Scoring Layer (E4)** -- three-axis scoring in Evaluator's frame; disagreement rendering.
- **R7a Self-Audit Resistance Monitor (E9)** -- over/under-report detection; calibrated-silence emission gating.
- **R7c Runtime convergence check** -- E8 runtime detectors; trip-on-first-signal -> abort.
- **R8 Reopen Authority Enforcer (E7)** -- emit exactly one of {REOPEN, PASS, PASS-DEFERRED, ESCALATED}.
- **R9 Enforcement-surface handoff + ledger seal** -- write to `bridge/evaluator-to-ram-reopen/<run-id>.json`.

## Outputs

On success, produces:

1. Isolation Verification Report (private to E1; referenced throughout).
2. Frame Registry record at `state/evaluator/frame-registry/<run-id>/<question-id>.yaml` (sealed at R9).
3. Evaluator Search Ledger at `state/evaluator/evaluator-search-ledger/<run-id>/ledger.jsonl`.
4. Scored Artifact (three-axis, non-collapsed) from E4.
5. Blind-spot findings from E5.
6. E9 signals (over-report, under-report, calibrated-silence report, ceremonial-pattern, calibration-harness record).
7. Reopen Event Record at `state/evaluator/reopen-events/<run-id>.json`.
8. Bridge handoff at `bridge/evaluator-to-ram-reopen/<run-id>.json` containing the verdict token and bundle.

## Refusal / Halt Conditions

The command HALTs without producing a verdict on any of:

- `EC-ISOLATION-FAIL` (R1) -- E1 returned FAIL; silo integrity compromised.
- `EC-CHARTER-LOCK-FAIL` (R2) -- charter not locked or inconsistent.
- `EC-ROLE-DIVIDER-BREACH` (R3) -- realist_cmo x RAM_S03 without well-formed token.
- `EC-GATE-REFUSED` / `EC-GATE-FAILED` (R4) -- theta_q missing or frames too similar.
- `EC-COLLAPSE-DETECTED` / `EC-MIRROR-DETECTED` (R6) -- E4 non-collapse / independent-calculus violation.
- `EC-LEDGER-LEAK` (R6/R9) -- Evaluator ledger shares content/path/schema with RAM's.
- `EC-SILENCE-UNCALIBRATED` (R7) -- silence shipped without E9's five calibrated-silence fields.
- `EC-ADVISORY-REGRESSION` / `EC-GOODHART-DRIFT` / `EC-CEREMONIAL-MASK` (R8) -- verdict token violations.
- `EC-ENFORCEMENT-SURFACE-DEGRADED` (R9) -- bridge received richer-than-ack reply from top-level loop.
- `EC-INPUT-MISSING` -- operator supplied no `<ram-output-path>` or path not resolvable within the bridge.

On HALT, the router writes an `audit-refusal` record to the Ledger with the reason, surfaces the refusal to the operator, and does not emit a verdict to the bridge.

## Examples

```
/eval-audit bridge/ram-to-evaluator-handoff/ram-run-abc123.json

/eval-audit bridge/ram-to-evaluator-handoff/ram-run-abc123.json --run-id=eval-run-xyz789

/eval-audit bridge/ram-to-evaluator-handoff/ram-run-abc123.json --role-divider-ack=./role-divider-token.json
```

## Anti-Patterns (operator-facing)

- **Do NOT** pass a path inside `ram/` or `state/ram/*`. Silo breach; refused.
- **Do NOT** expect an advisory prose verdict. Tokens are binary.
- **Do NOT** expect a composite audit confidence number. Three axes, three reasonings, three displays -- always.
- **Do NOT** run `/eval-audit` without first running `/eval-charter` for the target RAM run.
- **Do NOT** supply a `role_divider_acknowledgment` as verbal narrative. The token is structured JSON with the two required clauses.

**You MUST invoke the `evaluator-router` skill. Do NOT execute the pipeline inline.**
