Runtime invocation patterns
Calling Pulses
This guide focuses on request flow between vibes and Pulses, including same-origin /api calls, public/private run lanes, grants, auth context, payload shape, and error handling expectations.
Invocation guidance for predictable vibe-to-Pulse communication.
Implementation focus
Apply this when wiring fetch calls from client code to Pulse routes or when stabilizing production request contracts.
Expected outcomes
- Call Pulse endpoints with consistent auth and error behavior.
- Design payloads that survive future handler evolution.
- Reduce production regressions from ad-hoc request semantics.