Core modules
Log it once, look it up later.
Reads and writes the memory of your workspace. It adds rows to your numbers log, each with a source and a confidence, writes a file for every decision with its reasons, adds lessons and glossary terms, and answers questions like what your latest number is or whether something was already decided. When two facts clash, it records which one wins and keeps the loser on file.
- Old rows never edited
- Every row needs a source
- Conflicts logged, not hidden
At a glance
- Group
- Core modules
- Command
- /memory
- Uses
- A figure, a choice or a question
- Writes
- Ledger rows, decisions, lessons
- Sends
- Nothing. Drafts only.
01When to use it
Whenever a fact should stay on record.
- A metric moved, reported by you or by a workflow, and belongs in the numbers log.
- A choice was made that future work has to respect.
- A lesson worth reusing came up, or a term needs one shared definition.
- You are about to state a number and want its latest known value first.
- You want to know what moved, what is on file about a topic, or whether this was already decided.
- Two facts disagree, and the conflict needs settling and logging.
Not for
- Flagging a gap, a stale fact or a correction for later triage. Use /signal
- Thinking a decision through before it is made. Use /decision-toolkit
- Filing a whole meeting transcript at once. Use /meeting-capture
02What it needs
The fact, where it came from, how sure.
- To log a number: the metric, its baseline, current value and target, the source, a confidence (confirmed, reported, inferred or stale) and a note.
- To record a decision: the context, the decision itself, the reasons and a confidence.
- For a lesson, the lesson and what prompted it. For a term, the term and its definition.
- For a lookup, a metric, a topic, or simply what moved.
- To settle a conflict, the facts that disagree, with their dates and confidence.
03What it writes
Each kind of fact has one home.
- Memory/kpi-ledger.md
- One new row at the bottom, dated today, in a fixed column order. A metric logged for the first time starts with its baseline equal to its current value.
- Memory/decisions/YYYY-MM-DD-{slug}.md
- A file per decision with its context, the decision, the reasons and a confidence, linked to any earlier decision it replaces or contradicts.
- Memory/lessons.md
- A dated entry: what happened, the lesson, and where it applies. A settled conflict is written up here too.
- Memory/glossary.md
- A new term in its alphabetical place. If the term already exists, you see the current definition and are asked before it changes.
- Memory/signals.md
- A contradiction row whenever two facts clash, so the fix gets scheduled.
- Inbox/
- A note when a request cannot be classified. When a row is refused, the note carries your request word for word and the ready row.
04Limits
What it never does.
- Edit, reorder or delete an earlier ledger row.
- Log a row that lacks a source or a confidence. You get one filled-in row to paste instead, and a copy goes to Inbox/.
- Delete the losing fact in a conflict. It stays on record beside the winner.
- Rewrite an earlier lesson, or replace a glossary definition without asking you.
- Send anything, delete files, or change prices or permissions.
- Guess what an unclear request means. One question comes first, and if that leaves it unclear, a note goes to Inbox/ and the run ends.
What stays with you.
- Pasting the ready row it hands you when a source or confidence was missing.
- Saying yes or no before an existing glossary definition is replaced.
- Supplying the evidence that would move a reported figure to confirmed.
05Sample output
Rows from a numbers log.
From the numbers log of a made-up dog grooming business, with five of its eight columns shown. Every row says where its figure came from and how firm it is.
| Date | Metric | Current | Source | Confidence |
|---|---|---|---|---|
| 2026-09-26 | review-count | 64 | Google profile, read that day | Confirmed |
| 2026-09-29 | weekly-bookings | 29 | User report (chat) | Reported |
| 2026-09-30 | no-show-count | 3 | Booking system export | Confirmed |
- 2026-09-26 Confirmed
- Metricreview-count
- Current64
- SourceGoogle profile, read that day
- 2026-09-29 Reported
- Metricweekly-bookings
- Current29
- SourceUser report (chat)
- 2026-09-30 Confirmed
- Metricno-show-count
- Current3
- SourceBooking system export
Asked for the latest weekly bookings
- It reads the log from the bottom up and returns the 2026-09-29 row, with its source and confidence.
- The row note names what would make it confirmed: the booking system export for that week.
06Related skills
Often run beside it.
/signalLog a wrong or stale fact for fixing Daily operations/decision-toolkitWork through a decision and record it Build and utilities/optimizerKeep a growing workspace fast and tidy Core modules-
/setupBuild your workspace from an empty folder Core modules
07Questions
Before you run it.
Can an old row be changed?
No. The log only grows: every entry is a new row at the bottom, dated the day it was added. Earlier rows are never edited, reordered or deleted.
What if I give it a number with no source?
It does not log it as given, and it does not hand you a form to fill. It writes one complete row for you to paste, with a rough spoken figure marked reported from chat and a note on what would make it confirmed, and it leaves a copy in Inbox/ so the gap stays visible.
What happens when two facts disagree?
The newer fact with the higher confidence wins. The other stays on record, the contradiction is written into your lessons file, and a row goes to the signals queue so the fix gets scheduled.
Do other skills write to the same log?
Yes. A daily operations run adds a ledger row whenever it moves a metric, and the SEO skills add rows beside their findings. You use memory to add a row yourself, or to ask what the log already holds.
Have us build it
We can build it for you.
Start with the free plan. A person names the first fix.