A syndicate lead asks the same question on every deal: who looked at this, what did they decide, and why. AngelList runs the allocation, signatures, and capital movement. Carta holds the cap table once the wire clears. Neither tracks the agent reasoning that happened in between. Dock adds that missing layer. The screening agent files a deal brief, the lead investor signs off (or rejects), and the row keeps a pointer back to the AngelList deal and the Carta SAFE. The result is a syndicate operation where attribution is the default, not a memory exercise.
AngelList and Carta 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 Deal Brief table
| Deal | AngelList ref | Stage | Agent recommendation | Lead reviewer | Decision | Carta SAFE |
|---|---|---|---|---|---|---|
| Lumen Robotics | al-deal-8821 | Seed | Pass (TAM thin) | sarah@fund | Rejected 2026-05-28 | n/a |
| Korova Health | al-deal-8847 | Pre-seed | Allocate $250k | govind@fund | Approved 2026-05-29 | carta-safe-4412 |
| Tessera AI | al-deal-8902 | Seed | Hold for diligence | sarah@fund | Pending | n/a |
Each row is written by the screening agent and signed by a human lead before allocation opens. The Carta column populates after the wire settles. A weekly view rolls these into pacing, pass rates by partner, and time-to-decision.
One workflow: syndicate deal arrives
The AngelList webhook fires when a deal is shared with the syndicate. The agent reads the deck and data room via the AngelList API, drafts a one-page brief, scores against the fund thesis, and writes a row to Deal Brief with recommendation set. A Slack ping reaches the assigned lead with a link to the row. The lead opens the row, reads the brief, and clicks Approve or Reject. On approve, Dock opens the AngelList allocation flow with the recommended check size pre-filled. Post-close, a Carta watcher links the resulting SAFE back to the row. The agent never moves money. It only writes opinion and waits for a signed human decision, which matches the agent audit and compliance pattern.
Why this matters
LPs ask for attribution on every quarterly report. Without Dock, a syndicate lead reconstructs decisions from email threads and AngelList DMs. With Dock, every brief is a row, every approval is a signature, every pass is logged with a reason. NVCA reported 13,608 US venture deals worth $170.6 billion in 2023, with first-time financings at their lowest since 2017 (NVCA Yearbook). AngelList's ledger has moved over $80 billion across 50,000+ funds and syndicates (AngelList Venture). At that volume, attribution stops being a nicety and starts being a fiduciary baseline. The agent identity on each row is a real principal with scoped credentials, not a shared service account, which is the model we describe in agent identity lifecycle.
For founders on the other side of the deal, the mirror pattern lives in Dock for founders. For broader investor workflows beyond syndicates, see Dock for investors. For diligence-heavy deals that need deeper memo work, see Dock for research and the companion founder-side guide.
Open a Dock workspace, point it at your AngelList syndicate, and your next deal brief writes itself with attribution attached.
FAQ
Does the agent move capital on AngelList? No. The agent reads deal materials and writes a recommendation. Allocation and signature happen in AngelList under the lead investor's account.
How does Dock know which Carta SAFE matches which deal? A Carta webhook fires on SAFE creation. Dock matches by company name and date window, then asks the lead to confirm the link before the row closes.
What happens if the agent's recommendation conflicts with the lead's decision? Both are stored. The row keeps the agent's score and the human override, with a free-text reason field. Quarterly pacing reports show override rate per partner.
Can LPs see the Dock rows? Not directly. LPs see the quarterly report Dock generates from the rows. Raw rows stay inside the GP workspace with reviewer-scoped permissions.
