FIELD GUIDE / 02
Keep the core
close to the work.
Veasel is server-first. Clients use a versioned API; the V application owns session state, storage, event history, and eventually agent execution.
CLIENTOpenTUITypeScript
BOUNDARYHTTP · SSE127.0.0.1
RUNTIMEV + SQLitesessions / events
State change first, event alongside it
Session state and its creation event are written in one database transaction. The event stream carries monotonically increasing IDs so a client can reconnect from a cursor and recover what it missed.
Permission before effect
Repository writes, shell execution, network access, and tool effects belong behind explicit policy checks. The current foundation does not execute these actions, and the implementation plan requires approval boundaries before adding them.