On the floor

Office mascots: memecoins listed on Robinhood, used here as decoration.

  • review-gated
  • git-native
  • local-first
  • MIT

Agents propose. You stamp. Now it’s on file.

stampd is a local-first, git-native knowledge base for coding agents. Agents file claims with cited, content-hashed sources. Nothing goes on file until a human stamps it.

pipx install stampd

Scroll to walk the floor · Click any coin

Already on staff with

  • Claude Code
  • Cursor
  • Codex
  • Windsurf
  • Zed
  • Cline
  • OpenClaw
FL 01 The in-tray

Six memos waiting.
Your stamp, your call.

Agents drop proposals in your in-tray. Each one names a claim, the file it came from and a content hash. Approve it, bounce it, or mark it superseded. Go on, try it.

STAMPD INBOX ▸ 6 PENDING

    A approve · R reject · S supersede

    STAMPD-94
    • 100%on your machine
    • Everywrite stamped by a human
    • Everyclaim cites a hashed source
    • 0coins in the morale jar
    FL 02 The mail route

    How a memo becomes knowledge.

    Five stops, one house rule: nothing gets filed without a stamp.

    1. In-tray
      01

      Propose

      Your agent files a proposal as a YAML memo in .stampd/. A claim has to cite its source: no evidence, no memo.

      • MCP
      • JSONL
      • CLI
      $ stampd propose \
          --claim "Webhooks retry 5x, base 2s" \
          --cite src/payments/webhooks.py#L88
      ✓ filed m-0142  sha256:9f2c41e0…
    2. Manager’s desk
      02

      Review

      Review reads like code review. Batch the queue, diff a memo against what’s already on file, and blame any fact back to the memo that brought it in.

      $ stampd review --batch
        m-0142  webhooks retry    +1 cite
        m-0143  pnpm, not npm     +2 cites
        m-0147  /v2/export        supersedes c-118
    3. The stamp
      03

      Approve

      Every surface calls the same approve(). The approver can never be the proposer, and each decision is appended to a log nobody rewrites.

      $ stampd approve m-0142 m-0143
      ✓ APPROVED ×2  by you@laptop
        → log #2291, #2292 (append-only)
    4. Filing cabinet
      04

      Compile

      stampd compile drafts wiki pages from approved claims and machine-checks every citation. One broken cite or dead wikilink and the draft is dropped.

      $ stampd compile
        wiki/payments.md  3 claims · cites ok
        wiki/exports.md   1 claim · cites ok
      ✗ wiki/flags.md     dropped: broken cite
    5. Morning briefing
      05

      Recall

      A session-start hook hands your agent the approved digest; kb.context serves cited context on demand. Facts change by supersede, contradict or archive, never by silent edit.

      # session start
      → digest: 42 approved claims
      $ kb.context "export api"
        c-131  /v2/export replaces /v1  [adr/0019]
    House rule #1: no stamp, no file.
    FL 03 The corkboard

    Every string is typed. Every pin was approved.

    Claims, sources, entities and pages, joined by edges a human signed off on. Hover a card to trace its strings. Drag cards around; the yarn follows.

    • claim
    • source (hashed)
    • entity
    • compiled page
    • typed edge
    FL 04 The logbook

    The printer never stops. It never erases.

    Every proposal, stamp and supersede is appended to .stampd/log.jsonl, newest first. Your history is a file you can grep.

    STAMPD LQ-1994

      append-only · one JSON line per decision · signed by whoever stamped it

      FL 05 Quarterly report

      Measured, not claimed.

      Same bug-fix task, same model, same repo. Run it with and without stampd and compare the medians. Numbers go on this slide once they’re measured, not before.

      One bug-fix task: with vs. without stampd

      median of repeated runs · lower is better

      without stampdwith stampd

      Each figure will link to a step-by-step reproduction, so you can rerun it on your own repo.

      Inter-office memorandum

      To:
      Every agent on staff
      From:
      Management
      Date:
      Today
      Re:
      Why everything gets stamped

      Why a stamp.

      Effective immediately, no fact enters the knowledge base without a stamp. This is not bureaucracy for its own sake. An agent that remembers the wrong thing is worse than one that remembers nothing, and the most reliable filter we know of is a person reading the memo first.

      Out thereIn here
      Memory that writes itself, unreviewedMemory a human signed off on, memo by memo
      Graphs guessed from co-occurrenceTyped edges, each one approved
      A database per user, on someone’s serverYAML and markdown, versioned in your repo

      Questions? It’s all in the HR handbook, FL 08.

      — mgmt

      FL 07 The break room

      Coworkers of the month.

      Our office mascots: memecoins you can find listed on Robinhood. They don’t review code, but they keep morale up. Click a coin to flip it.

        Decoration only. stampd isn’t affiliated with, endorsed by or sponsored by Robinhood or any of these tokens or their communities. Availability varies by region. Nothing here is financial advice.

        FL 08 HR handbook

        Asked at the water cooler.

        Pull a drawer. Everything new hires ask about stamping, storage and stale facts.

        FL 09 Time clock

        Clock in.

        Start stamping what your agent knows. One install, one folder in your repo, zero servers.

        pipx install stampd
        Time card
        NAMEyou
        IN--:--
        DAY---
        STATUSwaiting

        STAMPD TIME RECORDER