You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Standups summarize state already in memory. The memory scanner promotes durable findings *into* memory from the day's sessions. Run order: standup -> scanner -> overnight ingester sweeps -> morning report next day.
124
+
Standups summarize state already in memory. The memory scanner promotes durable findings *into* memory from the day's sessions. Memory care checks existing cards for stale facts. Run order: standup -> scanner -> overnight ingester sweeps -> memory-care scan -> morning report next day.
Copy file name to clipboardExpand all lines: INSTALL_FOR_AGENTS.md
+4Lines changed: 4 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -32,6 +32,10 @@ You may be invoked as the agent behind any of these. They are isolated sessions;
32
32
33
33
See `memory/cards/pipeline-standups.md` and `memory/cards/memory-scanner.md` for the full job shape.
34
34
35
+
If this workspace is one of several agent homes, read `memory/cards/multi-workspace-handoff-admin.md`. Secondary setups should inform the canonical owner through handoffs rather than keeping separate durable truth.
36
+
37
+
If you are maintaining an established card set, read `memory/cards/memory-care-staleness.md` before editing stale cards. Refresh only from current source-of-truth files or route to manual review.
38
+
35
39
## If your harness loads a compact context
36
40
37
41
Some harnesses load a generated `llms.txt` or `llms-full.txt` instead of every bootstrap file individually. If those exist in this workspace, follow them and rebuild via the workspace's build script when source docs change. If they do not exist, default to reading the files listed in "Start here" directly.
The ingester is conservative. Handoffs with `Recommended memory action: create-card` and a safe filename + frontmatter become memory cards. Handoffs that route to `TOOLS.md`, `USER.md`, `rules/*.md`, or `.learnings/*.md` get appended. Anything ambiguous lands in `memory/handoff-inbox/` for manual review.
86
86
87
+
If you administer multiple agent setups, keep one canonical owner and pull remote handoffs into staging directories before ingesting them. See `memory/cards/multi-workspace-handoff-admin.md`.
88
+
87
89
## 7. Scrub before publishing
88
90
89
91
```bash
@@ -106,3 +108,4 @@ The fragments are JSON files you can inspect and merge into your `openclaw.json`
106
108
- Read [the cookbook](https://github.com/solomonneas/solos-cookbook) for the deep version of every concept here.
107
109
- Customize `USER.md` and `TOOLS.md` with your real preferences and runbooks (kept private; do not commit personal details).
108
110
- Wire the ingester on a cron or a manual end-of-day workflow.
111
+
- Add a memory-care staleness scan when your card set starts to matter. See `memory/cards/memory-care-staleness.md`.
The ingester is intentionally conservative. Safe card handoffs become cards. Targeted updates append to the right file. Ambiguous material gets kicked out for review instead of being trusted automatically.
96
98
99
+
For users running multiple agent homes, treat the owner workspace as the hub. Remote or secondary workspaces can write handoffs into their own `.claude/memory-handoffs/` directories, then a trusted sync pulls those files into a staging inbox on the owner. That keeps agents informed about what happened elsewhere without creating multiple canonical memories.
100
+
97
101
## Related
98
102
99
103
-[Solomon's Cookbook](https://github.com/solomonneas/solos-cookbook): the long-form guide and reference docs
Use `memory/cards/multi-workspace-handoff-admin.md` as the public-safe pattern for pulling handoffs from secondary agent homes into one canonical owner. Use `memory/cards/memory-care-staleness.md` for the card decay scanner and safe refresh loop.
Copy file name to clipboardExpand all lines: memory/cards/handoff-flow.md
+6Lines changed: 6 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -17,6 +17,12 @@ Claude Code, Codex, and other side harnesses write Memory Handoffs to `.claude/m
17
17
5. Handoffs route to: a memory card, an appendable document, or the review inbox.
18
18
6. Processed handoffs move to `.claude/memory-handoffs/processed/`.
19
19
20
+
## Multiple Workspaces
21
+
22
+
If you administer more than one agent setup, keep this flow hub-and-spoke. Secondary workspaces write local handoffs, then the canonical owner pulls them into staging directories and runs the same ingester. This lets agents on separate machines or repos inform each other about what changed without creating competing memory stores.
23
+
24
+
See [multi-workspace-handoff-admin](multi-workspace-handoff-admin.md) for the full pattern.
25
+
20
26
## Auto-promotion rules
21
27
22
28
Only three handoff shapes can silently mutate canonical memory. Everything else lands in `memory/handoff-inbox/` for manual review.
Memory needs care after it is written. Durable cards can become wrong when services move, workflows change, models are renamed, or project priorities expire. A staleness checker gives the memory owner a queue of cards that need refresh, without letting an agent rewrite sensitive or judgment-heavy knowledge blindly.
10
+
11
+
## Reference Loop
12
+
13
+
```text
14
+
memory/cards/*.md
15
+
|
16
+
v
17
+
card decay scanner
18
+
|
19
+
v
20
+
memory/cards/decay/scan-latest.json
21
+
memory/cards/decay/refresh-queue.json
22
+
|
23
+
v
24
+
safe refresh agent or manual review
25
+
```
26
+
27
+
## Scanner Output
28
+
29
+
Store scan state under `memory/cards/decay/`:
30
+
31
+
-`scan-latest.json` - latest full scan, counts, card statuses, decay ratios, and refresh queue size.
32
+
-`refresh-queue.json` - small queue of cards that are stale enough to review.
33
+
34
+
The scanner should report at least total cards, fresh count, aging count, stale count, critical count, and refresh queue size.
35
+
36
+
## Safe Refresh Rules
37
+
38
+
Only auto-refresh cards when current facts are grounded in local source-of-truth files read during the run. Good sources include `TOOLS.md`, `MEMORY.md`, recent `memory/YYYY-MM-DD.md`, local project docs, local scripts, and repo health reports.
39
+
40
+
Do not auto-refresh cards that require human judgment, personal context, career decisions, school work, business strategy, or outside research. Put those in a manual queue.
41
+
42
+
Never refresh by only bumping an `updated:` date. The content must change because a current source proves it should change.
43
+
44
+
## Suggested Schedule
45
+
46
+
- Daily scanner during quiet hours.
47
+
- Safe auto-refresh shortly after the scanner, capped to a small number of cards.
48
+
- Weekly deep report for manual review of sensitive or repeatedly skipped stale cards.
If the queue grows for several days, either the refresh agent is too conservative, the source-of-truth files are stale, or the cards need manual pruning.
Copy file name to clipboardExpand all lines: memory/cards/memory-scanner.md
+4Lines changed: 4 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -86,6 +86,10 @@ Avoid promoting during active sessions because card writes invalidate prefix cac
86
86
- the prompt should embed the skip-rules and cost controls above
87
87
- output goes either directly to `memory/cards/*.md` (if your harness can write there) or through `.claude/memory-handoffs/` for the conservative ingester to route
88
88
89
+
## Relationship to Memory Care
90
+
91
+
The memory scanner captures new durable knowledge. The memory-care staleness loop reviews old cards for drift. Run both: scanner for new facts, staleness checker for old facts that may no longer be true. See [memory-care-staleness](memory-care-staleness.md).
92
+
89
93
## Anti-patterns
90
94
91
95
-**Auto-promoting raw session fragments into `MEMORY.md`.** The index loads on every session; appending fragments nightly bloats it past the bootstrap budget and turns the on-load cache cost into a monthly tax. Write cards instead.
0 commit comments