[FIX] Stamp 16 superseded trackers; harvest the rule one of them carried
The record is updated where information ARRIVES and never where a reader LOOKS.
Three instances found the same day, each with the correct information already
written down elsewhere:
REVIEWED-81 (AUTHORIZED 07-28) -> PENDING-81 still reads open
the ARC open-work register, which -> those 6 trackers still read live
says in its own description that
it supersedes them, with a
per-file verified verdict
register entry A2: "the content -> register entry B3, one page below:
half (B3) is now unblocked + "[OPEN - gated on A2]"
started" (06-17)
The third is the sharpest: both halves sit in the SAME document, so no tooling
gap explains it. ~/CLAUDE.md already rules this under Memory Discipline
("mark the superseded record as superseded"); the rule is being applied to facts
and not to trackers, PENDING items or register entries, which are also facts
about state.
Executed under steward authorization, arrears only:
- 16 trackers stamped `superseded_by:` + `superseded_on:` AND a visible in-body
banner. The banner is the point — metadata alone repeats the defect, since the
finding is about what a reader sees. 9 obsoleted by the 2026-07-07 MemPalace
wind-down; 7 already carrying the register's own verified `DONE-retire`.
- B3's label corrected, with the two-month error left visible rather than
silently amended.
- Nothing moved, renamed or deleted: 381 pointers resolve, 0 dead, 0 mis-authored.
HARVESTED BEFORE STAMPING, and this is why the harvest came first:
`project-mempalace-library-incremental-remine-strategy` carried a steward-verbatim
rule that is instrument-independent — never run a single multi-day index; order by
criticality; gate each tranche on READBACK, not on write-success (933,576 drawers
once stored successfully and could not be read back at all). It lived only inside
a MemPalace tracker, so retiring the instrument would have retired the rule with
it. ~/CLAUDE.md names that exact hazard: "state the obligation first and the
instrument second, or the next retired tool takes a rule down with it." Now
`feedback-bulk-indexing-runs-incrementally-with-readback.md`, and it applies to
studium-engine corpus work.
Held back deliberately: 2 correctly-parked files with named dependencies, 2 named
nowhere (returned to the steward), and 39 trackers unread — recorded as a gap,
not as a finding.
Measurement note: every earlier estimate of tracker staleness was wrong, because
both mtime and git-last-commit were reset across 283 files by the 2026-06-06
normalization sweep. The honest figure excludes it: median 90 days.
Filed as PENDING-142 ADDENDUM 2 per steward direction (fold, do not file anew).
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_013Y6t6qx7cpaCu5xGdD36u4
This commit is contained in:
David F Glidden
co-authored by
Claude Opus 5
Claude Opus 5
parent
69e258116a
commit
ef6fa94dcd
@@ -6,7 +6,7 @@ metadata:
|
||||
type: note
|
||||
permalink: claude-memory/memory
|
||||
originSessionId: 22915403-bc5d-4796-9c7d-196b7c30d2f9
|
||||
modified: 2026-08-09T19:50:40.617Z
|
||||
modified: 2026-08-17T13:20:44.481Z
|
||||
permalink: claude-memory/memory
|
||||
---
|
||||
|
||||
@@ -40,6 +40,7 @@ permalink: claude-memory/memory
|
||||
- [Tool review after each use](feedback-tool-review-after-each-use.md) — review every tool we built after each run, success OR failure. **PASS-BUT-FALSELY is the priority signal.** Log: `chamber-library/_curation/tool-evolution-log.md`.
|
||||
- [Every canon doc's source lives in Chamber Sources](feedback-resolve-source-through-chamber-sources.md) — a canonical's source = whatever `resolve_archived_source` returns, **never** the master library or a path in frontmatter. Read the banked record before calling a mismatch a defect.
|
||||
- [Engine sources graduate to the permanent chamber](feedback-engine-sources-become-permanent-chamber-collection.md) — work added for the engine ALSO becomes permanent collection unless stated otherwise; take it all the way (clean→verify→graduate→catalogue→sidecar). Never leave staged.
|
||||
- [Bulk indexing runs in tranches, gated on READBACK](feedback-bulk-indexing-runs-incrementally-with-readback.md) — never one multi-day mine; order by criticality; **prove each tranche by reading back, not by write-success** (933k drawers once stored fine and were unreadable). Steward rule 2026-05-04, learned on MemPalace, **applies now to engine corpus work**.
|
||||
- [Studium Engine charter](reference-studium-engine-architectural-charter.md) — the engine's constitutional doc. Read before building. · [Sixtus-V collaboration](feedback-studium-engine-sixtus-v-collaboration.md) — build freely, surface only vision-forks; **constraint-candidates** = 3rd governed instrument. Studium-engine only.
|
||||
- [CapableHands standing authorization](reference-capablehands-standing-authorization.md) — M4 mini `david@10.0.1.136` durably authorized for remote OCR/inference; don't re-ask (steward 2026-07-01).
|
||||
- [Typography palace — query via CLI](reference-typography-palace-cli.md) — ~20 type masters at `~/.mempalace/palace-chamber-typography`; `mempalace --palace <that> search "…"`. For ARC typography; don't re-ask where it lives.
|
||||
|
||||
@@ -0,0 +1,47 @@
|
||||
---
|
||||
name: feedback-bulk-indexing-runs-incrementally-with-readback
|
||||
description: "Never run a single multi-day indexing/mining job. Go in tranches, ordered by criticality, and prove each tranche by reading back what was written before starting the next. Steward rule, 2026-05-04, after three days of compute produced unreadable output."
|
||||
metadata:
|
||||
node_type: memory
|
||||
type: feedback
|
||||
originSessionId: 81f817e9-4016-4867-ae16-a486f1e8fb46
|
||||
modified: 2026-08-17T13:20:31.039Z
|
||||
---
|
||||
|
||||
Never run a bulk index/mine/embed job as one long pass. **Tranches, ordered by
|
||||
criticality, with a write *and readback* check after each** before the next begins.
|
||||
|
||||
Steward, verbatim, 2026-05-04:
|
||||
|
||||
> *"go with path A. then we make a choice on how to remine the library incrementally
|
||||
> beginning with the most critical texts. I'm not losing days to this again."*
|
||||
|
||||
**Why:** a failure only visible after days of compute is unacceptable, and it is the
|
||||
*normal* outcome rather than the unlucky one. The 2026-05-01 → 05-03 chamber-library run
|
||||
spent three days of CPU/MPS and wrote **933,576 drawers that stored successfully and
|
||||
could not be read back at all** — storage reported success, search returned `Internal
|
||||
error: Error finding id`. A run that writes without ever reading back cannot tell
|
||||
"working" from "producing garbage at scale", so its own progress reporting is
|
||||
uninformative. An earlier attempt burned nine hours to reach 30 of 371 files.
|
||||
|
||||
**How to apply:**
|
||||
- **Tranche it.** No single job whose failure is invisible until it ends. Size the
|
||||
tranche so a wasted one costs an hour, not a weekend.
|
||||
- **Order by criticality.** Index what is actually load-bearing for live work first, so
|
||||
the useful half exists even if the run is abandoned midway.
|
||||
- **Readback is the gate, not the write.** Storage success is not the property you want;
|
||||
*retrieval of what you stored* is. Query each tranche before starting the next — this
|
||||
is the [[reference-verification-ladder]]'s discrimination rule applied to indexing:
|
||||
a check that only exercises the write path cannot see a broken read path.
|
||||
- **Watch for a global setting applied to a heterogeneous corpus.** The same run was
|
||||
compounded by one embedding model being forced across *all* collections; dimensions
|
||||
that suit a multilingual scholarly corpus need not suit anything else.
|
||||
|
||||
⚠ **This rule is instrument-independent and outlived the tool that earned it.** It was
|
||||
learned on MemPalace, which was wound down 2026-07-07 ([[project-mempalace-winddown]]) —
|
||||
and it was carried *only* inside a MemPalace tracker, so retiring the instrument would
|
||||
have retired the rule with it. `~/CLAUDE.md` names that hazard directly: *"state the
|
||||
obligation first and the instrument second, or the next retired tool takes a rule down
|
||||
with it."* Harvested here 2026-08-17, on the day the superseded tracker was stamped, for
|
||||
exactly that reason. **It applies now to the studium engine's corpus mining** — the same
|
||||
shape of work, a different tool.
|
||||
@@ -1,6 +1,13 @@
|
||||
---
|
||||
permalink: claude-memory/project-arc-404-page-design-pending
|
||||
superseded_by: project-arc-open-work-register.md
|
||||
superseded_on: 2026-08-17
|
||||
---
|
||||
> **SUPERSEDED 2026-08-17.** Register E3 → `[DONE—retire]` **[verified 2026-06-11]** — this file predates §VII.h; content/404.md and the built 404 conform exactly.
|
||||
>
|
||||
> Current record: **project-arc-open-work-register.md**. Kept for detail and provenance — do not read the
|
||||
> status below as live.
|
||||
|
||||
|
||||
---
|
||||
name: ARC 404 page — design + build pending
|
||||
|
||||
@@ -7,7 +7,14 @@ description: Tracks the multi-session refactor flowing from the universal dateli
|
||||
type: project
|
||||
originSessionId: 3bf7ae75-1138-4745-9024-0c40b3755ad3
|
||||
permalink: claude-memory/project-arc-apparatus-refactor-todo-2026-05-06
|
||||
superseded_by: project-arc-open-work-register.md
|
||||
superseded_on: 2026-08-17
|
||||
---
|
||||
> **SUPERSEDED 2026-08-17.** Register E4 → `[DONE—retire]` — Tiers 1/2 shipped; the Tier-3 residual lives on as register B1.
|
||||
>
|
||||
> Current record: **project-arc-open-work-register.md**. Kept for detail and provenance — do not read the
|
||||
> status below as live.
|
||||
|
||||
|
||||
# ARC apparatus refactor — todo list
|
||||
|
||||
|
||||
@@ -9,7 +9,14 @@ description: Steward identified 2026-05-01 that the breadcrumb system should app
|
||||
type: project
|
||||
originSessionId: 597aba4e-942b-4f20-8a89-3d801b14c971
|
||||
permalink: claude-memory/project-arc-breadcrumb-spec-pending
|
||||
superseded_by: project-arc-open-work-register.md
|
||||
superseded_on: 2026-08-17
|
||||
---
|
||||
> **SUPERSEDED 2026-08-17.** Register E1 → `[DONE—retire]` **[verified]** — breadcrumb componentized and governed 2026-06-03.
|
||||
>
|
||||
> Current record: **project-arc-open-work-register.md**. Kept for detail and provenance — do not read the
|
||||
> status below as live.
|
||||
|
||||
|
||||
# ARC universal breadcrumb system — pending
|
||||
|
||||
|
||||
@@ -9,7 +9,14 @@ metadata:
|
||||
type: project
|
||||
originSessionId: 2026-05-20-conversion-session
|
||||
permalink: claude-memory/project-arc-mimesis-acquisition-debt
|
||||
superseded_by: project-arc-open-work-register.md
|
||||
superseded_on: 2026-08-17
|
||||
---
|
||||
> **SUPERSEDED 2026-08-17.** Register E2 → `[DONE—archive]` — RESOLVED 2026-05-20, stated in this file's own body.
|
||||
>
|
||||
> Current record: **project-arc-open-work-register.md**. Kept for detail and provenance — do not read the
|
||||
> status below as live.
|
||||
|
||||
|
||||
# Auerbach *Mimesis* — acquisition debt — RESOLVED 2026-05-20
|
||||
|
||||
|
||||
@@ -6,6 +6,7 @@ metadata:
|
||||
type: project
|
||||
permalink: claude-memory/project-arc-open-work-register
|
||||
originSessionId: b85f1094-0658-47b4-a0ba-7a4323383aa9
|
||||
modified: 2026-08-17T13:22:01.355Z
|
||||
---
|
||||
|
||||
# ARC open-work register
|
||||
@@ -27,7 +28,7 @@ metadata:
|
||||
|
||||
- **B1. Glimpse location + title cleanup.** `[OPEN — steward manual]` **[verified]** — steward does this by hand (2026-06-11). 193 live glimpses; **4 lack `location:` frontmatter**; titles need a cleanup pass. NB the glimpse *rendering* bugs (phone full-bleed, no-vessel) were fixed + deployed in Stage M — this is content/metadata, not code. Absorbs the residual of `project-arc-apparatus-refactor-todo` Tier 3 (EXIF/location for existing glimpses — now ~done).
|
||||
- **B2. Threshold-`---` promotion walk.** `[OPEN — steward content track]` — apply the 2026-06-07 differentiated-hr doctrine across existing pieces: a bare `---` at a foreword→main-text *threshold* becomes `.ornament` (dots); `---` *within the body* stays silence. Doctrine + CSS settled (§IV amended, zero CSS change); the per-piece content walk remains.
|
||||
- **B3. Ornament content migration (Option A) — the content half of A2.** `[OPEN — gated on A2; scope VERIFIED 2026-06-11]` — steward ruled Option A (2026-05-03): once the cul-de-lampe asset exists (**A2**), migrate content off the retired-ornament classes onto the canonical Close/Pause, then retire the old SCSS. **Verified scope (sizable):** ~**95 content files** carry hand-authored `<div class="ornament …"></div>` — `completion` ×51 (= the Close / end-of-piece, the cul-de-lampe's job), `section` ×50, `thought` ×14, `chamber` ×12, `musical` ×7, `hermetic` ×5, `mathematical` ×2, … Several variants (`thought`, `mathematical`) aren't even in the current CSS → they already collapse to bare `.ornament`. All retired per §IV; all await the designed asset. Not negligible, and not runnable until A2. Files: `project-arc-ornament-spec-vs-content-mismatch-pending`, `project-arc-pause-close-ornament-and-hr-audit-pending`.
|
||||
- **B3. Ornament content migration (Option A) — the content half of A2.** `[OPEN — UNGATED 2026-06-17 when A2 landed; scope VERIFIED 2026-06-11]` — ⚠ *label corrected 2026-08-17: this read `gated on A2` for two months after A2 completed. A2's own entry had recorded "the content half (B3) is now unblocked + started" on 06-17 — so the fact was known and written, just never written **here**, which is where a reader checking B3's status looks. Kept as a marker of that failure mode rather than silently amended.* — steward ruled Option A (2026-05-03): once the cul-de-lampe asset exists (**A2**), migrate content off the retired-ornament classes onto the canonical Close/Pause, then retire the old SCSS. **Verified scope (sizable):** ~**95 content files** carry hand-authored `<div class="ornament …"></div>` — `completion` ×51 (= the Close / end-of-piece, the cul-de-lampe's job), `section` ×50, `thought` ×14, `chamber` ×12, `musical` ×7, `hermetic` ×5, `mathematical` ×2, … Several variants (`thought`, `mathematical`) aren't even in the current CSS → they already collapse to bare `.ornament`. All retired per §IV; all await the designed asset. Not negligible, and not runnable until A2. Files: `project-arc-ornament-spec-vs-content-mismatch-pending`, `project-arc-pause-close-ornament-and-hr-audit-pending`.
|
||||
- **B4. Major content audit / archive of non-current files.** `[OPEN — was deferred]` — per ARC `CLAUDE.md` Known state: deferred until "the current version of the site is established; do not rearrange the content tree until that session." Stage G sealed arguably satisfies that condition now — candidate to schedule.
|
||||
- **B5. Rethink the versioning links.** `[OPEN — design reconsideration; steward-raised 2026-06-17, NOT for now]` — the steward feels something "doesn't sit right" about the version-stamp links and couldn't yet name it. Current behaviour (verified in built HTML): the piece-end stamp reads *"Begun [place] **[origin-date→/v/]** · Revised [place] [revised-date, plain]"* — the **origin date is the only link**, leading to the prior version; the `/v/` page announces "You are reading a prior version… Read current →." Executor's candidate diagnoses (offered, not settled): **(1)** the cul-de-lampe (a *completion* seal, *finis coronat opus*) and the version link pull opposite ways — the close says *done*, the link a few lines below pulls *backward* into the superseded version; adding the close may have sharpened a latent tension. **(2)** "Begun [date]" frames the link as inception/seed, but the destination is a *complete prior essay*, not a beginning — label/destination mismatch. **(3)** for pieces revised by *subtraction* (Mushi-Ken's appendix, Vespers' loudness), the linked prior is the version the author *improved away from* — disclosing *that* a revision happened is integrity, but making the discarded version the foot-of-page reading-*destination* may overreach: provenance offered as invitation. Hunch: it's #1+#3 — ADR-005 designed versioning as a *record*, but rendered as a link it behaves like a parallel reading-path, and that sits oddly under a completion mark. Revisit when the steward can name it. (Grounds: ADR-005, essay-versioning-specification.md §3–4; the version-stamp builder in `site.hs`.)
|
||||
|
||||
|
||||
@@ -9,7 +9,14 @@ description: Two interlocking pieces of work that should be undertaken together
|
||||
type: project
|
||||
originSessionId: 8d9ac240-47df-4578-aec1-a9dd32965027
|
||||
permalink: claude-memory/project-arc-pause-close-ornament-and-hr-audit-pending
|
||||
superseded_by: project-arc-open-work-register.md
|
||||
superseded_on: 2026-08-17
|
||||
---
|
||||
> **SUPERSEDED 2026-08-17.** Register A2 → `[DONE 2026-06-17]` — the cul-de-lampe is designed, first-instanced, rolled out to 7 essays, spec resolved. The CONTENT half continues as register B3, which is live work.
|
||||
>
|
||||
> Current record: **project-arc-open-work-register.md**. Kept for detail and provenance — do not read the
|
||||
> status below as live.
|
||||
|
||||
|
||||
# ARC §IV Pause/Close ornament + `<hr>` content audit — pending
|
||||
|
||||
|
||||
@@ -9,7 +9,14 @@ description: Aspiration logged 2026-05-03 — at an appropriate future point, re
|
||||
type: project
|
||||
originSessionId: 8d9ac240-47df-4578-aec1-a9dd32965027
|
||||
permalink: claude-memory/project-arc-spec-master-typographer-audit-pending
|
||||
superseded_by: project-arc-open-work-register.md
|
||||
superseded_on: 2026-08-17
|
||||
---
|
||||
> **SUPERSEDED 2026-08-17.** Register E5 → `[DONE—retire — superseded]` **[verified 2026-06-11]** — the masters pass was performed (_audits/deep-typographic-audit-2026-06-09.md). Reopen only for a NAMED uncovered dimension.
|
||||
>
|
||||
> Current record: **project-arc-open-work-register.md**. Kept for detail and provenance — do not read the
|
||||
> status below as live.
|
||||
|
||||
|
||||
# ARC spec — master-typographer compliance audit (pending)
|
||||
|
||||
|
||||
@@ -9,7 +9,14 @@ description: Inventory of web-only and web-medium typography elements in ARC tha
|
||||
type: project
|
||||
originSessionId: 8d9ac240-47df-4578-aec1-a9dd32965027
|
||||
permalink: claude-memory/project-arc-web-typography-spec-coverage
|
||||
superseded_by: project-arc-open-work-register.md
|
||||
superseded_on: 2026-08-17
|
||||
---
|
||||
> **SUPERSEDED 2026-08-17.** Register E6 → `[DONE—retire]` **[verified 2026-06-11]** — Tiers 1–3 done; only the <abbr>/<mark> corner remains and no content meaningfully uses them.
|
||||
>
|
||||
> Current record: **project-arc-open-work-register.md**. Kept for detail and provenance — do not read the
|
||||
> status below as live.
|
||||
|
||||
|
||||
# ARC web typography spec coverage — what still needs care
|
||||
|
||||
|
||||
@@ -5,7 +5,14 @@ description: The ONE job for the cleared context. Full chamber-library re-mine o
|
||||
type: project
|
||||
originSessionId: a156edbb-0c3d-4285-b3ed-f5a45b8dda66
|
||||
permalink: claude-memory/project-bge-m3-full-remine-plan-2026-05-11
|
||||
superseded_by: project-mempalace-winddown.md
|
||||
superseded_on: 2026-08-17
|
||||
---
|
||||
> **SUPERSEDED 2026-08-17.** An execution plan for a palace that no longer exists. The DISCIPLINE it was written under survives: see feedback-bulk-indexing-runs-incrementally-with-readback.md.
|
||||
>
|
||||
> Current record: **project-mempalace-winddown.md**. Kept for detail and provenance — do not read the
|
||||
> status below as live.
|
||||
|
||||
|
||||
# bge-m3 full re-mine plan
|
||||
|
||||
|
||||
@@ -6,7 +6,14 @@ description: Architectural framework for a BMF connector that queries MemPalace'
|
||||
type: project
|
||||
originSessionId: 597aba4e-942b-4f20-8a89-3d801b14c971
|
||||
permalink: claude-memory/project-bmf-mempalace-connector-parked
|
||||
superseded_by: project-mempalace-winddown.md
|
||||
superseded_on: 2026-08-17
|
||||
---
|
||||
> **SUPERSEDED 2026-08-17.** Parked on two conditions that have both lapsed: MemPalace was retired 2026-07-07, and BMF L1 is blocked on PENDING-94 and staying down. Resume would need a fresh framing, not this one.
|
||||
>
|
||||
> Current record: **project-mempalace-winddown.md**. Kept for detail and provenance — do not read the
|
||||
> status below as live.
|
||||
|
||||
|
||||
# BMF–MemPalace Connector — Project Framework
|
||||
|
||||
|
||||
@@ -1,6 +1,13 @@
|
||||
---
|
||||
permalink: claude-memory/project-mempalace-bge-m3-mine-search-broken-2026-05-03
|
||||
superseded_by: project-mempalace-winddown.md
|
||||
superseded_on: 2026-08-17
|
||||
---
|
||||
> **SUPERSEDED 2026-08-17.** Diagnostic state of a palace that no longer exists.
|
||||
>
|
||||
> Current record: **project-mempalace-winddown.md**. Kept for detail and provenance — do not read the
|
||||
> status below as live.
|
||||
|
||||
|
||||
---
|
||||
name: MemPalace bge-m3 mine — drawers stored, search broken (Internal error: Error finding id)
|
||||
|
||||
@@ -11,7 +11,14 @@ metadata:
|
||||
type: project
|
||||
originSessionId: 8952fe77-1cf0-401d-9d88-01f9f0b13bcc
|
||||
permalink: claude-memory/project-mempalace-chunking-bug-2026-05-16
|
||||
superseded_by: project-mempalace-winddown.md
|
||||
superseded_on: 2026-08-17
|
||||
---
|
||||
> **SUPERSEDED 2026-08-17.** Filed upstream as MemPalace/mempalace#1534 and left to upstream by steward direction. With the instrument retired this is no longer ours to track.
|
||||
>
|
||||
> Current record: **project-mempalace-winddown.md**. Kept for detail and provenance — do not read the
|
||||
> status below as live.
|
||||
|
||||
|
||||
# MemPalace `_chunk_by_paragraph` oversized-chunk bug
|
||||
|
||||
|
||||
@@ -8,7 +8,14 @@ description: After 3 days lost to bge-m3+MPS chamber-library mine that produced
|
||||
type: project
|
||||
originSessionId: 45a40b1e-09cd-42bb-a41a-7298f78a8cf0
|
||||
permalink: claude-memory/project-mempalace-library-incremental-remine-strategy
|
||||
superseded_by: project-mempalace-winddown.md
|
||||
superseded_on: 2026-08-17
|
||||
---
|
||||
> **SUPERSEDED 2026-08-17.** ⚠ The steward's rule this file carried is INSTRUMENT-INDEPENDENT and was harvested before this stamp: feedback-bulk-indexing-runs-incrementally-with-readback.md. It applies now to studium-engine corpus work. Superseded for MemPalace operations only.
|
||||
>
|
||||
> Current record: **project-mempalace-winddown.md**. Kept for detail and provenance — do not read the
|
||||
> status below as live.
|
||||
|
||||
|
||||
## Context
|
||||
|
||||
|
||||
@@ -1,6 +1,13 @@
|
||||
---
|
||||
permalink: claude-memory/project-mempalace-mps-transition-pending
|
||||
superseded_by: project-mempalace-winddown.md
|
||||
superseded_on: 2026-08-17
|
||||
---
|
||||
> **SUPERSEDED 2026-08-17.** A paused bge-m3/MPS mine on a palace that was wiped and then retired. The backup paths named below may still exist on disk and are the only part worth acting on.
|
||||
>
|
||||
> Current record: **project-mempalace-winddown.md**. Kept for detail and provenance — do not read the
|
||||
> status below as live.
|
||||
|
||||
|
||||
---
|
||||
name: MemPalace bge-m3 + MPS transition — paused mid-flight; resume in fresh session
|
||||
|
||||
@@ -7,7 +7,14 @@ metadata:
|
||||
type: project
|
||||
originSessionId: 8b47c0eb-d396-43d5-98eb-7623e6f04357
|
||||
permalink: claude-memory/project-mempalace-operational-stance-2026-05-16
|
||||
superseded_by: project-mempalace-winddown.md + studium-engine docs/seed-brief.md
|
||||
superseded_on: 2026-08-17
|
||||
---
|
||||
> **SUPERSEDED 2026-08-17.** The MemPalace half is retired. The live half — the two-layer split between session continuity and voice-attributed corpus consultation — is carried more fully in the studium-engine seed-brief §3.2–3.3, which states it as one architecture asked to do two jobs.
|
||||
>
|
||||
> Current record: **project-mempalace-winddown.md + studium-engine docs/seed-brief.md**. Kept for detail and provenance — do not read the
|
||||
> status below as live.
|
||||
|
||||
|
||||
# MemPalace operational stance (post-issue-#1526)
|
||||
|
||||
|
||||
@@ -8,7 +8,14 @@ description: MemPalace is not a deliverable, not a long-term substrate, not part
|
||||
type: project
|
||||
originSessionId: 597aba4e-942b-4f20-8a89-3d801b14c971
|
||||
permalink: claude-memory/project-mempalace-role-as-instrumentation
|
||||
superseded_by: project-mempalace-winddown.md + mempalace-is-unaffiliated-stopgap.md
|
||||
superseded_on: 2026-08-17
|
||||
---
|
||||
> **SUPERSEDED 2026-08-17.** The territory rule (MemPalace is a third-party project, never conflated with BMF/CapableMind) is live and now carried by mempalace-is-unaffiliated-stopgap.md. The operational half — bge-m3 transition phases — retired with the instrument.
|
||||
>
|
||||
> Current record: **project-mempalace-winddown.md + mempalace-is-unaffiliated-stopgap.md**. Kept for detail and provenance — do not read the
|
||||
> status below as live.
|
||||
|
||||
|
||||
# MemPalace's role in the current period
|
||||
|
||||
|
||||
@@ -5,7 +5,14 @@ metadata:
|
||||
node_type: memory
|
||||
type: project
|
||||
originSessionId: 5a8200e7-d734-4dc1-b69e-93d77076cab2
|
||||
superseded_by: project-mempalace-winddown.md
|
||||
superseded_on: 2026-08-17
|
||||
---
|
||||
> **SUPERSEDED 2026-08-17.** A scheduled 3.3.6 → 3.4.0 upgrade of an instrument retired before the slot came.
|
||||
>
|
||||
> Current record: **project-mempalace-winddown.md**. Kept for detail and provenance — do not read the
|
||||
> status below as live.
|
||||
|
||||
|
||||
# MemPalace upgrade 3.3.6 → 3.4.0 — scheduled plan (ratified 2026-06-07)
|
||||
|
||||
|
||||
@@ -5,7 +5,7 @@ metadata:
|
||||
node_type: memory
|
||||
type: feedback
|
||||
originSessionId: 81f817e9-4016-4867-ae16-a486f1e8fb46
|
||||
modified: 2026-08-17T12:34:44.862Z
|
||||
modified: 2026-08-17T13:23:05.853Z
|
||||
---
|
||||
|
||||
# Session Ledger — 2026-08-17
|
||||
@@ -19,6 +19,18 @@ metadata:
|
||||
did" — the record is the fullest of the week. Third firing, third false alarm; it is the
|
||||
candidate task the steward left open for today.
|
||||
|
||||
- **2026-08-17T~15:05 — the scoped task was not the defect.** `wrap_inside` was queued as a
|
||||
two-valued-detector fix. Diagnosing the class first found four defects; the arity was #4 and
|
||||
the cause was a UTC/local time-base mismatch (+7201 s against a 900 s tolerance). Proven by
|
||||
old-vs-new on the reconstructed wake instant: fixing only the scoped item would have shipped a
|
||||
fix that left the alarm firing.
|
||||
- **2026-08-17T~15:25 — nearly reported 50 stale trackers off mtime.** Fifty files sharing
|
||||
*exactly* 72.3 d is a bulk operation, not fifty edits. Checked git: it agreed with mtime, so the
|
||||
bulk-touch suspicion was **refuted** — and then the commit itself turned out to be
|
||||
`3f9a89b`, a 283-file normalization sweep that reset *both* signals. Third and fourth instances
|
||||
in one day of an instrument whose subject is adjacent to the claim. The honest measure is the
|
||||
last commit excluding the sweep.
|
||||
|
||||
## What held
|
||||
|
||||
- The wake read every claim it reported against the substrate rather than relaying the digest:
|
||||
@@ -46,6 +58,15 @@ metadata:
|
||||
|
||||
## Authorization moves
|
||||
|
||||
- **2026-08-17 — steward authorized Groups A+B stamping, harvest first**, and directed the general
|
||||
finding be folded into PENDING-142 rather than filed as a new item. Executed: rule harvested to
|
||||
`feedback-bulk-indexing-runs-incrementally-with-readback.md` **before** any stamp; 16 trackers
|
||||
stamped `superseded_by` + visible in-body banner; B3's label corrected with the two-month error
|
||||
left visible. Nothing moved, renamed or deleted — 381 pointers still resolve, 0 dead.
|
||||
- **Held back from the same act:** Group C (2 correctly-parked files, named dependencies) and
|
||||
Group E (2 files named nowhere — returned to the steward). The 39 unread trackers are recorded
|
||||
as a **gap, not a finding**.
|
||||
|
||||
## Sub-agent dialogues
|
||||
|
||||
## Bypasses
|
||||
|
||||
Reference in New Issue
Block a user