---
name: eval-charter
description: Lock or amend an audit charter for a specific RAM run. Runs Isolation Verifier (E1) pre-flight, then invokes Audit Charter Lock (E6) to validate VICTORE declarations and lock the charter. No audit runs -- this command only manages the charter envelope.
argument-hint: <charter-path> [--amend] [--target-ram-run-id=<id>]
---

# /eval-charter

## Purpose

Lock an audit charter (first lock OR amendment). Runs E1 pre-flight, then invokes E6 to validate the VICTORE declaration, cross-section consistency, and RAM-content-leak check. Does NOT run an audit -- that is `/eval-audit`. The locked charter is the precondition for any subsequent `/eval-audit` against the same `target_ram_run_id`.

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

## Argument Parsing

Required:
- `<charter-path>` -- path to the proposed charter envelope (JSON conforming to `templates/charter-envelope-schema.json`). Must be inside the Evaluator silo or operator workspace -- NEVER inside `ram/` or `state/ram/*`.

Optional:
- `--amend` -- flag the operation as a charter amendment. Triggers E6's re-baseline ceremony: prior findings tagged `pre-amendment-v{N-1}`; in-progress operations restart under the new charter; no aggregation across versions.
- `--target-ram-run-id=<id>` -- the RAM run this charter governs. Required for amendments. On initial lock, may be derived from the charter envelope.

## Required Charter Sections

Per E6 Phase A, the proposed charter MUST include:

1. **Audit question(s)** -- bounded set the audit will answer.
2. **Target RAM artifacts** -- exhaustive list (by artifact-type and identifier).
3. **Evidence classes admissible** -- explicit list.
4. **Stakeholders** -- parties whose questions are answered AND parties whose evidence is consumed.
5. **Audit mode per question** -- `artifact-check` (default) or `replication`.
6. **VICTORE declaration** -- all seven dimensions (volitions, implementation, contexts, time, outcomes, rivalry, emergence). Empty / TBD / placeholder fails.
7. **Amendment policy** -- who may request, default re-baseline rule.
8. **Theta_q table** -- per question class, from calibrated records or conservative defaults (per `THETA_Q_CALIBRATION_DEFAULTS.md`).
9. **Frame assignment per question** -- `frame_id` + `ram_frame_id`. Role-divider trigger if realist_cmo x RAM_S03.
10. **Reopen thresholds** -- reopen ceiling N, dwell-time floor, composite-trigger spec, escalation receiver ID, materiality threshold, disagreement threshold, noise floor.

## Orchestration (what the router does)

- **R0 Intake** -- parse command, verify `<charter-path>` resolves within allowed paths (NEVER inside RAM silo).
- **R1 Isolation Verifier (E1) HALT gate** -- MANDATORY even for charter events, because E6's ram-content-leak detection depends on E1's inter-library overlap check.
- **R2 Audit Charter Lock (E6)** -- invoke `audit-charter-lock` with `{proposed_charter}` (first lock) or `{amendment-request, target-ram-run-id}` (amendment).
- E6 runs Phase A (initial) or Phase D (amendment). Router propagates `charter-locked` or `charter-amended` record.
- No R3..R9; audit pipeline does not start.

## Outputs

On success:

1. `charter-locked` record at `state/evaluator/charters/<target_ram_run_id>/locked.json` with:
   - `charter_version` (monotonic integer)
   - `content_hash`
   - `locked_at` (ISO-8601)
   - Full charter envelope
   - `isolation_verifier_clearance_id`
2. Ledger entry `charter-locked` / `charter-amended` in the Evaluator Search Ledger.
3. On amendment: diff record against prior version; re-baseline tags applied to prior findings.

## Refusal / Halt Conditions

- `EC-ISOLATION-FAIL` -- E1 pre-flight failed.
- `charter-intake-incomplete` -- missing envelope fields.
- `charter-intake-inconsistent` -- audit question implies artifacts / evidence / stakeholders not in charter.
- `victore-dimension-missing` -- any of the seven dimensions empty / placeholder / TBD.
- `ram-charter-content-leaked-into-audit-charter` -- HARD ERROR. Re-triggers E1 Phase-5 isolation reopen review. Audit charter REJECTED. Operator must redraft without reading RAM's charter.
- `amendment-frequency-exceeded` -- more than one amendment per audit cycle (default ceiling) escalates to operator with a recommendation for charter redesign.
- `stakeholder-added-midaudit` / `evidence-class-shift-without-reauthorization` -- if an amendment attempts either without the non-overridable operator acknowledgement, ESCALATE.

## Examples

```
/eval-charter ./charters/proposed-audit-abc.json

/eval-charter ./charters/proposed-audit-abc.json --target-ram-run-id=ram-run-abc123

/eval-charter ./charters/amendment-audit-abc-v2.json --amend --target-ram-run-id=ram-run-abc123
```

## Anti-Patterns (operator-facing)

- **Do NOT** pass a charter path that reads content from `ram/` or `state/ram/*`. HARD ERROR.
- **Do NOT** omit VICTORE dimensions and plan to "fill in later." Empty / TBD fails lock.
- **Do NOT** rewrite the charter to match observed audit work. Charter precedes work.
- **Do NOT** amend more than once per audit cycle without a charter redesign.
- **Do NOT** attempt to add a stakeholder mid-audit through `--amend` without the non-overridable operator acknowledgement. Signals 3 and 4 are NON-OVERRIDABLE.

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