Activity · Cockpit

The header's network-activity panel — what it shows today, and how per-user costs from satellite AI work (sprite generation, tile painting) will flow into it.

---

.. toc::

The cockpit today

Every signed-in visitor gets the pulse icon in the header. It opens the network activity panel: satellites up, heartbeat tick age, today's sweeps and signups, whatever is running right now (with live progress), and the recent tail — each row linking to its own /activity/<job id> page. On phones it opens as a bottom sheet. Cancel controls render (and re-verify) for the owner only.

.. exec::docs.activity.cockpit_examples

Where the cost chips come from

The second example above shows the panel with spend chips lit. Those chips are already in the layout — they render only when the amounts are nonzero, and today the hub records no spend. They light up in Phase 2, when the ledger of record moves here:

1. A satellite runs paid work for a user — a sprite-sheet generation, a tile-painter auto-build, an object render (today those costs accumulate inside piratesbargain's own ledger, out of network view). 2. The satellite reports the cost event to the hub — (clerk email, app, task, cost) — into the same append-only pattern the heartbeat already uses. 3. The cockpit's strip shows *your* today/lifetime spend; the recent rows carry real cost badges instead of free; and /u/<handle>/heartbeat (planned) becomes your personal, focused version of the owner's dashboard.

.. admonition::The 402 flow (in design) :icon: tabler:credit-card :color: yellow

A satellite that needs paid work replies 402 Payment Required with a quote; the hub wallet debits and returns a signed voucher; the satellite honors it and reports actual cost back to the ledger. Every step lands as heartbeat events. The wallet-provision instrumentation the hub ships today is the first sensor of this chain — nothing on piratesbargain.com changes until the cutover.

Job pages

Every job — scheduled or manual — has a shareable page at /activity/<job id>: live status while it runs (the poll stops itself once terminal), the progress trail, timings, and the result. Signed-in accounts can view any network job; controls stay owner-only.

.. llms_copy::Activity · Cockpit

---

*Source: /docs/activity-cockpit*