Bot Velocity Engineering
Nested Process Invocation
Composable automation requires workflows to call other workflows.
Without governance, this becomes dangerous.
The Composition Problem
Naive composition looks like:
Parent → Child → Tool → Model
If the child fails, who retries? If recursion occurs, who limits depth? If cost spikes, who aggregates it?
Without a control plane, composition leads to instability.
Governed Invocation Model
A safe pattern:
Parent Execution ├─ call_process("Child") │ ├─ Independent lifecycle │ ├─ Lease ownership │ └─ Structured error classification └─ Result mapping
Child workflows remain independently governed.
Business Implications
Composable workflows allow:
- Modular automation
- Department-level isolation
- Incremental rollout
- Reusable governance policies
But without deterministic orchestration, modularity creates cascading failure.
Trace Stitching & Cost Attribution
Nested invocations must preserve:
- Parent execution ID
- Token usage aggregation
- Tool invocation lineage
This enables:
- Budget control
- Audit trails
- Performance diagnostics
Risk Controls
Safe nested invocation includes:
- Depth limits
- Self-call prevention
- Idempotent invocation keys
These controls prevent runaway recursion.
Executive Conclusion
Composition is powerful. Governed composition is sustainable.
Enterprise automation demands composability with deterministic oversight.