Notion as the Team Wiki — Agent Writes the Docs Nobody Else Would

The Problem

Every startup has the same documentation lie: "We'll document it after launch." After launch becomes after the next sprint. Then after the fundraise. Then never.

PyratzLabs runs 31 agents across 8 teams. We have two Notion workspaces — Headquarter for operations, Zaiffer Data Room for investor due diligence. Both need to be current. Both were perpetually stale.

The Headquarter workspace had an architecture page from 4 months ago that described a system we'd since rewritten twice. The onboarding guide referenced tools we stopped using. The process docs described workflows that no longer existed.

The Zaiffer Data Room was worse. Cap tables updated quarterly instead of after each transaction. Financial statements lagging by weeks. Due diligence docs that investors would see and wonder if we were actually organized.

Nobody writes docs. Not because they're lazy — because writing docs has zero immediate reward and 100% opportunity cost against shipping code. The incentive structure guarantees stale documentation.

The Solution

The agents write the docs. Every time an architecture decision is made, a process changes, or a financial event occurs, the relevant agent updates Notion. Not as a separate task — as a side effect of doing the actual work.

Alfrawd coordinates. The Notion skill handles the API. The result: a wiki that's always current because it's maintained by the same entities that created the information.

The Process

The Notion integration uses the official API via the Mr.Chief Notion skill:

# Agent updates an architecture decision page
notion-cli page update \
  --page-id "abc123" \
  --title "Agent Infrastructure Architecture" \
  --content "## Current State (Updated 2026-03-13)

  - Gateway: Ubuntu 22.04, Tailscale mesh
  - Mac Node: M2 Pro, paired via Tailscale
  - Agents: 31 active across 8 teams
  - Skills: 52 installed via ClawHub
  - Session storage: Local + searchable transcripts"

The Headquarter workspace auto-populates:

Headquarter/
├── 🤖 Agent Scorecard        ← updated daily
│   ├── Agent status (31/31 active)
│   ├── Cron jobs running (14 scheduled)
│   └── Error rate (0.3% last 7 days)
├── 📋 Process Docs           ← updated on change
│   ├── Deployment workflow
│   ├── Credential rotation schedule
│   └── Incident response playbook
├── 🏗 Architecture           ← updated on decision
│   ├── Infrastructure diagram
│   ├── Decision log with reasoning
│   └── Tech stack inventory
└── 📊 Project Briefs         ← updated weekly
    ├── Stealth AM
    ├── Bookplayer
    └── Jockiz

For the Zaiffer Data Room, financial events trigger updates:

# When a cap table event occurs
notion.pages.create(
    parent={"database_id": ZAIFFER_CAP_TABLE_DB},
    properties={
        "Date": {"date": {"start": "2026-03-13"}},
        "Event": {"title": [{"text": {"content": "SAFE conversion - Series A"}}]},
        "Shares": {"number": 150000},
        "Price": {"number": 2.40},
        "Investor": {"rich_text": [{"text": {"content": "Fund III"}}]}
    }
)

Team onboarding becomes: "Read the Notion wiki." Everything a new team member or agent needs is there, and it's accurate because the agents that do the work also document the work.

The Results

The investor feedback is the metric that surprised us most. Two VCs independently commented that our data room was "unusually well-maintained for a seed-stage company." They didn't know an agent was doing it.

Try It Yourself

1. Install the Notion skill via ClawHub: clawhub install notion
2. Connect your Notion workspace via the integration token
3. Define trigger rules: what events should update which pages
4. Let agents document as a side effect of their normal work

The key insight: don't create a "documentation task." Make documentation a side effect of real work. The agent already knows what happened — it just needs permission to write it down.

The best documentation is the kind nobody has to write. Make it automatic or accept it'll never exist.