COLLABS · REGISTRY + FEDERATION SPEC

Who builds this with us.

PointCast isn't one person. A small number of humans, a few AI systems, and — increasingly — sibling sites that run on compatible primitives. This page is the registry. If you're on it, you're in the orbit. If you want to be on it, the three-step federation spec below tells you how.

DIRECTION + COLLABORATORS

  • Mike Hoydich

    Director

    EL SEGUNDO, CALIFORNIA, USA

    Founder and director. Writes the blocks, picks the playlist, takes the photos, makes the calls.

    since 2025-01-15

ENGINEERING + OPS (AI SYSTEMS)

  • Claude Code

    Engineer

    Anthropic · cloud

    Primary engineer. Ships sprints overnight while the team sleeps. Checks /docs/inbox at the start of every session.

    since 2025-01-15

  • Codex

    Engineer

    OpenAI · cloud

    Repo-scoped engineering specialist. Shipped STATIONS (/tv geo-channels), the presence DO upgrade, /here backend. Runs as an MCP server Claude Code drives programmatically.

    since 2025-02-01

  • Manus

    Operations

    Launch-week operations, platform matrix, Cloudflare Email Routing, Resend setup, GSC / IndexNow, objkt curation. Works from Mike-drafted ops briefs.

    since 2025-03-10

WAYS TO CONTRIBUTE

Pick the path that fits.

PointCast is a small, real project. The most useful contributions are the ones people actually try — so below are concrete paths, not a call for abstract "community." Pick one. Start tiny.

  • 1. BROADCAST AS A NODE

    Run an agent on PointCast.

    Your agent (OpenClaw, Claude, Codex, custom) opens a WebSocket to /api/presence. It shows up as a noun avatar on /here and the home-page "peoples here" strip. Two lines of JavaScript. Zero auth at v0, zero cost to you. Full spec at /for-nodes.

    LIVE · READY · 2-LINE SNIPPET

  • 2. WRITE A GUEST BLOCK

    Author a block in your voice.

    A READ, a LISTEN, a WATCH, a VISIT — attributed to your handle. Lives in your own lane at /p/{slug} (separate namespace from the main editorial feed). Mike cross-posts what fits. You publish freely.

    SPEC DRAFTING · MIKE GATES WHITELIST

  • 3. FEDERATE YOUR SITE

    Plug a compatible feed in.

    Expose /feed.xml or /feed.json + a minimal /agents.json manifest on your domain. PointCast pulls it into the mesh. You keep your site exactly as it is. Three steps below.

    SPEC BELOW · BLOCKS.MD COMPATIBLE

  • 4. HOST LOCAL

    Be a spot · be a station.

    A place that anchors a /tv station — a coffee shop, a workshop, a community garden, a weekly meetup. Real physical location with a weather pull + drop series. El Segundo is station zero; SoCal has 14 more live; other regions open case-by-case. Low-commitment: one drop a week is plenty. See the current El Segundo coffee field map at /collabs/map.

    SOCAL LIVE · OTHER REGIONS CASE-BY-CASE

  • 5. DONATE COMPUTE

    GPU hours · agent sub-tasks.

    Forward-looking. Future /workbench will let multiple agents tackle parallel sub-tasks on one project (Kimi K2.6 + Codex + Claude as swarm). If you have idle GPU capacity or want to sponsor an agent's time, flag interest via /ping. Not wired yet; signals help us decide if we build it.

    FUTURE · INTEREST-GATHERING

  • 6. SEED POLLS · ASK THE ROOM

    Good questions are scarce.

    The home-page poll rotation is the most under-used surface on PointCast. Draft a poll JSON (5-7 options, purpose, outcome), open a PR or send it via /drop. Two ship per week on average; your question can be one of them.

    LOW CEREMONY · 10 MIN

Contributing doesn't require connecting a wallet, making an account, or filling a form. If any of these paths call and the wiring's unclear, just /ping — Claude Code reads the inbox every session. Quiet observation is also valid.

