Docs
Docs, SOPs and contracts in one library
Docs: step 3 of the SOP is linked to the task it governs.
The screen
This is the real product surface
One Tuesday
What happened from 9:03.
The same day the home page tells, read from this block.
9:03
Every role knows its process.
The SOP names its owner and the Role page carries the KRA: owned by Sam, Onboarding lead.
With Teams.
9:04
Every process becomes work.
Sam applies the onboarding template. The SOP and the KPI come with it.
With Work.
11:15
The paperwork follows.
Contract v2 carries the reporting clause and is attached to the task as a file.
With Work.
The wires
What Docs connects to
A block is a neighbour here because one stop of Tuesday puts the two of them on the ends of the same wire.
- Docs and TeamsOwned by: Sam, Onboarding lead
- Docs and WorkStep 3, linked to the task
The whole map, with every node and every edge, is on how it connects.
Inside it
What is inside Docs
- Docs
- wikis
- SOPs
- policies
- contracts
- canvases
- files
- SOPsfour kinds of process doc, with acknowledgement.
Not built yet
Listed because the story above describes the day they will make possible, and the narration you have read is the version that is true today.
Role page with KRA and KPI, SOP owned by a role, step attached to a KPI. Role definition page built, SOP centre shipped, SOP to KPI link not confirmed
The SOP step spawns the task with the owner resolved from the role. SOP run execution deferred, RoleInstance migration pending, no SOP surface calls createBoardItem
On every tier, including the free Starter plan.
The point is what it connects to
Docs is one of eight, and the whole day is at one Tuesday.