Memory Ledger

A native method for Grok Bot

Memory Ledger

Standing rules live in a Page and a small file vault. Bots read a short index first, then one file. Nothing changes until you say yes.

Four layers, one owner

Give this job to the bot that already coordinates the rest. Specialists do not keep their own copies of the rules.

  1. 01

    Page

    Decisions Log

    The human-readable source of truth. One sentence per rule, with a date, a source, and what it replaces. Pin it.

  2. 02

    Catalog

    INDEX.md

    A one-line list of every file. Bots read this before they open anything. Newest first.

  3. 03

    Vault

    Dated files

    The full note lives in a typed folder. A bot loads only the file whose topic matches.

  4. 04

    Guard

    Monday routine

    Looks for stale notes, contradictions, and index drift. Proposes a list. Changes nothing until you say yes.

What gets written

The vault sits on the computer every bot already shares. The index is the only file they should open by habit.

Folder

/workspace/memory/
├── README.md
├── INDEX.md
├── decisions/
├── preferences/
├── projects/
└── findings/

Each file

Named YYYY-MM-DD-short-topic.md. Same four lines as the Page.

YYYY-MM-DD | Type: Decision | Topic
One clear sentence of the rule or decision.
Source: short quote + date
Supersedes: (previous entry or "none")

Standing instruction

Before answering anything that depends on a past decision, rule, or preference:
1. Read the Decisions Log Page.
2. Read /workspace/memory/INDEX.md.
3. If a matching topic appears, load only that full file.
4. Prefer the Page entry if both exist. If unsure or you find a conflict, say so and quote both.

Rules that keep it honest

  • 01The Decisions Log Page wins over a file when both exist.
  • 02The newest dated file wins over an older one.
  • 03One bot writes. Every other bot only reads.
  • 04Writes happen only after you say yes.
  • 05No passwords, tokens, or private client material.

Index drift means INDEX.md no longer matches the files: a missing line, a path that points nowhere, or lines out of date order. The Monday routine quotes the mismatch and waits.

Give this to your main bot

Paste it once into the bot that should own the system. It creates the Page, the folders, the index, the standing instruction, and the Monday routine.

You are now the owner of a shared memory system for this account. Implement the following exactly. Change nothing irreversible without my explicit yes.

1. Create and pin a Library Page titled **Decisions Log**. Use this exact entry format going forward:

YYYY-MM-DD | Type: Decision | Topic
One clear sentence of the rule or decision.
Source: short quote + date
Supersedes: (previous entry or "none")

Only you append or edit this Page, and only after I approve. Pin it so it stays at the top of the Library.

2. On the shared computer, create this folder structure:

/workspace/memory/
  README.md
  INDEX.md
  decisions/
  preferences/
  projects/
  findings/

Write a short README.md that explains:
- Newest dated file wins
- The Decisions Log Page wins over a file when both exist
- Conflicts must be flagged and both sides quoted
- Only you write here, and only after approval
- No credentials or private client material ever goes in

3. Create /workspace/memory/INDEX.md as a living catalog:

# Memory Index
Newest first. Decisions Log Page wins over files. Load the full file only when a topic matches.

- 2026-11-18 | Decision | Shared memory system | decisions/2026-11-18-shared-memory-system.md

Also create the matching example file in decisions/ using the same four-line header format.

4. Save this standing instruction in your own memory and in the shared memory every bot can see:

Before answering anything that depends on a past decision, rule, or preference:
1. Read the Decisions Log Page.
2. Read /workspace/memory/INDEX.md.
3. If a matching topic appears, load only that full file.
4. Prefer the Page entry if both exist. If unsure or you find a conflict, say so and quote both.

5. Create a Monday Routine (8:00 AM in my time zone) that:
- Scans native notes, the Decisions Log Page, and /workspace/memory/ for stale, duplicated, or contradictory items.
- Checks INDEX.md for drift (missing lines, dangling paths, wrong order).
- Sends me a short quoted list of proposed deletes, merges, or index fixes.
- Changes nothing until I say yes.
- After approval, updates the Page, the matching file, and INDEX.md together (newest first).
- Stays quiet if nothing needs attention.

6. Confirm when done by showing:
- The Decisions Log Page link
- The contents of INDEX.md
- Confirmation that the folders and Routine exist
- The standing instruction as saved

Do not create new bots. Keep ownership here. Start by creating the Page and folders.