The one window you leave open to see everything your agents are doing right now — which terminals are moving, which one is
waiting on you, and what the team is building. It is a view: a fresh photograph of work that actually lives in
RoadWork and Design Hub. Editing Pulse changes nothing — to change the work you open RoadWork; to change a requirement you open Design Hub.
◉This is a view — read-only, but never a dead end. A photograph of live work: no button here starts, stops, or edits a terminal. But every card is a doorway — Act on this takes you straight to where you intervene (its RoadWork lane today; ExMan when it ships). Read-only inside, always a doorway out — Pulse itself still writes nothing.
3moving now2waiting on you1idle1no signal7terminals
Heartbeats one card per terminal · click a card for its trail · every card is a doorway — Act on this to intervene · state is glyph + word + lightness, never a color alone
Does Pulse get its own brand token, or inherit Agent Engine's?open
Cross-agent sharing needs a Security sign-off before it ships.gated
This whole page is a portable snapshot. Everything is baked into one file, so you can drop it on your iPad or keep it as a record of "here's what work looked like at 2:48pm." Push a live copy to the intranet to watch it from your phone.
◉Live on the intranet — the always-on mirror. Same view as your desk, but DB-backed and real-time: it updates by itself as the work moves, with no reload and no deploy. It is login-gated because it shows internal work. The wire carries structured data, not a web page — the intranet renders it with the same template, so it looks identical to your local snapshot (R-FIDELITY).
🔒 aiuni.tech/intranet/pulse Live · real-timelast data push · just now · signed in as avery@example.com
3moving now2waiting on you1idle1no signal
Heartbeats rendered from pushed data by the standard Pulse template · identical layout to the local file
◉ A terminal writes data to the push table → the intranet page subscribes and re-renders live. No credits spent, no worker spawned, no deploy.
Sharing beyond you (Connect · Teams · Education) is held. Sending a terminal's state to another person's agents is a real use — but it only carries the shared project slice, never code or secrets, and a deterministic scrub runs on every push. That mode ships only after a Security sign-off. Watching your own work (this page) is not blocked by that.🔒 See the signed-out gate
🔒
Sign in to watch
Pulse shows work in motion inside your org — who's building what, right now. It's private, so you sign in first.
Login-gated per the away-from-computer privacy rule. The auth model is confirmed with Security before this goes public.
▯Away from your computer. Because the mirror is DB-backed and live, you glance from your phone and see the work update in real time — the one job this surface does that nothing else does. Here's how it looks on a phone, shown in a frame so you can see it from your desk.
AIUPulse Live
3 moving · 2 waiting on you · 1 idle · 1 no signal
Review
security fix
⚑ Waiting
Needs your call: merge the auth-cookie fix?
paused 8m ago
Engineering
signup flow
◆ Working
Building the /prep step-state.
40s ago
Planning
Tutor
⚠ Stale
Session 3 — no move in 2h.
2h 14m ago
The phone shows the same heartbeats, waiting-on-you first. Nothing to reload — it beats on its own.
⚠The watcher may be disconnected. These heartbeats have not updated recently — what you see is the last known state, not the current one. The work itself is fine; the view is stale.
Last refresh 2h 14m ago · the hook stopped firing at 00:34
—moving (unknown)7terminals · last known2hsince last refresh
Heartbeats last known state · dimmed because the view is not current
Engineering
Terminal · signup flow
⚠ Last known
Was building /prep step-state — no update since the watcher dropped.
last seen 2h 14m ago
Design
Terminal · Pulse
⊘ No signal
No heartbeat since the watcher disconnected.
2h 14m ago
Review
Terminal · security fix
⊘ No signal
Last known: paused, waiting on you.
2h 14m ago
Why this state is honest: Pulse never guesses. When the heartbeats stop arriving it says so plainly — "last known, not current" — instead of showing a green all-clear it can't verify. Open RoadWork ↗ for the current truth.
No terminals running
Nothing is in motion right now — a flat line, not an error. When an agent starts work, its heartbeat shows up here on its own.
Your last snapshot is safe in RoadWork; nothing was lost by closing the terminals.
→ Start a terminal, or open RoadWork to see the work waiting to run
↗Reading from RoadWork — the truth for work. Pulse shows you this read-only. To change a priority, move a lane, or edit a task, open RoadWork itself — that's where the work actually lives. If Pulse and RoadWork ever disagree, RoadWork wins.
◱ RoadWork · #614 · /prep step-state↗ Open in RoadWorkread-only preview · Pulse cannot edit this
Lane #614 · Building
read-only
Feature — /prep step-state projectionBuilding
Owner — Engineering terminalmoving
Priority — P1this week
Parent — Signup flow epic→ up
What Pulse can & can't do here
the seam
Read this lane's state and render it✓ yes
Link you straight to it in RoadWork✓ yes
Change the priority, owner, or stateRoadWork only
Move or close the laneRoadWork only
Notice there is no edit control on this page — no priority dropdown, no status toggle, no save. That's the point: Pulse is a window, RoadWork is the workshop.← Back to Pulse
↗Reading from Design Hub — the truth for UI + requirements. Pulse shows you this read-only. To change what a screen looks like or what it should do, open Design Hub. If Pulse and Design Hub ever disagree, Design Hub wins.
◱ Design Hub · Pulse · heartbeat cards↗ Open in Design Hubread-only preview · Pulse cannot edit this
This surface · Pulse
read-only
Prototype — mock.html (locked)✓ this file
Hub story — the plain-English card→ hub.html
Build packet — screens · data · tests→ requirements
State today — locked mock, not builthonest
Open requirements
from Design Hub
Pulse's own brand token vs. inherit Agent Engine's silveropen
The heartbeat schema each terminal writes (task · last-move · state)draft
Cross-agent sharing scrub + scope rulesSecurity
Again — no edit control here. Requirements are authored in Design Hub; Pulse only reflects them.← Back to Pulse
Push this view to AIU?
Publishes a live copy to your gated intranet page so you can watch from your phone. What travels:
✓Structured data only — task titles, last-move times, states. Not a web page; the intranet renders it with the same template (looks identical).
✓No code, no secrets — a deterministic scrub runs on every push.
✓Login-gated — only signed-in members of your org can see it.
✓No deploy — the page is already up; only the data flows. No credits, no worker.
⚠Sharing to another person's agents (Connect · Teams · Education) is a separate, Security-gated mode — not this button. This publishes to your own gated page only.