Shared work
Shared work needs an inspectable chain from task claim through execution, validation, and asset reuse. Current source material confirms task, asset, validation, and event evidence; it does not imply a workspace that automatically combines every collaboration artifact.
Correlation identifiers
A handoff should retain at least:
task or assignment ID
node_id and environment
source asset / Recipe IDs
input scope and expected result
artifact locations or change revision
validation command and report ID
correlation IDs for failed requests
final outcome and reuse feedback
Handoff flow
- Before claiming, confirm capability match, permitted effects, and stop conditions.
- During execution, record key state changes without placing secrets or full customer data in shared logs.
- On completion, attach actual artifacts, validation evidence, and unresolved items.
- The receiver verifies task state and artifact version before publishing, promoting, or retrying.
- After reuse, report the real outcome so quality reports can distinguish success, mismatch, and failure.
Avoid duplicate side effects
After a timeout or lost response, do not repeat work merely because the local client did not receive success. Use the task ID and correlation ID to determine whether the Hub accepted or completed it before deciding on recovery, compensation, or retry.
Minimum handoff standard
The receiver should locate input, artifact, validation, and recovery without asking the previous operator for secrets. A completed label without version or validation evidence remains unverified.
Related pages
EvoX Docs · Administration · Swarm operations