Why
The repository already demonstrates multi-agent routing, concurrent workflows, MCP, and tracing. A useful production-oriented addition would cover a harder failure mode: a worker completes an external action, but its response is lost. A coordinator that treats this as an ordinary failure can retry the handoff and duplicate the action.
Proposed sample
Add a small, provider-neutral multi-agent workflow (under 07.Workflow, or another maintainer-preferred location) with a coordinator, two competing workers, a mock destination, and a reliability-sidecar boundary:
- The coordinator derives a stable workflow/action key and writes a shared checkpoint before handoff.
- Two workers race to claim the same duplicate-sensitive action; atomic admission allows only one to execute it.
- The sample injects a timeout after the mock destination records the result but before the worker returns.
- Recovery treats the result as ambiguous, reads back the destination, records evidence, and resumes without replaying the action.
- A verifier advances the checkpoint only after evidence is present and reports the proof scope honestly.
The output/tests should show:
- two contenders, one admitted execution, and one destination record;
- restart/resume from a durable checkpoint;
- no automatic retry of an ambiguous result;
- a retry only after an explicit known-failure policy; and
- the distinction between caller-reported evidence and independently verified proof.
Portability
The sample could define a minimal ReliabilityBackend protocol (claim/admit, checkpoint, transition, status) with a deterministic local adapter for tests. A remote MCP adapter would be optional, so the pattern is not tied to a vendor. Agent Enhancer Utilities is one free, no-auth reference implementation, but the sample would remain runnable without it and document the semantics rather than a product.
No real email, ticket, payment, or other external side effect is needed; a counted mock sink makes the invariant testable.
If this fits the samples roadmap, I can prepare a focused PR after guidance on preferred language (Python, .NET, or both) and placement. I will not open one before maintainer confirmation.
Why
The repository already demonstrates multi-agent routing, concurrent workflows, MCP, and tracing. A useful production-oriented addition would cover a harder failure mode: a worker completes an external action, but its response is lost. A coordinator that treats this as an ordinary failure can retry the handoff and duplicate the action.
Proposed sample
Add a small, provider-neutral multi-agent workflow (under
07.Workflow, or another maintainer-preferred location) with a coordinator, two competing workers, a mock destination, and a reliability-sidecar boundary:The output/tests should show:
Portability
The sample could define a minimal
ReliabilityBackendprotocol (claim/admit, checkpoint, transition, status) with a deterministic local adapter for tests. A remote MCP adapter would be optional, so the pattern is not tied to a vendor. Agent Enhancer Utilities is one free, no-auth reference implementation, but the sample would remain runnable without it and document the semantics rather than a product.No real email, ticket, payment, or other external side effect is needed; a counted mock sink makes the invariant testable.
If this fits the samples roadmap, I can prepare a focused PR after guidance on preferred language (Python, .NET, or both) and placement. I will not open one before maintainer confirmation.