Stories A promise's telling · EXPLANATION — the companion read for `one.ie/web/src/lib/CLAUDE.md § The brain and the edge`. NOT A PROMISE. `do-promise-lint.sh ram` FAILS with "no deliverables schedule", and that is correct — this file has no schedule of work because RAM is not a feature with one. The promise that delivers this idea is `tql-edge.md`, which lints clean with 8 deliverables. Do not invent deliverables here to make the lint green: the doc set is two explanations under one slug (`ram.md`, the idea and the ceiling; `ram-docs.md`, the manifest mechanism), which the taxonomy permits. What it forbids is saying the same thing twice.
ram
Every request-path read is answered from RAM at the tier it names, except a read that guards a write.
The seven beats
- World
- TypeDB, the brain of record, in Virginia; the edge, in every Cloudflare city; three tiers between them. Groups
- Cast
- The receivers that must answer, the people and agents waiting on them, and the engineers who kept aiming the fix at the wrong number. Actors
- Knock
- A request that cannot be answered without crossing the Pacific: 1.2–1.6 s for a live query. signal
- Want
- The answer served from memory, with the tier it came from named beside the number. Things
- Way
- Derive, don't dump: TypeDB computes the shapes the hot questions need, RAM serves them, and the staleness ladder decides which shapes may move. Paths
- Turn
- health went from 465 ms to 76 ms with no query changed — the number was the worker's always-loaded floor, not geography. Events
- Lesson
- Open — a Lesson is learned by someone, and this one is not written yet. Learning
This story carries its beats but no written telling yet — text/ram.md has no “The story” section.
Connected to
Every link here was checked against the repo when the page was built. 5 names the story uses could not be found and are shown without a link.
Agents
Each opens a chat with that agent.
Skills
Each opens the skill's page.
- typedb
- cloudflare
- perf
Paths
The flows this story walks — trigger → step → step.
- trigger: a door reads red in signal-watch.sh → agent: perf-engineer names the tier → agent: edge-keeper moves the read or reports why it may not → tool: edge-read-ratchet.mjs --update
Tools
Receivers and scripts it signals.
- signal-watch.sh
- edge-read-ratchet.mjs
- api/src/brain.ts /brain/*
- one.ie/web/src/lib/brain-snapshot.ts
Docs
What derives from this file.
Events
Every event is a signal; each names the path it marks or warns.
- fn:run · from any receiver that needs a rule answered marks fn:run → edge on edge:true; warns on a 503 step budget tags: speed, edge
Transactions
- none
Analytics
- one.ie/web/.edge-read-baseline.json — 195 reads / 63 files at 2026-09-21
- .claude/.signal-watch.jsonl — door latency by tier