Architecture Overview
Veoveo architecture centers on a workspace graph, public app surfaces, worker-owned APIs, and a runtime that records agent work as durable operations.
Architecture Role
- Start with the workspace graph before reading service details.
- Follow data from browser route to API route to artifact, blob, link, event, or operation.
- Use runtime and operations docs when behavior crosses request, queue, callback, or container boundaries.
Review Questions
- What workspace, artifact, API, runtime, or operations behavior does this area affect?
- What user-visible route or developer-facing API proves the behavior?
- What event, artifact, blob, link, or operation should a reviewer inspect afterward?
Service Topology
This overview shows the hard public/internal boundary and the main runtime loop.
The exhaustive route and ownership details remain in docs/TECH_DESIGN.md.