tribunallisted

# tribunal The deepest, most expensive review codeArbiter offers — convened rarely, on demand, never as a gate. Routed to when the user invokes `$ca-tribunal`. Eleven specialist lenses judge the codebase; every finding persists to its own file (plus append-only triage/run logs) under a run dir that survives compaction and disconnects, so the run resumes from disk. ## Pre-flight Read these, or STOP and surface the gap — never guess a command or a path: - `<project-root>/.codearbiter/tech-stack.md` — stack, async model, concurrency primitives, test/lint/secrets commands, and, when documented, the tracker command. Stop if the test/lint/secrets commands are missing; do not guess. - `<project-root>/.codearbiter/CONTEXT.md` — the `stage:` maturity value and domain vocabulary. - `<project-root>/.codearbiter/coding-standards.md` — the conventions lenses judge against. - `<project-root>/.codearbiter/security-controls.md` — trust boundaries, approved crypto/secret stores; feeds the appsec and secrets lenses. Absent on some repos — proceed without the security lenses' control-file checks if so. - A git repository must be present. - The reference set under [routines/tribunal/references/](references) — each is cited at its phase, loaded on demand. Do not preload them. ## Phase 0 — Cost, model & resume · gate: STOP This lane is expensive. Orient and get explicit go-ahead before dispatching anything. - **Resume check.** Scan `.codearbiter/reports/` for the most recent run dir matchin