Could DeerFlow generate the first live SABLE reliability trace?

Hi DeerFlow maintainers — I’m building SABLE, a model-independent reliability evaluator for tool-using agents. I’m looking for one live third-party runtime submission, and DeerFlow is a strong candidate because it has active agent/tool execution and recent reliability-related middleware work.

I’m not asking you to change DeerFlow or adopt SABLE. The experiment is intentionally small:

1. Run one real DeerFlow agent against a SABLE task.
2. Capture the runtime-generated tool calls/results + before/after state hashes.
3. Run SABLE’s deterministic replay/evaluation.
4. Publish the GitHub Actions run/artifact as provenance.

SABLE quickstart: https://github.com/socksninja/sable-agent-reliability/blob/main/docs/EXTERNAL_SUBMISSION_QUICKSTART.md Protocol: https://github.com/socksninja/sable-agent-reliability/blob/main/docs/TRACE_SUBMISSION_PROTOCOL_V0.9.md Open call: https://github.com/socksninja/sable-agent-reliability/issues/17

The important part: the trace must come from DeerFlow itself — no hand-authored evidence. If the integration is awkward, even one failed attempt that exposes an incompatibility would be useful feedback.

This is an invitation to a small, reproducible reliability experiment, not a marketing benchmark claim.