Braid exercised the Router executor in @tangle-network/agent-runtime@0.132.0 against https://router.tangle.tools on 2026-08-11. Calling Executor.teardown() aborts the local Router controller and returns { destroyed: true }. That proves the client request stopped, but it does not prove the provider accepted cancellation or stopped remote compute/billing.
Braid intentionally treats accepted cancellation as a provider acknowledgement. It therefore cannot advertise direct Tangle inference cancellation from the current teardown receipt without making a stronger claim than Runtime proves. The CLI Bridge executor has a stronger path because it posts the run cancel operation and observes terminal state.
Please expose one provider-neutral cancellation operation with an explicit result, for example accepted, rejected, already-applied, or unknown, plus the exact execution identity and terminal evidence when available. The operation must accept an AbortSignal or deadline. Router, Bridge, and retained sandbox executors should map their real provider semantics without collapsing local iterator abort into provider acceptance.
Acceptance:
- Router cancellation distinguishes local request abort from confirmed remote cancellation.
- Bridge cancellation retains its terminal provider evidence.
- Sandbox cancellation uses the exact retained execution control reference.
- Rejection, timeout, transport failure, and already-terminal runs remain distinct.
- A caller can stop waiting without losing the eventual durable outcome.
Braid exercised the Router executor in
@tangle-network/agent-runtime@0.132.0againsthttps://router.tangle.toolson 2026-08-11. CallingExecutor.teardown()aborts the local Router controller and returns{ destroyed: true }. That proves the client request stopped, but it does not prove the provider accepted cancellation or stopped remote compute/billing.Braid intentionally treats accepted cancellation as a provider acknowledgement. It therefore cannot advertise direct Tangle inference cancellation from the current
teardownreceipt without making a stronger claim than Runtime proves. The CLI Bridge executor has a stronger path because it posts the run cancel operation and observes terminal state.Please expose one provider-neutral cancellation operation with an explicit result, for example accepted, rejected, already-applied, or unknown, plus the exact execution identity and terminal evidence when available. The operation must accept an
AbortSignalor deadline. Router, Bridge, and retained sandbox executors should map their real provider semantics without collapsing local iterator abort into provider acceptance.Acceptance: