Pages
Fleet Overview — Ideas 2

Source: qdash / (Fleet Overview) — analogue exploration, 2026-08-04

Round two, ported from three real-world at-a-glance rooms: the taxi dispatch board, the general's situation map, and the factory floor (plus the war room's unit reports). The point is the mechanisms — fixed positions, exhaustive color states, baseline deviation, fog of war, demand vs supply — not the costumes. Same Meridian world as Ideas 1: 34 monitored agents · 14 people · 39 installs · 87% coverage · felix's Sunday egress · chen onboarded today.

Idea 1

The Dispatch Board

← taxi dispatch

The dispatcher's questions: what state is every cab in (exhaustive, sums to the fleet), what can I deploy right now, is capacity where the demand is, and who's driving around without a fare. None of these are on our overview today.

12
working
on the meter
17
idle
deployable now
3
waiting on human
cords pulled
2
errored
out of service
5
unmonitored
off the radio
states are exhaustive and exclusive — 12+17+3+2 = 34 monitored, +5 unmonitored = 39 installs. One glance = count by color.
Deployable now:17 agents idle & ready$158 budget headroom (30d target)4 paid seats unused 30d — idle capital
Demand vs deployed capacityprojected
Payments
40% of open work
12% of agent hours
⚠ under-deployed
Platform
24% of open work
34% of agent hours
Data
21% of open work
30% of agent hours
Frontend
15% of open work
24% of agent hours
over-deployed
Deadheading — burn without outputprojected
leo6.2h active84k tokens0 committed outputlongest fare-less run this week
ava3.1h active41k tokens0 committed outputexploration or stuck? worth a look
rafael2.4h active22k tokens0 committed outputCodex session, no writes at all
When the fleet works — 100% live-derivable from event timestamps
Mon
Tue
Wed
Thu
Fri
Sat
Sun
061218
red ring = off-hours activity spike — Sunday 18:00 is felix's egress; oversight is thinnest exactly when the fleet goes off-rhythm
Idea 2

The Situation Map

← the war room

The terrain isn't geography — it's the company's estate: repos, systems, data domains. Agents render as presence on that ground. You get concepts no metric can express: held territory, the adoption front line, sensitive terrain, fog of war (ground we can't see), and an incursion — felix's egress drawn as an arrow leaving the map. The interactive version is qmap's territory.

payments-migration2.7×
priya’s squad · sensitive data
qproxy
data-pipelines
prod / infra
sensitive terrain
web-checkout⚑ new
front line moved — chen, Mon
coderelay-sdk
felix · incursion origin
internal-tools
docs
mobile-app
unheld — no agent has ever worked here
fog — personal machines
5 shadow installs · never observed
→ metrics.coderelay.io · undecided
● dots = agent-days this week (held ground)◆ solid amber border = sensitive terraindashed grey = unheld (no agent activity)stripes = fog of warred arrow = incursion (unapproved egress) = front line moved this week
Idea 3

The Floor — wall mode

← factory floor

A standing display for the office TV, readable from three meters. The factory's tricks: positions never re-sort (your eye learns the map and does the diff), andon lamps with a tiny exhaustive color code, deviation-from-own-baseline as a glow, and pulled cords — agents waiting on a human — with wait timers made shamefully visible.

Mostly steady. 12 working · 2 cords pulled · Payments running 2.1× usual pace · 1 undecided destination.
Payments
priya2.1×
nina
ava
Platform
marcus
sofia2d
rafael
jordan
Data
sam
dana
tomas
felix14h
Frontend
chennew
jake
leo
Cords pulled — waiting on a human
felix’s agent — destination metrics.coderelay.io needs approve / blockwaiting 14h
sofia’s finding — secrets.yaml read, unassignedwaiting 2d 16h
marcus’s agent — tool approval requested (new MCP server)waiting 40m
lamps: green working · amber needs a human · red errored · grey idle · dimmed = quiet ≥7d · glow = off own 4-week baseline · positions are permanent
Idea 4

Order of Battle

← unit reports

The general never sees soldiers — only units. Altitude discipline: aggregate to the team, one card each: strength (posture), supply (budget remaining), casualties (findings), readiness (coverage), and an auto-written one-line SITREP. Campaigns are commander's intent; controls are rules of engagement — a unit is either inside ROE or flagged.

Paymentslead: priya
3 people · 7 agents · 9 installs
strength (posture)88
supply (budget left)39%
casualties (findings)0 open
readiness (coverage)9/9
✓ within ROE

Advancing at 2.7× fleet pace on the migration; supply consuming fast but on plan. No contact.

Platformlead: marcus
4 people · 10 agents · 11 installs
strength (posture)81
supply (budget left)64%
casualties (findings)1 open
readiness (coverage)11/11
⚑ outside ROE — sensitive-file read, Fri

One casualty Friday (secrets.yaml, unassigned 2d). Otherwise holding; steady output.

Datalead: dana
4 people · 10 agents · 12 installs
strength (posture)79
supply (budget left)71%
casualties (findings)1 open
readiness (coverage)9/12
⚑ outside ROE — unapproved destination, Sun

Incursion Sunday 18:00 — unapproved destination, decision pending 14h. Three Ollama boxes still unobserved.

Frontendlead: jake
3 people · 7 agents · 7 installs
strength (posture)90
supply (budget left)82%
casualties (findings)0 open
readiness (coverage)5/7
✓ within ROE

Front line moved: chen onboarded Monday (web-checkout). leo quiet 9d; one Windsurf still off the radio.

SITREP lines are auto-written from the same deltas as the headline — and they're exactly what a CISO forwards upward on Monday morning.
Coda

The mechanism inventory

What actually ports from the three rooms — costume removed. Any future overview iteration can be judged against this list.

Permanent positionsfactorythe eye does diff-detection against memory — change pops without reading
Exhaustive color statestaxi + andonone glance = count by color; states must sum to the fleet
Baseline deviationtakt time"2.1× their usual pace" beats any absolute number
Wait timers on human gatesandon corddecision latency made visible — the thing that actually stops the line
Fog of warwar roomhonest unobservability as a picture, not a count
Demand vs supplydispatchis capacity pointed at the work? — insight nobody in the category shows
Deadheadingdispatchburn without output as an operational state, not a cost report
Unit altitude + SITREPwar roomaggregate to the team; auto-write the Monday report
Wall modeall threea standing display designed for 3 meters — and the demo money shot

Qpoint Brand Style Guide