The business that runs on rails.
Plans that cannot start before sign-off, phases that execute strictly in order, meeting notes and weekly reports that follow one shape, SOPs that live as executable process instead of a wiki page nobody reads.
what monday looks like
- 01Install the Business Ops pack: meeting notes, weekly report, SOP, decision memo
- 02Run this week's report through the workflow: same shape as next week's
- 03Move one real process into a plan: phases execute in order, after your approval
- 04Write the SOP as steps the AI executes, not prose it might read
The plan lifecycle, as it runs
Define
The plan is described, decomposed, scoped.
Elaborate phases
Child phases created, each an executable, ordered chunk.
Approval gate
No phase starts until a human signs the plan off.
Phases execute in order
sequential_children: each phase must land before the next activates.
Verify
Acceptance is checked against the plan, not against vibes.
Complete
The plan closes only when every child is terminal.
install these
questions
Can our SOPs become executable?
That is the move: write the SOP as workflow steps with instructions, and the AI executes it instead of maybe reading it. The SOP Documentation template is the on-ramp; the result is process that runs rather than process that sits in a wiki.
How do sign-offs work?
Approval gates hold the run until the accountable human says go, and sequential ordering means phase two cannot start before phase one lands. Both are engine-evaluated, not etiquette.
What audit trail do we get?
A high-level activity feed plus field-level before-and-after diffs on tasks and workflow instances, each row separating the agent's label from the server-verified human. Reviews stop being archaeology.
Does recurring work need someone to start it?
No. Put the weekly report on an RRULE schedule and each fire creates the task carrying the whole process. You govern it at the gates.