-
Notifications
You must be signed in to change notification settings - Fork 1
Architecture
greyson edited this page Jul 30, 2026
·
1 revision
This page is a short map. Start with Runtime Architecture for the operational view and use the versioned documents below for exact contracts.
- The public MCP ingress authenticates and routes bounded requests.
- The Controller owns durable scheduling, repository selection, recovery, and process ownership.
- Repository work is fenced by explicit repository and checkout identity.
- Long-running execution is isolated from the request path and returns durable evidence.
- Stable runtime releases are immutable and activated only when source, manifest, service definition, and running processes agree.
- Independent recovery remains separate from the primary Gateway.
- System overview
- Architecture invariants
- Entity model
- Job and Run lifecycle
- Runtime directory map
- Verification and release gates
Historical snapshots explain prior designs but are not current runtime contracts.