tribunalsolid

# tribunal The deepest, most expensive review codeArbiter offers — convened rarely, on demand, never as a gate. Selected by a deliberate request for a deep codebase audit, including `$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. ## Entry boundaries A direct audit request is sufficient routing intent; do not ask the user to repeat a command. An explanation-only question does not start an audit. Ordinary diff review, periodic checkpoints and a single-feature threat model retain their separate owners. Cost acknowledgment, issue filing and telemetry authorization remain separate below. `[scope-path]` limits the audit to that subtree (default: repository root). Evaluate applicability across the full roster; skip a lens only when its concern is absent and record the launched/skipped set. A smaller scope does not require irrelevant lenses. `--tag <label>` supplies the optional freeform run label governed by the telemetry card; it is not authorization to transmit anything. ## 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>/.