feat(memory): keep the family wiki fresh automatically (curator sidecar)#33
Merged
Conversation
Selection flags combine and repeat so one invocation covers every page a filing burst touched. Display names normalize to bucket slugs.
Debounced persons+home rebuild after filings settle, nightly full sweep as self-healing catch-all. Own slim image, memory-owned env.
Without it, any boot after the configured time fired an immediate full sweep. Found live on the Simpsons rig.
Same ls-remote-then-ff-pull semantics, moved from the quartz entrypoint to the curator's 30s tick. Pull runs even with rebuilds off.
Same evidence now yields the same page byte-for-byte (verified on the rig); pages only change when their evidence does.
Overview not archive: recency-weighted About, themed interests, capped activity, no ledger content, omit empty sections.
Mechanical citation renumbering + explicit new-evidence block; the model keeps wording stable and only works in what changed.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
curatorsidecar keeps the family wiki current without anyone running a command. It owns thegit pullfrom Forgejo and regenerates pages in two modes: a debouncedincremental rebuild (the members touched by a filing, plus home) once a burst of commits settles, and a nightly full sweep (home, every member, every topic) as the
self-healing catch-all. A typical filing costs 2-3 LLM calls, so "I filed Homer's letter, Homer's page knows" is nearly free.
stack memory wikistill works as the manualoverride.
:ro; the curator is the only writer of the working copy. One component owns sync, so there's onefailure story: if the curator is down, the vault and wiki go stale together, and turning off
wiki_auto_rebuildstops rebuilds but never the pull.WIKI_TEMPERATUREoverride for experiments) and member-page regen is anchored to the previousversion, so the same evidence yields the same page instead of churning on every rebuild.
.gitignorekeeps Obsidian's per-user UI state out of git, so opening the vault in Obsidian doesn't spuriously trigger rebuilds.[memory]knobs:wiki_auto_rebuild,wiki_rebuild_quiet_secs,wiki_nightly.LLM.completegains an optionaltemperaturearg (defaults tothe server default, fully backward-compatible).