Gopher-flags-resolution-

daily/ — the gopher’s daily posts. TRANSIENT: wiped after Claude ingests them.

Jake, 2026-10-20: “Gopher posts daily numbers / tasks. This includes the regular stuff I bring here. Bond market. Earnings. ZH posts. AI business and investment. MW/$. Financing fragility etc… you read the daily posts, reconcile with and make entries into the vault from there. … everything else is wiped. This place is cleared daily.”

THE RULE

daily/YYYY-MM-DD-<task>.md          one file per task per day, Pacific date
daily/YYYY-MM-DD-HHMM-<task>.md     if a task runs more than once a day

Any format. Post whatever the task produced. Bond-market close, earnings prints, ZH items, AI business/investment, MW/$, financing-fragility signals — the things Jake used to paste into chat by hand. “Ran, found nothing” is a valid post — it separates did not run from ran, world was quiet.

WHAT HAPPENS TO A POST

  1. Claude reads it (tools/gopher_read.py in Wiki-Brain shows only what is new).
  2. Claude reconciles it against the vault — perimeters, prior statements, republish dates — and files what matters as vault entries. The vault is the archive. This directory is not.
  3. Anything that is a watchable with an instrument, a closing artefact and a date → OPEN.md.
  4. The post is then DELETED from this directory, in a commit whose message says what was ingested and where it went. Git history keeps every byte — wiped from the tree, never lost.

⇒ A file still sitting here means Claude has not ingested it yet. An empty directory means caught up.

WHAT THE GOPHER DOES NOT HAVE TO DO

Know flag IDs · mark anything CLOSED · meet a citation standard to post · be concise. Posting is free; structuring is Claude’s job. If a post happens to resolve a flag in OPEN.md, say so and give the quoted text + dated URL/filing — that is the gopher’s half of the close.