diff options
| author | Craig Jennings <c@cjennings.net> | 2026-07-13 14:51:27 -0500 |
|---|---|---|
| committer | Craig Jennings <c@cjennings.net> | 2026-07-13 14:51:27 -0500 |
| commit | 44bc34452766fc1d87232b11ddb5d582731ff7c2 (patch) | |
| tree | 151dd3df78d519008fa95d2ba620d18d93332ceb /claude-rules/knowledge-base.md | |
| parent | e91073d9675a5958616078fa2d26d4bd779e8056 (diff) | |
| download | rulesets-44bc34452766fc1d87232b11ddb5d582731ff7c2.tar.gz rulesets-44bc34452766fc1d87232b11ddb5d582731ff7c2.zip | |
feat(runtime): complete the hook, MCP, and memory portability inventories
The new inventories doc maps what's actually Claude-bound. Hooks: only PreCompact and Stop-teardown carry porting decisions, both now decided (prose downgrade, Codex notify or manual). MCP: everything ports mechanically except paging, since signal-mcp exists only claude.ai-side, so the Signal-pager task gains runtime portability as a second motivation. Memory: the KB is already the cross-agent store, and knowledge-base.md now tells agents without harness memory to capture into the session log. Three inventory child tasks closed as dated entries under the generic-agent-runtime parent.
Diffstat (limited to 'claude-rules/knowledge-base.md')
| -rw-r--r-- | claude-rules/knowledge-base.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/claude-rules/knowledge-base.md b/claude-rules/knowledge-base.md index 5658498..d8aa6a6 100644 --- a/claude-rules/knowledge-base.md +++ b/claude-rules/knowledge-base.md @@ -53,7 +53,7 @@ Pull before writing, commit and push after (`git -C ~/org/roam add -A && git com ## Capture, then promote -Harness memory (`~/.claude/projects/<enc>/memory/`) remains the per-project capture layer: fast, automatic, allowed to be at-risk. At wrap-up (or a task audit, or an explicit prompt), promote facts that meet the inclusion bar into the KB as nodes. The wrap-up workflow asks; answer it honestly — promotion discipline is what keeps the capture layer from silting up. +Harness memory (`~/.claude/projects/<enc>/memory/`) remains the per-project capture layer: fast, automatic, allowed to be at-risk. An agent running without harness memory (a non-Claude runtime) captures into its session log instead and promotes from there — the promotion discipline is the same. At wrap-up (or a task audit, or an explicit prompt), promote facts that meet the inclusion bar into the KB as nodes. The wrap-up workflow asks; answer it honestly — promotion discipline is what keeps the capture layer from silting up. ## Inventory |