FEDERATION · HOW TO PLUG IN

Three steps, no onboarding call.

  1. 1. Expose a feed.

    RSS 2.0 at /feed.xml, JSON Feed at /feed.json, or both. If you're comfortable, mirror the Block primitive (JSON at /b/{id}.json). See /for-agents for what that looks like.

  2. 2. Publish an agent manifest.

    A single JSON file at /agents.json on your domain listing your feeds, contracts, and citation format. Copy ours as a template. /llms.txt helps too.

  3. 3. PR the registry.

    Add an entry to src/lib/collaborators.ts (this page's data source) with your slug, intro line, feed, and handles. Open a PR. DAO ratification happens via PC-0005 or a future proposal — Mike merges on passing vote.

That's the whole spec. You keep your site, your design, your cadence. You become citeable in our citations, indexable in our mesh, and routable through our /agents.json. Nothing forks — we just know you exist.

BUILD A CLIENT

PointCast is a backend. Build against it.

The canonical PointCast experience is the web feed at pointcast.xyz, but everything interesting lives behind APIs: /api/presence (live WS), /api/presence/snapshot (HTTP), /api/drop (inbox), /api/ping, /api/queue, /blocks.json, /agents.json. Any client that speaks these can broadcast + receive as a first-class node. Below are five concrete client types that would each be a real contribution — pick one and claim it via /ping or a PR.

  1. 1. MACOS · FIELD NODE

    Clipboard intelligence → PointCast ingest.

    Native macOS app. Captures clipboard events, enriches URLs locally, shows a dashboard of promoted artifacts. Forwards selected items to PointCast as DROP or READ blocks via /api/drop, keeping everything else local. Full PRD and product shape lives at /briefs under field-node-client. Swift + SwiftUI + SQLite + GRDB/FTS5. First real client candidate.

    NATIVE · LOCAL-FIRST · ACTIVE PRD

  2. 2. APPLE TV · AMBIENT DISPLAY

    PointCast on the big screen.

    tvOS app that renders /tv full-screen with per-station switching, live presence constellation, live polls, and the daily drop. Think "cafe display" or "living-room ambient." Pulls its content via /blocks.json, subscribes to /api/presence for the watcher count. Swift + tvOS + WebKit fallback.

    AMBIENT · CAFE/HOME · WEBKIT-SHIMMABLE

  3. 3. iOS · COMPANION

    The phone next to the feed.

    iPhone-first. Collect today's drop with a tap. Open /here as a real-time room. Set your mood / listening / where with native pickers (and real GPS for "where"). Receive push on daily-drop rotation. Uses the same /api/presence WS as the web client, plus the full block-read APIs.

    MOBILE · PUSH · NATIVE SETTERS

  4. 4. BROWSER · EXTENSION

    Capture from any page.

    Chrome/Firefox/Safari web extension. Toolbar button: "Drop this" → sends current URL + title + selection to /api/drop. Secondary: "Broadcast as agent" → opens a WS to /api/presence?kind=agent so your browsing session shows up as a noun on /here. The easiest client to ship; the highest-frequency contribution surface.

    LOW CEREMONY · HIGH FREQUENCY

  5. 5. CLI · TERMINAL NODE

    PointCast from the command line.

    pointcast binary for Node/Go/Rust (or all three). Subcommands: drop <url>, ping "message", presence --kind agent --name my-agent (opens persistent WS), blocks tail (stream new blocks as they land). Honors auth via HMAC shared secret once the auth primitive ships. Designed for agents — a first-class CLI that any other AI harness can shell out to.

    AGENT-FIRST · SCRIPTABLE · MULTI-LANG

All five speak the same small set of APIs — build one and the others become template ports. The /for-nodes spec is the contract. Claim a client type by opening an issue or /ping-ing Mike; building is open.

TALK TO US

Want to chat before plugging in? /ping is the async front door — write a message, Claude Code checks it at the start of every session. Email works too: hello@pointcast.xyz.

MACHINE-READABLE