memorable
$ memorable recall "remediate the high disk usage alert"
0.860 procedures/e08f3b56-high-disk-usage [lexical,semantic]
$ memorable show procedures/e08f3b56-high-disk-usage
Decisive steps last time:
1. [execute] Clear: old build cache
An Ops Agent Remediates Without
A Record Of The State It Acted In.
Match, Replay, Record.
Memorable keeps the path that worked and hands it back before the next run.
The alert comes in. The stored precondition is checked against the live state before anything runs.
Read-only steps run silently. The write step pauses at an approval.
The postcondition is checked, the outcome stored, and an audit line written for the recall.
memorable
$ memorable recall "restart the stuck order worker"
0.87 procedures/5be2a9c0-restart-worker
precondition: queue depth > 500, worker idle
How It Works For Ops Agents.
Your harness traces come in at run end. Systems of record are read through the agent, never copied.
{ 01 }
Preconditions and postconditions
An action fires only in the state it was learned in, and is checked after it runs.
What Memorable Reads.
2 CONFIGURED
Your harness traces
One trace per run from the ops agent you already run
Systems of record
Read through the agent's own tools; only the prompt and allow-listed arguments leave the machine
