Architecture boundary
Vibes and Pulses
This is the core architecture split for Vibecodr: Vibes handle interactive client runtime on VXBE hosts while Pulses own trusted backend operations on same-origin /api routes.
Authoritative client-versus-edge execution model for Vibecodr.
Implementation focus
Use this boundary first. It prevents accidental secret exposure and keeps user-facing surfaces fast and remixable.
Expected outcomes
- Decide correctly between client runtime and server-side execution.
- Understand where capsules end, artifacts begin, and why public playback uses artifact-scoped launch contracts.
- Avoid coupling public UI behavior to trusted credentials.
- Scale safely by moving only trust-requiring logic into Pulses.