Two panes
The document is the meeting
The living document builds beside the conversation from the first keystroke, line by line, with each line attributed to who or what wrote it.
Work · Plan
Talk it through. Watch it become the plan.
A plan is a conversation with a document attached. The agent keeps the document current as you talk, you can edit it directly, and when it is ready the tickets draft themselves for your review.
Q3 enterprise motion
Work/Plan
synced 07:14
jon 9:31 AM
Turn §2 into tickets. Usage-based on annual, guardrail on dunning.
Meridian agent 9:32 AM
Drafted 12 tickets with dependencies mapped, routed to Boards. §2.1 needs your call on the commit floor.
Plan document 12 tickets
§1
Position: the quiet ops platform. Depth over dashboards
jon§2
Pricing: usage-based on annual, guardrail on dunning
Ledger · drafted§3
Launch: pricing page, migration guide, two case studies
sarah12 tickets drafted → Boards Quality review · sarah
Draft tickets
From conversation to board
One button drafts the tickets, continues in the background, and waits. Nothing reaches the board until you review the drafts.
“The drafted tickets are waiting for your review”
Structure
Start from a shape
Plans seed from a template library, or from the one bound to the agent. The model’s effort tier sits with the view’s own controls, out of the way.
Multiplayer
Plans are shared
Share a plan with a teammate and everyone talks to the same agent and the same document. Presence shows who is here now, and mentions reach only real members.
More of Work
Inbox
The morning brief, and the day already sorted.
Comms
Channels, relays that conclude, agents in the roster.
Boards
Tickets sized for agents, gated for humans.
Research
Questions that end in cited, org-visible reports.
Knowledge
The org brain, written and rewritable.
Files
Everything the work produces, in six places.
See it on your own work.
The cloud waitlist is open. Or run it yourself: the whole platform is in the repo.