Investors use Notion as the deal-memo workspace. The page holds the thesis, the market notes, the founder bio, and the recommendation. When an agent drafts sections of that memo, the firm needs to know which sentences came from the agent, which associate accepted them, and which partner signed off before the memo went to IC. Dock holds that record. The Notion page stays the artifact. Dock stays the audit trail. See the pillar at Dock for investors.
Notion and Affinity 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.
The Dock surface: Memo Draft Ledger
| memo_id | notion_page | affinity_org | section | agent | associate_edit | partner_signoff | status |
|---|---|---|---|---|---|---|---|
| MEM-218 | notion.so/.../runwell-seed | Runwell | Market sizing | research-agent-v3 | accepted with edits (Priya) | approved (Tomas, 2026-05-28) | to IC |
| MEM-219 | notion.so/.../helix-seriesA | Helix Bio | Competitive landscape | research-agent-v3 | rejected, rewritten (Daniel) | approved (Tomas, 2026-05-29) | to IC |
| MEM-220 | notion.so/.../portage-seed | Portage | Founder reference summary | research-agent-v3 | accepted (Priya) | pending | in review |
Each row points at the Notion block ID and the Affinity organization ID. If the agent quoted a 2024 ARR figure that the founder later revised, the Dock row still shows what the agent saw, what the associate accepted, and which partner signed under that assumption.
One worked workflow
A research agent prepares a memo for Runwell. It reads the Affinity organization record, pulls the founder thread, and drafts three sections in Notion: market sizing, competitive landscape, and team. It writes one Dock row per section, each with a pointer to the Notion block and the Affinity org. The associate, Priya, reviews. She accepts market sizing with light edits and flags competitive landscape for rewrite. Dock records both. The partner, Tomas, opens Dock filtered to MEM-218, sees that Priya stands behind the draft, and signs. The memo goes to IC with attribution attached. If IC later asks who wrote the market-sizing claim, Dock answers in one query. The founder side of this same record is a different view of the same ledger.
Why it matters
Memos without attribution rot. Six months in, no one remembers whether the partner read the competitive landscape section or whether the associate had already rewritten it. Dock fixes the rot at the row level. The agent's contribution is logged, the reviewer is named, and the sign-off is timestamped. Notion stays clean. The audit lives next to it. This is the research workflow applied to investment decisions, with the same audit posture we use elsewhere.
According to Notion's venture capital templates catalog, 196 templates already exist for deal flow, portfolio tracking, and memo writing, which tells you the workspace is where memos live. Tomasz Tunguz, in describing what Theory looks for in an investor, names "researching themes and debating the future" as core, work that increasingly happens with agent drafts in the loop.
CTA
If your firm runs memos in Notion and wants attribution on every agent-drafted paragraph, start a Memo Draft Ledger in Dock and point it at your Notion workspace. The founders rail shows the mirror pattern from the other side of the table.
FAQ
Does Dock replace Notion for deal memos? No. Notion stays the memo. Dock stores the per-section attribution: who drafted, who edited, who signed. Partners read the memo in Notion and the audit trail in Dock.
Why not just use Notion comments and version history? Notion comments are human-readable but not queryable across deals. Dock gives you one row per agent contribution, filterable by agent, by reviewer, by date, by IC outcome. Six months later you can ask which research agent drafted the strongest sections.
How does the agent prove it is the agent and not a teammate? Through signed agent identity. Each Dock row records the agent ID, the model version, and the credential used. See agent identity for the mechanics.
What about Affinity relationship data? The agent re-fetches Affinity organization and contact records at draft time. Dock stores the pointer, not the cached relationship data. When the partner opens the row, the agent can pull a current Affinity view if needed.
