Map vs Ledger
Present zones on the wall. Past decisions freeze in the ledger.
R7 · BLEED HERO · STAMP CENTER
The Titan is the headline.
Full-bleed zone wall in motion. Clay still speaks.
v01 · hero bleed
01 · problem
Belief is not a vault.
Agents store what they thought. Fleets need what was verified against the tree. Unverified cards wear the costume of done.
- Stale prose without a seal
- Map mixed with ledger history
- Ghost globs · zero hits · silent
02 · the seal
Press only what you reviewed.
The hand is the honesty. verifiedAt is a seal in clay — review first, stamp after, never for theater.
v02 · stamp press · press only what you reviewed
Until the hand presses, the honest string is unverified. Gaps stay visible on the wall. The bleed hero shows the map; this section is the law of the hand.
03 · solution
Code-verified memory.
owns.globs
git ls-files is the truth. Zero hits = hard error.
verifiedAt
SHA after human review — or unverified. No fake green.
04 · pillars
What the clay keeps
01
Plain vault
Markdown + YAML. Greppable.
02
Generated index
atlas build · gaps visible.
03
Honest freshness
From git history, not vibes.
04
Zero runtime deps
Thin toolchain. Travels with the repo.
05 · quickstart
Raise the vault
Four clicks. Copy each line. Stamp only what you reviewed.
$
npm install -g memory-atlas
#1 Install globally — bins:
atlas · memory-atlas
$
atlas init
#2 Scaffold the vault in this repo
$
atlas check
#3 Verify claims + ledger
$
atlas stamp <slug> && atlas build
#4 Stamp reviewed zones, rebuild index
$
npx memory-atlas init
#1 No global install — run from the registry
$
npx memory-atlas check
#2 Verify without linking
$
npx memory-atlas build
#3 Rebuild map/index.md
$
git clone https://github.com/muslewski/memory-atlas.git
#1 Clone the product repo
$
cd memory-atlas && npm install && npm link
#2 Link the CLI from source
$
atlas init
#3 Same verbs as the published package
✓ Prefer
memory-atlas if MongoDB Atlas CLI owns atlas on PATH.