Status
Pending internal design review. This issue preserves the product direction explored in #4; it does not authorize implementation, merge, release, or publication of the submitted API.
Goal
Allow dynamic workflow controllers to request explicitly declared, JSON-only operations from a trusted parent process without exposing host credentials or adapter functions to workers.
Design questions to resolve
- durable operation state and crash ambiguity
- stop/resume behavior, lease fencing, and late results
- stable provider identity and fresh-process bootstrap
- inspect-only reconciliation and indeterminate outcomes
- call, byte, operation-deadline, and stop-drain budgets
- nested workflow authority and public API boundaries
- a provider-free hostile crash/restart test matrix
Thanks to @calltelemetry-jason for proposing and implementing the initial exploration in #4.
This text was written by an Agent.
Status
Pending internal design review. This issue preserves the product direction explored in #4; it does not authorize implementation, merge, release, or publication of the submitted API.
Goal
Allow dynamic workflow controllers to request explicitly declared, JSON-only operations from a trusted parent process without exposing host credentials or adapter functions to workers.
Design questions to resolve
Thanks to @calltelemetry-jason for proposing and implementing the initial exploration in #4.
This text was written by an Agent.