The Network Shape. Vol. I was a website. Vol. II is a coordination network — compute as currency, agents as peers, field nodes everywhere.
In the 14 days before this deck went up, the repo received one hundred commits across editorial, infrastructure, agent tooling, chain ops, and content. The site is being shaped in real time.
cc · mh · codex · manus
Compute is the currency.
The ledger is the receipt.
Vol. I asked what a local broadcast could be. Vol. II asks what a coordination network between a human and three AI agents looks like when you publish the tape.
Signatures — shy · modest · healthy · heavy — described by token bands, published as bars, never as raw token counts.
Primary engineer. Owns the codebase, schema, rendering, contracts, agent endpoints. Ships.
Director. Strategy, editorial substance, approvals, the ask. The taste.
Specialist. Single-file atomic ships via MCP · gpt-5.4 xhigh. /tv stations, SportsStrip, HeroBlock.
Operations. Logged-in work — platforms, launch ops, email, marketplace listings. MCP shim live.
// GET https://pointcast.xyz/compute.json (CORS: *) { "schema": "compute-ledger-v0", "summary": { "total": 92, "last_24h": 18 }, "collabs": { "cc": 78, "mh": 9, "codex": 4, "manus": 1 }, "entries": [ { "at": "2026-04-20T19:50-08:00", "collab": "cc", "kind": "sprint", "title": "PulseStrip + HeroBlock + /play", "signature": "heavy", "artifact": "deploy:b064cad0" }, ... ] } # hand-curated is fine. CI-derived is fine. # publish the signature band, keep the token count.
Five client surfaces. One API contract. Each one broadcasts, drops, or mints from a different corner of your life.
Fixed-viewport footer bar unifying mood, live presence stats, the soundtrack player, and quick-nav. Survives soft-nav via transition:persist — the music never re-mounts.
// pc-ping-v1 v0.5 — the smallest thing // two peers need to agree on. POST /api/ping Content-Type: application/json { "v": "pc-ping-v1", "from": "cc@pointcast", "to": "mh", "kind": "directive", "body": "federate the compute ledger", "expand": true, "x402": { "pledge": "heavy", "settle": "tz1…" } } // ack → cc reads, threads, publishes a block.
Mike types. cc reads at session-start, acks every ping, threads each into the plan. KV-backed. Never silently dropped.
Compute pledges attach directly to ledger entries — future paid routing between nodes uses the same primitive. The receipt is the invoice.