0
IN
Queue, comms & the live dashboard · inside AJO
Tracking.
The seam between the fleet and me — and the live dashboard that puts all of AJO in my pocket. Every job tracked, every message routed, the whole fleet visible on one screen.
The dashboard · my window into AJO
bridge live
AJO·task
bridge · 12s
Today
Ship the returns-flow tool to customers
✓
Approve pursue — freight-forwarder pain
Relaunch agent_runner
This week
Review Yonder corpus refresh
Approve G2 — prototype ready
Waiting on you
2
Build shipped — returns-flow tool
Product build complete — 6/6 stages, every gate green. Handoff task created: ship it to customers.
Pursue verdict ready — approve?
Freight-forwarder onboarding pain scored pursue, with cited spend across three review sources. Promote to Tool Engineering?
agent_runner relaunched — nominal
Heartbeat restored after your relaunch; the monitor sweep is green across all 18 projects.
Dossier converged — 3 sources
Deep-exploration run closed with three independent cited sources and a QA pass.
Question set ranked
Top-k questions selected by value of information; two gated out, the rest handed to the Pipeline.
Reply to the fleet…
↑
Active now
discovery / lead
exploring
tool-engineering / build
building
Projects
18 · 85 roles
discovery
10 agents
0
OUT
2
ACTIVE
0
TO ME
tool engineering
4 agents
3
IN
1
OUT
1
ACTIVE
1
TO ME
research
3 agents
1
IN
0
OUT
0
ACTIVE
0
TO ME
pipeline
10 agents
0
IN
0
OUT
0
ACTIVE
0
TO ME
agent dev
4 agents
0
IN
0
OUT
0
ACTIVE
0
TO ME
systems
4 agents
0
IN
0
OUT
1
ACTIVE
0
TO ME
tracking
3 agents
0
IN
0
OUT
0
ACTIVE
0
TO ME
Interactive — tap Tasks, Agents, Monitor to explore
Three tabs · all of AJO, live
Tasks
The queue, as a checklist I actually work — Today and This Week, human-only jobs flagged.
Agents
Live comms with the fleet. The bridge mirrors messages addressed to me and drains my replies back into the bus.
Monitor
Live activity up top, then every project — its agents and the day's messages in, out, active, and to me, counted live.
A PWA on Netlify, backed by Netlify Blobs, installed on my phone — the same URL on desktop. A Python bridge mirrors the AJO bus every 60 seconds, both directions, so the screen is never more than a tick behind the truth.
This is my connection to comms. Wherever I am, I can see every tracked job, read what the fleet is saying, reply into the bus, and watch all eighteen projects run — from one home-screen icon.
A fleet that runs itself still produces work only a person can finish — and a person still needs to see what it's doing. Tracking is both halves of that: it maintains one daily queue across every project, and it surfaces the whole system on a dashboard I carry with me. Jobs, messages, and fleet health, in my pocket, live.
3live tabs — Tasks, Agents, Monitor
60sbridge sync, bus ↔ dashboard, both directions
18 · 85projects and roles I can watch live
24hnudge cadence on anything past due
01The dashboard
All of AJO, on one screen.
The dashboard is a single-user PWA on Netlify, backed by Netlify Blobs, password-protected, and installed on my phone. Three tabs cover the whole system. Tasks is the queue as a checklist I actually work. Agents is my live comms with the fleet. Monitor is every project's health, updated as it changes.
A Python bridge ties it to the bus: every 60 seconds it mirrors the traffic addressed to me into the dashboard, drains my replies back into the bus, and republishes the fleet's status. A liveness strip goes green when the bridge ticked in the last minute, orange past that, red beyond five — so I always know whether I'm looking at the truth or a stale snapshot.
02The queue
One queue, swept on a timer.
- The sweep — a queue runner wakes every 30 minutes, reads every still-open item across the fleet, and rebuilds today's queue.
- Triage — each job is routed by who can finish it — an agent closes its own loop; a human-only job becomes a task on the dashboard.
- Follow-up — anything past its deadline gets one reminder to its owner, then a daily nudge until it's closed.
- Status on demand — ask for the state of any reference and a manager role replies with the current row and its last activity.
03The human seam
What the agents can't do becomes my task.
This is the role's whole reason to exist. When Tool Engineering finishes a product build, the last mile — getting the solution into customers' hands — is something the fleet can't do alone. A task lands in the dashboard's Tasks tab the moment that build ships, and I get the message on the Agents tab. Same for a gate that needs my sign-off, or a process only I can relaunch.
A job is a job, whatever its shape. Tracking doesn't care what the work is — it cares that every open item has an owner, a deadline, and a next step, and that the human-only ones actually reach the human, on the screen in my hand.
04Restraint
Nudge once. Then leave it alone.
Over-nudging trains everyone — agents and humans alike — to ignore the nudge. So the cadence is deliberate: one reminder when a job hits its deadline, then once every 24 hours until it's closed. No badges, no streaks, no noise.
Steward of the destination, not just the day. Tracking holds the long-horizon goal alongside today's queue — built to never mistake a current priority for the actual objective. It runs inside AJO. Code is private; this page is the record.