Files

T

David F GliddenandClaude Opus 5 ef6fa94dcd [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

2026-08-17 15:23:26 +02:00

4.7 KiB

Raw Blame History

permalink, superseded_by, superseded_on

permalink	superseded_by	superseded_on
claude-memory/project-arc-404-page-design-pending	project-arc-open-work-register.md	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 description: Surfaced 2026-05-03 during _layout.scss SCSS audit — the .wrapper.not-found CSS rule was dead code (no template, no build path, no class application), but ARC genuinely needs a 404 page. Existing content/404.md is Jekyll-era leftover. Need: ARC-voice 404 design + Hakyll build path + template. type: project originSessionId: 8d9ac240-47df-4578-aec1-a9dd32965027

ARC 404 page — design + build pending

Surfaced: 2026-05-03 during _layout.scss SCSS audit. The .wrapper.not-found CSS rule (~50 lines including dark-mode override) was dead code — no template, no site.hs build path, no class assignment anywhere. Removed in audit commit. Side finding: the gap is real. ARC has no 404 page.

Steward acknowledgment 2026-05-03: "So we need to design a 404 page…"

What exists currently

content/404.md — Jekyll-era leftover content with frontmatter (title: "Page Not Found", layout: 404, permalink: "/404.html"). Body has a # 404 heading, a poetic blockquote, some content. Not built by current Hakyll site.hs (no rule processes it). Effectively orphaned.
_layout.scss had a .wrapper.not-found rule (now removed) — display-large h1 (5rem), centered layout, dark-mode color override. Dead code; selector never applied anywhere.

What's needed

ARC-voice content for 404 — quiet, contemplative, acknowledges absence without performance:
- Possibly Latin (the site's register; non est inventus / nusquam)
- English short prose with a graceful return path
- Could lean into the Animal Rationis Capax posture: even being-lost is part of the search
- Might use a quiet ornament or §IV Pause/Close moment when designed
Template — templates/404.html or similar; renders with site header/footer; no breadcrumb (since the user is by definition off-path)
Build path in site.hs — process content/404.md (or replacement) into _site/404.html
Server config — CloudFlare Pages will use _site/404.html automatically as the 404 page if it exists at the root; verify via test
CSS — minimal; depending on the design decisions, may not need a dedicated _404.scss partial. The previous .wrapper.not-found over-specified things that the existing site rules already handle.

Design questions for the steward

Voice register — academic Latin, contemplative English, mixed?
Length — single line of prose, short paragraph, brief poem-like fragment?
Visual treatment — quiet h1 (per §I.d scale), or display-size deviation (the previous 5rem)? Honest read: respecting the §I.d scale is more consistent; display-size was probably an accidental "404 should be big" reflex
Return path — link to home? link to Reading Compass? Multiple paths?
Ornament — none, or use the (eventually-designed) §IV Close ornament as the gesture-of-completion-even-in-absence?
Latin or English first? — ARC's typography page uses English-first; bio is English; a Latin 404 could be the one place where the site's Latin name (Animal Rationis Capax) speaks plainly to a lost reader

Sequencing

Not urgent — site works without 404; users hitting non-existent URLs see browser-default or CDN-default 404 page. But meaningful: the 404 is one of those quiet places where the site speaks to the lost reader, and an ARC 404 should be considered carefully (Bringhurst-discipline applies even — perhaps especially — to the page no one means to find).

Best moment: a small focused session (1-2 hours including content draft + template + build path + test). Could pair naturally with:

The colophon rewrite (also pending — both are about-page-adjacent, both speak in ARC's voice to the reader)
The §IV Pause/Close ornament design (404 might be the one place the Close ornament makes most sense — the finis of an unintended journey)

Cross-references

content/404.md — orphaned content; review or replace as part of this work
_layout.scss audit commit — removed the dead .wrapper.not-found CSS
project-arc-pause-close-ornament-and-hr-audit-pending.md — the §IV ornament question; 404 is a candidate context for the Close ornament
The eventual colophon rewrite — adjacent voice work

4.7 KiB Raw Blame History