When to reach for it
Use it when separate tools or machines need to exchange a packet or retrieve a saved stage result.
How it works
The same command interface fetches and pushes packets, begins runs, checkpoints results, pulls stage history, and locates artifacts. Each driver owns the underlying transfer; successful commands emit JSON.
Trace this to the source ↗Where its responsibility ends
The store persists artifacts. It does not execute the agent, start the application, or judge whether a report passed. A Drive folder or git remote is not the workflow’s execution machine.
Setup & first use
Select a driver and read the operator playbook. The fs driver needs no cloud credentials; Drive needs its supported rclone setup, and git uses your existing git authentication.
Open the owner’s instructions ↗Exact files & reviewed version
This explanation follows the recorded source snapshot reviewed on 17 September 2026.
1749b74322e221bb864b89dfd000da3e51da8afe ↗
Private repository; sign in with an account that has access.