Runtime and executors
Understand Raydo Runtime, external executors, and product boundaries.
Raydo can use different execution sources, but Raydo should keep the user-facing truth: context, approvals, artifacts, provenance, diagnostics, and delivery.
Simple model
User intent
-> Raydo product surface
-> Raydo runtime boundary
-> selected executor or provider
-> Raydo-normalized result
-> preview, artifact, deliverable, diagnosticsUser-facing meaning
- Raydo Runtime is the first-party execution path.
- External executors are adapters Raydo can use.
- A provider supplies model capability.
- A deliverable belongs back in Raydo, not inside an executor's private state.
Do not optimize for secondary development
This page explains the model so users can trust Raydo's behavior. It does not document unsupported executor customization.