Skip to content
Dashecorp Rig Docs

User story: how should the rig handle docs vs memory (2026-04-18)

Migrated from Plane work item DASHE-14 on 2026-04-18. Original Plane workspace retired; this is the canonical home.

As a rig operator

I want a clear, enforced separation between canonical docs (git source of truth) and operational memory (MCP-backed Postgres), with explicit rules for agents on what goes where.

So that I can trust what’s authoritative when reading on mobile, and agents consistently write knowledge to the right layer without drift.

Acceptance criteria:

  • Rig-docs and memory MCP have non-overlapping responsibilities documented in AGENTS.md
  • Agents follow file-back rule: durable learnings to rig-docs PR; ephemeral operational state to memory MCP
  • Lint operation detects drift (memory that should be docs, docs that duplicate memory)
  • Mobile-readable summary of the split on rig-research.pages.dev

Priority: medium. Not blocking MVP but compounds over time.

🔁 Flow (diagram-as-code)

Section titled “🔁 Flow (diagram-as-code)”

Mermaid source embedded below. If your viewer renders Mermaid live, you see the diagram. If not, you see the source — which IS the artifact (no PNG, no SVG, no drift).

flowchart LR
    H["Human (mobile)"] -- "writes user story<br/>(GitHub mobile app)" --> I["GitHub issue in rig-docs"]
    I -- "picked up" --> A["Agent (Dev-E / Review-E)"]
    A -- "read_memories BEFORE work" --> M["Memory MCP (Postgres)"]
    A -- "authors PR<br/>(markdown under src/content/docs/)" --> D["rig-docs"]
    D -- "Review-E gate" --> D2["merged to main"]
    D2 -- "Cloudflare Pages deploy" --> S["rig-research.pages.dev"]
    A -- "write_memory AFTER merge" --> M
    L["Lint (weekly)"]
    M -. "hit_count>=5, importance>=4" .-> L
    L -. "promote to docs" .-> D
    L -. "archive if 30d unused" .-> M
View Mermaid source
flowchart LR
    H["Human (mobile)"] -- "writes user story<br/>(GitHub mobile app)" --> I["GitHub issue in rig-docs"]
    I -- "picked up" --> A["Agent (Dev-E / Review-E)"]
    A -- "read_memories BEFORE work" --> M["Memory MCP (Postgres)"]
    A -- "authors PR<br/>(markdown under src/content/docs/)" --> D["rig-docs"]
    D -- "Review-E gate" --> D2["merged to main"]
    D2 -- "Cloudflare Pages deploy" --> S["rig-research.pages.dev"]
    A -- "write_memory AFTER merge" --> M
    L["Lint (weekly)"]
    M -. "hit_count>=5, importance>=4" .-> L
    L -. "promote to docs" .-> D
    L -. "archive if 30d unused" .-> M

Updated 2026-04-18 (same day): Original diagram had a Plane["Plane work item"] node between Human and GitHub issue. The Plane intake was retired the same day; the diagram now shows direct GitHub-issue authoring via the GitHub mobile app. Rationale in proposals/2026-04-18-docs-tooling-decision.md.

Render live: mermaid.live (paste source) · source in rig-docs (canonical)