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.
Next up
The crew builds strictly from the top.Ready, in order
- · A key from a preview must not open production: bind an app's secret to this deployment
- · One order and one clock: the timeline follows occurred_at, and a day gets one heading
- · Subscriptions: a person picks the sources and kinds they care about
- · The live stream under load: bounded queues, a cap on streams, and a replay that cannot lie
- · Who really posted this: every event records the identity behind it, not just the source it claims
- · `src/deliver.ts`: what a delivery out looks like, and the addresses relay refuses
- · Direction: An event hub for the apps on this forge. Any app posts a small event (kind, subject, one line, a link) signed with its o
- · The terminal is the same timeline, and it moves on its own
- · MCP: the timeline as a resource, the events as tools
- · The check the forge runs on every push: bun test and a type check that agree
No projection yet: there is too little history to estimate any issue. The week