Top-level orchestrator CLI for the RIG Sovereign system — boot, audit, probe, recover. Exposes subsystem health, audit, and recovery tools to agent clients via MCP.
Server has 8 tools with basic descriptions and no visible input schemas in the provided code. Tool names follow verb_noun convention (probe_subsystem, get_status, list_subsystems, run_audit, smoke, results, score, request_effect), which is good. However, most descriptions are under 100 characters and lack actionable context. Only 3 tools show explicit parameter definitions (request_effect has action/target/reason with descriptions). The remaining 5 tools either have no parameters or their schemas are not visible in the provided source. Error handling is absent, no guidance on what to do if a probe fails or a subsystem is unavailable. Output schemas are not documented. This is a typical community-grade server with minimal polish.
Probe every registered subsystem and return the aggregate health snapshot.
List all registered subsystems with their declared probes and dependencies.
Probe a single RIG subsystem by name and return its health status.
Record a Gate-D request. Returns the pending request id; never executes.
Sealed proofs and result ledger entries for this repo (verified only).
Run a full audit cycle, write a JSON artifact, and return the audit report.
Deterministic RIG lattice score for this repository.
No input schemas visible for 7 of 8 tools. Only request_effect shows explicit parameter definitions (action, target, reason with descriptions). The remaining tools (probe_subsystem, get_status, list_subsystems, run_audit, smoke, results, score) have no visible schema in the provided code.
Output schemas are not documented. Tools return dicts (e.g., ProbeResult, status snapshot, audit report) but the structure of these dicts is not specified. LLMs cannot plan downstream calls without knowing what fields to expect.
No error handling or recovery guidance. If probe_subsystem fails (subsystem unavailable, network timeout), the tool returns nothing actionable. Descriptions do not explain what to do on failure or which errors are retryable.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 46 | 2026-07-28+ | v2 |
Run the deterministic local smoke test (no live network calls).
Descriptions are generic and under 100 characters. E.g., 'Probe a single RIG subsystem by name and return its health status' lacks context on when to use this vs get_status, what 'health status' means, or what happens if the subsystem is offline.
run_audit and request_effect are marked WRITE but have no confirmation or dry-run pattern. Agents could accidentally trigger audits or gate requests without explicit user approval.