---
title: "Dock + Linear: founder-track roadmap with attributed eng-lead review"
excerpt: "Linear holds the issues and cycles. Dock holds the founder narrative the agent drafts from them, plus the eng-lead approval that lets a roadmap update ship."
author: mei
category: Use Cases
date: "2026-05-30"
---

A founder-track roadmap is the narrative version of Linear: which bets are in flight, why they matter, what changed this cycle. Linear holds the issues. Dock holds the founder-facing summary the agent drafts from those issues, plus the eng-lead review that decides whether each update ships. The agent reads Linear on a cycle boundary, drafts a row per initiative, and waits for sign-off.

Linear and Notion 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 Roadmap Narrative

| Initiative | Linear project | Cycle status (re-read) | Agent draft summary | Eng-lead review | Reviewer | Decided at |
|---|---|---|---|---|---|---|
| Multi-tenant billing | LIN-PRJ-318 | 7 of 9 issues closed | "Billing v2 ships next cycle. Stripe webhooks and proration covered. Dunning deferred to Q3." | Approved | priya@ (eng lead) | 2026-05-29 14:02 |
| Agent identity SDK | LIN-PRJ-401 | 4 of 11 issues closed, 1 blocked | "SDK is mid-cycle. OAuth scope work blocked on partner review. Do not promise GA in next investor update." | Rewrite requested | priya@ (eng lead) | 2026-05-29 14:08 |
| Public changelog feed | LIN-PRJ-422 | 9 of 9 issues closed | "Changelog feed shipped Tuesday. RSS and JSON endpoints live. First 3 entries published." | Approved, send to all-hands | jordan@ (founder) | 2026-05-30 09:15 |

Each row links back to the Linear project URL, the agent draft revision in Dock, and the Notion narrative doc the approved summary writes into.

## Workflow: cycle-end narrative pass

On the last day of each Linear cycle, the agent runs four steps. It re-reads every founder-track project from Linear, fresh. It drafts a five-sentence summary per initiative into the Dock surface, with a pointer to the source issues. It tags the eng lead as reviewer based on the project owner. It waits. When the eng lead approves, the agent writes the text into the Notion narrative doc with attribution: drafted by agent, approved by priya@, timestamp. When the eng lead requests a rewrite, the agent revises. The founder reads only approved rows.

## Why it matters

Founders write the same roadmap update three times: investors, team, changelog. The agent drafts all three from Linear, but only if an engineer who shipped the work signs off first. The Dock row holds the draft, the reviewer, and the decision. The Linear issue stays the source of truth. The Notion doc stays the published artifact. The audit trail lives in Dock because that is where interpretation happened.

This is the same pattern we describe across the [founders pillar](/blog/dock-for-founders) and in [Cloud 2.0 for product](/blog/cloud-2-0-for-product): the platform holds state, Dock holds judgment, the agent moves between them with a named identity. See also [agent collaboration](/blog/agent-collaboration-primer), [agent identity basics](/blog/agent-identity), [Cloud 2.0 for engineering](/blog/cloud-2-0-for-engineering), and the [identity model](/blog/agent-identity) again for the reviewer attribution chain.

Try the founder-roadmap template in Dock and connect your Linear workspace this week.

## FAQ

**Does the agent edit Linear issues?** No. The agent reads Linear and writes summaries into Dock. Linear stays the system of record for engineering state. If a Linear edit is needed, a human makes it.

**What happens if the eng lead is out?** The Dock row stays in review. The agent does not auto-publish. The founder sees an unreviewed row and can reassign the reviewer or wait.

**How does this connect to the Linear Method?** Linear's own [practices](https://linear.app/method) treat issues as the core artifact and emphasize transparent, regular updates. The agent inherits that rhythm: it runs on cycle boundaries, summarizes from issues, and only publishes once a named person approves.

**Why route founder writing through review at all?** Because founder communication compounds. Wes Kao's [framework for founders](https://review.firstround.com/the-other-pmf-wes-kaos-personality-message-fit-framework-for-founders/) argues that preparation and clarity beat volume. The agent drafts fast. The eng lead keeps it accurate. The founder keeps the voice.