Skip to main content

Module actions

Module actions 

Source
Expand description

What a person can do now: one list, computed by the runtime and rendered by every interface — the dashboard’s n, c and : today, a desktop app or another workbench later. Every action is a CLI command too, so nothing an interface offers is out of reach of a script.

Structs§

Action
One thing a person can do now.
ActionId
What an action is, independent of its wording: its kind and what it is about (the task, the skill, the issue). An interface finds an action by this, never by its label.
JourneyFacts
Facts the journey is derived from.
JourneyStep
One step of a feature’s journey: spec, plan, tasks, commit, run, review.

Enums§

ActionKind
What kind of action it is: one per Runnable kind (a run split by whether it names a task), plus ActionKind::Command for an action an interface does not run itself. Exhaustive at any one version; a new kind arrives with its Runnable variant (the adding a kind contract of speccoder_runtime::actions::perform).
BatchVerdict
A batch decision.
CommentOp
What a comment action does.
FeatureSource
Where a new feature’s description comes from. Later rungs add theirs (an Explore brief, a promoted quick change) when they are built.
PlanFrom
What plan through starts from.
PolicyList
A prefix list in speccoder.toml.
Runnable
How an interface runs an action itself.
SkillRole
The part a planning skill plays in its format’s planning, from the format’s adapter: what an interface finds “the create step” or “the analysis step” by, without naming a format’s skill.
StepState
Where a step of the journey is.
Through
How far plan through goes.
Via
The interface a person acted through, as a write records it (via): one vocabulary for every record. Records written before it named cli, tui or dashboard (read as Via::Terminal) and editor <name> (read as Via::Acp, the name a separate client).

Functions§

identity
The identity of the action that runs run (or, without one, stands for command): derived, so it cannot disagree with what runs.
journey
The journey from a spec to a reviewed branch, and where the feature is on it: everything before the first open step is done (or skipped, when a later planning file exists without it), that one is now.
primary
The primary action: the first runnable one of the next group.