From d9ac615b67530c3dbb7b4dbd3bd38e247d81e1b5 Mon Sep 17 00:00:00 2001 From: Claude Bot Date: Mon, 26 Oct 2026 14:37:08 +0100 Subject: [PATCH] docs(encyclopedia): which group fingerprint consolidation remembers Co-Authored-By: Claude Opus 5.5 --- .../specs/2026-10-26-encyclopedia-consolidation-design.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/superpowers/specs/2026-10-26-encyclopedia-consolidation-design.md b/docs/superpowers/specs/2026-10-26-encyclopedia-consolidation-design.md index d684a8b..3c4edc5 100644 --- a/docs/superpowers/specs/2026-10-26-encyclopedia-consolidation-design.md +++ b/docs/superpowers/specs/2026-10-26-encyclopedia-consolidation-design.md @@ -38,7 +38,7 @@ Interleaving keeps both kinds in the prompt when one alone would fill the cap. A **Merge** uses fold's mechanics (`ArticlePlan.Fold`): sources move into the target, `redirects[from] = into`, public when both language files of `from` were public at the run's start (`publicRedirects`), redirects to `from` move along. Additionally the children of `from` move to `into`; if `into` was a child of `from`, it takes `from`'s parent. A move that would close a cycle leaves the child without parent. -**Memory.** `_state.json` gains `ConsolidatedGroups` (fingerprint → when) for usable replies and `FailedGroups` (fingerprint → when) for unusable ones; a group with a remembered fingerprint is not asked again. Fingerprint: `Prompts.Version` and, per member in slug order, slug, titles, category, scope and parent. Source counts are left out: they change whenever a note is added and say nothing about whether two articles share a subject; with them, most groups would be asked again every night. Both maps keep only the fingerprints of groups formed in the latest run that reached the step, so they do not grow without bound. A call that fails with `HttpRequestException` skips that group only and is not remembered. +**Memory.** `_state.json` gains `ConsolidatedGroups` (fingerprint → when) and `FailedGroups` (fingerprint → when); a group with a remembered fingerprint is not asked again. After a usable reply the fingerprint remembered is that of the group's surviving members as the reply left them (merged ones gone, new parents set; the same as asked when nothing changed), so the next night's identical group is not asked about its own result. After an unusable reply the fingerprint as asked goes to `FailedGroups`. Fingerprint: `Prompts.Version` and, per member in slug order, slug, titles, category, scope and parent. Source counts are left out: they change whenever a note is added and say nothing about whether two articles share a subject; with them, most groups would be asked again every night. Both maps keep only the fingerprints of groups formed in the latest run that reached the step, so they do not grow without bound. A call that fails with `HttpRequestException` skips that group only and is not remembered. `ReconcileSummary` gains `Merged` (merges applied) and `Parented` (parent links set); the commit message, endpoint body and status panel report them.