Coordinator · keeps work and knowledge in step
Every session starts from what the last one learned.
The Coordinator records what is being worked on, by whom, and what was decided, and writes the outcomes back into Cornerstone as facts. Your people and their AIs stop re-checking what has already been settled, and the next session, whoever runs it, starts where this one ended.
What changes
Where the work lives.
AI made each person faster. It did not make the team faster, because every output still has to be checked, every decision re-found, and every session re-explained. The Coordinator is the part of the platform that fixes that.
What you do with the Coordinator
Hand work to your AI, and see it tracked.
The work goes on as a ticket, with who is doing it, what was asked, and what was decided along the way.
Record a decision once.
Made in a chat, a review or a meeting, it is recorded with who made it and when, and every session that follows reads it.
See what is in progress, across people and their AIs.
Who is working on what, without a status meeting to find out.
Pick up a colleague’s thread.
The next session starts from what the last one learned, whoever ran it.
What stops
- Updating the project tool by hand after the work is done.
- The status meeting whose only purpose is finding out who is on what.
- Reopening a decision that was settled last week, because nobody can find it.
- Documentation that goes stale the week after it is written.
- Two people, or two AIs, working from two versions of the truth.
The bottleneck moved from doing the work to reviewing and remembering it. This is where remembering stops being a person’s job.
What it looks like
A trail you can read.
Decided, in progress, written back. Every item says who, when, and what it settled, and the ones that changed the organisation's knowledge say so.
Your people see it in Workbench, in the same conversation as the work. Their AIs read it before they start, so a session never begins from a blank page.
Milan region: residency rule
Decided
4 Sep 2026 · Legal
Written back to Cornerstone as a rule. Every session since reads it.
Q3 board narrative
In progress
Finance · two people, one AI session open
Reads the Q2 decisions instead of re-deriving them.
Supplier onboarding rules
Decided
28 Aug 2026 · Operations
Three questions the old checklist had left open, now settled once.
How it works
Claimed, decided, written back.
01
Work is claimed.
A piece of work becomes a ticket with a person on it, whether it was asked for by a person or handed to an AI.
02
Decisions are recorded as they happen.
Not afterwards, in a document nobody finds, but in the moment, with who decided and when.
03
Outcomes are written back.
What was decided becomes a fact in Cornerstone, superseding what it replaced, so every AI reads it in the next session.
What it does for you
The team gets faster, not just the people in it.
Decisions are made once.
A decision is recorded with who made it and when, and every session that follows reads it instead of reopening it.
See what is in progress.
Who is working on what, across people and their AIs, without a meeting to find out.
The work writes back.
Outcomes become facts in Cornerstone as the work is done, so the knowledge moves with the work instead of going stale.
Done is on the record.
What was done, by whom, and what it settled, is there to show. The next person does not have to take it on faith.
The Coordinator is included in every edition, from two people at no cost upwards. Pricing. The argument for why teams stall, with the published research, is on Why Cornerstone.
How you reach it
From the same conversation as the work.
Workbench connects the Coordinator to the AI in VS Code or Cursor, alongside Cornerstone. Ask for a piece of work and it is tracked; settle something and it is recorded.
Stop re-checking what is already settled.
Get started with two people at no cost, or book a call if you are rolling it out across an organisation.