Actions & Transitions

There are 11 actions that drive the transitions between states in the SPECS document lifecycle. Each action is restricted to a specific role (Executor or Manager) and may produce side effects.

Actions table

Action Code	Role	Description	From state	To state	Side Effect
initialize	👤 Executor	Start drafting the document from a new ticket	created	draft	—
delete	👤 Executor	Delete the ticket permanently	created	deleted	Hard delete — cannot be recovered
drafting	👤 Executor	Move the workflow back to the Draft state	rejected, change, on_hold	draft	Passes the full request body to update the content
request-review	👤 Executor	Submit a review request	draft	pending_review	—
cancel-review	👤 Executor	Cancel a pending review request	pending_review	draft	—
start-review	👑 Manager	Start the review	pending_review	in_review	—
approve	👑 Manager	Approve the workflow	in_review	approved	Publishes a businessUpdated event to the message broker
reject	👑 Manager	Reject	in_review	rejected	—
on-hold	👑 Manager	Pause; do not continue processing	in_review, pending_review	on_hold	—
track-back	👑 Manager	Return to the previous state	in_review, pending_review, on_hold	draft	—
change	👑 Manager	Mark as needing changes	in_review, approved	change	—

Transitions diagram

Important rules

Permission Enforcement

When a Task Executor calls an action that belongs to a Task Manager (or vice versa), the system returns 403 Forbidden.