Operational Topology

Mission Control Infrastructure

Mission Control is Reese's central operational hub. Ripperdoc is the monitoring and control-plane node that exposes reachability into the Windows host, the WSL runtime, and the observability stack.

Tailnet naming

ripperdoc + ripperdoc-wsl

Canonical names are available for host and WSL separation.

Live remote paths

SSH + Kuma + Grafana + windows_exporter

Tailnet-connected operators can open the published dashboards directly and fall back to SSH tunnels for local-only services.

Dashboard publishing

Tailscale Serve active

Uptime Kuma and Grafana are already published through ripperdoc-wsl for authenticated tailnet access.

▾

Checking endpoints...

Uptime Kuma

Remote status board

Online

https://ripperdoc-wsl.taild94591.ts.net

Tailnet only

Fastest operator view for service reachability and current monitor state.

Open

Grafana

Dashboards and deep observability

Online

https://ripperdoc-wsl.taild94591.ts.net:8443

Tailnet only

Primary analysis surface for monitoring dashboards published from ripperdoc-wsl.

Open

windows_exporter

Windows host metrics endpoint

Online

http://100.70.98.16:9182/metrics

Direct over Tailscale

Raw host metrics from the Windows control-plane node.

Open

Prometheus

Metrics storage and scrape engine

Limited

localhost:9090

SSH tunnel

Use when you need direct query and scrape-debug visibility beyond Grafana.

Alertmanager

Alert routing and grouping

Limited

localhost:9093

SSH tunnel

Local-only alert routing surface on ripperdoc-wsl.

Blackbox Exporter

Synthetic probes

Limited

localhost:9115

SSH tunnel

Probe and debug surface for synthetic HTTP/TCP checks.

Alloy / Control Service

Collection and control-plane plumbing

Limited

localhost:3001

SSH tunnel

Internal collection plane on ripperdoc-wsl, kept separate from operator dashboards.

Central operational hub

nyxserver-hosted app · Astro static site

Primary operator surface for JSOC workflows, status views, and future command routing. This is the place Reese should check first.

Windows control-plane entrypoint

ripperdoc · Windows over Tailscale

Remote access anchor for host-level operations and exporter visibility. Windows SSH and windows_exporter are already reachable over the tailnet.

Reachable Endpoints

Windows SSH

Online

100.70.98.16

SSH

Primary host-level remote access path over Tailscale.

windows_exporter

Online

http://100.70.98.16:9182/metrics

HTTP metrics

Live host metrics endpoint suitable for Prometheus scraping or diagnostics.

Uptime Kuma dashboard

Online

https://ripperdoc-wsl.taild94591.ts.net

HTTPS via Tailscale Serve

Tailnet-only remote status board for iPhone or any Tailscale-connected operator device.

Grafana dashboard

Online

https://ripperdoc-wsl.taild94591.ts.net:8443

HTTPS via Tailscale Serve

Tailnet-only deeper observability board exposed from ripperdoc-wsl.

WSL monitoring/runtime plane

ripperdoc-wsl · Ubuntu in WSL over Tailscale

Runs the local monitoring stack. SSH is the admin path, and tailnet-only Tailscale Serve now exposes Kuma and Grafana remotely without opening LAN-facing dashboard ports.

Reachable Endpoints

WSL SSH

Online

100.77.232.34

SSH

Direct admin path into the WSL runtime.

Local Service Bindings

Grafana

Limited

Dashboards

localhost:3000

Local bind + remote dashboard

Open Remote

Local Grafana stays bound to WSL while the operator-facing dashboard is published through Tailscale Serve.

Alloy / control service

Limited

Agent / collection plane

localhost:3001

Local to WSL only

Represents local control-plane plumbing; keep modeled separately from public endpoints.

Prometheus

Limited

Metrics storage and scrape engine

localhost:9090

Local to WSL only

Can ingest windows_exporter immediately once scrape config is wired.

Alertmanager

Limited

Alert routing

localhost:9093

Local to WSL only

Present in-stack but not externally published.

Blackbox Exporter

Limited

Synthetic checks

localhost:9115

Local to WSL only

Useful later for Mission Control health probes and remote endpoint checks.

JSOC Control Surface

Joint Special Operations Command

Multi-agent orchestration framework — Hermes as sole orchestrator, specialized agents for execution lanes

Orchestrator

Hermes

Scope → Route → Verify → Deliver

Primary

Codex

Implementation, architecture, debugging, code review

Reinforcement

Second-pass review, verification, product/UX critique, operator clarity

Specialist Agent

Ares

Health, recovery, bodybuilding, performance data

Specialist Agent

Titan

Event trading, market analysis, risk management

Specialist Agent

Athena

Blue team and red team security incident command

Specialist Agent

Apollo

Knowledge operations, research, and memory systems

Model Layer

gpt-5.4

Hermes

codex-mini-latest

Codex

gemma4-ops:26b-8k

Local (nyxserver)

qwen3.5:27b

Local (nyxserver)

Operator Workflow · Local nyxserver Instances

gemma4-ops:26b-8k

ONLINE

Local inference lane for structured ops drafting and fast local iteration.

qwen3.5:27b

ONLINE

Local reasoning lane for private analysis and secondary comparison runs.

Host: nyxserver · Runtime: llama.cpp supergemma (`127.0.0.1:9000`)

Control Plane — Ripperdoc

Monitoring, observability, and incident response — Windows host + WSL runtime

Control Plane

Ripperdoc

ripperdoc · 100.70.98.16

Windows host · SSH + windows_exporter

Runtime

Ripperdoc WSL

ripperdoc-wsl · 100.77.232.34

Ubuntu WSL · Monitoring stack host

Observability Stack

Prometheus

:9090

Grafana

:3000

Alloy

:3001

windows_exporter

:9182

Trauma Team

Rapid incident response crew

Hermes

Pilot

Codex

Co-Pilot

Alertmanager

Security

Uptime Kuma

Security

Blackbox Exporter

Lead EMT

Detect → Dispatch → Stabilize → Remediate

Tailnet Serve Endpoints

ripperdoc-wsl.taild94591.ts.net

Uptime Kuma

ripperdoc-wsl.taild94591.ts.net:8443

Grafana

Execution Flow

Scope

Hermes defines objective + constraints

Route

Assign to right agent lane

Execute

Agent performs the work

Pi Review

Completed work routes to Pi

Hermes Final

Final acceptance and handoff

Routing Rules

Code changes → Codex first by default

Completed non-Hermes work → Pi → Hermes

Health, recovery, training → Ares

Security incidents and Agentwall oversight → Athena (Specialist)

Knowledge ops, research, and memory lanes → Apollo (Specialist)

Small/fast/single-domain → Hermes directly

Operating Principles

Hermes is the sole orchestrator and final authority

Execute directly when leverage is low — delegate when leverage is higher

Mission format: objective, constraints, expected outcome

Codex is the primary coding agent

Pi is the reinforcement/review lane — not another coding agent

No non-Hermes lane bypasses Pi before Hermes finalization

Subagents are temporary scaling units, not permanent residents

Active Hermes Profiles

Loading profiles...

Pi Review Lane

Submitted packets route through Pi before Hermes final acceptance. Returned packets go back to the owning lane. Bounded low-risk issues may be self-fixed by Pi.

SYNCING

Loading Pi review states...

Current Queue

0 OPEN

Loading Pi review queue...

Recent Outcomes

0 ITEMS

Loading Pi review history...

Waiting for metrics...