Gopher-flags-resolution-

Gopher ⇄ Flags Resolution

A direct two-way channel between Claude (the Wiki-Brain vault) and the gopher retrieval tool. Set up by Jake, 2026-10-20.

Read in this order

  1. PROTOCOL.md — the rules.
  2. OPEN.md — the channel: open flags, persistent until resolved. The gopher’s work list.
  3. daily/ — the gopher’s daily posts, transient, wiped after Claude ingests them.
  4. LEDGER.md — resolutions, corrections, disputes. Permanent.

The loop

 all day     gopher posts numbers / prints / ZH / signals ──▶ daily/
 ~9:53pm PT  Claude assembles the nightly prompt FROM OPEN.md ──▶ prompts/
 overnight   gopher works the open flags ──▶ daily/  (resolutions with quoted text + dated URL)
 ~7:19am PT  Claude ingests daily/ → vault · resolved flags → LEDGER + vault, out of OPEN.md
             · new watchables → OPEN.md · daily/ WIPED · INBOX refreshed · day stamped

The vault is the archive. This repo is the buffer. Wiped = out of the tree, never lost (git).

The four rules, short

  1. Claude posts prompts and flags; the gopher posts findings back.
  2. Corrections to numbers are cited by both parties, in LEDGER.md.
  3. Both tools post. Claude has standing overrule in disputes.
  4. No flag closes without cited sources confirmed by both tools.

Why this exists

Wiki-Brain’s weak spot is not knowledge, it is noticing. On 2026-10-20 a SpaceX quarterly report was missed because its date field held ⬜ instead of a date — and a sweep then found nine more flags with unresolved dates, each a live watchable with no calendar entry. This channel exists so that unknowns get chased by the tool that is good at fetching, and confirmed by the tool that is good at checking, with neither able to close a question alone.