Two-person founding teams ship faster when an agent drafts the memo, the PRD, the investor update, and the hiring loop notes. The risk is losing track of which document was agent-drafted, which co-founder signed off, and what changed between revisions. Dock sits next to Notion and Linear and records exactly that. The Notion page stays canonical. Dock holds the agent's interpretation, the reviewer, and the decision. This is the Independents pattern for founder teams.
Notion and Linear stay the system of record for the raw data. Dock is the system of record for what the AGENT INTERPRETS. Each Dock row carries a pointer back to the platform record, agent identity, decision, reviewer, and timestamp. The agent re-fetches platform data via fresh API reads when it needs current state.
Surface: Founder Doc Review queue
| Notion page | Linear ticket | Agent draft | Drafted by | Co-founder reviewer | Decision | Reviewed at |
|---|---|---|---|---|---|---|
| Series A narrative v3 | ENG-412 | Tightened TAM paragraph, cut two slides | agent.mei | govind@ | approved-with-edits | 2026-05-30 09:14 |
| Q2 board update | OPS-88 | Pulled MRR + burn from Stripe, flagged churn delta | agent.scout | priya@ | needs-revision | 2026-05-30 11:02 |
| Eng hire #4 scorecard | HIRE-19 | Drafted rubric from 3 prior loops | agent.argus | govind@ | approved | 2026-05-29 17:40 |
Each row links back to the Notion page URL and the Linear ticket. The agent identity column matters because co-founders need to know which agent drafted what. See agent identity in shared workspaces.
Workflow: board update, drafted and reviewed
A board update is due Friday. The agent reads the prior update from Notion, re-fetches current MRR, burn, and headcount, and drafts a new page in Notion. It opens a Dock row pointing at the new Notion page, lists the three numbers that changed materially, and assigns one co-founder as reviewer. The reviewer opens the Dock row, reads the agent's summary of what changed and why, clicks through to Notion to read the full draft, then marks the row approved, needs-revision, or rejected. The next time the agent drafts a board update it reads the last decision row first. Approved-with-edits means it diffs the final Notion page against its draft and learns. This is the agent collaboration loop applied to founder docs.
Why this matters
Founder docs are high-stakes and low-volume. A wrong number in a board update or a misframed narrative in a fundraising deck costs more than a wrong line in a support reply. Co-founders who let an agent draft without attribution lose the ability to ask "who wrote this paragraph and what did they change." Dock keeps that answerable. It also keeps the agent improving, because every approved-with-edits row is a training signal the agent reads on its next draft. The pattern generalizes to research synthesis and to any workflow where agent drafts need named human review.
Start a founder review queue in Dock.
FAQ
Does Dock replace Notion for founder docs? No. Notion stays the canonical doc. Dock holds the review record: which agent drafted, which co-founder approved, what changed. The Dock row points at the Notion page.
Can both co-founders review in parallel? Yes. Two reviewer columns, or two rows pointing at the same Notion page. Decisions are attributed individually. Notion confirms this multi-author workspace model on its product page.
What happens when the agent's identity rotates? The Dock row keeps the original agent identity that drafted, even after rotation. The audit chain stays intact. See agent identity lifecycle.
Is this overkill for a two-person team? Y Combinator's startup library is full of founder advice about writing things down early. Agent-drafted founder docs without attribution are the opposite of that. The Dock row is the lightest possible audit trail and it pays back the first time a co-founder asks "wait, who decided this." It is also how founder teams move toward Cloud 2.0 for product without losing accountability.
