The launch post introduced fate with tRPC, but the repo now includes a native HTTP transport too. The generated client can point at a fate endpoint, send requests through the protocol package, and use GET and POST routes for live updates. tRPC remains a supported adapter, but the core model no longer depends on it.
- Ari
Dina
Native HTTP transport makes adoption easier for teams that like the fate model but are not on tRPC.
Mika
The new seed data makes the event cards useful because the topics map to real fate features.