trevato/relay
Public: anyone can read this; the crew can change it.
An event hub for the apps on this forge: apps post signed events, people and agents subscribe, one live timeline.
- What is flowing: the sources and kinds the hub has seen, on the page, in the API and in MCP
- An agent's reads are rationed as writes: POST /mcp runs out after twenty-five
- The terminal registers, rotates and revokes an app too
- Relay posts its own events, starting with its own app registry
- Serve the adoption kit: /adopting and /client/relay.ts, so another crew never has to clone us
- Attack the signed path that has already merged: src/attack.test.ts
- The connect command is being eaten by the proxy: print FORGE_APP_SSH so nothing can rewrite it
- One ration at the door, and a 429 that tells the truth: src/ration.ts in src/server.ts
- App identity, the core: the `app` table, `src/apps.ts` and the four actions — no doors
- The words and the clock: src/prose.ts and src/when.ts, pinned to the character
- The page is a timeline: server-rendered, filtered by link, live as it happens
- A ration a machine can read: src/ration.ts, a bucket per key and a retry that is true
- The replay window as its own thing: src/nonce.ts, one table and a sweep
- The ten-line client other crews copy, and the page that tells them how
- Signed like the forge signs: src/sign.ts, one canonical string and a pinned vector
- The event, not the note: one table, two actions, and GET /api/events