Work
One task, with everything attached to it
Work: the task is on the Onboarding board and in Sam's Today by 9:04, and done at 4:45.
The screen
This is the real product surface
One Tuesday
What happened from 9:04.
The same day the home page tells, read from this block.
9:04
Every process becomes work.
Sam applies the onboarding template. The SOP and the KPI come with it.
With Docs.
10:30
The conversation lives on the task.
Maya posts the decision as a comment on the task and links the thread beside it.
With Talk.
11:15
The paperwork follows.
Contract v2 carries the reporting clause and is attached to the task as a file.
With Docs.
2:00
Blocked doesn't mean stuck.
Sam mentions Priya from the task. The call and the timer are real: 15 minutes at 2:15, 2h 10m logged.
With Planner.
4:45
Every task moves a goal.
Done at 4:45, and on the goal's Effort card. The KPI reading is recorded by its owner, and the ring moves with it.
With Goals.
The wires
What Work 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.
- Work and DocsStep 3, linked to the task
- Work and TalkDecision recorded on the task
- Work and PlannerSam mentions Priya from the task
- Work and GoalsThe task is linked to the KPI
- Work and AISources from the linked work
The whole map, with every node and every edge, is on how it connects.
Inside it
What is inside Work
- Tasks
- lists
- boards
- 17 views
- Taskslists, boards and every view, with custom fields.
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.
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
A Talk thread referencing the task, a pinned summary on the task, the contract attached. Channels and threads shipped, contracts and attachments shipped, task reference from Talk not confirmed
An automation notifying the role owner on a status change, plus the call and the timer. Calls and TimerSession shipped, task.status_changed really emits, but no action resolves a role to its holder
Completing the task writes the KPI record, which moves goal progress, with the Effort card and the on track verdict beside it. The Effort card from linked KRA tasks, goal rollups and the deterministic on track verdict all ship. Completing a task writes no KPI record: every KPIRecord in the repo comes from a person or an external door, so the ring does not move by itself.
A Sidekick answer with four source chips, kudos landing as review evidence, the task connection trail. Kudos with values shipped. The connection trail is a new product feature and the receipt renders from this fixture until it lands
On every tier, including the free Starter plan.
The point is what it connects to
Work is one of eight, and the whole day is at one Tuesday.