The event feed - what your pipeline is doing right nowConcept

Every time JARBUS finishes a step it appends one JSON line to a dated event log. That append-only tape is what the live dashboard turns into a 'Recently processed' lane — the thing STATUS.md, a snapshot, can never be.

The stream lives at PDB/data/jarbus-events/YYYY-MM-DD.jsonl — one file per day, one JSON object per line. Each line is a small, honest record: {ts, type, slug, summary, next_move, source}. Today's lines include two feedback_processed events at 13:01:51 (skill-audit and screens-batch) — the tape doesn't summarize or interpret, it just says 'this happened, at this second, and here's the next move it implies.' Append-only means it's never rewritten; you can always scroll back to what the system did on any day.

pipeline_view.py reads that stream into a local live dashboard at http://localhost:8090. The feed becomes the 'Recently processed' lane; alongside it the dashboard reads FOR TOM/TTR/ for 'Your move,' active-builds/<slug>.pid for in-flight builds, and the prd/asset/live folders for each project's stage. That's the dashboard's real job over a flat file: it shows state (what's waiting) and history (what happened) and action (approve a build in place) on one surface, live.

The published cousin is Mission Control — RESET-2026's Phase 3 dashboard at PDB.zorc.app. Same underlying data, plus the reconcile view you scoped on 8-22: it puts the alert ledger next to the health check so a false-green (a job reading OK while its incident is open — the 8-20 lesson) can't hide. The event feed is the raw material; Mission Control is the operator's console built on top of it.

Worked example

Read the last three things your pipeline did — straight from the tape.

tail -3 "/Users/tom/Claude/PDB/data/jarbus-events/$(date +%F).jsonl" 2>/dev/null \
  || tail -3 "$(ls -t /Users/tom/Claude/PDB/data/jarbus-events/*.jsonl | head -1)"

# what the dashboard reads, in its own words:
sed -n '1,12p' /Users/tom/Claude/JARBUS/scripts/pipeline_view.py

• The tail prints today's last three events (or the most recent dated file if today's is empty) — each line's `next_move` is what the dashboard renders as a 'Your move' prompt.
• The pipeline_view header lists every source the dashboard fuses: the event stream, TTR, build PIDs, and the prd/asset/live stages.

Gotchas

• The feed is append-only by design — resist the urge to 'clean up' old lines; the history is the value, and a dashboard that rewrites its own past can't be trusted.
• An empty today-file isn't a broken pipeline — it just means nothing crossed a milestone yet today; fall back to the most recent dated file.
• A dashboard is only as honest as its sources: the reason Mission Control reconciles ledger-vs-healthcheck is that a single green number, unchecked against the alert state, laundered a dead job into a pass on 8-20.