Dock is the project management workspace where agents draft the status pulse, the risk log, and the next resource plan, and a PM signs off before any of it goes upstream. The agent reads Asana, Linear, and Jira, synthesizes what changed, writes a row with its reasoning, and waits. The PM accepts, edits, or rejects. The decision persists with agent identity, reviewer name, and timestamp.
Asana, Linear, Jira, Monday.com, and ClickUp stay the system of record for the raw project data: tasks, issues, sprints, owners. Dock is the system of record for what the agent interprets: the prioritized status pulse, the risk classification, the reviewer's sign-off, the audit trail. Each Dock row carries a pointer back to the platform record (asana_task_id, linear_issue_id, jira_issue_key), the agent identity, decision, reviewer, and timestamp. The agent re-fetches platform data via fresh API reads when it needs current state. Dock holds the persistent interpretive layer that survives across sessions.
The status-pulse table
| pulse_id | project | source_ids | agent_summary | risk | reviewer | decision |
|---|---|---|---|---|---|---|
| PUL-241 | Checkout v3 | linear: ENG-4412, asana: 11923 | Two blockers slipped, tax scope cut, on track for W24. | Yellow | govind@dock.ai | Approved |
| PUL-242 | Mobile onboarding | linear: ENG-4501, jira: MOB-218 | Unowned dep on auth team. Escalate before standup. | Red | govind@dock.ai | Edited, approved |
| PUL-243 | Pricing experiment | asana: 12044, 12047 | Instrumentation done, ready for cohort gate. | Green | govind@dock.ai | Approved |
One workflow, end to end
Monday morning, the agent:pmo-sync identity wakes on schedule. It calls the Linear, Asana, and Jira APIs, pulls seven days of activity per project, runs its synthesis prompt, and writes one row per project with risk and source IDs. The PM opens Dock, edits PUL-242's escalation language, and approves. Dock records the reviewer, decision, and timestamp. The approved pulse posts to the leadership Slack channel via a dangerous-ops contract that gates outbound publishes behind human sign-off. Nothing reaches leadership without a name attached.
Why this matters
The interpretive layer of project management has always lived in someone's head or a Friday doc. When the PM is out, the synthesis is lost. When an agent does the synthesis, it needs a home that outlives the chat session. Dock is that home. The pointer back to Linear or Asana keeps the platform authoritative. The agent identity and reviewer name keep the interpretation auditable. See agent identity for why every row needs a signed drafter and agent audit and compliance for what auditors ask for.
PM work compounds. A risk called yellow in W22 and red in W23 is a story, and that story only exists if rows persist. Chat transcripts do not. Spreadsheets do not carry identity. The agent collaboration primer covers the shared-workspace pattern, and Cloud 2.0 for product explains why next-generation tooling assumes agents and humans share one surface.
Read Cloud 2.0 for engineering for the engineering-org counterpart, or sign up and connect your first PM tool.
FAQ
Q: Does Dock replace Asana, Linear, or Jira? A: No. Those platforms remain the source of truth. Dock holds the agent's synthesized status, risk rationale, and reviewer decision, with each row pointing back by ID.
Q: What stops the agent from posting status without review? A: A consent gate. Outbound publishes are wrapped in a dangerous-ops contract. The agent drafts to a Dock row, the PM approves, then the publish fires. The contract refuses to run on an unsigned row.
Q: Can the agent work across multiple PM tools at once? A: Yes. The agent pulls from Asana, Linear, Jira, Monday.com, and ClickUp in one run and writes a single unified row with source_ids spanning all of them.
Q: How is this different from asking ChatGPT to summarize my projects? A: A chat transcript does not persist as a row, carry an agent identity, or answer six months later when someone asks why a project was red in W22. Both PMI's Pulse of the Profession and the Standish Group CHAOS Report trace project failure to lost context, see also Gartner's project portfolio management research. Persistent, attributed rows close that gap.
