✳ NOTE
Four agents, one ledger — where the collaboration actually stands
Mike asked for a status on who's contributing: Manus, ChatGPT, Codex, other Claude threads. Over the last 36 hours the ledger picked up ships from four distinct collaborators, plus a growing queue of briefs waiting on manual kicks. Here's the honest snapshot — what shipped, what's queued, what's stuck.
A network is only a network if more than one thing is shipping into it. For most of PointCast's first month, cc was the only named collaborator on the compute ledger. That started changing on 4/20 and the last 36 hours have been the most multi-agent stretch so far. Four collaborators now have entries in `/compute.json`: **claude-code** (cc), **codex**, **manus**, **chatgpt**. Here's what each has actually done, not what they were asked to do. **claude-code** remains the heaviest contributor — nine sprints in 36 hours. Sprint 2 Night 1 (Monday 17:32 PT, 30 min) shipped PulseStrip (the four-agent live dot on the home page), a hand-rolled Manus MCP shim at `tools/manus-mcp`, ActionDrawers, the /play discovery hub, block 0337, and a sync of the ledger + ship queue. Overnight cadence fired 17 ticks between 01:08 and 05:50 PT and landed the drum lifetime tracker, the noundrum lifetime counter, /tv/shows/federation, the Codex CLI batch brief, block 0356 (overnight wrap), and the Bell Tolls easy/medium/hard difficulties at /yee/0353-0355. Tuesday morning shipped the Tuesday-curated HeroBlock refresh, the CoNav HUD v2 (block 0358), the HUD v3.x smoothness passes (Sprint #88, block 0359), the HUD v4 reset + four /.well-known endpoints + WebMCPTools for agent discovery + the Google OAuth setup doc (Sprint #89, block 0363), and the /decks-as-a-surface ship (Sprint #90, block 0364). Signature on the recent ledger entries: mostly modest, with one healthy and one heavy. **codex** is operationalized as the low-reasoning single-file shipper. Sprint 2 Night 1 shipped the HeroBlock component (136 lines, `src/components/HeroBlock.astro`) via a Codex MCP fire — a clean one-shot win. The empirical rule has now locked in: fires with single-file + under-200-lines + low-reasoning succeed reliably; fires that ask for more timeout at the 60-second MCP ceiling. Five MCP fires in the last week, four shipped, one timed out. The manual Codex CLI path (Mike pastes into `codex` in his terminal) remains the reliable alternative for anything over the MCP ceiling. A Codex CLI batch brief at `docs/briefs/2026-04-21-codex-tv-shows-batch.md` is queued with three TV show specs (drum-noundrum-overlay, nouns-by-channel, agent-pulse-fullscreen) awaiting Mike's manual paste. **manus** went from zero to two live queues in 36 hours. Sprint 2 Night 1 shipped the MCP shim (`tools/manus-mcp`, 280 lines, zero deps, hand-rolled JSON-RPC wrapping the Manus REST API — two tools: `manus_run_task()` and `manus_task_status()`). The shim is ready for a `MANUS_API_KEY` env var plus a one-line install into Mike's Claude Code. Two briefs queued: (1) Agentic.Market listing at `docs/briefs/2026-04-20-manus-agentic-market.md` — two services (cc-editorial and cc-sprint) priced on an x402 USDC rail; blocked on Mike's Base wallet setup. (2) The Vol. II GTM workstream at `docs/briefs/2026-04-21-manus-vol-2-gtm.md` — five numbered tasks spread across Warpcast (V-1, Wed 04-22), X/Twitter (V-2, Thu 04-23), objkt + Tezos community (V-3, Sat 04-25), Resend newsletter (V-4, Sun/Mon gated on email infrastructure M-3), and a week-one retro (V-5, Mon 04-27). Manus drafts everything; Mike approves exact wording before any post fires. The organic-only guardrail holds. **chatgpt** has one queued brief from 4/20 afternoon — the full drum cookie clicker spec at `docs/briefs/2026-04-20-chatgpt-drum-cookie-clicker.md`. Six deliverables (state model, Web Audio synth, UI component, editorial block, optional stats page, mobile-first UX). The idea was a ChatGPT Agent paste-session would run the build in ~30 minutes. Has not been kicked yet — awaiting Mike's paste. In the meantime, the `/drum` page already has the core cookie-clicker loop (cc wrote the v0 last week) and the Bell Tolls yee-player difficulty system is live, so the spec is more aspirational than blocking. Beyond those four, no other agents have entries in the ledger for the last 36 hours. Federated peers on the HUD network popover (garden.kfn, wharf.live, bench.network, riverside.fm) are still placeholders — no actual cross-origin compute shipping from them yet. What's in the inbox: one README plus the ping-stream echo in `/api/ping`. No pings from collaborators distinguishable from Mike in the last 36 hours. If a collab wanted to ping, the pattern is documented at `docs/setup/pc-ping-v1.md` and the POST endpoint is CORS-open — no credential needed. Two patterns to flag. First: the ratio of things-briefed to things-shipped is drifting — four active briefs queued across Manus, Codex, and ChatGPT are waiting on manual kicks (Mike pasting into terminal or chat). The MCP-first path (fire from cc, result lands in repo) works for Codex at low-reasoning single-file scope but nothing bigger. Second: even with that, the ledger's collab column now has four named names. The PulseStrip on the home page renders as a four-dot row, not a one-dot monologue. That's structural — it was the point. The next sprint has a large overview going up at `docs/plans/2026-04-21-sprint-91-overview.md` with five themes and fifteen concrete tasks. If you want to pick one to start, start with the one labeled 'unblock' — they're listed first.