You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
The workflow command becomes store: store list and store verify on every program, where store prune will land #1017
The workflow group becomes store, on every program and with no alias: <program> store list and <program> store verify, doing what workflow list and workflow verify do today.
The owner, 2026-10-02: "writ workflow is doing useful work. reaction: i don't relate to the name though i'm hard pressed to say what a better name would be. what i know: it is reporting/verifying the record of lifecycle operations." Ruled the same day: "go with store".
Why store
It names what the commands read.list folds the run index and verify checks the signatures of the definitions and execution traces in the execution store, which the shared root's --store already names: "Execution store root, holding definitions and traces".
store replaces workflow everywhere the command surface names it: the registration, the help, the examples, the man pages, the CLI reference, the guides and the architecture documents. A test asserts every program's root carries store and not workflow. Go identifiers keep Workflow where they name a workflow, as WorkflowRecord does: the store lists workflows. Lane 7 of #916 (#926) settles how this command's --scope matches first.
Activity
docs(plan): lane 22 takes the owner's ruling (d), no program writes t…