Primary execution lane
governed runtime lane · receipt-backed execution
- mode
- plan/run/verify/review/approve
- review posture
- receipt-backed
- handoff
- policy and review required
AgentFoundry routes engineering work through governed execution lanes with leases, permissions, trace capture, run evidence, rollback notes, and human approvals.
ready
readyready
readyready
readybuilder
readybuilder
readygoverned runtime lane · receipt-backed execution
plan/run/verify/review/approvereadyindependent verification lane · checks and replay
plan/run/verify/review/approvereadyrollback-aware recovery lane · pause and resume
plan/run/verify/review/approvereadyspecialized implementation lane · bounded autonomy
plan/run/verify/review/approvegatedparallel background lane · governed fan-out
plan/run/verify/review/approvegatedreview-focused lane · evidence consolidation
plan/run/verify/review/approvegatedisolated trial lane · policy-gated execution
plan/run/verify/review/approvegatedcustomer-scoped lane · explicit approvals required
plan/run/verify/review/approvegatedgoverned runtime lane · receipt-backed execution
independent verification lane · checks and replay
rollback-aware recovery lane · pause and resume
specialized implementation lane · bounded autonomy
parallel background lane · governed fan-out
review-focused lane · evidence consolidation
isolated trial lane · policy-gated execution
customer-scoped lane · explicit approvals required
Objective state, approval logic, replay, and handoff decisions stay visible as first-class product state.
Governed execution lanes route work, collect receipts, and preserve rollback paths across runs.
Repositories, browsers, shells, and other sensitive systems stay behind scoped permissions and review rules.
Checks, artifacts, screenshots, and review notes compile into a decision-ready review surface.