Operators | Acropolis Ops

Live systems

Agent rosterChecking

Syncing…

InfrastructureChecking

Syncing…

ServicesChecking

Syncing…

Task boardChecking

Syncing…

Gateway & agentsChecking

Syncing…

Gateway controlChecking

Syncing…

Scheduled jobsChecking

Syncing…

Cron timelineChecking

Syncing…

Command Vespera owns scope, routing, integration, and final acceptance

Build Lane Grok-4.3 (grok-builder) executes bounded implementation slices

Verify Lane Codex (GPT-5.5) uses the-verifier-agent: atomic claims, read-only, exact Report

Final Reese receives verified result or escalation

JSOC command structure

Vespera routes. Specialists execute. Proof returns to command.

Reese owns intent. Vespera owns command routing and acceptance. Agent lanes stay bounded, RipperDoc supplies observability, and verification closes the loop before delivery.

Command cards 10

Review-gated 6

Tool scopes 26

Interactive command map

Authenticated API · redacted static UI

Operating doctrine

JSOC routes by risk, proof, and domain.

ScopeReese states intent. Vespera turns it into a bounded mission packet.

RouteVespera chooses direct action, Codex/Claude build, Pi client ops, Athena cyber, Ares health, Titan markets, or RipperDoc proof.

ExecuteSpecialists work inside their lane. No agent self-finalizes material work.

ChallengeJanus and Verifier pressure-test assumptions, evidence, and downstream outcome.

RecoverRipperDoc watches live health, triggers Trauma Team recovery, and returns proof to Vespera.

AcceptVespera finalizes. Reese approves high-risk, public, account, money, health, or sensitive gates.

RipperDoc / Trauma Team

Live health, proof, and recovery posture.

RipperDoc should become the recovery layer: watch the environment, wake machines, prove failures, capture RCA, and feed Vespera clean evidence instead of noise.

Power posture Not wired

Power-recovery posture is unverified: there is no live probe for Wake-on-LAN or boot-after-outage yet, so RipperDoc cannot claim it is recoverable until a real check reports in.

Mission Control API Awaiting auth

Authenticated API, host health, uptime, memory, and disk proof.

Authenticate to load live proof.

Pi / local model runtime Awaiting auth

Qwen proxy, raw model health, service state, and event-log proof.

Authenticate to load live proof.

Athena security posture Awaiting auth

Auth gates, reverse proxy policy, and self-check evidence.

Authenticate to load live proof.

Power recovery Awaiting auth

Wake-on-LAN configured and BIOS power-restore posture tracked for RipperDoc.

Authenticate to load live proof.

Trauma Team workflow

RipperDoc should work like an incident medic.

01 Triage

Detect outage, classify blast radius, identify which host/service/path is failing.

02 Stabilize

Restore the fastest safe path: wake host, restart service, fail over, or isolate the bad component.

03 Recover

Confirm the real downstream service is back, not just that a command exited cleanly.

04 Prevent

Capture RCA, add probe coverage, tighten alert thresholds, and automate the next safe fix.

Recommended expansion

What RipperDoc can do next.

Wake-on-LAN recovery button with explicit confirmation and audit log.
Power outage proof: last boot time, unexpected reboot detection, UPS/router reachability, and recovery timeline.
Synthetic checks for Mission Control login, API auth gate, Qwen proxy, and critical dashboards.
Service watchdogs that restart known-safe daemons and report the before/after evidence.
Disk, memory, GPU, model-server, and certificate-expiry thresholds with alert routing.
Backup proof: latest backup age, restore-test receipts, and failed backup escalation.
Network path map: LAN, Tailscale, public reverse proxy, DNS, and router reachability without exposing addresses.
Incident packets for Vespera: what failed, what changed, likely root cause, evidence, and next action.

Grok builds. Codex verifies. Vespera integrates.

Vespera routes. Specialists execute. Proof returns to command.

JSOC routes by risk, proof, and domain.

Live health, proof, and recovery posture.

RipperDoc should work like an incident medic.

What RipperDoc can do next.

Start the room. Watch the turns.

Speaker turns.