Handbook
Fleet as an Approved Execution Rail
Generated draft. Review source-of-truth ownership, claims, and links before promotion.
Updated
Generated draft. Review source-of-truth ownership, claims, and links before promotion.
Reader Problem
Readers need a human-oriented explanation of 'Fleet as an Approved Execution Rail' before they can act on the technical detail.
Outcome
They understand the business meaning, the Forge mechanism, and the next safe step.
Forge Mechanism
Fleet runs automation jobs inside controlled infrastructure boundaries.
Trust Boundary
The hydration agent generates review drafts only; humans choose whether and where to promote them.
Draft Narrative
This note should explain the platform boundary: Forge Platform owns contracts, schemas, routing language, and ecosystem architecture. Execution remains in product runners, forge-workcells, or Fleet jobs. That distinction keeps the platform as a control-plane spine instead of a monolithic agent runtime.
Suggested CTAs
- Open the platform reference architecture.
- Review the workcell catalog before adding execution code.
- Confirm product boundaries before promoting implementation claims.
Promotion Notes
- Keep runtime implementation claims aligned with the platform/workcells split.
- If this becomes canonical architecture, add it to the relevant handbook index.