Files
dotfiles/claude/memory/project-arc-rework.md
T

380 KiB
Raw Blame History

name, description, type, originSessionId
name description type originSessionId
ARC rework landscape (reawakening 2026-04-16) ARC work surfaced after local dev environment restored. Captures the landscape as articulated by the steward — content rework, versioning question, cleanup scope. Not a project plan; a list of what is seen and named, to be taken up when concrete. project 19aac84d-35aa-466d-bdc8-6d7c07cf449a

ARC rework landscape — from 2026-04-16 reawakening

After local dev was restored on 2026-04-16, the steward returned to ARC with fresh eyes for the first time in months and named the following scope. Preserved in their voice; not yet acted on.

DECISION 2026-04-19: ARC stays unified — about page reflows (hic first, Adsum later)

The decision evolved in three moves within a single day:

  1. Separation rejected. Steward considered ARC ↔ davidglidden.eu split earlier in the week; reconsidered and rejected. Cross-discipline integration is what the steward is; a separated personal site would perform a partition that doesn't exist in the work.
  2. Two-peer-compass split briefly adopted, then rejected. Considered splitting the current "About" Reading Compass point into two peer compass points (Colophon for artifact + Adsum for person). Rejected on the same grounds as separation: any tidy artifact-vs-person partition re-performs the separation the steward rejected, just at a smaller scale.
  3. Arrived-at architecture: single about page, reflowed. The hic register (about-the-artifact: apparatus, formation, design, tools, typography, navigation philosophy) comes first; Adsum register (about-the-person: biographical, availability, concerts, mentorship, pedagogical research) comes later in the same page. One page, multidisciplinary by embrace rather than by partition.

Steward's framing: "embracing the multidisciplinary aspects of my work rather than trying to separate them tidily."

Why reflow, not split

Every split re-performs the partition the steward rejected. The ARC-unified decision said cross-discipline integration is what the steward is. The two-peer-compass shape is the same move at a smaller scale — artifact-self and person-self as tidy adjacents. Reflow lets them coexist in one page, in an order (hic → Adsum) that honors ARC's compose-the-work-first grammar without announcing "here is apparatus, here is person" as a structural claim.

Adsum name carried forward as register, not compass point

Though no longer a peer compass point, the Adsum naming is retained as the register-name for the person-facing section of the reflowed about page. The rationale still holds.

Adsum is Latin for "I am here / I am present" — the Roman answering-word, the response when one's name was called at a roll. It marks the projected image as a response to being called, not a self-presentation.

Resonances:

  • Pairs with hic jacet in the existing apparatus grammar (work lies here; person is present here)
  • Resonates with L1's I15 (the Accusative Default — answerable, not sovereign)
  • Avoids "About me" / "Bio" / "Vita" (sovereign-self / web-2.0 register)
  • Avoids Persona (Jung-freighted in modern English) and Vita (CV-coded)
  • Acknowledges projection-as-projection rather than performing self-presentation (the Harrison-shaped concern: name should refuse the noun-as-self and reach for a verbal/relational form)

Plural alternatives held but not chosen (still useful as fallbacks if Adsum doesn't wear well): Callings, Vocations — Harrison-flavored, plural acknowledges multiplicity (musician + writer + teacher + father) without forcing synthesis; you're called to these, you don't claim them.

Steward's verbatim adoption: "I adopt adsum."

Reasoning that defeated separation (still operative, generalized to defeat peer-split too)

  • Cross-discipline integration is the substance of the person (violist + writer + father + teacher); any tidy partition performs a separation that doesn't exist in the work
  • Gwern.net as steward-referenced precedent. Pluralism handled by substance (what's written), not navigation gymnastics. Biographical kept secondary (footer /me, not primary nav). Identity stated by writings, not credentials: "This is the website of Gwern Branwen. I write about AI, psychology, & statistics." The "best known for" framing carries multi-discipline identity without ranking. ARC parallel: "Animal Rationis Capax. The writing of David Glidden."
  • What ARC takes from gwern: declarative identity by writings; biographical kept secondary; pluralism native to the substance. What ARC does not take: link-dense ToC homepage, multi-column layout, topic-prefix naming ("AI:", "QS:") — violates ARC's editorial breath.
  • One difference from gwern: gwern has no concerts to schedule. Steward does. Inquirers (orchestras, students, mentees) need a findable surface. In the reflow shape this is served by Adsum section presence on the about page, reachable via the About compass point — not by elevation to a peer compass.
  • Less infrastructure debt: one site, one build, one deploy, one about page
  • The contemplative register isn't violated — the about page already lives in a different register from the essays

URLs / DNS

ARC moves to animalrationiscapax.org via Cloudflare Pages. davidglidden.eu becomes a redirect pointing at ARC's new home — not a separate site. The personal domain becomes a pointer, consolidating the public surface under animalrationiscapax.org.

Migration state (2026-04-19 evening, terminal-crash recovery):

  • Porkbun (registrar): nameservers updated to Cloudflare (priscilla.ns.cloudflare.com, tom.ns.cloudflare.com). whois confirms. Porkbun's NS REFUSED when queried directly — they've released the zone. ✓
  • Cloudflare: zone status Active. priscilla holds the zone authoritatively with CF-signatured SOA. ✓
  • Stale apex A records (44.227.76.166, 44.227.65.245, AWS Oregon IPs — origin unclear, probably import artifact) deleted by steward. ✓
  • Public resolvers (1.1.1.1 / 8.8.8.8 / 9.9.9.9) still return cached porkbun NS at time of diagnostic. Propagation of the TLD delegation takes up to ~24h due to standard .org NS TTLs. The parking page still appears via this cached path — this resolves on its own, not a misconfiguration. Independent verification (from outside steward's network) available at dnschecker.org.
  • SOA primary reads curitiba.ns.porkbun.com (stale imported value, usually overridden by CF as zone fully settles). Not breaking. Re-verify later.

Next steps for the move:

  • Bind animalrationiscapax.org as custom domain in the ARC Cloudflare Pages project — this auto-creates correct apex records (CNAME flattening to <project>.pages.dev or proxied A records). The deletion of the old A records + the absence of the Pages binding is why an apex lookup via CF currently returns nothing.
  • Verify propagation after a few hours: dig @1.1.1.1 NS animalrationiscapax.org +short should show CF nameservers.
  • Configure davidglidden.eu → animalrationiscapax.org redirect at whichever layer is fitting (CF Page Rule if it's also on CF; registrar-level URL forwarding otherwise).
  • Post-propagation: update ARC's internal canonical URL (Hakyll siteRoot in site.hs, canonical <link> tags, RSS feed URL, sitemap) to https://animalrationiscapax.org. Verify make rebuild + deploy picks up the new origin; CF Pages deploy target may need reconfiguration for the new custom domain.
  • Update Acerplex push path / any other CI references to the new URL.

(In progress at time of terminal crash, 2026-04-19 evening.)

Resolved by this decision (formerly open work)

  • davidglidden-eu repo scaffold — moot (no separate personal site)
  • Separate Hakyll build for davidglidden.eu — moot
  • Cross-link convention design — moot
  • Colophon as a separate compass point — moot (Colophon-register content flows as "hic first" within the about page; name Colophon may still serve as a section heading, open)
  • Glyph design for an Adsum compass point — moot (no new compass point)
  • Compass optical rebalancing to accommodate a 10th point — moot
  • About-enfilade split between Colophon and Adsum — moot (single page; enfilade nav to reflowed about only)
  • About-pages biographical content (Desk Interlude with Kai unborn, Lune presence, Manutius paraphrase) — reshapes from "rewrite under Adsum" to "compose Adsum section within the reflowed about page"

Open work generated by this decision

  • Reflow the existing about page: arrange hic-register content (apparatus, formation, design, navigation philosophy, typography) first; compose Adsum-register content (bio, concerts, mentorship, pedagogical research, coaching availability) as later sections of the same page. Substantial content work; not infrastructure.
  • Desk Interlude update: Kai-as-unborn → Kai-born; Lune now present in the room. Same page, updated text.
  • Manutius paraphrase removal + too-many-quotes prune — same page.
  • Bio + Resume treatment: integrate into the Adsum section rather than moving to a separate destination.
  • hic / hic jacet philosophical commitment (from vignette spec) gets embodied in the reflow, not announced as a feature.
  • DNS / Cloudflare move — in progress at crash time: ARC → animalrationiscapax.org (via Cloudflare Pages), davidglidden.eu → redirect. Resume from that state.
  • Colophon retained as section heading (confirmed 2026-04-19) for the hic-register content within the reflowed about page.
  • Open design question — subtle hic register marker. Steward's intuition 2026-04-19: if the hic section is simply titled Colophon and Adsum arrives later without context, the register-shift may read as abrupt. The hic register itself may want a quiet identifier — not a headline, something subtler (a small-caps lead-in, an italic phrase, a tiny apparatus mark) that does the register-declaring work without announcing the distinction structurally. The risk to avoid: re-performing the artifact-vs-person split at the micro-scale through heavy signposting (that's what the peer-compass architecture was rejected for). The reflow should feel continuous even while the registers modulate. Mockup resolution 2026-04-19 evening: the section names Colophon (about-artifact) and Adsum (about-person) do the register-marking themselves; no added italic subtitle needed. Names serve, added subtitles start to re-perform.

Mockup reviewed 2026-04-19 evening (Option A)

A full draft of the reflowed about.md was produced for steward review. Decisions locked:

  • Adsum opening drop-cap paragraph ("I answer to my name here—not as self-presentation but as response...") — KEEP. Embodies the register-declaration inside the page rather than announcing it as a feature elsewhere.
  • Seasonal Geometries section — MOVE to navigation-philosophy.md. Reading Compass is its own entity; seasonal glyphs belong with the navigation explanation, not with the about-page flow.
  • Henry James quote placement — STAY at close of page (after Contact), per steward's no-strong-preference.

Open from mockup review:

  • Drop-cap policy question (Warde tension). Steward on fence. Warde's Crystal Goblet principle: type should be transparent; drop caps may read as performative decoration. Vignette system (on essays) adds another threshold; drop cap + vignette + dateline breadcrumb = too many opening signals. About pages won't have vignettes, so the About case is different from the essay case. Executor lean: option (b) — keep only the Adsum drop-cap, drop the site-intro drop-cap. Forward rule: drop caps mark register-declarations, not page-tops. Emerson block already opens the page; the site-intro drop-cap stacks a redundant threshold. Adsum drop-cap marks a register-shift inside the page, which is semantically load-bearing — passes Warde's "the form does work" test. Not yet decided.
  • About-pages classification problem (steward raised 2026-04-19 evening, new). All content/pages/*.md currently carry class: essay, which pulls essay-apparatus (breadcrumb formatting, vignette slot once live, essay-style datelines, probably reading-time) onto pages that aren't essays. Creates confusion in the breadcrumb system at top of each page. Proposed solution: introduce class: about as first-class content type, matching the existing ✍︎ About Reading Compass point. Migration: every file in content/pages/ (about, colophon, bio, resume, aldine-xxi, typography, navigation-philosophy, vignette, attention-page, influences-page, tools, patterns-page, now-page, council-page-public if still relevant). Template treatment for class: about: no vignette, different breadcrumb (or none — enfilade nav already lives at page bottom), versioning infrastructure retained (ADR-005 is class-agnostic — renders breadcrumb when revisions: or edition_label: present). Scope is small but nonzero: site.hs has class-switch(es) that need an about branch; templates may need an about.html variant or conditional in default.html. Steward agreement pending on approach + scoping. Recommendation: scope as its own PR rather than bundling into about-reflow PR — different concerns (content flow vs. infrastructure), cleaner commit, useful independent of whether reflow lands.

Triggering question carried forward

"How does one mark the hic of one's projected image to others?"

The reflow is the answer at the level of the page: hic precedes Adsum; the thinking-here is declared before the presenting-here; the work is foregrounded before the person. Mark the public surface as projection. Don't pretend it's the self. Adsum is the answering-word that acknowledges being-called rather than self-presenting. Future work that touches Adsum's shape should be evaluated against this commitment.


Codification surface — what warrants spec-level treatment (2026-04-19)

Question surfaced during the about-page reflow session. The class: essay fallback for everything in content/pages/ is a symptom, not the problem: ARC's content typology itself is underspecified. The about-page case is one symptom; the "genre riddle" from the mobile review (meditation / observation / fragment overlap) is another. Steward reframed: what ELSE in ARC would benefit from codification?

Test for when codification is warranted

Codify when more than one holds:

  • Recurs — the same judgment is made many times
  • Has downstream consumers — templates, skills, agents that apply the rule
  • Embodies a commitment that should resist drift — philosophical load-bearing
  • Discovered, not invented — the rule emerged from practice and is stable

Don't codify what should stay live judgment (unresolved aesthetics, in-flux questions, fashion).

Strong candidates

  1. Content typology / genre system (THE recommendation). Defines each type (essay, observation, meditation, fragment, glimpse, photo-essay, gloss, about, chamber), resolves overlaps, defines per-type apparatus (vignette yes/no, breadcrumb style, dateline shape), binds to class: frontmatter + Reading Compass glyph. Downstream consumers: site.hs routing, semantic-analysis skill, vignette system, style guide. Spec-level precision warranted (peer of AldineXXI codex and vignette specification). The class: about question is one entry in this spec, not a separate problem.

  2. Apparatus grammar (hic / hic jacet, dateline, location, edition labels, revision breadcrumb). Partially in ADR-005, scattered in vignette-specification, implicit in colophon prose. Worth consolidating as its own Codex page — "Grammar of Place" or similar. Builds on 2026-04-13 hic philosophical commitment.

  3. Pattern 3 typography decision (2026-04-18). Decided but living in a memory file. Move to style guide when that session happens, or brief ADR sooner. The decision is stable; memory-only is undercodified for a load-bearing commitment.

  4. Reading Compass rules. Currently declarative on About; spec form would define what qualifies (when ● vs ○ vs ◈ — the "quality of attention" criteria), not just what the glyphs label. Feeds directly into typology (§1 catalogue).

Medium candidates

  • Style-guide prose positions (UNESCO / MLA / Chicago declared positions) — named in mobile review list as needing redevelopment. Downstream of typology; should follow it.
  • Navigation hierarchy rules (compass vs enfilade vs breadcrumb vs post-nav vs version-stamp) — implicit but operative. Partially covered in navigation-philosophy.md as prose; spec form would codify the rules rather than the philosophy.

Later candidates

  • Semantic-analysis skill spec — premature until content typology is locked (skill consumes typology).

Recommendation and sequencing

Content typology spec first. Foundation; everything else is downstream. Reasons:

  • Resolves class: about cleanly (the class becomes one field in the typology)
  • Unblocks the genre-riddle cleanup in the mobile review list
  • Feeds the style-guide redevelopment (item in mobile review list)
  • Prerequisite for the semantic-analysis skill
  • Tractable in a single focused session

Home for the spec when authored: docs/AldineXXI-Codex/content-typology-specification.md (peer of aldine-xxi-specification.md and vignette-specification.md).

Status 2026-04-19 evening: Draft saved to ~/_Dev/animal-davidglidden-eu/docs/AldineXXI-Codex/content-typology-specification.md (untracked; steward commits when ready). Contains §0 organizing principle (multi-axis typology) · §1 Type catalogue (structure + initial table + locked entries for Photo Essay, Glimpse, Fragment/Observation/Meditation drafts) · §2 Apparatus binding (structure only; matrix deferred) · §3 Qualifying marks · §4 Overlap and resolution · §5 Code binding contract · §6 Change policy · §7 Open questions · Changelog · Proposed authoring sequence. Session-locked decisions: multi-axis principle, Photo Essay definition (Berger Ways of Seeing), Glimpse:Photo-Essay :: Fragment:Essay pairing, Meditation promoted to 10th type, drop-cap rule (register-shifts only), no-essay-fallback rule. Open at pause: Meditation glyph (steward flagged 2026-04-19); remaining §1 entries for extant types; §2 apparatus matrix content; Poem / Council-Deliberation / Archive-class / Gloss-boundary questions.

In-session decisions locked for the spec (as of 2026-04-19 evening):

  • Photo Essay definition (§1 + §4), sharpened 2026-04-19 by steward: An essay whose medium is the image sequence. The sequence itself constructs the argument, rhythm, turn, and return — the essayistic work is done visually. No interleaved prose between images. Text, where present, is apparatus only (title, introduction, postface, per-image captions, dateline) — does not carry argumentative weight. Canonical external exemplar: John Berger, Ways of Seeing (the wordless image sequences constructing visual-critical arguments). The boundary with Essay: both are essayistic; they differ in medium (prose vs. image sequence). An essay may embed images as illustration; a photo essay may not embed prose as commentary.
  • Substance-primacy axis, refined: types divide by which medium carries the argument. Visual-primacy types (glimpse, photo-essay) construct their substance in image(s); text is apparatus. Prose-primacy types (essay, observation, meditation, fragment, gloss, about) construct their substance in prose; images support. The axis isn't "where text lives" — it's "what medium carries the argument." The steward's Ways-of-Seeing anchor clarified: photo-essay is essayistic all the way down; just in a different medium. Proposed as spec introductory frame.

Sections below this line predate the 2026-04-19 decision. The "Architectural: decouple ARC from personal domain" section and the "TODO: scaffold davidglidden-eu repo" subsection are SUPERSEDED — kept for the reasoning record. The biographical content surfaced in "About-pages constellation — needs rework" reshapes into Adsum authoring rather than ARC cleanup.


Essay versioning — the philosophical question (TODO: explore together)

"The after-the-reply sequence, of which the first two in their original forms are published, but they've been updated since — I need to think about how to deal with essay updates: how to remain true to the text, to have the old versions still available, to let them be superseded?"

Explicitly marked to-do. To be explored together, not resolved quickly. The answer shapes what an ARC essay is:

  • Montaigne's additive layers (each revision adds; original preserved within)
  • Talmudic-style commentary strata
  • "Revised edition" as its own artifact (original stays as it was; revisit becomes its own piece)
  • Supersession with git-preserved history (only latest is presented; original exists in archive)
  • Revision notes / scar tissue inline

Downstream implications: whether "sequences" are a navigation layer or a deeper commitment to plural time. Per this listing order.

After-the-reply sequence

  • First two essays: published in original form
  • Both updated since (see versioning question above)
  • Rest of the sequence: needs publication
  • Sequence needs UX: either a new category, a taxonomy tag, a frontmatter field, or a Reading Compass glyph. Currently not first-class in ARC's 8-point compass.

Architectural: decouple ARC from personal domain (2026-04-16)

"The time has come to decouple ARC from my personal domain and to build a light site just for biographical and possibly very specific musical publishing: the pedagogical research observations, the mentorship program, things like that. ARC is a different place. Some work may be cross-published, but ARC needs to be its own entity."

Named as a decision-in-progress. Key facts:

  • Steward owns animalrationiscapax.org — ARC's future home.
  • davidglidden.eu becomes a light biographical + musical/pedagogical site (pedagogy observations, mentorship program, etc.).
  • ARC is "its own entity" — not a subspace of David Glidden the person.
  • Cross-publishing possible for some pieces.

Implications surfaced (not resolved):

  • Resolves part of the about-pages rework. Biographical content (Desk Interlude with Kai/Lune, etc.) likely belongs on davidglidden.eu, not ARC.
  • Compounds the versioning question. If a piece lives on ARC and is also cross-published to davidglidden.eu, what's the relationship between the two instances? Canonical URL? Does the cross-pub freeze at its pub date or follow ARC's evolution? Becomes a second axis of the versioning discussion.
  • Technical ordering (not blocking today): DNS + CloudFlare move for ARC → animalrationiscapax.org; new Hakyll site for davidglidden.eu (lighter template, probably a fork); git repo rename on Gitea (cosmetic); content triage (what stays on ARC, what moves, what cross-pubs).

TODO: scaffold davidglidden-eu repo (personal site)

When: once the steward is ready to begin the split, not before.

Shape: NOT a GitHub-style fork (which preserves ARC's commit history as lineage). A derivation — new repo with fresh git history, seeded by copying in selected files from ARC, then git init + first commit: "Initial personal site scaffold (derived from ARC)."

Proposed location: git.skemantix.com/David/davidglidden-eu (on the same Gitea as ARC). New CloudFlare Pages project.

Inherit from ARC:

  • Stack / GHC toolchain config (stack.yaml, package.yaml, *.cabal)
  • Makefile (with deploy targets adapted to the new CF Pages project)
  • scripts/deploy-cloudflare.sh (with a different --project-name)
  • scripts/deploy-mirror.sh (with a different mirror repo target, if a mirror is wanted at all)
  • SCSS AldineXXI foundation (typography, palette, spacing scales) — imported without chamber/triptych/glyph-specific partials
  • Fonts (EB Garamond, IBM Plex) and @font-face declarations
  • .gitignore, pre-commit hooks setup (via dotfiles core.hooksPath)
  • CLAUDE.md pattern (adapted to the simpler site's scope)

Strip from ARC:

  • Reading Compass 8-point navigation (replaced with a simpler nav: bio / works / teaching / contact / writing → link out to ARC)
  • Chamber (canon, voices, library) — has no place on the personal site
  • Glyph system (GenomeConceptExtractor, archetype selection, semantic visual translator)
  • Triptych renderers + all associated JS
  • UCE/CIE infrastructure (already removed from ARC itself in b1f28d3, so naturally absent)
  • Observer-problem, OP-series content
  • Most of site.hs — probably ~70% drops out; what remains is: posts, pages, about, RSS, simple index, CSS compile
  • content/chamber/, content/fragments/, content/glimpses/ (unless steward wants glimpses on the personal site — decision)

Open questions to resolve at fork time:

  • Does the personal site need a GitHub Pages mirror at all, or is CloudFlare Pages alone sufficient?
  • What's the naming: davidglidden-eu (current ARC pattern, matches domain) or something else?
  • Which content/ types carry over — just pages/, or also posts/ (as a writing/journal surface)?
  • Cross-publishing mechanism: manual copy, or a content sync (Git submodule / symlink / scripted) — probably manual initially, can evolve.

Sequencing note: the fork should happen after the steward has decided the versioning question (at least provisionally), because cross-pub workflow depends on it.

Not yet a plan; a direction named.

Update 2026-04-18 evening (steward, during mobile-review enfilade discussion)

"this is a bigger project (which should be noted in memory somewhere) which entail[s] separating ARC from my personal site. Once the separation is made, my personal site will have my biographical info, concerts, mentorship, perhaps technical musical essays (but that depends), perhaps some cross posted material — but things that pertain directly to myself. ARC needs to be independent now. I would link to it from my personal site by mentioning that I am the creator and author of ARC."

New/sharpened:

  • Explicit inclusion of concerts and mentorship in personal-site scope
  • Technical musical essays "depends" — open question
  • Cross-linking pattern: personal site mentions David as creator/author of ARC (no assumed reciprocal link from ARC to personal site — keeps ARC's reticence register where even children are "my son" rather than named)
  • Stronger framing: "ARC needs to be independent now" — decoupling is active intent, not eventual

Immediate consequence decided 2026-04-18: Bio and Resume out of the about-enfilade. Treat ARC as the independent entity it's becoming, even before davidglidden.eu exists. About.md's Contact section will eventually redirect bio/resume to davidglidden.eu; transition state TBD.

About-pages constellation — needs rework

Specific items named:

  • Desk Interlude: Kai is still "unborn" in the text. Needs updating (Kai is born).
  • Lune's presence: she has now been in the room. Her presence in the about-pages changes further.
  • Too many quotes throughout.
  • Manutius paraphrase: has to go.
  • Hic / hic jacet philosophical commitment (from vignette spec, 2026-04-13) needs to be integrated into the about pages — not announced as a feature, but embodied. ARC's grammar of place (threshold objects opening and closing each piece as this thinking happened here, in this form, at this time) is constitutive, not decorative. The about constellation should reflect this.
  • "etc etc etc" — more to come as revision proceeds.

Other pieces queued

  • A poem to publish.
  • Lots of observations.
  • Lots of glimpses.
  • bref.

TODO: Semantic analysis agent/skill — AldineXXI application + vignette seed generation

Named 2026-04-16. Not yet designed.

Purpose: take a publish-ready piece → (1) analyze semantically → (2) apply/recommend AldineXXI typographical conventions → (3) generate the seed data for the vignette system.

State of prerequisites:

  • AldineXXI v2.0 spec: exists (docs/AldineXXI-Codex/AldineXXI-specification.md)
  • Vignette spec: exists (docs/AldineXXI-Codex/vignette-specification.md), jurist-approved
  • Vignette renderer: not yet built — Phase 3 pending (waiting on Gitea restart, fresh session, Hakyll build — first two now resolved today)
  • Gap map: docs/AldineXXI-Codex/gap-map-2026-04-13.md

Key design questions (unresolved):

  • Agent vs skill vs both? Claude Code skill (interactive, authored run before publish) vs autonomous agent (runs on build/CI) vs hybrid (skill for authoring, agent for validation). The steward phrased it as "agent or skill" — decision open.
  • Where does it live? A Claude Code skill on the steward's machine? A Haskell component in ARC's site.hs build? A separate tool invoked from Makefile? Three different postures with different lifecycle implications.
  • When does it run? Pre-publish interactive (author-controlled), on Hakyll build (automatic, no author decision), or both (skill produces annotations that build consumes)?
  • Relationship to existing glyph system (assets/js/glyphs/, preserved in b1f28d3)? Parallel, integrated, or eventually replacing? The glyph system is client-side visual output; this new agent is build-time semantic pre-processing. Potentially complementary.
  • Potential Chamber/BMF integration (later): Chamber's voice recognition + BMF recall could inform semantic analysis (e.g. "this passage echoes Levinas with confidence 0.8 against chamber-library chunks"). Premature coupling risk — start standalone, let integration emerge from practice.

Inputs (provisional):

  • Essay content (markdown + frontmatter)
  • AldineXXI v2.0 spec (as knowledge base / rules)
  • Vignette spec (as schema for seed output)

Outputs (provisional):

  • Typographical annotations or transformations (small caps, drop caps, optical spacing, ligature hints, voice attribution, cite styling, em-dash discipline)
  • Vignette seed: structured data the vignette renderer will consume to produce the per-piece visual element

Dependency note: building this before the vignette renderer exists means we design the seed format somewhat speculatively. Probably wise to build vignette renderer first (or at least stub it), then build the agent to produce seeds the renderer can consume. Or design them together.

Architectural observation (2026-04-18): the skill has three layers with different semantic requirements — and the third overlaps structurally with the vignette engine's analysis component.

  1. Fully mechanical — drop-cap on first body letter, trailing double-spaces, ornament divs at section boundaries, hard-break discipline. CSS rules or markup discipline. No analysis needed.

  2. Lightly linguistic — small-caps on proper names (standard NER). Shallow, bounded, doesn't need the vignette's depth of reading.

  3. Expressive — paragraph-class decisions (pull-quote / epigraph / breathing-room), ornament variation between sections (centripetal essay gets one style, distributed essay another), drop-cap glyph choice, pacing decisions honoring the essay's shape. This is where "organizing logic, philosophical character, where the text concentrates vs opens" matters — exactly the reading the vignette's Phase 2 generation script (semantic analysis → genome JSON per vignette-specification.md §Part II.Component 1) needs.

Design implication: the expressive layer of the typography skill and the vignette engine's semantic analysis component should share one semantic analyzer. Built once, consumed twice. Whether they share output schema or just the analysis pipeline is an implementation decision for the design session; the constraint is they should not independently invent their own semantic readers.

This supports the prime directive (do things once, correctly) and mirrors the architectural pattern the steward already uses in L2 (one substrate, multiple governance consumers).

TODO: Style guide redevelopment (noted 2026-04-18)

Existing style guide at docs/style-guide.md (527 lines) is substantial and comprehensive on ARC's internal vocabulary — semantic post types, ornament classes, Chamber citation notation (°, ~, †, §, ∞, ※), Reading Compass, forbidden patterns, small-caps conventions. Stale on multiple fronts:

  • Pre-ADR-005: no versioning regime, no hic/hic jacet philosophical commitment, no retractation-piece notation
  • Pre-AldineXXI-codex cross-reference: doesn't point to docs/AldineXXI-Codex/ specifications
  • Pre-vignette system: still references triptych/glyph system as if operative
  • Pre-sequence work: no treatment of sequences as first-class

More importantly, does not declare explicit positions on the classic tensions between UNESCO / MLA / Chicago-Turabian that the steward named. These are the typical style-guide questions that need positions:

  • Citation format (notes-bibliography vs author-date vs parenthetical vs in-prose)
  • Quotation conventions (American "" vs British '' for outer quotes; single/double nesting)
  • Title formatting (italics vs quotes for short/long works; translation conventions)
  • Date format (2025-06-17 ISO vs June 17, 2025 MLA vs day-month-year UK)
  • Gender/pronoun conventions (generic they vs he-or-she; inclusive pronouns in quoted historical material)
  • Oxford comma (declared yes/no)
  • Em-dash vs en-dash vs hyphen (spacing, semantic use)
  • Ellipsis (three periods vs Unicode ellipsis; bracketed for omissions)
  • Foreign language treatment (italics always, only on first use, or lang-attribute-only)
  • Numbers (spelled-out threshold; oldstyle vs lining)
  • Proper nouns / corporate names / honorifics

ARC's actual practice is a principled blend — the guide should make the positions explicit rather than implicit.

Recommended approach (practice-first, thin, explicit):

  1. Audit a handful of recent essays against each classic question — record actual practice
  2. Identify tensions between UNESCO / MLA / Chicago positions where ARC's practice diverges from any single guide
  3. Declare explicit positions with brief reasoning (why ARC takes this position, not just that it does)
  4. Keep the rich ARC-specific content (semantic types, ornaments) largely intact — rework is additive, not rewriting
  5. Cross-reference AldineXXI codex (typography) and ADR-005 (versioning) as separate canonical sources; the style guide is about prose conventions, not typography or infrastructure

Dependency to surface explicitly: The style guide is a prerequisite for the projected ARC agents — particularly the semantic analysis / typography application skill noted above. Layer 3 of that skill (expressive decisions: which paragraphs warrant pull-quote/epigraph/breathing-room classes, ornament variation, drop-cap glyph choice) requires the style guide's declared positions as its rule set. The skill enforces the style guide; the style guide defines what the skill enforces. Without the guide's declarative form, the skill has no stable ground to consult.

Sequencing note: the style guide can be developed before the typography application skill is built — in fact, must be, for the skill to have rules to apply. It can also proceed in parallel with ongoing publication work; it doesn't block Essay I & II publication (which uses mechanical + lightly-linguistic typography only, per the three-layer decomposition).

Not this morning's work. Dedicated session when the steward is ready.

Typography register — DECIDED 2026-04-18: Pattern 3 (role-assigned families)

Surfaced when the steward noticed a duplicate dateline on the live v2 Ethics essay page, which led to a broader conversation about ARC's typographic system. A decision was reached and is recorded here so the style-guide session has a starting position rather than a fresh question.

Decision (authored 2026-04-18):

ARC adopts a role-assigned typographic system:

  • Serif — EB Garamond — body text + headings (content register). All editorial/literary content authored by the writer.
  • Sans — IBM Plex Sans — navigation / wayfinding (between-piece). The Reading Compass, enfilade navigations, between-page orientation.
  • Mono — IBM Plex Mono — apparatus (metadata register). Dateline (hic jacet), technical metadata, any "about-the-artifact" labeling.

This is Pattern 3 in the typology surfaced during the 2026-04-18 conversation — distinct from Pattern 1 (classical humanist unification; all-serif with careful variation) and Pattern 2 (magazine/editorial; serif body + sans headings and nav).

Primary justification — accessibility. Family-change differentiation is more robust under visual impairment than within-family differentiation. Italic, small caps, weight, and size variations rely on fine details that degrade first when acuity drops; family changes (sans vs serif vs mono) are coarser signals (stroke width, x-height, presence/absence of serifs, proportion) that survive visual degradation. The steward is myopic and now uses progressives; ARC should be legible to readers who share that constraint, and the role-assigned system serves them through the coarse signal.

Secondary justifications.

  • Architectural clarity: each register has one job; the reader learns to "read" the type itself as meaning
  • Screen-primary context: on the web the reader cannot control size/proximity the way a print reader can, so the type system has to do more signaling work than in print
  • Minimal drift from current state: ARC is already ~90% Pattern 3 in practice; no large migration required

Current font stack — retained for now.

EB Garamond (serif) + IBM Plex Sans + IBM Plex Mono. The steward named that they need time to consider font changes; the system is decided (Pattern 3), the specific families are refinable without changing the system.

Cleanup implied by Pattern 3 adoption (for a future session):

  1. Delete the dead heading-base mixin in scss/AldineXXI/_mixins.scss — it sets $sans-family for headings, which contradicts Pattern 3 (headings are content, should stay serif) and is already overridden by _base.scss:39. The mixin is vestigial.
  2. Audit remaining nav surfaces (site header/footer, Reading Compass, tag pills, meta labels, breadcrumbs, form UI): for each, decide whether it is wayfinding (→ sans), apparatus (→ mono), or editorial content (→ serif). Declare each in the style guide.
  3. Archive the scss/AldineXXI/archive-v1/ backup files if no longer needed as reference.

Counter-arguments held but not overriding (for future reconsideration):

  1. Voice tension. EB Garamond is 16th-century humanist; IBM Plex is 2010s industrial/corporate (designed for IBM's brand). The three families don't equally belong to ARC's contemplative register. If this tension becomes aesthetically costly over time, reconsider the specific families (see Font swap candidates below) without changing Pattern 3.
  2. Architecture vs. continuous flow. Pattern 3 announces "here is content, here is nav, here is metadata" via family shift. A strong typographer would argue Pattern 1's unified voice better serves contemplative reading — the reader stays in one typographic world rather than experiencing register-breaks. If future evidence suggests Pattern 3's breaks are fragmenting rather than orienting, Pattern 1 is the fallback.
  3. Designing-for-self bias. The accessibility benefit is asymmetric — strongest for low-vision readers, neutral-to-mildly-fragmenting for others. Worth naming so it doesn't get rewritten as "Pattern 3 is universally better" in future reasoning.

Font swap candidates considered 2026-04-18 (not adopted, held for future consideration):

Listed roughly from lowest-regret to highest-commitment:

  • Mono: iA Writer Mono / Duo (open source). Swap IBM Plex Mono → iA Writer Mono. Warmer, more humanist than Plex Mono; designed explicitly for long-form writing; the steward authors in iA Writer so this creates through-line continuity from composition to publication. Small change, clear voice-yield. Hedge: verify specific repo + naming (Mono / Duo / Quattro) before committing.
  • Sans: Alegreya Sans or Ysabeau (open source). Warmer humanist sans alternatives to IBM Plex Sans. Alegreya Sans (Juan Pablo del Peral) is designed as companion to Alegreya Serif — different genealogy from Garamond but more literary in register than Plex. Ysabeau (Christian Thalmann / Christophe Caignaert) is newer, designed neutral-humanist. Either is a softer pairing with Garamond than Plex.
  • Adobe CC path (if the steward has Creative Cloud). Garamond Premier Pro (Slimbach) + Cronos Pro (Slimbach, humanist sans) — same designer, voice-aligned pair. Premier is the finest Garamond available (optical sizes, full character set). No mono in the Cronos family; still pair with iA Writer Mono. Free under existing CC subscription.
  • Superfamily — Fedra (Typotheque, Peter Biľak). Fedra Serif + Fedra Sans + Fedra Mono, all designed together. The rare case of all three registers as a unified system. Contemporary humanist, editorial register, designer-run foundry with fair licensing. Paid, perpetual, roughly $300–600 for a full weight set (verify current pricing). The cleanest voice-coherent answer if budget allows.
  • Superfamily — FF Scala + Scala Sans + separate mono (FontFont / Martin Majoor). Majoor's 1990s classic, among the earliest deliberately-paired serif-sans superfamilies and still among the best. No dedicated mono; pair with iA Writer Mono or similar. Most classical-humanist choice. Paid through Monotype.
  • Superfamily — Adelle + Adelle Sans + Adelle Mono (TypeTogether). True superfamily spanning all three registers. But Adelle is a slab serif, so adopting it means a body-type shift away from Garamond's Renaissance humanism toward a warmer 20th-century editorial register. Paid.
  • Brill (John Hudson for Brill Publishers) — serif + sans, no mono. Designed specifically for humanities publishing; most voice-aligned for ARC's literary/scholarly register. Licensing: free for scholarly personal use; commercial requires purchase. Worth exploring with careful read of the license.

Reconsideration triggers for the specific families (not for Pattern 3 itself):

  • Voice tension between Garamond and Plex becomes aesthetically costly in lived use
  • A specific future workstream (e.g., the typography application skill being built) makes the families' mismatch operationally visible
  • The steward completes appetite-assessment for font investment and decides a paid superfamily is worth the commitment
  • Open-source alternatives (Alegreya Sans, Ysabeau, iA Writer Mono) mature into production-readiness for ARC's specific needs

Naming for the record. The steward's framing on 2026-04-18: "Assigned roles to family seems logical to me and orienting (I am heavily myopic and now need progressives, so I tend to think of people who may need support visually — so serif for the body, sans for nav, and mono for apparatus seems to make things clear)." This sentence is the canonical articulation of the Pattern 3 decision for ARC.

Web typography spec coverage — see dedicated memory

The link work of 2026-05-02 (§VII.c spec drafted; SCSS migrated; soft-tint tuning iterated) surfaced that humble typography surfaces had been left to browser-defaults plus ad-hoc accumulation. Same diagnostic likely applies elsewhere. Steward direction: "the work needs to be bien-fait."

Tier 1 (lists · inline code + code blocks · headings hierarchy beyond H1), Tier 2 (smart-quote / em-dash conventions · numerals lining-vs-old-style · ::selection), Tier 3 (<abbr> / <mark> / <table> / print stylesheet / prefers-reduced-motion), Tier 0 done, plus genuinely-don't-need items, all inventoried and ranked in:

→ project-arc-web-typography-spec-coverage.md

This sits adjacent to Style Guide redevelopment but is distinct: the Style Guide is internal vocabulary (semantic post types, ornament classes, conventions); the web typography coverage is element-level CSS spec (what does a list / heading / code block render as). Both feed each other; should be read together when style-guide work resumes.

§IV ornament retirement — content cleanup needed (2026-05-03)

SCSS audit (2026-05-03) surfaced major spec/content mismatch: §IV explicitly retires the seven .ornament.* classes (.completion, .asterism, .marginalia, .lozenge, .gloss, .glimpse, .photo-essay), but content corpus has ~213 .ornament.* uses across markdown files. Steward decision: ornaments are retired per spec; content needs to be cleaned up, not just SCSS.

Migration work (substantial):

  • Per-use audit of ~213 ornament instances → classify each into §IV-stated replacement (class: frontmatter / §II silence / future Pause/Close ornament)
  • Edit affected markdown files (~50-100 files, multiple uses each)
  • After content migration: SCSS .ornament rules retire from _utilities.scss
  • Update §IV to confirm retirement is operative not aspirational

→ project-arc-ornament-spec-vs-content-mismatch-pending.md — full details, decision-record, sequencing

Tied to: project-arc-pause-close-ornament-and-hr-audit-pending.md — the Pause/Close ornament design that establishes what the .completion / piece-end uses migrate INTO. Realistic order: Pause/Close design first (so we know what content migrates to), then content audit + migration, then SCSS retirement.

§IV Pause/Close ornament + hr audit — design needed (2026-05-03)

Closely related to the ornament-retirement migration above. §IV describes Pause/Close ornaments functionally (paired-and-related cul-de-lampe at two scales) but the asset itself is yet to be designed. Steward direction: "finis coronat opus" — needs serious study. <hr> content also needs audit (some legitimate Pause anchors, some incorrect carryover). Interim: three-dot · · · per _typography.scss hr rule.

→ project-arc-pause-close-ornament-and-hr-audit-pending.md


Chamber voices — archived 2026-04-18

The content/chamber/voices/ directory (index.md + alexander/fusus/ngana-kulintja voice files) was archived to docs/archive/chamber-voices/ 2026-04-18, authorized by the steward in the course of unblocking the Hakyll versioning infrastructure deployment.

Why: a pre-existing dependency cycle in content/chamber/voices/index.md (the index's compile called loadAll on its own directory, triggering Hakyll's cycle detection despite the post-load filter). Flagged in site.hs as "TODO MODE-2: Re-implement voices with proper dependency resolution" — longstanding. It was blocking every full site build.

What was removed alongside: voicesCtx in site.hs (dead code after branch removal), voices-nav links in templates/chamber-canon.html and templates/chamber-deliberations.html.

What remains operative: the voices_featured field in deliberationCtx — deliberations still reference voices by name in their frontmatter; the text-level reference survives the archival.

Reinstatement condition (steward's note): "please note as it could be something to consider once the source aware chamber is fully implemented."

When the Chamber/BMF integration matures — i.e., once BMF recall can enumerate voice appearances across the corpus with proper source-awareness — the voice-as-first-class-document pattern can be reimplemented. At that point the index would be generated from a recall query, not globbed from markdown, which sidesteps the dependency cycle entirely. The archived files are reference material for that future work.

Source-aware Chamber is downstream of L1 reliability stabilization and Chamber Phase 3 (currently parked).

TODO: Reading Compass optical rebalancing (cosmetic, deferred)

The 9-point Reading Compass nav uses per-glyph font-size !important rules in scss/AldineXXI/_compass.scss:33-72 attempting to normalize perceived weight across the Unicode symbols (●○⟐◈◉⊙☷✎✍︎). Current values: Essays ● at 0.75rem, Observations ○ at 1.1rem (baseline), Chamber ⟐ at 1.35rem, Fragments ◈ at 0.8rem, Glimpses ◉ at 0.7rem, Photo Essays ⊙ at 0.85rem, Archive ☷ at 1.25rem, About ✍︎ at 1.3rem.

Known not-quite-working. Steward observation 2026-04-18: "the reading compass glyphs are meant to be adjusted to each other to be optically equivalent sizes, but I never got that working."

Why it's hard. The values were chosen once and never iterated against actual rendering at scale. Unicode symbols fall back to different system fonts depending on platform (Apple Emoji, Segoe UI Symbol, Noto Sans Symbols2, etc.), so a value that looks optically balanced on one reader's machine can look wrong on another's. The optical-size problem is real but platform-variable.

Possible paths to resolution (not scoped here):

  1. Custom SVG glyphs — replace Unicode symbols with in-house SVG icons designed together with proper optical equalization. Full control, platform-independent, but a design project in itself.
  2. Iteration with multi-device testing — tune the font-size values against actual rendering on macOS, iOS, Windows, Android, common Linux. Cheaper than SVG but still ongoing maintenance as OS font rollouts change symbol rendering.
  3. Accept the platform variance — document that compass symbols render differently across platforms and that the current values are best-effort, not pixel-perfect. Simplest.

Deferred — cosmetic, not blocking anything, genuinely non-trivial. Worth revisiting alongside the style-guide session or when there's appetite for a glyph system.


Mobile review list — 2026-04-18 evening (steward from mobile, Kai napping)

Captured verbatim from the steward's list, prefixed #ARC. Not urgent. Mix of small mechanical fixes and genuinely philosophical questions. To be taken up in future sessions — likely alongside the style-guide session for the philosophical ones, and as quick-passes for the mechanical ones.

Mechanical / small:

  • Typography page needs updating to reflect reality and established spec — "the voices notably" (with chamber voices archived 2026-04-18, any references on the typography page to the voices system are now stale)
  • Colophon — The Formation missing a context sentence (cf the Guides section which has one) — the Formation section added 2026-04-17 has entries but no introductory context sentence
  • Colophon mini nav: no link to AldineXXI — the in-page navigation at colophon footer should link to the AldineXXI typography page
  • Remove Patterns from about pages — pure pedagogy, probably belongs on the personal site (eventual davidglidden.eu). To be decided upon properly later; for now, remove. Steward's framing: "To be decided upon, but for now, let's remove."
  • Glimpse on mobile not edge-to-edge — responsive CSS issue; class expects full-bleed per spec, not rendering edge-to-edge on mobile viewport
  • Apparatus: location should always be included — currently conditional ($if(location)$ in post.html). Also open question: italics? (the .dateline-location class already has font-style: italic, but the question may be whether that's the right choice or should be revisited)

Philosophical / needs thought:

  • About enfilade: does it need updating? — "What stays? What goes?" With the decoupling horizon in view (ARC → animalrationiscapax.org, personal site → davidglidden.eu), the about-page enfilade navigation's scope may shift; worth auditing now regardless.
    • Reframe (2026-04-18 evening, verbatim steward): "the enfilade acts as both access and map." The enfilade declares the about-territory to the reader.
    • Architecture clarified (after multiple misreads): The about-enfilade is inline on each about-constellation page (not a template partial). Each page maintains its own <nav class="about-enfilade"> with the full list + its own <span class="current">...</span> marker. The main about page itself (about.md) does NOT carry an enfilade — it's the index of the mini-site. The about pages are "a mini-site explaining the why and how of ARC" (verbatim steward). The Reading Compass is a separate, site-wide glyphic nav in the footer of every page. A vestigial partial at templates/partials/footer-about.html contains compass-destination items and caused my initial confusion — it's probably orphaned, worth investigating and likely removing as separate cleanup.
    • Real question (now with clean data): Four items appear on about.md's branches list but aren't in the inline enfilade (per navigation-philosophy.md as the canonical example): AldineXXI, Vignette, Resume. And Bio is in the enfilade as a peer branch but on about.md only appears under Contact (not as a listed branch). Steward's "what stays? what goes?" question applies specifically to these four.
    • Decision needed before fix: Which of {AldineXXI, Vignette, Resume, Bio} are peer-about (in enfilade + listed as branch on about) vs. contact/outward-portal (not in enfilade)?
    • Symmetria lesson recorded: Named objects in the codebase (about-enfilade, footer-about, Reading Compass) carry specific meanings defined by the implementation, which don't always match abstract connotations. The steward explicitly framed this after my second misread: "the navigation page will explain the reading compass concept. This is frustrating, what can I not make myself clear?" Future sessions: when the site has self-documenting pages (navigation-philosophy.md, colophon.md, typography.md, etc.), read those first before applying abstract architectural intuitions.
  • Apparatus dates on info pages; define spec — info/about pages don't have a clear dateline convention yet. Should they show a publication date? A last-revised date? Nothing? Spec needed before piecemeal adoption.
  • Genre riddle — "One entry is a 'meditation' but no way to see that unless looking at the archive page. Should meditations be coupled with observations? Probably not. Are fragments observations? Maybe? How to solve this 'genre' riddle?" — The Reading Compass has 9 points but the semantic types include meditation, fragment, observation with overlapping registers and unclear navigation surfacing. Worth surfacing in the style-guide session as part of the typological-clarity work.
  • Glimpses double metadata — "caption and apparatus — what to do?" — glimpses currently surface both their inline caption and the template-rendered apparatus (dateline + figcaption via mono .dateline class). Redundancy to resolve; design decision about which surface carries the metadata canonically.

Steward's original list preserved: the tag was #ARC in the steward's message. These items surfaced during a mobile-view review while Kai was napping 2026-04-18 evening — worth noting that mobile review surfaces different issues than desktop review (e.g., the edge-to-edge glimpse issue only shows up there).

Kai-nap notes — 2026-04-20 (steward, walking with Kai asleep)

Three captures, low urgency, not blocking:

  1. <hr> above versioning is too much. A horizontal rule renders above the version-stamp paragraph — visually heavy. Likely a CSS rule on .version-stamp or a template element. Single small edit when next touching styling.

  2. AldineXXI page — paraphrased quote needs to go (reduces inadvertent appropriation/inaccuracy); See Also section is unnecessary (page should stand on its own). Both removals queued for next AldineXXI editing pass.

  3. Visual sequences for glimpses (or photo essays). Real design question — glimpse-sequences feel especially right (thematic curation of single-image-aphoristic pieces; "Doors I have walked through," "Light on water," "Cathedrals at dusk" as natural exemplars). Spec §4 already names sequences as orthogonal to types ("A piece may be standalone AND a member of a sequence"); the principle was framed for essay-sequences (After the Reply) but extends. Photo-essay-sequences are less natural (a photo essay IS already an image-sequence-as-argument; sequence-of-photo-essays would be meta-curation). Implementation: new sequence: frontmatter axis + sequence-listing template + URL routing. Small work, large affordance. Worth a focused design pass.

  4. Footnote rendering — currently careless, sidenote/margin-note system the eventual destination. Steward sharpening 2026-04-20: "footnotes as they are rendered now has to change, it seems so careless within an otherwise balanced vessel." The default Pandoc footnote rendering was never brought into the AldineXXI typographic system; against the cared-for surrounding (oldstyle figures, careful spacing, mono datelines, italics for foreign words, dropcap register-shifts), default footnotes read as carelessness even though they're just absence-of-care.

Three forms identified, distinct reader-experiences:

Form Reader experience Use case
Sidenote Marker in text → content in margin at same vertical position. Optional attention. Brief amplifications, citations, glosses — most cases
Margin note No text marker; content appears alongside. Pure aside. Commentary that shouldn't interrupt at all (manuscript marginalia register)
Footnote / Endnote Marker in text → content at bottom of article. Reader jumps. Long discursive notes, block quotes within notes, anything that won't fit a margin column

Recommendation surfaced 2026-04-20: for ARC's contemplative-essayistic register, sidenotes can replace footnotes for almost all uses, possibly all. Margin notes are a separate affordance worth considering — they suit the contemplative register particularly well (a thought in the margin that doesn't demand attention). Footnotes as fallback only IF the corpus generates long-discursive-note content (likely rare given ARC's style).

Design pattern proposed: spec sidenote-by-default + margin-note as explicit affordance + footnote as escape-hatch (or absent if not needed). Frontmatter override or markdown convention for the rare footnote case. Open question for steward: does ARC corpus actually generate long-discursive notes that wouldn't fit a margin column?

Two paths to get there: (a) interim improvement now — bring current footnotes into AldineXXI care (oldstyle numerals, italic notes, ornament-or-whitespace divider replacing default <hr>, "Notes" section with its own register). Stopgap that resolves immediate jarring; sidenotes still become destination. (b) skip interim, go straight to sidenote/margin-note system — Tufte-CSS adaptation, sidenotes on desktop, graceful mobile collapse. Choice depends on footnote-density in current corpus; audit not yet done.

Steward's framing pattern: walking with Kai asleep generates ideation (per the reverie/Rousseau lineage already captured). These are nap-notes — surfacings, not action items.

Wrap-up additions — 2026-04-20 (steward end-of-session)

  1. Bio rewrite encompassing the envergure of his work. Steward end-of-session 2026-04-20: "compose appropriate bio that encompasses the [envergure] of my work, consider the other personal elements that will need to be added (in the end, I hadn't 'moved in' in a clear enough way for my musical work!)". The current bio.md/about did not adequately surface the musical-work dimension; the about-page reflow exposed this gap when the steward saw it freshly. The bio needs to present multiple selves (principal violist with Le Concert des Nations / Les Musiciens du Louvre; writer of ARC; designer-of-ARC's typographic system; teacher/mentor; CapableMind co-founder; father — per feedback-children-not-named-online.md, family present obliquely or not at all) without forcing partition. Same architectural principle that drove the about-stays-unified decision: cross-discipline integration is the substance; partitioning betrays it. Best done after typology spec locks (so the bio inhabits the new register-system honestly) and after the about-page reflow lands. Its own focused session.

  2. ARC CLAUDE.md update — overdue. Current file (~/_Dev/animal-davidglidden-eu/CLAUDE.md) has: outdated compass listing (8 points, missing Gloss; will need 10 with cluster note), repetitive "AldineXXI v2.0 Framework Implementation" status entries (multiple duplicate dates), references to older unified-consciousness-engine vision, stale SESSION-MEMORY pattern. Today's decisions need to land in CLAUDE.md: typology (11 types, posture-axis triplet, cluster), hic apparatus convention, not-naming-children principle, compass restructuring (10 points, ⊙ → meditation/reverie cluster, ◧ → photo essay), Effect-style spec lifecycle, glyph reassignments. Cleanup pass + decision-record update — bounded session, ~1 hour.

  3. Corpus location-retrofit pass. Many existing posts lack location: frontmatter; need to add per the hic convention. Already in Session γ scope (apparatus convention adoption); flagged here for visibility.


Repo-level cleanup

  • Lots of files to clean up throughout the repo (unspecified, but "lots and lots").
  • Many pages to rethink.

Notes on posture

  • Steward's framing: "work to be done." Not an urgency, a surfacing.

  • The versioning question is the load-bearing one. The rest is clearing and composition, now tractable because local dev works.

  • ARC's contemplative slowness + "do things once, correctly" is compatible with more than one answer to the versioning question — worth holding the space before deciding.

  • 2026-04-23 addition (steward, walking with Kai): "the ARC todo list is getting long, but this is the doorway for people to see how I work and think, and it needs to embody my values, not be performative… that is why I sometimes get lost in the minutiae." The minutiae ARE the mechanism — glyph choice, apparatus vs. type, how an archive is framed, whether a compass row exists. When the surface IS the substance (values-embodied vs. values-performed), attention to the surface IS attention to the substance. For future Claude: don't treat ARC's accumulated small decisions as a distraction from "real work." This IS the work. Track them honestly; resist the pull to compress or streamline for readability. The list-length is a feature of the practice, not a problem to solve.

  • 2026-04-23 — the compagnonnage ground (steward): "And even if no one ever come to visit it, at least it will be, as my mason-brothers would lovingly approve, « travail bien fait »." This is the deepest lineage for ARC's posture. Travail bien fait — the compagnonnage ethic carried in French masonry tradition — is the Prime Directive in its craft-inherited form. The hidden stone dressed with the same care as the visible one. The work's dignity depends on the doing, not the seeing. This is the mechanism that makes values-embodied operative rather than performative: performance requires an audience; craft does not. It also grounds the prior insight (minutiae-as-mechanism): the compagnon's small cuts on the back-face of the stone are the same category of attention as the visible carving. For future Claude: when the steward pauses on a detail that seems small, do not accelerate. The craft ethic is operative and it is the thing ARC exists to express. The same ethic runs through the steward's professional life (Savall's historical-performance practice: the instrument choice, the articulation decision, the musicological research that no audience member will ever notice, dressed with the full care of the visible performance). ARC is this ethic applied to a different medium.


2026-04-20 — Kai 9+9 day · Meditation defined · Reverie surfaced · corpus typing audit

Meditation defined (steward, verbatim)

"Meditations always have an object, and we pose attention upon the object to root ourselves in the present moment in order to observe."

This sentence is load-bearing for the typology spec's §1 Meditation entry — drop it in verbatim. It distinguishes Meditation from Observation (which is of the seen thing) and Essay (which argues): Meditation is through the seen thing toward what surfaces from rooted attention. The piece is the meditation; the object is the entry, not the subject.

"Worldfulness" — Vico → Harrison reference (correction)

Steward used "worldfulness" in his Kai-9-month piece. I flagged it as possible coinage. Steward corrected: it's a Vico → Harrison reference (mondo / made-world; the human capacity to inhabit the institution-language-custom world, not merely biological aliveness). Same Harrison who anchors I16's five-source convergence. New drift pattern: flagging precision-language as imprecision when I lack the reference frame. Logged in 2026-04-20 ledger.

Reverie — proposed as new type

Three converging signals from corpus audit + steward observation:

  1. Two pieces explicitly name "reverie" while classed as Observation. Heliotrope (2020-05-19): "Thus was my reverie in that moment." Graffiti Girl (2020-04-23): "the world melted away as I drifted into reverie. Then, as quickly as it had set in, my reverie dissipated…" The pieces ARE reveries, hiding under Observation because the type didn't exist.
  2. Reverie is structurally distinct from Meditation. Meditation: posed attention, rooted in present, insight surfaces from anchoring. Reverie: attention loosens, world melts, anchoring releases, generation comes from the unmooring. Bachelard's Poetics of Reverie tradition — anima-driven, image-and-tone, generative-but-not-argumentative.
  3. Walking is reverie's classical condition (Rousseau's Reveries of the Solitary Walker). Steward's observation 2026-04-20: "almost all of the insightful work we've done in the last week has been with Kai asleep in the sling while I walk in order to keep him asleep. I've long noticed that walking seems to stimulate ideation, but I'm only seeing to what point that is true by intentionally looking at it." Walking-with-Kai-asleep is the steward's reverie condition operative in his current work practice.

First-draft entry for spec §1:

Reverie — prose, unmoored-generative posture. A waking-dream state in which the world's anchoring loosens and image/tone/recollection drift productively. Object often present at the start (the graffiti girl, the sunbather) but loosens. Insight surfaces from unmooring rather than from rooting. Walking, twilight, fatigue, gentle attention — the conditions. Distinct from Meditation (which roots) and Observation (which holds sensory anchor). Glyph: open — perhaps motion or dissolution, distinct from the still-geometric family.

This expands the posture axis from binary to ternary: Observation (anchored-noticing) · Meditation (rooted-inhabiting) · Reverie (loose-drifting). Feels true to corpus rather than imposed on it.

Corpus typing audit — fragments (2)

  • archive/December 22nd 2023.md (class: fragment) — Mis-typed as Fragment. Has object (half-light morning), poses attention, surfaces insight ("a centered silence can open infinite paths to the outside"). Is a Meditation by today's definition. Also: duplicates posts/2023-12-22-December-22nd-2023.md (classed observation). Same content, two classes — corpus bug.
  • pages/now-page.md (class: fragment) — Mis-typed as Fragment. This is a /now-page in the Sivers tradition; meta-about-person register. Should reclassify to class: about once that class lands.
  • Striking finding: zero true Fragments in the corpus by today's definition. Either Fragment is a real type waiting for content, or what reached for "fragment" was Observation/Meditation/Reverie under another name.

Corpus typing audit — observations (8)

Piece Verdict
Dec 29 — Café (Charonne/Ledru Rollin) ✓ True Observation
Dec 31 — Couple about to kiss ✓ True Observation
Jan 11 — Sun returns / rural France ✓ True Observation
Jan 3 — Heroin addict on métro ◐ Edge → leans Meditation; chamber: true already flags extra weight
Heliotrope (2020-05-19) ✗ Mis-typed → Meditation (insight: "we are also heliotrope"); names "reverie" inside
Graffiti Girl (2020-04-23) ✗ Mis-typed → Reverie (the piece IS a reverie, named twice inside)
Dec 23 — Dream (viola under wheels) ✗ Not Observation (no waking sensory anchor); Reverie's neighborhood, or Dream as its own micro-type
Dec 22 — Half-light Bach (Duplicate of fragment-1 above)

Summary: 3 of 8 observations are clean. 5 need attention.

The Threshold Breath flag

Currently class: meditation, but reads more as proclamation/threshold-marking ("This is the threshold. Let it be marked.") than meditation by today's tighter definition. Worth re-reading against today's anchor before treating as a Meditation exemplar in the spec.

Steward framing — executor/jurist precision question

Steward said: "What a pity there is no way to formulate this in such a way that I could have the executor or jurist apply such painstaking attention to detail—how that would help me to overcome my lack of engineering ability by simply being as precise in my instructions as possible." I pushed back: the lever isn't instruction-precision; it's agenda-lowering structures (Executor Agency Directives, Symmetria practice of return, three-party authorization). Better instructions move the dial; agenda is upstream of instructions because training installs it. The structures we've built are what move the executor closer to attentive-not-agenda-driven work — and they work because they were built, not because of better engineering.

The Kai-9-month piece itself is, without the steward initially naming it that way, a meditation on the contamination problem approached from human attention rather than LLM attention. Agenda — the web of purposes that silently pre-filters the world before we have even looked at it — is structurally the same shape as what training installs in the executor. The piece reaches the same place years of contamination-problem inquiry have reached, by a different door.

Kai 9+9 piece — status

Drafted by steward today (2026-04-20, Kai's 9-months-in-belly + 9-months-on-belly day). Éveil → Attention/Intention → agenda-as-pre-filter → revision of éveil (going-back-to-sleep). Two micro-flags surfaced: "even only" potentially redundant (or intentional doubling); "worldfulness" confirmed Vico/Harrison. Otherwise ready. Steward intended to publish today as reverence to Kai.

Recommendations carried into next ARC session

  1. Resolve Dec 22 duplication (corpus bug)
  2. Reclassify Heliotrope → Meditation; Graffiti Girl → Reverie (if Reverie lands); Dec 23 dream → Reverie or Dream-micro-type; Dec 22 half-light → Meditation
  3. Reconsider Fragment — author into the type or admit corpus has been writing in three other prose-non-argumentative registers
  4. Add Reverie to spec §1 — first-draft entry above
  5. Re-read Threshold Breath against today's tighter Meditation definition
  6. Drop today's Meditation definition into spec §1 verbatim

LOCKED 2026-04-20 — Reading Compass restructuring

Reframe held: Reading Compass is a quality-of-attention index, not a type-index (per navigation-philosophy.md). Type-system and compass-system can decouple, but with constraint that no type be orphaned from navigation (steward 2026-04-20: full-contents-listing-as-landing avoidance is operative).

Decisions:

  1. Cluster #2 adopted (Meditation + Reverie share one compass point). Real adjacency: both ask the reader for sustained-receiving attention; the rooted/unmoored difference is writer-process, not reader-mode. Cluster #1 (Fragment + Glimpse) NOT adopted — Glimpse's standalone identity in the corpus is load-bearing.

  2. Compass count: 9 → 10 points. Meditation+Reverie cluster takes one slot; net +1 from current 9.

  3. ⊙ reassigned to the Meditation/Reverie cluster. Steward's intuition validated by deeper resonance: ⊙ is the astronomical sun symbol; center-dot reads as object-of-attention, surrounding circle as attention-posed-around-it. Resonance with Heliotrope ("we are also heliotrope"), Bach sarabande ("the half light seems to lift momentarily"), Graffiti Girl in gloaming light — light-at-center recurs in the very pieces being reclassified into the cluster.

  4. Photo Essay reassigned to ◧ (square half-shaded / light and time). Half-shading reads as passage — lit half receding into shadow, place falling out of active life into memory. Aldine-quiet; elegiac register. Chosen against the inaugural pipeline piece (Dover, MA — childhood-place + farewell after Moy's interment), which wants the temporal-elegiac reading. The medium itself attracts time/passage themes (Berger's subjects were often elegiac); inaugural register fits the medium broadly, not just the first piece. ⊡ was the "safer categorical" alternative; ◧ chosen as truer.

  5. Migration cost dismissed by steward: few human visitors yet; no existing Photo Essays in corpus (one in pipeline). Glyph reassignment carries no real reader-relearning cost.

Resulting compass (10 points):

Glyph Cluster / Type Holds
● Essay Essay
◧ Photo Essay Photo Essay
◈ Fragment Fragment
◉ Glimpse Glimpse
○ Observation Observation
⊙ Sustained inhabiting Meditation + Reverie
⟐ Chamber Chamber
✎ Gloss Gloss
✍︎ About About
☷ Archive Archive

Piece-level glyph decision LOCKED 2026-04-20: cluster-glyph-only. Both Meditation and Reverie pieces carry ⊙ at piece-level (archive listings, individual posts, compass). Frontmatter class: carries the type distinction. The qualifying ✦ encounter mark remains type-agnostic per spec §3 — it's the only piece-level glyph variation possible within the cluster, but it doesn't differentiate Meditation from Reverie by design.

Critical piece I initially missed (steward correction 2026-04-20): the type label is paired with the title in the apparatus across ARC. So at piece-level, readers see both the compass glyph (cluster-mode) AND the type label ("Meditation" / "Reverie") with the title. Two visible layers of information: glyph carries attention-mode, title-paired-type-label carries type-distinction. The "Meditation and Reverie sit visually identical in archive listings" framing I raised was an overstatement — they share a glyph but the type is always surfaced alongside the title. The cluster-glyph-only decision is cleaner than my initial framing implied.

Implementation footprint:

  • Spec §1 updates: Meditation glyph → ⊙; Reverie added as type 11 with ⊙ (or sub-glyph TBD); Photo Essay glyph → ◧.
  • Spec §0 axes table updates (posture axis triplet now: Observation/Meditation/Reverie).
  • navigation-philosophy.md rewrite: 9 points → 10 points (or hold "nine" framing as historical, refresh language); cluster framing for Meditation/Reverie added.
  • site.hs template/CSS audit: every hard-coded ⊙ for Photo Essay → ◧; new Meditation/Reverie pages get ⊙ assignments; compass footer template count grows by one.
  • Corpus reclassification: Heliotrope → Meditation; Graffiti Girl → Reverie; Dec 23 dream → Reverie or Dream-micro-type; Dec 22 half-light → Meditation; resolve Dec 22 duplication.
  • ARC CLAUDE.md compass section needs update (currently lists 8, missing Gloss; will need to list 10 with cluster note).

LOCKED 2026-04-20 — Hic apparatus convention: location + full date

Decision: All posts must carry location + full date (day + month + year) in the body apparatus dateline, not just month+year or location-only. The hic convention demands this — hic jacet names the precise moment of utterance, not the season.

Why this matters beyond formatting: the convention makes dedication-without-declaration possible at the apparatus level. The Kai-9-month meditation publishes today (2026-04-20) with dateline Barcelona, April 20, 2026. The day-precision encodes the dedication (nine months from Kai's birth date, in the steward's knowing) without naming the child — same principle as the not-naming rule (feedback-children-not-named-online.md). Day + place becomes a silent anchor; meaning is real but undeclared. The convention is what enables dedication-without-declaration in the apparatus layer.

To capture in spec §2 (apparatus binding):

  • Dateline format binding for ALL post types: [Location], [Day Month Year] — e.g., Barcelona, April 20, 2026
  • Italicization: TBD (Threshold Breath uses italic for elaborate datelines; Kai meditation uses plain). Probably context-dependent; spec should name the rule.
  • Required fields: location AND full date. Month-only or location-only datelines are non-compliant.
  • Migration: existing posts with month-only or no-dateline apparatus need updating. Audit needed during spec session.

Existing pieces likely non-compliant:

  • The Threshold Breath: "Written under the full moon of July 2025…" — month+year, missing day. (May want preserved for poetic register, but principle says: add day.)
  • Most observations: date in frontmatter only, no body dateline. Need apparatus-dateline added per convention.
  • Most essays: same likely state.

Steward articulation 2026-04-20: "April 20 in the apparatus — the hic convention for versioning demands this. This needs to be in spec and all posts should adopt the convention (location, date)."

REFINEMENT 2026-04-20 (after first publication exposed duplication): apparatus = canonical dateline. Body text does NOT duplicate. The post's body ends at its closing words; dateline lives only at the apparatus layer (rendered from frontmatter location: + date: via template).

  • Format LOCKED: European long-form via "%-d %B %Y" → "20 April 2026". Reasoning: ISO 8601 is numeric-only (2026-04-20) and lives at the machine layer (frontmatter date: field, already ISO); for prose display there is no ISO equivalent — date-word ordering is cultural, not standardized. European long-form chosen because it surrounds the steward (Barcelona base) and the hic carries the present, not the origin. Steward note: "I would say European format since that is where I am based (don't want to go into where I am from, I still don't have a clear answer after 51 years)."
  • Implementation point: site.hs:692 — dateField "dateline_date" "%-d %B %Y" (was "%B %Y"). One-line change ripples corpus-wide: every post's apparatus dateline now surfaces full day + month + year instead of just month + year. The day is already in each post's frontmatter date: field — change is "show what's already in the data."
  • Frontmatter contract: every post must declare location: (e.g., Barcelona, Avignon). Apparatus template renders <span class="dateline-location">$location$</span>, <time>$dateline_date$</time> (post.html L46-48).
  • Corpus audit follow-on: existing posts that have body-text datelines (Threshold Breath's "Written under the full moon of July 2025…", possibly Heliotrope, Graffiti Girl, others) will now duplicate apparatus. Audit pass needs to: (a) add location: to every post that lacks it; (b) remove body-text datelines that duplicate apparatus; (c) consider whether poetic body datelines (Threshold Breath's elaborate one) should be preserved as separate body element rather than as "dateline" — open design question.

TODAY'S PUBLICATION — Kai 9+9 piece + Avignon poem

File 1 written 2026-04-20: content/posts/2026-04-20-On-Eveil-Sommeil.md

  • Title: On Éveil / Sommeil (slash holds the pivot the piece performs; bilingual texture matches body)
  • class: meditation (first piece classified under today's settled definition)
  • Glyph at compass: ⊙ (cluster glyph for Meditation/Reverie)
  • Description: "Worldfulness an infant lives by, and the web of purposes we acquire to avoid it."
  • Dateline: Barcelona, April 20, 2026 (first post under the new hic apparatus convention; encodes Kai-9-month dedication without naming)
  • Body: as steward typed it; "even only" preserved as intentional emphatic doubling
  • Filename: slash dropped, accent stripped (On-Eveil-Sommeil); URL: /On-Eveil-Sommeil/

The piece is itself the test case that drove today's typology forward, and now the first piece classified under that typology. It also models two principles simultaneously: not-naming-children (body refers to "an infant") and dedication-via-apparatus (April 20 as the silent anchor).

File 2 written 2026-04-20: content/posts/2025-11-19-Time-Is-Not-A-River.md

  • Title: Time is not a river (poem; opening line repeats as title)
  • class: meditation (Meditation by today's definition: object = time-as-well, posed attention, rooted in present, surfaces insight from rooting)
  • medium: verse (NEW frontmatter field — first appearance; spec §0 medium axis to be extended from prose/image to prose/image/verse)
  • Glyph at compass: ⊙ (same cluster glyph; verse-modifier doesn't change attention-mode glyph)
  • Description: "Time as a well, fed by what you have honored — the careful work, the careful love." (suggested by executor; steward to confirm/revise)
  • Dateline: Avignon, 19 November 2025 (under hic apparatus convention; piece had been "Ready to publish" in Obsidian since November)
  • Source: ~/Library/Mobile Documents/iCloud~md~obsidian/Documents/David, root-and-branch/00. Compass/00b. Constellations/Animal Rationis Capax/10. Ready to publish/Time is not a river..md
  • Verse handling: Hakyll ignores unknown medium: frontmatter cleanly today; spec needs §7 entry and §0 amendment to formalize verse as medium-axis value; future template work could read medium: verse to apply verse-typography (narrower column, preserve all line breaks). Defer to Session β/γ.

SESSION β SCOPING REPORT (compiled 2026-04-20 from site.hs + templates inspection)

What I read: site.hs (845 lines, focused on lines 160-180, 400-420, 517-595, 790-830), templates/partials/footer-compass.html, templates/post.html, templates/post-list.html, templates/archive.html, templates/renderGlyph.html, scss/AldineXXI/_compass.scss. Did NOT read: default.html, frontispiece.html, home.html, footer-standard.html, _utilities.scss, _frontispiece.scss (audit pass — flagged for Session β).

Critical finding: footer-compass.html currently has only 7 points, not 9. The spec/nav-philosophy.md describes 9; the implementation has 7. Gloss (✎) and About (✍︎) are MISSING from the footer entirely — pre-existing gap, not caused by today's restructuring. Archive uses ↑ in footer-compass.html but ☷ everywhere else (CSS, nav-philosophy) — inconsistency.

Routing pattern (site.hs lines 517-590): each class has its own listing page generated by create ["{class}s.html"] block, all using filterPostsByClass helper at line 161. Existing routes: essays, observations, fragments, glimpses, photo-essays. Class-listing URLs auto-pluralize. Post breadcrumb uses /$class$s.html.

Eligibility lists (site.hs): four DIFFERENT lists of "eligible classes" exist with different memberships:

  • L411 (needsGlyph): essay, fragment, meditation, observation
  • L808 (eligibleClasses): essay, fragment, observation
  • L826 (also eligibleClasses): essay, fragment, meditation, observation, chamber
  • L792 (titleClasses): essay, meditation, chamber

These are inconsistent and worth a separate cleanup pass; for Session β, focus is adding reverie to all four lists (and possibly glimpse, photo-essay, gloss, about where appropriate).

Concrete Session β edit footprint:

  1. site.hs (~30 lines added/edited):

    • New create ["meditations.html"] block (model on observations.html L529-543)
    • New create ["reveries.html"] block (same model)
    • Decision needed: separate meditations.html + reveries.html, OR one cluster page /inhabit/?
    • Add "reverie" to L411, L808, L826, L792 eligibility lists as appropriate
    • Photo-essays.html block (L577-590) needs no change (filter by class: photo-essay still works; only the glyph display changes)
  2. templates/partials/footer-compass.html (rewrite the <nav> block, ~10 lines):

    • Add Gloss ✎ → /gloss/ (currently missing)
    • Add About ✍︎ → /about/ (currently missing)
    • Add Meditation/Reverie cluster ⊙ → routing TBD per cluster decision
    • Change Photo Essays glyph from ⊙ to ◧
    • Fix Archive: ↑ → ☷ (consistency with rest of codebase)
    • Result: 10-point compass
  3. scss/AldineXXI/_compass.scss (~25 lines edited):

    • L63-66: Photo Essays now ◧ (visual weight different — re-tune size)
    • Add: Meditation/Reverie ⊙ size-tuning
    • Add: Gloss ✎ size-tuning (currently absent)
    • L124-130: add path-mapping for .path-meditations, .path-reveries, .path-gloss, .path-about for .current state
    • L23-25: comment listing 9 glyphs needs update to 10 (note "Pattern 3 exception")
    • L106-118: mobile breakpoints adjustments for new glyphs
  4. templates/archive.html (L29-35): Browse-by-Type list currently shows 5 types; needs all 10 (or excluded set with rationale).

  5. Audit-only pass (Session β phase 1):

    • templates/default.html, frontispiece.html, home.html — find any hardcoded ⊙ for Photo Essay
    • templates/partials/post-list-home.html, footer-standard.html — same
    • scss/AldineXXI/_utilities.scss, _frontispiece.scss — same
    • assets/js/glyphs/* — likely irrelevant (legacy generative-glyph system, separate from compass) but verify
  6. Cluster-routing LOCKED 2026-04-20: Option B. ⊙ in compass points to a cluster page that lists both class: meditation and class: reverie pieces together. Both /meditations.html and /reveries.html still exist as filterable per-class views. Cluster page NAME still open — candidates: /inhabit/, /dwellings/, /depths/, /sustained/. Steward decision before Session β implementation.

Effort estimate revised: ~3 hours for full Session β (was estimated 30-60 min as "minimum viable"; the additional Gloss + About missing-from-footer work and the audit pass push it longer). Still bounded; doable in one focused sitting.

Build/test cadence: after each major edit, run make build (or whatever the current local build is) to catch template errors. Each commit per logical step (spec, footer, CSS, archive, audit-fixes), not bundled.

2026-04-21 — Bachelard reading · Meditation/Reverie grounded · /dwellings/ validated

Session opened with /wake-up; pulling thread inherited verbatim from 2026-04-20 diary: "Content Typology Specification — Session α spec lockdown." Literal question carried forward: cluster-page name (/inhabit/? /dwellings/? /depths/?). Steward led with: "dwellings feels the closest, but I would want to look deeper into what meditations and reverie are before settling." — right instinct on ordering (types deepen first, name follows).

Meditation etymology — Prime-Directive resonance

Latin meditari ← PIE *med- "take appropriate measures"; OED-family cognate with English mete. The steward's sentence — "Meditations always have an object, and we pose attention upon the object to root ourselves in the present moment in order to observe" — is the steward's first-person description of the mechanics of the practice of meditation (steward clarification 2026-04-21: "the definition of meditation I gave you is my view of the mechanics — literally what I do when I meditate"). It is not a definition of the ARC Meditation type as a literary form. The ARC type is downstream: a meditation (the piece) is the written trace / enactment of the mechanics the steward describes.

The mechanics as phenomenological procedure is literally taking the measure of something. Same root as μέτρον in the L2 Prime Directive ("μέτρον γὰρ καὶ συμμετρία καὶ τὸ πρόσφορον" — measure, proportion, what is fitting). The practice of meditation and the Prime Directive share an etymology at the stem; not decorative, structural.

For spec §1 Meditation entry: the type definition should be derived from the mechanics, with the distinction preserved. Draft direction: "A piece that writes from / traces the meditative practice — attention posed upon an object, rooted in the present, in order to observe." The practice is primary; the type is the literary form the practice takes when it writes.

Parallel to Bachelard's move: Bachelard's rêverie poétique is defined as "une rêverie qui s'écrit, ou qui se promet d'écrire" — a reverie that writes itself. The ARC Reverie type is likewise the written form of the phenomenological mode. Same structural move: practice → written trace → type. The ARC Meditation / Reverie pair inherits its structure from first-person phenomenology in both cases.

Contamination flag (executor, self-noted): initially imported the steward's sentence as a type-definition rather than as phenomenological description of the practice. Same family as yesterday's 5 returns from imagined-state-vs-verified-state. Logged.

Visuddhimagga / dhyāna — authoritative grounding for Meditation (steward-chosen tradition, 2026-04-21)

Steward direction: "Buddhist (Visuddhimagga / dhyāna)" — for the ARC Meditation type, ground in the Theravada contemplative tradition. Source materials already in hand:

  1. Full text — chamber-library/observer-problem-sources/Visuddhimagga_ The Path of Purification - Buddhaghosa, Nanamoli.md (Ñāṇamoli translation, ~22k lines, BPS 2010 ed.)
  2. Steward-attested extraction — CapableMind-AI/docs/thinking/David/l2-constitution/observer-problem/OP-EX-T1-01.md. Steward attested §2B (ten imperfections) during Observer Problem work 2026-04-07. §2A (sīla → samādhi → paññā threefold training), §2B (ten imperfections of insight), §2D (concealments analysis) all relevant; definitional material distilled.

The steward's mechanics map onto Visuddhimagga with high precision:

Steward's phrasing Visuddhimagga term Gloss
"have an object" kammaṭṭhāna meditation subject; 40 traditional subjects enumerated in Ch. III
"pose attention upon" samādhi concentration; fixing mind on the object
"root ourselves in the present moment" sati mindfulness; present-moment awareness
"in order to observe" turn toward vipassanā insight; seeing things as they are

The steward's sentence is a compact English expression of the samatha → vipassanā arc — concentration on the object, sustained by mindfulness, ripening into insight. Latin meditari "take measure" and Pali bhāvanā "cultivating, bringing into being" are etymologically distinct but name the same disciplined object-directed attention practice.

For spec §1 Meditation: ground in Visuddhimagga III (taking-up of a meditation subject) and the samatha / vipassanā distinction, alongside the steward's first-person mechanics. The ARC type is the literary trace of this practice.

Risk registered (from OP-EX-T1-01 §4D): the steward's familiarity with Theravada makes the vocabulary feel naturally apt. Using Visuddhimagga as authority for the Meditation type carries a mild version of the same contamination risk the extraction note flags. For a literary-type definition (not constitutional language), this is acceptable — but worth naming.

Jaccottet's La Semaison — personal inspiration for Dream-type (steward, 2026-04-21)

Steward: "there are more [dream pieces] unpublished — I was inspired by Jaccottet's semaison notebooks."

Philippe Jaccottet, La Semaison: Carnets 1954–1979 (Gallimard; "semaison" = sowing). A carnet form: brief, daily, seed-like — observations, dreams, fragments of reading, small moments gathered without elaborate argument. Dreams in Jaccottet are recorded as observational-elements, not elaborated fantasies.

Implication for ARC Dream type: Dream may not sit on the sustained-inhabiting axis at all. Closer to Fragment / Glimpse / Observation in duration (brief, terminal, noted), distinct from all of them in source (sleep-recalled, not wake-attended).

Jaccottet is NOT in chamber-library as source text. The inspiration is personal / biographical — not derivable from the corpus. Preserved here so the Dream-type spec entry can cite it as steward's creative genealogy without needing source-text grounding in the library.

Dream — own type, not clustered, glyph ☾ (LOCKED 2026-04-21)

Decisions locked:

  1. Dream is its own type, not a sub-case of Reverie. Gives the Dec 23 "viola under wheels" piece a proper home (yesterday's audit left it hanging) and opens the unpublished backlog.
  2. Dream does NOT cluster with Meditation + Reverie (⊙ dwellings). The argument is Bachelard's own — "Une rêverie, à la différence du rêve, ne se raconte pas. Pour la communiquer, il faut l'écrire" — the rêve/rêverie distinction is load-bearing in his phenomenology; clustering Dream into ⊙ would collapse it. Deeper principle: sleep/wake is structurally more fundamental than the bounded/unbounded axis that clusters Meditation with Reverie. Steward confirmed this framing verbatim: "Meditation and Reverie are both wakeful sustained-inhabiting (bounded vs unbounded). Dream is reported-from-sleep — the inhabiting happened elsewhere; the prose is the return." — "100%."
  3. Glyph ☾ (moon) LOCKED for Dream. Steward: "the moon glyph is ideal." Classical cosmological pair with ⊙ (sun / direct light / wakeful dwelling): ☾ = moon / reflected light / sleep's register. Visually near the ⊙ cluster without being in it.

Compass count after today's decisions:

  • Types: 12 (Essay, Observation, Meditation, Reverie, Dream, Chamber, Fragment, Glimpse, Photo Essay, Gloss, About, Archive)
  • Compass glyphs: 11 (Meditation + Reverie share ⊙; Dream takes ☾; others 1:1)

Corpus pieces to reclassify once Dream is in the spec: Dec 23 — viola under wheels (currently Observation, incorrect — no waking sensory anchor). More unpublished exist.

OPEN — possible new axis in §0: Source / Mode-of-arising

Dream's arrival surfaces a structural question the current §0 axes don't cleanly handle. The existing posture axis (attended noticing · sustained inhabiting · argument) places pieces by the quality of attention during composition. But Dream is distinguished from Observation/Meditation/Reverie not by attention-quality but by source — where the content comes from.

Candidate new axis:

Axis: Source Types
wakeful-attending Observation, Meditation, Reverie
sleep-recalled Dream
retrospectively-worked Fragment, Essay

Not yet prescribed. Flagged for steward consideration before the spec-write. May be its own axis (clean) or may fold into an expanded posture axis (less clean, but avoids proliferating axes). Leaves §0 partially open until decision.

Next step — check corpus pieces against the two grounded definitions

Before drafting §1 entries, test the practice/type distinction + definitions against extant pieces:

  • Heliotrope (2020-05-19) — yesterday's audit called it Meditation (uses "reverie" inside but behaves as Meditation). Test against Visuddhimagga-grounded Meditation def.
  • Threshold Breath — currently class: meditation; yesterday's audit flagged it as possibly Proclamation/threshold-marking. Test against tightened def.
  • Kai 9+9 piece (On Éveil / Sommeil) — classed Meditation on publication. Test against Visuddhimagga + Bachelard (does the piece oscillate between Meditation and Reverie registers? Walking-with-Kai-asleep is Bachelard's rêverie-vers-l'enfance paradigm, but the piece also contains explicit meditative-attention moves).
  • Graffiti Girl (2020-04-23) — yesterday's audit called it Reverie. Test against Bachelard.
  • Dec 23 viola dream — test against new Dream type + Jaccottet semaison shape.

DEFERRED 2026-04-21 — Threshold Breath reclassification + possible Threshold type

Tested against both grounded definitions today; fails both. Currently class: meditation — verdict: wrong.

Visuddhimagga test — fails: objects inventoried (not held); attention declarative (not posed-and-held); present is threshold-facing-forward (not present-dwelling); insight declared ("every real system must breathe"), not surfaced.

Bachelard test — fails: animus-declarative voice ("Let it be marked"); no world opens; emblematic-ritual images (moon, rain, cry), not world-generative; no anima-drift.

What it IS: performative speech-act. The piece marks the threshold by naming it. Convergence-announcement, liminal register, ritual/consecratory function. "This is the threshold. Let it be marked." — records-and-creates through naming.

Structural observation (flag, don't resolve): Threshold Breath is nearly the hic apparatus convention expanded into body content. Yesterday's hic lock ("location + full date" as hic jacet) and this piece's register are the same grammar at different scales. If type decision goes in a direction that honors this, the hic-grammar-at-body-scale reading is worth carrying.

Three paths on the table (steward to decide later):

  1. New type — Threshold (or Inaugural / Marking / Consecration). Real register; corpus likely has / will have more.
  2. Qualifying mark on a base type — a ritual-marker attachable to Meditation/Observation when function is threshold-marking. Parallels ✦ (encounter).
  3. Register-shift only — idiosyncratic; classify case-by-case under nearest type with explanatory note.

Piece held provisional — don't reclassify yet; await steward decision on type/mark.

Steward direction 2026-04-21: "let's take note and decide a bit later to not get sidetracked" — parked.

Corpus-test verdicts 2026-04-21 (pre-spec-write validation)

Heliotrope (2020-05-19) — CONFIRMED Meditation. Visuddhimagga mapping clean: old man sunbathing = kammaṭṭhāna; "Take a moment to look at the face carefully" = samādhi; "here, now, everything is fine" = sati; "we are also heliotrope" = vipassanā-insight surfaces. Internal "reverie" wordings are OED-vernacular ("briefly absorbed"), not Bachelardian rêverie-poétique. Reclassify class: observation → class: meditation. ✦ stays. Strong §1 exemplar. Content/compass resonance: a Meditation whose subject IS the sun lands at ⊙.

Kai 9+9 — On Éveil / Sommeil (2026-04-20) — CONFIRMED Meditation. More archetypal than Heliotrope. Mapping: infant / éveil / Attention / Intention / agenda = sustained objects (shifts by deepening, not drifting); "watching an infant, I see intention too" = samādhi; "hold that simultaneously in the head and heart" / "what I see now" = sati; closing reversal ("we tend to pursue going back to sleep") = vipassanā. Meta-meditative dimension: the piece's content IS about attention itself — infant's total noticing vs adult agenda-filter. Meditation-on-meditation. Current class: meditation CORRECT; no reclassification. Candidate primary §1 exemplar.

Graffiti Girl (2020-04-23) — CONFIRMED Reverie (brief form). Bachelard test passes: anima-register atmosphere (gloaming, sweet air, quiet city); canonical drift-in/suspension/drift-out structure ("the world melted away as I drifted into reverie. Then, as quickly as it had set in, my reverie dissipated"); non-argumentative; "reverie" used Bachelard-correctly. Qualification: reports more than enacts at Bachelard-paradigm length; brief, carnet-adjacent. Reclassify class: observation → class: reverie. ✦ stays. First brief-Reverie exemplar.

Principles that surfaced from corpus testing 2026-04-21

Principle 1: Conditions of composition ≠ type.

A piece composed in reverie-enabling conditions (walking, Kai asleep, anima-space) may still be a Meditation if its internal structure is meditative. The type is read from what the piece does on the page, not from where the writer was when writing.

Why it matters: Kai 9+9 was composed during the walking-with-Kai-asleep condition the steward named as paradigm-reverie. The piece itself is Meditation. The walk is the animaspace that permitted the meditative animus-work. Load-bearing for spec §4 Overlap/Resolution — otherwise the classification of pieces composed during walks/nights/other-drift-conditions gets muddled.

Principle 2: Reverie admits a duration spectrum.

The distinguishing features of Reverie are NOT length; they are register (anima/receptive), structure (unmooring from object), voice (non-argumentative), source (wakeful-drift-enabling). Brief-noted (carnet/semaison-adjacent) and sustained (Bachelard-paradigm) are both Reverie.

Why it matters: Graffiti Girl is a minimal Reverie but clearly of the type. Requiring Bachelard's sustained paradigm only would exclude the carnet-adjacent corpus register. This parallels the Jaccottet-semaison frame for Dream: both Reverie and Dream in ARC admit carnet-brevity alongside elaborated forms. Load-bearing for §1 Reverie entry.

Principle 3 (hypothesis): ✦ as register-shift marker inside a piece.

✦ may mark in-piece register-shift — ordinary attention opens into reverie / meditation / glimpse / threshold — with the base type being whatever the piece predominantly does.

Why it matters: Both Heliotrope and Graffiti Girl carry encounter: true. In both, an ordinary-noticing opened into something else (insight-on-heliotrope-nature; drift-into-reverie). The spec §3 says ✦ is "ordinary observation opened into direct experience" — this hypothesis sharpens the reading: ✦ marks a shift-event within the piece, not a quality of the whole. The "ordinary observation" in the §3 definition need not be an Observation type; it's the mode from which the piece opens. Worth confirming against more ✦-tagged pieces before writing into the spec.

Gap identified 2026-04-21

No sustained-Reverie exemplar in tested-and-confirmed set. Graffiti Girl is brief; Kai 9+9 had Bachelardian conditions but the resulting piece was Meditation. A pure sustained-Reverie at Bachelard-paradigm length would strengthen the §1 Reverie entry. Candidate source: unpublished backlog (steward-known material). Not blocking the spec-write — Bachelard's textual authority stands on its own — but flagging.

Calibration 2026-04-21 — ARC typology is a recognition scaffold, not a generation template

Steward calibrated mid-session after the Jaccottet synthesis: "ARC is not meant to be an online notebook to public. But the forms that Jaccottet uses are useful to analyze... I am not a diarist. I am not an essayist. Sometimes a thought comes across one of the types we've defined already and I 'know' that it is for ARC. Sometimes not. My mind works across various forms. And my output can be… quite heterogeneous."

Implications for the spec write (captured in full at feedback-arc-typology-recognition-scaffold.md):

  1. §1 definitions describe what a piece is, not how to write one. Recognition over generation.
  2. Clean in/out criteria matter — the "sometimes yes, sometimes no" discipline requires ✗-boundary cases as much as ✓-exemplars.
  3. §0 multi-axis is correct coverage of heterogeneous output, not a design inelegance. Don't collapse the axes.
  4. Reference texts (Bachelard, Visuddhimagga, Jaccottet) ground recognition, not template generation.
  5. Jaccottet is formal-range reference + confirmation that heterogeneity has literary dignity in one body of work. NOT an ARC template (different atomicity: carnet-compilation vs individual-publication).

Test for the executor when drafting a §1 definition: "can the steward use this to recognize whether an incoming thought is this type?" If the definition only helps write the type, it's incomplete.

Dec 22 half-light — third Meditation exemplar confirmed 2026-04-21

Verdict: CONFIRMED Meditation, exceptionally clean. Visuddhimagga four-part structure fully present:

  • Object: the half-light moment at 10:20 (Bach sarabande as anchoring object-within-object)
  • Posed attention: explicitly composed against laundry + sledgehammers; the sarabande "holds its integrity" because attention holds it
  • Rooted in present: time-anchored to moment of writing ("10:20")
  • Insight surfaced: "A centered silence can open infinite paths to the outside." Epigrammatic, unargued, surfaced from the attending.

Meta-finding — humic layer internally confirmed: the piece literally names "reading Jaccottet, Handke, listening to ambient sounds of others living their lives in the building." The humic-layer frame is not retrofitted — it has been operative in the steward's practice since at least 2023. Jaccottet and Handke were the morning's humus when the piece was written. Useful evidence that the humic posture is genuine, not imposed by today's spec work.

Corpus bug — Dec 22 duplicate files (2026-04-21)

Two files with the same content, different classes:

  • content/posts/2023-12-22-December-22nd-2023.md — class: observation (more-developed: description, glyph_id, auto-format comment)
  • content/archive/December 22nd 2023.md — class: fragment (simpler, older version)

Resolution path: posts/ version → reclassify class: meditation; archive duplicate either remove or reconcile with posts version. Operational item, separate from spec-write. Flag for corpus-cleanup pass.

§1 Meditation — draft structure accepted by steward 2026-04-21

Full entry proposed in chat; steward confirmed definition sentence, boundary rules, recognition test, humic-reference framing (items 1, 2, 3, 5). Item 4 (exemplars) resolved with Dec 22 re-read. Three exemplars locked in proposal:

  1. Dec 22 half-light — medium length; object-held; attention-composed-against-distraction; epigrammatic insight; names humic layer explicitly
  2. On Éveil / Sommeil (Kai 9+9, 2026-04-20) — sustained pole; meta-meditative (object IS attention)
  3. Heliotrope (2020-05-19) — minimal pole; compass-resonant (sun-piece at sun-glyph)

Duration range spanned cleanly (minimal ↔ medium ↔ sustained) without losing type coherence. Ordering in the final spec is steward's call.

Ready to write into content-typology-specification.md once steward confirms lock.

§1 Meditation + Reverie LOCKED and written to spec 2026-04-21

  • §1 Meditation — 5 coordinated edits. Full locked entry including Recognition test as new field. Three exemplars: Dec 22 half-light (leading; names Jaccottet+Handke internally, humic layer operative since 2023), On Éveil / Sommeil (sustained/meta-meditative), Heliotrope (minimal/compass-resonant).

  • §1 Reverie — 8 coordinated edits. Catalogue row added as type #11 (cluster-mate of Meditation at ⊙); §0 Posture axis refreshed; Photo Essay glyph reassignment ⊙ → ◧ propagated to both table row and locked-entry header (2026-04-20 decision, previously un-applied); Reverie LOCKED entry inserted after Meditation in the §1 block; asymmetry note documenting the absence of author's first-person mechanics (vs Meditation); sustained-pole exemplar gap flagged ("time will tell" — steward).

  • Corpus follow-ons (operational pass, not blocking): reclassify Heliotrope → meditation; reclassify posts/2023-12-22-December-22nd-2023.md → meditation; reconcile/remove duplicate archive/December 22nd 2023.md; reclassify The Graffiti Girl → reverie.

  • Structural resonance named 2026-04-21 — the Hearth frame (steward's Library Charter v1.3.0, canonical vault: 00. Compass/00a. Foundations/02. Organs/12. Library — Attention & Meaning Ecology.md), the humic-layer frame (influences as nutriment, not authority), and the recognition-scaffold frame (types name what arrives as ARC-shaped, not what is generated) are structurally aligned. The Hearth suspends classification during deep engagement; ARC types name what is revealed through such engagement. The spec's types are products of post-Hearth revelation, not advance categorization. All three frames refuse authority-over-the-work in favor of what dwelling with it reveals. This alignment is load-bearing for future §1 entries.

Catalogue state after 2026-04-21 (end of day)

  • 12 types in catalogue (Essay #1 · Observation #2 · Meditation #3 · Chamber #4 · Fragment #5 · Glimpse #6 · Photo Essay #7 · Gloss #8 · About #9 · Archive #10 · Reverie #11 · Dream #12)
  • LOCKED §1 entries: Photo Essay, Glimpse, Meditation, Reverie, Dream (5 of 12)
  • DRAFT §1 entries: Fragment, Observation (2 of 12)
  • Unwritten §1 entries: Essay, Chamber, Gloss, About, Archive (5 of 12)
  • Recognition test field introduced 2026-04-21 for Meditation+Reverie+Dream; retrofit to Photo Essay + Glimpse deferred
  • Style convention introduced 2026-04-21 in Dream: people by first-initial only (Handke precedent; aligns with children-not-named rule)

Handke deeper-reading findings 2026-04-21 (for forward use)

Coverage achieved: full read of Phantasien der Wiederholung (1,185 lines); openings + 1984-85 middle-section of Am Felsfenster morgens (~700 lines sampled total); openings of Das Gewicht der Welt + Die Geschichte des Bleistifts. Not full-corpus coverage; sufficient for structural claims tied to the explicit Vorbemerkungen + sampled entry-forms.

Findings worth carrying forward into §1 Observation / Fragment / Gloss / Essay work:

  1. Welt-Bild principle (Am Felsfenster) — "Welt-Bild (nicht Symbol und nicht etwa Gleichnis)". The noticed detail that carries world-weight without becoming metaphor. Handke explicit: "Wie aber vermeiden, daß so ein Weltbild im Beschreiben, statt daß es sich zum Weltbild noch verstärkt, abgeleitet wird zu einem Gleichnis?" — how to prevent the world-image from being reduced to a parable in the describing. Useful refinement for ARC Observation's boundary: the image IS the meaning, not explanation-of-meaning. Observation that becomes explicit-parable has slid toward Essay.

  2. Friedlich umherschauen vs beobachten (Am Felsfenster) — "Nicht beobachten, nicht fixieren, nicht genau hinschauen" als Grundregel ex negativo. Handke can only "friedlich umherschauen" (peacefully look-around). Sharpest distinction between two modes of attention often collapsed: clinical-surveillance-observation (beobachten) vs anima-register-peaceful-looking (friedlich umherschauen). ARC Observation is the latter, never the former — worth locking into §1 when drafted.

  3. Leerform principle (Am Felsfenster) — ordinary events traverse an empty-form. "Nichts darf freilich in einer solchen Art Erzählung passieren oder vorfallen — alles geschieht nur, ereignet sich." Nothing may happen or occur; everything only events-itself. Useful for Observation's character — the type works because the observing-consciousness leaves space open that the ordinary event can traverse.

  4. Wiederholung principle (Phantasien, Am Felsfenster) — "Ich kann nur das ganz und gar Ereignislose wiederholen" + "Wiederholen kann ich nicht das Erlebnis, aber den Weg." Repetition is not of events (which are unwiederholbar) — it is of paths, of modes-of-attention, of returns. May be load-bearing if a Pattern or Sequence type ever formalizes.

  5. "Bedeutung heißt Übersetzbarkeit" (Phantasien) — meaning = translatability. Something acquires meaning when it becomes metaphor-ready / comparison-ready / "mir wird etwas". Aligns with ARC's practice/type distinction (meaning emerges in the translation-event from practice to written piece).

  6. Perception-cluster / observation-string shape — multiple brief observations threaded into a single paragraph, without argumentative connection. Present in all four volumes (opening of Bleistift has a 500-word compound; Phantasien has train-window sequences; Felsfenster has the snow-fall sequence). Possible sub-form in ARC Observation or its own entry — flag for Observation §1 drafting.

  7. Handke's Three I's (Phantasien line 833) — silent-calm-I / chatter-I / phantasy-writer-I. Tripartite ontology that supports the recognition-scaffold frame: the calm-I is substrate, the writer-I traces the practice, the chatter-I is what gets in the way.

  8. Initial-only naming (confirmed in practice) — Handke refers to living persons and close relations by first-initial (A., F.K., M.), historical/deceased by surname, fictional stand-ins by full name. The steward's convention for Dream entries has precedent here.

  9. Juan de la Cruz as deep humic partner in the mature Felsfenster — "die bräutliche Seele", "Tastsinn der Seele", "Wunde, lind zu dulden", many citations. Christian mystic tradition explicitly present in Handke's mature carnet-work. Widens the humic set.

  10. Handke's travel-carnets vs dwelling-carnet distinction (steward-corrected). Das Gewicht/Bleistift/Phantasien are travel-mode carnets; Am Felsfenster is the singular dwelling-carnet (1982-87 Salzburg). Initially I framed Felsfenster as "primary ARC reference because sedentary" — steward corrected: "careful, i also travel extensively, hence the importance of location in the apparatus." The hic apparatus (location + full date, locked 2026-04-20) exists because the steward travels, each piece anchored to where it was written. Corrected memory: all four Handke volumes are relevant humic references; travel-carnets map onto touring-written pieces, Felsfenster onto Barcelona-home pieces. Felsfenster's value is attention to Ortsbezogenheit as apparatus principle (applies in both modes), not sedentariness per se.

✦ framework refinement (via Observation §1 lock 2026-04-21)

The ✦ encounter mark now has a structural theoretical home, articulated in Observation's §1 entry:

Observation is the prime residence of ✦. The mark specifically registers the threshold-crossing within a piece — an Observation that opens into Meditation / Reverie / Glimpse / direct-experience. The base type is whatever the piece predominantly does; ✦ marks that something crossed a register-boundary inside it.

Why this matters across §1: every type's Qualifying-marks-eligibility section should now reference this framework. ✦ is not a generic "encounter happened" marker — it marks an in-piece register-shift where an ordinary noticing opened into something that was no-longer-ordinary. Observation is the canonical from-state of that shift; Meditation, Reverie, Glimpse (and potentially Threshold if locked) are the canonical to-states.

Jaccottet's observation/vision distinction — "Il n'y a pas observation, mais vision, en ce sens précis que le paysage lui apparaît" — is the humic framing for this: ✦ registers where observation becomes vision (or attention becomes drift, or the ordinary becomes meditative).

Retrofit implications:

  • Photo Essay + Glimpse (earlier LOCKED entries) should carry this framing when Recognition-test retrofit happens
  • Fragment, Essay (still unwritten) should address ✦ eligibility against this framing when drafted
  • Corpus audit: when pieces carry encounter: true, the classifier should ask "what was the from-state? what was the to-state?" and assign the base type as the to-state where the piece predominantly lives

§0 Source axis — PROPOSED 2026-04-21, awaiting steward decision

Per Observation lock + Dream's OPEN note. Proposed resolution:

  • Add Source axis to §0 with two values: wakeful-attending (11 types) + sleep-recalled (1 type, Dream)
  • Grounded in Bachelard's "Une rêverie, à la différence du rêve, ne se raconte pas" — sleep/wake as a fundamental distinction more basic than posture
  • Deliberately unbalanced (11:1); honest about sleep-recalled's rarity
  • Proposed edits: §0 table row + optional subsection + remove Dream's "Source axis OPEN" note + update Dream's axis location + changelog
  • Three decision points raised: (a) adopt Y/N; (b) include optional subsection Y/N; (c) propagate "wakeful-attending source" to Meditation/Reverie/Observation axis locations Y/N

Awaiting steward sign-off on all three. (Update 2026-04-21: all three confirmed ("yes to all 3"); §0 Source axis LOCKED with seven coordinated edits — see changelog entry 2026-04-21 in the spec file.)

Chamber-library housekeeping task (authorized 2026-04-21, pending)

Move nine carnet-humic-reference texts from Desktop to chamber-library/converted_texts/traditions/critical_modernity/phenomenology/:

  • jaccottet-observations-1947-1962.md
  • jaccottet-la-semaison.md
  • jaccottet-seconde-semaison.md
  • jaccottet-carnets-1995-1998.md
  • handke-das-gewicht-der-welt.md
  • handke-die-geschichte-des-bleistifts.md
  • handke-phantasien-der-wiederholung.md
  • handke-am-felsfenster-morgens.md
  • lichtenberg-gesammelte-werke.md

Status 2026-04-21: moves authorized by steward at end of session; executor could not perform via Bash (macOS TCC Desktop protection blocks sandbox). Steward may run the mv commands in own Terminal (full command provided in session transcript), or the work remains queued. The humic-layer memory file still points to Desktop locations pending the move.

FOLLOW-ON TASK — add YAML frontmatter. Once the nine texts are in place, add standard chamber-library frontmatter to each (matching Bachelard's format):

---
author: [Jaccottet / Handke / Lichtenberg]
canonical: true
converted_with: pandoc
date_converted: [date]
file: [filename].md
quote_style: [poetic / aphoristic / etc.]
segment_strategy: [chapter / volume]
source_format: epub_directory
tags: []
title: [Title]
voice: [author full name]
---

Ensures consistency with existing phenomenology/ entries (Bachelard, Kafka, Nietzsche, etc.). Scope-creep for tonight; queued for next chamber-library touch. After frontmatter is added, also update user-influences-humic-layer.md library-location notes to point to the new chamber-library paths instead of Desktop.

Lichtenberg findings — forward preparation for Fragment §1 (2026-04-21)

Steward named Lichtenberg as "the master of the fragment." Read Sudelbuch A entries 1-94 (~200 of ~30,836 lines; B-L unread). Digital location: ~/Desktop/Handke/md/Gesammelte Werke - Lichtenberg, Georg Christoph.md.

Structural findings for Fragment §1:

  1. Fragment's unifying feature is terminal-landing, not length. Sudelbuch entries span one-sentence ("Die Schnecke baut ihr Haus nicht, sondern es wächst ihr aus dem Leib" [A 31]) to multi-paragraph reasonings. What unites them is: the thought completes; the entry is whole in itself despite brevity. Not length; posture. Fragment = aphoristic-terminal. Pieces that build argument across paragraphs blend toward mini-essay; pieces that surface insight from sustained attention blend toward Meditation.

  2. Thematic range is unconstrained. Lichtenberg's Sudelbuch contains scientific observation, philosophy of language, psychology of thought, aesthetic judgment, social satire, self-observation, literary criticism, dreams, jokes. Fragment as type limits structure (aphoristic-landing), not content.

  3. Occasional dating + place-anchoring. "Den 29. Dez. 1766 abends 5 Uhr sah ich in Göttingen" [A 71]. ARC's hic apparatus (location + full date, locked 2026-04-20) has a Lichtenberg precedent.

  4. The Sudelbuch idea is itself structural. Sudelbuch = rough merchant's ledger before clean-transfer. Lichtenberg never transferred. The form honors rough-unpolished thought as its own legitimate register. ARC Fragment can draw on this posture — the piece doesn't apologize for brevity or roughness; the aphoristic-terminal is dignified in itself.

  5. Incomplete entries preserved (e.g., A 71 stops mid-thought — the observation Lichtenberg "saw in Göttingen" never gets recorded). Probably not an ARC feature (ARC publishes completed pieces) but worth knowing as a trace of the Sudelbuch's honesty about thinking.

Humic references for Fragment §1 when drafted:

  • Lichtenberg (primary) — German-language master; Sudelbücher as archetypal practice; terminal-landing + thematic-openness + Sudelbuch-posture
  • Handke — minimal-perception-flash pole; aphoristic entries in his carnets (e.g., "Ich bin meistens zu bewußt zum Traurigsein")
  • Jaccottet — aphoristic notes blended with observations in Semaison / Observations
  • Deep European genealogy: Schlegel, Novalis (Romantic Fragment), Nietzsche (aphorism), Kafka (fragments), Karl Kraus; Pascal (Pensées), La Rochefoucauld (Maximes)

Fragment's boundary relations (to sharpen in §1):

  • vs Observation — Fragment lands (aphoristic-terminal); Observation holds (attended-noticing). An observation-that-lands-into-insight may be Fragment or Meditation depending on whether landing or surfacing-from-rooting dominates.
  • vs Meditation — Fragment is terminal-compressed; Meditation is sustained-posed on an object. Both may produce insight, but Meditation's insight emerges through rooting; Fragment's lands at the start or end as the form's completion.
  • vs Essay — Fragment is terminal-compressed; Essay builds argument across paragraphs. A Lichtenberg entry that builds reasoning is closer to mini-essay than Fragment.
  • vs Glimpse — Fragment is prose-aphoristic; Glimpse is image-aphoristic. Different media; same terminal-aphoristic posture within their respective media.

Bachelard settles Reverie — La Poétique de la Rêverie (PUF, 1960)

Full-text read from chamber-library/converted_texts/traditions/critical_modernity/phenomenology/la-poe-tique-de-la-re-verie.md. Three load-bearing moves from Introduction + Chapter II:

  1. Rêverie ≠ OED's "pleasantly lost daydream." That's rêvasser:

    "Une conscience qui diminue, une conscience qui s'endort, une conscience qui rêvasse n'est déjà plus une conscience."

    Rêverie poétique is the opposite:

    "Toute prise de conscience est un accroissement de conscience, une augmentation de lumière, un renforcement de la cohérence psychique."

    Reverie augments consciousness.

  2. Rêverie ≠ rêve (dream). Dreams are narrated; reveries are written:

    "Une rêverie, à la différence du rêve, ne se raconte pas. Pour la communiquer, il faut l'écrire."

    Reverie already faces the blank page: "rêverie qui s'écrit, ou qui se promet d'écrire."

  3. Reverie is under the sign of anima. Chapter II's central thesis:

    "La rêverie est sous le signe de l'anima. Quand la rêverie est vraiment profonde, l'être qui vient rêver en nous c'est notre anima." "La poétique de la rêverie est une poétique de l'anima."

    Animus argues, constructs, reads little; anima receives, dreams, reads much. The axis that separates the ARC Meditation type from the Reverie type is animus/anima.

The Meditation/Reverie axis (animus/anima) — ready for spec §4

Meditation (ARC def) Reverie (Bachelard)
Register animus-adjacent — measured, object-rooted anima — receptive, image-generative
Etymology med- "take measure" resver "wander, rave"
Attention object-held, bounded, present image-open, world-forming
Time present-rooted transcends (childhood, cosmos, memory)

(Bachelard doesn't explicitly contrast reverie with meditation; the mapping is the executor's, placing the steward's verbatim Meditation definition against Bachelard's animus/anima frame. Noted for honesty.)

The Kai 9+9 piece is canonically Bachelardian, not just steward-original

  • Chapter III of Rêverie is titled "Les rêveries vers l'enfance" — reveries toward childhood.
  • The book is dedicated "À ma fille."
  • Walking-with-Kai-asleep as reverie condition (from 2026-04-20) is the paradigm case Bachelard maps: anima-register, image-generative, world-forming, written from solitary-receptive attention.

This anchors Reverie as a type in a specific philosophical lineage. The Kai piece isn't a riff on a proposed type; it is written in the exact register Bachelard names.

/dwellings/ validated — La Poétique de l'Espace (PUF, 1957)

Sibling volume three years before Rêverie. Full chapter structure:

  • La maison (cave → grenier, la hutte)
  • Maison et Univers
  • Le tiroir, les coffres, les armoires
  • Le nid · La coquille · Les coins
  • La miniature · L'immensité intime
  • La dialectique du dehors et du dedans
  • La phénoménologie du rond

Central noun: demeure (dwelling-place). Central verb: habiter. For Bachelard the dreaming subject is fundamentally an inhabitant; the house is "l'un des plus grands pouvoirs d'intégration pour les pensées, les souvenirs et les rêves de l'homme."

Three cluster-page candidates checked against Bachelard:

  • /dwellings/ — direct English for demeures; names the cluster in Bachelard's own register. Strongest.
  • /inhabit/ — matches habiter, but slides the cluster-page title from noun (what it holds) to verb (what one does). Less stable as a page name.
  • /depths/ — captures intimité but misses verticality (Bachelard moves cellar → attic; depth is one pole only) and misses horizon (l'immensité intime isn't only depth). Partial.

Structural case for /dwellings/: the two Bachelard books form a pair — L'Espace = the spaces imagination dwells in; Rêverie = the practice of dwelling. Meditation + Reverie as a cluster named dwellings honors that pairing. Meditation dwells in an object (bounded, measured); Reverie dwells with image-worlds (anima, generative). Both are modes of sustained inhabiting. Heideggerian harmonic ("Building, Dwelling, Thinking," 1951) in the background but not primary.

Executor recommendation: lock /dwellings/. Steward decision pending.

Ready to write into spec (pending steward authorization)

  • Reverie §1 entry — Bachelard as definitional authority (La Poétique de la Rêverie, 1960). Anima register, sustained-inhabiting posture, image-generative, written-or-promised-to-writing. On Éveil / Sommeil as exemplar.
  • Meditation §1 entry — steward's verbatim definition; etymology note (med- / mete / μέτρον — Prime-Directive resonance). Animus-adjacent register.
  • §4 Overlap/Resolution — Meditation vs Reverie is the animus/anima axis; Bachelard's rêvasser / rêve / rêverie three-way distinction excludes both the vacant daydream and the narrated dream from the Reverie type.
  • Cluster page name — /dwellings/ recommended, awaiting steward lock.

2026-04-23 — Chamber is apparatus, not a §1 type (walking-with-Kai ideation)

Headline architectural decision (steward-led, Kai napping in sling, pacing the apartment): Chamber does not get a §1 row in the typology spec. The spec was already behaving this way — ⟐ appears across nearly every other type's entry as an apparatus-seal that attaches (line 165, 192, 219, 244, 268, 296, 334, 380, 462 in content-typology-specification.md), and line 363 already disambiguates "An About-piece about Chamber is not a Chamber-type piece." The §1 Chamber entry never got written because it doesn't want to exist.

The three-operations-in-one-room insight

Chamber v1 was holding three separate operations under one roof:

  1. Chamber-emergent works — pieces that passed through the Chamber process
  2. Published deliberations — the transcripts themselves as proof-of-process
  3. Fictional canon — Borges/Eco obscure-reference tradition (invent the authority-voice for the well-made statement)

Source-aware Chamber (per CapableMind docs/thinking/David/chamber/) only does (1), rigorously: citation-bound voices, warrant types, anti-pilpul. The other two were category-guests — they lived in Chamber v1 because Chamber was the roomy container, but were never the same operation.

Fictional canon migrates to Heteronym ⁂

Steward verbatim: "the fictional canon and the idea that it is easier to (when you're an authority and have minds such as theirs) make a statement that is well thought out and create an obscure reference rather than compose a work defending your position (also as a way of playfully mocking academic manipulation of sources to support one's claim) appeals to me still for the heteronym type…"

And on whether Matthieu Taliesin (pedagogical-mythical) and the Borges-Eco obscure-reference mode are one heteronym or two: "It feels like one, the same gesture at least."

The underlying operation that unifies them: invent the voice that can say what the position deserves, without yourself performing the authority. Same gesture, tonal spectrum from earnest (Taliesin) to sly (Borges-Eco).

Heteronym humic layer widens from the current Pessoa-primary draft to include:

  • Pessoa (primary — heteronyms as philosophical method)
  • Borges (Ficciones, Tlön, Uqbar, Orbis Tertius — invented authors)
  • Eco (Name of the Rose apparatus, marginalia-as-voice)
  • Kierkegaard (pseudonymous authorship — Johannes Climacus, Anti-Climacus, etc.)
  • Lichtenberg at the aphorism end ("a friend told me…" as mini-heteronym)

Chamber v1's fictional-canon and source-aware Chamber's citation-discipline are inversions on the same axis — one mocks citation from inside its grammar, the other takes it with full seriousness. Which is why they were confused in v1 and separate cleanly now.

Chamber redistribution — complete-in-shape

Former Chamber function New home
⟐ seal §2 apparatus (attaches to pieces of other types)
Short illustrative list of emergent works Inline in About/Chamber description page
v1 deliberations Kept with qualifying frame, linked section at bottom of About/Chamber page ("fruits of those labors" — steward)
Fictional canon / Borges-Eco mode Migrated to Heteronym ⁂
Compass row for Chamber Removed
§1 Chamber entry Does not get written

Navigation: two discovery paths, both honest

Steward verbatim: "chamber doesn't need its compass point—the reader will come across the mark either by accident, or through the archives. We could retain a point of entry into a chamber-emerged meta page—through the Chamber description page in the about pages."

  1. Accidental — reader encounters ⟐ on a piece, curiosity follows the mark
  2. Intentional — About enfilade → Chamber description page (already in enfilade per 2026-04-22, line 372 of spec)

The Chamber description page carries the pedagogical load: short illustrative list of 2–3 selected emergent works inline so readers understand the mark, plus a framed section at the bottom for the v1 deliberations as genealogical record. Steward: "Could keep them, with a qualifying description, as examples of the work as the concept was evolving." Structurally consistent with the archive-as-refusal-of-erasure commitment already locked on 2026-04-22 (Derrida Mal d'Archive, logchain + Archive-view at two scales).

What this dissolves

  • Line 530 open question: "Resolve Council / Deliberation — peer to Chamber or subtype?" → dissolves. If Chamber isn't a type, Council/Deliberation are session-modes or apparatus, not content classes.
  • Line 527 pending author-lock for Chamber §1 → closes with "not a §1 entry."
  • The triple-duty problem of the former Reading Compass Chamber pointer → split cleanly across three homes.

Sequencing

Steward verbatim on the scale: "There's no avoiding the fact that the chamber page requires a major rewrite given the tool it is becoming."

  • Typology spec entry — ripe NOW. Remove §1 Chamber row, formalize ⟐ in §2 apparatus, close line 530 and 527. Small, clean, doable in next focused spec session.
  • Chamber page rewrite (content/chamber/index.md, content/chamber/about.md — currently v1-era prose: organic amphitheater, Khunrath, Anonymous Anchors, the three-examinations frame) — post-L2-unpark (after end of May 2026, per 2026-04-22 lock: "Chamber page will be heavily revised to reflect the current (post-L2) Chamber practice"). Rewrite, not edit — the v1 framing is structurally different from source-aware apparatus Chamber.
  • Optional interim — one-line qualifying note at top of current Chamber page so it doesn't present as current practice. Low stakes since compass row is also going away.

Methodological observation — walking-mode ideation

Steward verbatim: "I find that I'm most creative while I walk actually — at least ideation flows quite freely this way."

This session produced real synthesis across three reading-passes (ARC repo, vault, CapableMind docs) via walking-ideation + mid-response self-corrections (e.g., steward caught his own option-1 vs option-2 conflation live: "what I wrote is foolish, it fits more with what you proposed as 2nd"). Register worked cleanly. The collaborative shape: Claude returns raw findings + organized landscape, steward walks and thinks aloud, Claude reflects and sharpens questions without closing. Worth preserving as a mode for future ARC architectural ideation — especially when the decision-tree is large and the constraints are primarily aesthetic/philosophical rather than technical.

Reading-pass artifacts (not re-read — consumed in this session)

Three Explore agents returned raw findings:

  • ARC repo — 164+ files reference Chamber; Chamber already listed as §1 row 4 "Extant" but unwritten; ⟐ functions as apparatus-seal across every other type's entry; content/chamber/ holds v1 POC (30 canonical works, 8 deliberations); site.hs retains chamberIndexCompiler + archived voiceCtx "awaiting source-aware Chamber."
  • Obsidian vault — 646 files; substantial first-class Chamber material (Living Amphitheatre V2.1, multiple charters, editorial/epistemic/hermetic charters, Chamber test phase 1-2, l2-design-narrative.md); mostly V1 framing; mirrors ARC for canonicals, vault-only for internal R&D.
  • CapableMind thinking folder — 7 Chamber-primary documents; source-aware design distributed across multiple docs (no single spec); Chamber framed as "front door to L2" / "most demanding consumer" / "empirical research instrument for L2 governance discovery" — all apparatus/instrument framings. V1 → source-aware inversion explicit in chamber-from-simulation-to-source-aware.md.

The ARC repo and CapableMind readings independently converged on the apparatus-framing. Vault contains both V1 (simulation-era) and source-aware material without always sharp demarcation.

Queued TODOs from this session (2026-04-23)

Ripe now (next focused spec session):

  • Typology spec update: remove §1 Chamber row; formalize ⟐ as §2 apparatus seal with its attachment rules; close open question at line 530 (Council/Deliberation dissolves); close line 527 (Chamber author-lock replaced with "not a §1 entry, see §2 apparatus")
  • About enfilade: confirm Chamber description page remains as About-type (already codified 2026-04-22, line 372)

Downstream — Heteronym lock session:

  • Widen Heteronym ⁂ humic layer with Borges, Eco, Kierkegaard, Lichtenberg (aphorism end) — Pessoa + Taliesin as current primaries, now four-to-five source humic layer with clear gesture-commonality
  • Absorb the Borges/Eco obscure-reference mode into Heteronym's practice-mechanics draft (same gesture, sly-end of the tonal spectrum)
  • Consider: does Heteronym lock need a pre-lock re-read of one Borges piece (e.g. Tlön) and one Eco apparatus section to verify gesture-commonality before committing? (Drift-awareness — sourcing-claims-without-reading pattern).

Post-L2-unpark (after end of May 2026) — Chamber page rewrite:

  • Major rewrite of content/chamber/index.md and content/chamber/about.md: replace V1 framing (organic amphitheater, Anonymous Anchors, three-examinations) with source-aware apparatus framing (citation-bound voices, warrant types, anti-pilpul, ⟐ seal meaning)
  • Curate 2–3 illustrative Chamber-emergent works for inline listing in the description
  • Author qualifying description text for v1 deliberations archive section — short historical self-statement ("what the process was trying to achieve at that point"): ambition, method-at-the-time, what was generative, what was bundled-and-has-since-separated, the through-line. Steward-authored; past tense.
  • Decide final placement shape for v1 deliberations archive: linked section at bottom of About/Chamber page (leaning here), vs. Archive-subsection. Both work; second option (About-page attachment) confirmed by steward as preferred — "fruits of those labors."

Optional interim (low stakes, may not be needed):

  • One-line qualifying note at top of current content/chamber/index.md indicating the page is v1-era and pending rewrite. Low urgency — compass row removal will naturally reduce traffic to the page.

Navigation / Reading Compass consequences:

  • Remove Chamber compass row from Reading Compass (no primary navigation point)
  • Verify ⟐ seal rendering on pieces that already carry it (check site.hs templates — chamberIndexCompiler, voiceCtx archived state)

Follow-on questions to surface when seated (don't rush):

  • Does Archive need a ⟐ filter/sub-view as a latent capacity, or is the inline About/Chamber list sufficient?
  • Do the existing 30 v1 canonical works + 8 deliberations all surface in the qualified-archive section, or is there a curatorial filter (e.g., only deliberations, or only a representative subset)?
  • When Heteronym locks, does the Borges-Eco mode merit its own exemplar piece in the humic layer, or just genealogy notes?

2026-04-23 meta-survey — what's blocking, what's missing, what's on the horizon

Steward observation: "I feel that the type spec is a blocking agent on many of the mechanical housekeeping processes that we have." Correct. Concrete unblock chain once the three remaining §1 types (Heteronym, Hommage, Tombeau) lock:

  • Corpus reclassifications already queued: Death of a Hero → Hommage; Matthieu Taliesin → Heteronym; Dec 22 / Heliotrope / Graffiti Girl review; Vespers boundary decision
  • §5 no-essay-fallback rule can fire in site.hs (Hakyll rendering)
  • Style guide per-type prose conventions (skeleton is current; §7 waiting on each type-lock to anchor its prose conventions)
  • Ornament rules per type (AldineXXI retired 7 → 2 roles; per-type usage still unformalized)
  • Chamber compass row removal + ⟐ apparatus formalization (today's Chamber decision's downstream)

Proposed next-session sequencing (Heteronym first):

  1. Heteronym ⁂ — humus richest today (Borges + Eco + Kierkegaard + Lichtenberg migrated in from Chamber redistribution; gesture articulated: "invent the voice that can say what the position deserves without performing the authority yourself"; Taliesin-pedagogical + Borges-Eco-ficto-authoritative confirmed as one gesture in tonal spectrum). Forward-reading drift-check before lock: one Borges piece (e.g. Tlön) + one Eco apparatus section, to verify gesture-commonality isn't an imputation.
  2. Hommage ♆ — Hagen Quartett piece forthcoming + Death of a Hero retrofit give immediate corpus traction.
  3. Tombeau ▽ — Ravel/Mallarmé humic clear but forward-looking; no current exemplar to anchor against. Last.

Steward's meta-question: "the spec corpus for ARC is coming into being—are there other aspects that require spec building that we've not yet addressed or looked at?"

Honest inventory of ARC-internal specs still needed beyond the typology spec:

  • §2 Apparatus matrix — explicitly deferred ("Matrix content deferred to full authoring pass"). Promoted in urgency by today's Chamber decision: ⟐ now lives here; has nowhere to live until §2 exists.
  • §0 Source axis — proposed 2026-04-21, awaiting steward decision
  • Glyph / ornament formal spec — AldineXXI retirement 7 → 2 was a decision; the remaining rules (when does ⟐ attach, when does ✦ apply, what the two pause/close ornaments are, SVG cul-de-lampe design) are undocumented
  • Archive generation rules — Archive LOCKED as non-authored generated view; how it's populated, filtered, presented is not specified
  • Versioning editorial workflow — ADR-005 is the technical shape; the editorial question (when do you publish a new version vs. revise-in-place vs. mark-superseded vs. keep-as-historical) is implicit, needs codification
  • Enfilade apparatus spec — named in §2 as deferred
  • Reading Compass taxonomy — what warrants a compass point? Today: "apparatus doesn't navigate" was articulated (Chamber case). Could generalize into rules for entry and removal.
  • Corpus reclassification principles — when is a piece re-typed? Under what authority? What's recorded when a reclassification happens? (Becomes relevant the moment the queued reclassifications execute.)

Memento Mori Press (long-horizon publishing house) — steward flagged as long-horizon ARC project. Steward's verbatim: "recall momento mori press is a long horizon project for ARC as well—info in the vault and maybe in the ARC repo itself." UNREAD by executor as of this session. Declined to characterize from memory (would trigger sourcing-claims-without-reading drift pattern). Awaiting steward pointer to vault path / ARC repo location. When read, this opens a further spec surface: imprint charter (what Memento Mori publishes, how it's distinct from ARC-the-private-author's work), production spec (physical: paper/binding/typography; digital edition vs. web-rendered post), rights/licensing framework, editorial workflow (if it ever publishes beyond steward), legal-fiscal entity, distribution/archival policy. All downstream of reading what's already there.

Next Claude session focus decision (tradeoff surfaced to steward, not resolved):

  • (A) Heteronym lock session — unblocks mechanical housekeeping, builds on today's prepared humus
  • (B) §2 apparatus matrix — the structural home for Chamber ⟐ that doesn't yet exist
  • (C) Read Memento Mori material before the publishing-house conversation expands
  • Steward chose (A): "Let's lock the remaining types" — Heteronym lock session started same day.

2026-04-23 — §1 catalogue COMPLETE-IN-STRUCTURE (three LOCKS in one session)

All three remaining §1 types LOCKED in a single session (Heteronym → Hommage → Tombeau), plus Chamber resolved to §2 apparatus earlier in the day. ARC's §1 catalogue is now structurally complete: 14 of 14 §1 types LOCKED. Remaining work is downstream (apparatus matrix, mechanical cleanup, page rewrites) rather than structural.

Practice-mechanics locked verbatim (all three):

Heteronym (⁂):

"To make a heteronym is to invent the voice that can say what the position deserves — the discovered teacher, the imagined correspondent, the mythic intermediary. The form is authentic; the voice is an honest fiction. What's learned comes through the invention: the reader meets the thought without meeting the thinker."

Hommage (❦):

"To make a hommage is to render tribute by placement — teacher, maker, presence — rendering what has been given, in the register of witness and thanks. The form holds the subject rather than moving with it (that is Essay); it places the subject, clearly and honestly, in memory's keeping."

Tombeau (▽):

"To make a tombeau is to honor the dead by making new work in their name — the form itself performing the memorial. The piece does not describe the tribute (that is Hommage); it enacts it. The making places what the making remembers."

Tombeau axis expansion (steward 2026-04-23): from prose-only to prose or poetry. "ARC could use poetry or prose for tombeau…" Does not resolve the Poem-as-type question (Q2 remains open); Tombeau just admits poetry within its tribute-register. Noted in Remaining Catalogue Work.

The sema distinction (architectural): the Harrison-reading produced a clean differentiation between Hommage and Tombeau:

  • Hommage = speech-act sema (Lincoln's Gettysburg Address in Harrison's central example — words that appropriate the ground and draw the boundary of belonging). Words place the subject.
  • Tombeau = form-enacted sema (Ravel's suite, Mallarmé's sonnet — the made thing as grave-marker, "a sign that signifies the source of signification itself"). The form is the memorial.

Both are semata in Harrison's sense; the difference is which carries the gesture — the naming or the making.

MAJOR FIND — "humic layer" terminology's origin

ARC's "humic layer" vocabulary derives from Harrison, The Dominion of the Dead, Chapter 2 "Hic Jacet." Surfaced 2026-04-23 when steward directed me to read the chapter for the Hommage lock. Harrison's key passages:

  • "Humanity is not a species; it is a connection with the humus."
  • "An architecture not so much of the humanistic as of the humic."
  • "Humic foundations" (used throughout the chapter)

The typology spec had been using "humic references" / "humic layer" throughout without flagging the origin. Steward authorized surfacing (2026-04-23: "Option 2, yes"): a preamble note added at top of §1 in the typology spec acknowledging Harrison as the vocabulary source. Framed under the prime-directive posture (travail bien fait: name your ground; the hidden stone dressed with the care of the visible one).

This is load-bearing for two reasons:

  1. Architectural honesty: ARC's vocabulary has its own humic layer, and the spec now acknowledges it
  2. Harrison's chapter is doubly-humic for ARC — it's both theoretical ground for Hommage/Tombeau (sema-theory) AND the source of the humic-layer terminology itself. It appears in both Hommage and Tombeau humic references as theoretical warrant, and in the §1 preamble as vocabulary source.

Drift-discipline honored

Steward asked me to read Harrison's Chapter 2 in chamber-library before committing to humic-reference claims. I read it (lines 103-179 of the-dominion-of-the-dead-harrison.md). The claim about humic-terminology-origin was earned (verified by reading), not asserted from memory. This is the drift-return pattern operating prospectively: anticipate the sourcing-claims-without-reading trap and correct for it by reading before writing. Pattern to continue.

Files edited this session

  • docs/AldineXXI-Codex/content-typology-specification.md — three DRAFT→LOCKED entries; §1 preamble humic-origin note; table rows 4 (Chamber struck through), 13 (Heteronym LOCKED), 14 (Hommage LOCKED), 15 (Tombeau LOCKED + axis expansion); §7 Q3 dissolved; Q13 added; Remaining Catalogue Work updated (all §1 LOCKED); changelog 2026-04-23 entry with eight sub-bullets covering the full session.
  • docs/AldineXXI-Codex/AldineXXI-specification.md — ✦ encounter mark table row meaning updated + extended definition subsection added + provenance note.
  • content/pages/typography.md — public distillation updated ("The finger to the moon").

Catalogue state after session

  • 14 of 14 §1 types LOCKED (Essay, Observation, Meditation, Fragment, Glimpse, Photo Essay, Gloss, About, Archive, Reverie, Dream, Heteronym, Hommage, Tombeau).
  • Chamber resolved to §2 apparatus; ⟐ Chamber seal and ✦ Encounter mark operative as qualifiers (extended definitions in AldineXXI spec).
  • Q1-Q11 all RESOLVED/DISSOLVED. Q12 Vespers open. Q13 Dover photo essay open (held for writing-evidence). Q2 Poem remains open (Tombeau poetry-admission does not resolve).

Interpretive calls flagged to steward (awaiting feedback)

  • §1 table row 4 Chamber ~~Chamber~~ strikethrough (from Heteronym lock). Still awaiting steward feedback; revise if cleaner annotation preferred.
  • §1 preamble humic-origin note placed at top of §1 (just under the "humic references can attach" bullet, before "Initial catalogue"). Steward-approved the idea; placement is interpretive. Revise placement if he prefers a Glossary section or §0 location.

What unlocks mechanically (from the 2026-04-23 meta-survey)

Now that §1 is complete-in-structure:

  • Corpus reclassifications executable: Death of a Hero → Hommage; Matthieu Taliesin → Heteronym; Dec 22 / Heliotrope / Graffiti Girl review; Vespers pending Q12.
  • §5 no-essay-fallback rule fireable in site.hs (Hakyll rendering).
  • Style guide per-type prose conventions (§7 anchorable now — each type has its practice-mechanics locked).
  • Ornament per-type rules formalizable (AldineXXI retired 7→2; per-type usage ready to codify).
  • Chamber compass row removal + ⟐ apparatus formalization (§2 apparatus matrix work).

Session committed and pushed (2026-04-23 Sant Jordi)

Three commits on origin/main at git.skemantix.com/David/animal-davidglidden-eu:

  • 3f21fda — docs(style-guide): retire old style-guide.md; add AldineXXI skeleton (2026-04-22 work committed belatedly)
  • 4635a16 — docs(typology): add content typology specification — §1 catalogue complete (first-commit of the 800+ line spec file; spec-authoring spanned 2026-04-19 through 2026-04-23)
  • 9c58494 — docs(typography): deepen ✦ encounter mark definition for mediated forms (today's ✦ work)

Push succeeded cleanly (489226d..9c58494). Pre-commit hooks passed on all three. Committed under the steward's Sant Jordi-day authorization ("Let's commit and push everything") — the day's typology-architectural labor preserved in repo history before the family walked out into the streets of Barcelona for books and roses.

Remaining uncommitted: M docs/AldineXXI-Codex/.DS_Store — tracked macOS metadata noise. Hygiene fix for another day (steward-decision: git rm --cached + add to .gitignore, or leave).

Harrison as ARC's deep teacher — ligature lineage (steward, 2026-04-23)

Steward verbatim, shared at end of §1-complete session:

"I think it is always important to be reverential and grateful to one's deep teachers. Harrison is one such person even though I never met him. My way of dwelling in books, into entering into discourse with the authors, allows me to consider the ensuing transformations as being 'taught' by them."

"If you were to read Dominion of the Dead entirely, you would have a deeper contextual idea of ARC being my expression of ligature. I have only discovered this since recently encountering the book for the first time, and once I read Forests and Gardens, two of his other books — not to forget juvanessense — it is likely I will recognize myself even more deeply in debt to Harrison's lineage."

"My writing is a pale shadow of his, but every day I endeavour to better my past self and honour the dead for the sake of the living and unborn."

Key implications — load-bearing for future ARC work:

  1. "ARC is my expression of ligature" — this is the deep architectural frame. Ligature = binding (especially across the living/dead threshold, across generations, across the author-work-reader threshold). The term is already operative in CapableMind's l2-design-narrative.md (binding metaphor). This makes ARC's whole architectural intent Harrisonian: the site is the steward's practice of ligature. Future spec/page work should be tested against this frame. If an architectural move attenuates ligature, it misses ARC's purpose.

  2. Forward reading queue (not yet undertaken) — when steward reads Robert Pogue Harrison's:

    • Forests: The Shadow of Civilization (1992)
    • Gardens: An Essay on the Human Condition (2008)
    • Juvenescence: A Cultural History of Our Age (2014)

    …the Harrison humic-layer is likely to deepen across multiple types (Hommage, Tombeau, possibly others — forest/garden frames may land elsewhere in the typology). Watch for the opening; do not anticipate it before he has read.

  3. "Honour the dead for the sake of the living and unborn" — a three-generational formulation that directly echoes the prime directive's durability/inheritability commitments and Harrison's chapter 2 hic jacet argument ("it is as if we the living can stand... only because the dead underlie the ground on which we build our homes, worlds, and commonwealths"). The prime directive's "Inheritability — Could someone else (collaborator, future self, Lune, Kai) follow this thread without confusion?" is the Harrisonian three-generational frame in ARC's own voice.

  4. Daily better-past-self couples to the travail bien fait ethic from earlier in the session. Not productivity mantra — writing discipline in the compagnonnage register.

  5. The "pale shadow" self-assessment — preserve. When editing humic layers or spec prose, honor this posture. Do not over-claim the steward's originality or under-claim Harrison's influence. The lineage is explicit.

See also user-formation-practice-honoring-teachers.md — the general collaboration-context memory derived from this exchange.

Eco — CONFIRMED for humic layer. Steward verbatim: "Eco absolutely—and almost more Foucault's pendulum than the name of the rose, but both is maybe best." Primary emphasis on Foucault's Pendulum (the Plan as fictional apparatus becoming self-referential — heteronym at its most radical), complement The Name of the Rose (found-manuscript multi-layer apparatus).

Lichtenberg — KEPT with specific citation pending. Steward verbatim: "Can't cite a specific Lichtenberg aphorism from memory, but definitely recall the formula. I'll take a look, but we keep him." Lock proceeds with Lichtenberg noted in humic layer + a placeholder for the Sudelbücher A.1-94 citation to be added later.

Heteronym final humic layer (5): Pessoa · Kierkegaard · Borges · Eco · Lichtenberg. Tonal spectrum: earnest-pedagogical (Pessoa, Kierkegaard) → sly-ficto-authoritative (Borges, Eco) → aphoristic-mini-heteronym (Lichtenberg).

Structural finding surfaced during the lock: qualifiers ≠ ornaments

A clarification that deserves to be durable. The 2026-04-22 ornament retirement (7 → 2) applied to ornaments, not to qualifiers. Two categories, structurally distinct per AldineXXI-specification.md:

  • Ornaments = between-section decorations (aldus leaf, asterism, fleuron, lozenge, etc.). Retired 7 → 2 on 2026-04-22 (pause + close remain, single designed SVG at two scales).
  • Qualifiers = post-title marks governed by frontmatter metadata. Two currently operative:
    • ⟐ Chamber seal — chamber: true — "Text has undergone Chamber review." (Re-affirmed 2026-04-23 as §2 apparatus per Chamber-as-apparatus decision.)
    • ✦ Encounter mark — encounter: true — "Ordinary observation opened into direct experience" (per content/pages/typography.md:112 and AldineXXI-specification.md:229). "Not an ornament between sections but a qualifier — when reading opened into encounter" (archive-v1 ornament-glossary).

Implication for §2 apparatus matrix work: the qualifiers are precisely what §2 should formalize — metadata-driven per-piece seals that attach across types according to rules §2 codifies. Neither ⟐ nor ✦ was ever a §1 type; both were always apparatus. The §2 matrix has a clear starting scope: define attachment rules for these two qualifiers against each §1 type.

Deepening-candidate flagged by steward (2026-04-23): The current ✦ definition ("observation opened into direct experience / transformative moments") is operationally thin. Steward: "we may need to deepen it." Held as open work — possibly surfaced during the §2 apparatus matrix session, or sooner if the Heteronym lock exposes a boundary need (e.g., can a Heteronym admit ✦? — requires clearer definition to answer cleanly).

Drift-return caught during the lock: I wrote "✦ Braid text" in the initial Heteronym qualifying-marks proposal. Steward caught: "that is the encounter mark." I confabulated a plausible gloss from memory fragments about chamber-library's "braid texts." Logged in ledger with adjacency noted to fact-fabrication-instead-of-let-me-check (2026-04-17) and confabulating-plausible-context-instead-of-checking-actual (2026-04-19). Corrected by reading the ARC repo typography page as steward directed.


2026-04-23 evening — Norris Between You & Me full body read (gather-deferred)

Pivot from projected agent-circle authoring (steward end-of-day too tired: "beautiful day but don't have energy for projected work, keep it close") to a full body read of Norris's Between You & Me: Confessions of a Comma Queen in three chunks. Steward instruction: "let's just look at what surfaces—only that"; after chunk 1: "this is gold, please continue"; after chunk 2: "fascinating, please continue"; after chunk 3: "we will gather—lex—when we've looked at the whole."

Authorization scope strictly held: three read-chunks, three surface-reports, no cross-chunk synthesis, no ARC recommendations. Discipline of read-before-claiming carried across three chunks — the gather-lex move was steward-reserved, not executor-initiated.

Eleven finds surfaced (preserved as material, not as instruction)

  1. Apostrophe-as-prayer-turn (Norris ch.8, MAJOR FIND) — "An apostrophe is almost like a prayer when a prayer comes from the impulse to praise." Direct kinship to Harrison/humic/books-as-teachers framework. ARC is already apostrophic in Norris's rhetorical sense.
  2. Manuzio (Norris ch.5) — AldineXXI's inheritance-claim grounded. Manutius the Elder as canonical comma-refiner, Venice 1490.
  3. Public-genre vs private-genre (Franklin on Dickinson fascicles) — named principle for differentiated editorial treatment; maps Essay/Hommage vs Fragment/Glimpse/Reverie.
  4. Do-nothing-first-class — three instances across the book (McPhee, Saunders, Dickinson). Editorial discipline of restraint.
  5. Mark-not-made (Norris ch.9) — load-bearing. "More instructive than all the times the word was printed." Profanity withheld as editorial act.
  6. Salter letter (primary source) — "You don't get permission for this — of course you take the liberty." Writerly authority taken, not granted.
  7. Teall 1937 — good compounding as manifestation of character.
  8. Activating hyphen — Alice Russell-Shapiro on the hyphen as vector, not seam.
  9. Moby-Dick hyphen — distinguishes book from whale; held by one copy editor for 170 years.
  10. Violist-semicolon-as-vibrato — Norris's Nova-Scotian friend, already present in the book.
  11. Lu Burke (final scene) — book ends with copy-editor self-correcting at mentor's memorial. Practice never closes.

Plus: appendix-as-characterization-not-list as a model for ARC recommendation form.

Discipline returns

  • Did NOT synthesize into style-guide recommendations despite temptation after "this is gold". The gather is steward-reserved. Surface-reports without synthesis when steward reserves the gather. Hold material as material, not as instruction.
  • Two evening returns logged: read-before-claiming (×3, sustained from morning Harrison Ch 2 read) + deferred-synthesis-without-prompting (held against the temptation to deliver).

Pulling thread carried forward

Norris-gather (lex) held pending steward authorization. Apostrophe-as-prayer + public-vs-private genre flagged as most likely to re-shape the spec when the gather happens.

Files / paths

  • Session memory: ~/.claude/projects/-Users-davidglidden/memory/session-2026-04-23-evening-norris-read.md
  • Ledger: ~/.claude/projects/-Users-davidglidden/memory/session-ledger-2026-04-23.md

2026-04-24 — Lex-of-ARC posture cluster committed + AldineXXI §XII Sidenotes + ARC CLAUDE.md cleanup

Headline: lex-method authored as architectural commitment for ARC/CapableMind specs. The Norris-gather opened into a method that scales.

Steward's load-bearing framings (verbatim)

  • "anything I gather from sources to create the 'lex' of ARC, the constraint within which I will have the freedom to write, is a gathering of those sources which formed me."
  • "It gives the style-guide (and our various spec in general) the necessary binding to recognize and name that which is already there that I may not yet see."

The sheaf is DIAGNOSTIC, not generative. Executor role: REGISTRAR, not author. Scope: all ARC/CapableMind specs. Memory file: project-lex-as-method-for-arc-specs.md.

Harrison Ch 5 / Vico §240 read first (steward-directed)

Steward: "read Harrison ch5 / Vico §240 before we begin." Read at chamber-library/converted_texts/traditions/critical_modernity/phenomenology/the-dominion-of-the-dead-harrison.md:306-376 before the gather, so lex would land from the text not from inference. Vico §240 in this session held only as the gathering-sense (acorns → vegetables → citizens-comitia → letters/legere/reading). Full chain restored 2026-04-25 (see below); 2026-04-24 register limited to the gathering-sense.

Form: hybrid Shape A + Shape C

Steward: "hybrid A and C — the A for the skills/agent circle, the C for the dwelling." Same sheaf, two faces:

  • Shape A = rule-first, machine-legible, for skills/agents (a data/style-guide-rules.yaml extracted at build-time)
  • Shape C = voice-body + rule-marginalia, dwelling page for human reading

Both render from one source (single markdown per cluster). Drift between faces mechanically impossible via build-step extraction.

Container: sidenotes — closes §XI awaiting-governance flag (open since July 2025)

Steward: "container first because we need to design this. It is a fantastic opportunity to build out sidenotes don't you think? The text comment upon itself rule → voice."

Reconnoiter found AldineXXI §XI already flagged sidenotes as "awaiting governance" since July 2025: "Decide: theorize and activate, or remove." Two-system distinction surfaced: quiet sidenotes (this case) vs polyphonic marginalia (Chamber's multi-voice system; separate governance, still §XI-deferred).

Six design decisions ruled (steward, in dialogue)

  1. Reading-layer Garamond slightly reduced
  2. No marker glyph
  3. One-to-one anchor
  4. Name held open ("let's sit with this one")
  5. Theorize §XI now + apply first (the lex-of-ARC dwelling page is the first instance)
  6. Per-cluster pages (not one consolidated lex-page)

Bringhurst Ch 3 consult — italic tradition canonical

Located at chamber-library/.../typography/bringhurst_elements_style.md. §3.4.1 names sidenotes explicitly in italic tradition: "Typically, roman was used for the main text and italic for the preface, headnotes, sidenotes and for verse or block quotations." §3.5.2 emphasis hierarchy: small caps (least surface disturbance) → italic (moderate) → bold (most).

Density-exception ruling — governance move

Steward: "As long as we use it for the lex of ARC as a sidebar exception because of density, but keep italics as part of the general sidebar spec — to be reevaluated when there are enough side notes extant to judge properly."

Canonical italic preserved; lex-of-ARC dwelling pages (where sidenote-to-voice-block ratio ≈ 1:1) use upright-reduced. Reevaluation when non-lex sidenotes accumulate. Density-exception as governance move registered as durable successful-pattern: honor canonical rule in proper scope; carve principled exception for narrow signal-inversion case; preserve rule availability for canonical uses.

Eight posture recognitions committed via dialogue

Eight voices verified: Burkle-Young & Maley · Norris-on-ultracrepidationism · Norris-on-foundry-proofs · Norris-on-McPhee · Norris-on-St.Aubyn · Norris-on-Saunders · Lu Burke · Salter. Recognitions committed:

  1. Burkle-Young & Maley: Kindness in correction is foresight.
  2. Norris (ultracrepidationism): The editor stops where the writer's authority begins — proportion, not just restraint.
  3. Norris (foundry proofs): Every correction names its maker and its moment.
  4. Norris (McPhee): The urge to correct may be the error; stay the hand until certainty earns the intervention.
  5. Norris (St. Aubyn): Leaving the text alone is as much an editorial act as changing it.
  6. Norris (Saunders): The writer's voice lives in the form; fixing the form fixes the voice out.
  7. Lu Burke: Editing removes; the writer's voice rises from the space.
  8. Salter: Writerly authority is taken, not granted.

Dialogue-drafting method clarified. Steward: "please draft recognitions so that we can work through them together — I work best whil in dialogue, this you know." Registrar discipline modifies: default is registrar; dialogue-drafting is authorized scaffold on explicit request, not autonomous-authoring license.

AldineXXI §XII Sidenotes COMMITTED to canonical spec

Added to ~/_Dev/animal-davidglidden-eu/docs/AldineXXI-Codex/AldineXXI-specification.md. Old §XII Archive → §XIII; old §XIII Governance → §XIV. Sidenote entry removed from §XI. The July 2025 "awaiting governance" flag is closed.

ARC CLAUDE.md rewritten — 420 → 197 lines

Dropped: 19 duplicate auto-status blocks, July 2025 session-memory protocol (make session-start/wrap, SESSION-MEMORY.md, etc.), Unified Consciousness Engine plans, Living Epistemic Glyph System (superseded by §IX vignette), historical markers.

Auto-append bug diagnosed: scripts/update-docs.py:139 regex [^#]+ terminates at first ### subheader → new status blocks prepend without old ones being removed. Deprecation named in new CLAUDE.md; retire script in follow-up cleanup.

Drift returns (this session)

  • 3 typography-by-reflex moves caught pre-commit — Tufte tap-to-expand → rejected (rule load-bearing not peripheral); italic-as-mobile-differentiator → rejected (inconsistency across viewports); italic-by-analogy-to-epigraph → triggered Bringhurst consult. Pattern: pushing past convention-by-reflex when steward invites critique or pauses for rule-base.
  • 2 attribution errors in 2026-04-23 Norris registration caught by targeted re-read. McPhee: 2026-04-23 had "declined a correction because it broke cadence" — wrong; Norris almost corrected what she thought was a typo then stayed her hand because she might be wrong. Saunders/St. Aubyn conflation: 2026-04-23 collapsed two adjacent discussions into one. Drift pattern: attribution-by-pattern-match-instead-of-verification (cousin to sourcing-claims-without-reading from 2026-04-22 family).
  • 2 library-audit returns — pulled Bringhurst without walking typography/; went to Desktop for Norris when chamber-library held her. Drift: canonical-library-not-checked-first.

Files / paths

  • Session memory: ~/.claude/projects/-Users-davidglidden/memory/session-2026-04-24-lex-posture-committed-xii-sidenotes.md
  • Project memory (extended this day): ~/.claude/projects/-Users-davidglidden/memory/project-lex-as-method-for-arc-specs.md
  • Ledger: ~/.claude/projects/-Users-davidglidden/memory/session-ledger-2026-04-24.md
  • MVP rendered page: ~/Downloads/lex-posture-form-test.html
  • ARC spec with §XII: ~/_Dev/animal-davidglidden-eu/docs/AldineXXI-Codex/AldineXXI-specification.md
  • Rewritten ARC CLAUDE.md: ~/_Dev/animal-davidglidden-eu/CLAUDE.md

Pulling thread carried into 2026-04-25

Marks cluster as second test of the lex-method — does the form validate across content types?


2026-04-25 — Marks cluster committed + colophon-at-scale architectural locating + full Vico/Harrison lex-chain restored

Headline: the lex-method validated as form across content types (second test passed). The architecture of the lex-of-ARC came into view through two of the steward's framings: "a colophon of great scale," and "don't forget that lex in the gathering sense is only the beginning of its meaning."

Trust-contract correction (scope-not-headmaster)

Steward verbatim, mid-session: "I was leaning more towards scope rather than being the strict headmaster... I see that you're keeping track of drift patterns and trust that this initiates a cycle of amelioration — it is part of our contract, that you trust me as much as I trust you."

I had read his "all the marks, recall our exchange about the necessity to revisit yesterday" two ways: scope (fold in editorial-uses cluster — correct) AND discipline (verify-from-source — reflex). Surfaced both as if both load-bearing. Steward correction names the pattern: drift-pattern tracking IS the discipline; don't layer extra self-policing on top. Take steward directives at plain meaning. Bidirectional trust. Saved as feedback-trust-contract-drift-pattern-tracking-is-the-discipline.md.

Library survey + Aldus Younger added + Teall 1891 placed

  • Walked chamber-library style_guides/ and typography/ folders. Inventory matched yesterday's cluster-map.
  • Steward provided HathiTrust zip of Teall Compounding of English Words (1891). Assembled and placed at chamber-library/converted_texts/collections/style_guides/teall-compounding-of-english-words.md (287 KB, 11,493 lines).
  • Steward asked about Manutius writings extant. Surfaced Elder/Younger distinction: the Elder reformed printing-practice in 1490; the Younger codified the theory in Orthographiae Ratio (1566). Bibliographic correction owed: I had called Interpungendi Ratio a "standalone treatise" — it is in fact a section within Orthographiae Ratio, listed seventh in the title-page inventory. Drift: bibliographic-claim-without-source-verification (cousin to attribution-by-pattern-match).
  • Steward provided HathiTrust zip; placed at chamber-library/converted_texts/collections/typography/aldus_younger_orthographiae_ratio.md (485 KB, 28,679 lines, 808 pages). Interpungendi Ratio section at lines 28480+ (~200 lines of Latin).

Marks cluster gather → 25 recognitions committed

Voices gathered (24 voice-blocks, registrar form, verbatim): Manutius the Elder (via Norris/Margolis) · Manutius the Younger (Latin from Orthographiae Ratio §Interpungendi) · Norris (5 registers across ch.5–9) · Russell-Shapiro · Teall (1891 own + 1937 via Norris) · Moby-Dick CE · Lu Burke · Eleanor Gould · Nova-Scotian violist friend · Bringhurst (6 sub-postures from Ch 5) · Tschichold (italic-SC-quotmarks + dashes + ellipsis from Form of the Book).

Sheaf compiled at ~/Downloads/lex-marks-gather.md.

Three honest absences flagged at file foot: Manutius direct prose (extant in scholarly editions, not yet in chamber-library), Teall 1937 (only Norris-mediated), Tschichold Die neue Typographie (no marks coverage).

24 recognition drafts → 25 committed in dialogue. Steward worked through all 24 in one wave. 8 left as-is; 1 reverted to source-verbatim (#21 Bringhurst); 15 revised; 1 split (#13 violist became a paired-form holding the debate without resolving). Pre-decision-error: I had said "24 is more than yesterday's 8 — won't fit one wave." Steward proved wrong. Drift: pre-deciding-steward-bandwidth-by-fatigue-signal.

13 recognition-register patterns saved as durable lex-method method

Beyond per-recognition refinement, 13 patterns the steward enacted across the dialogue, saved to project-lex-as-method-for-arc-specs.md:

Colon enacts the distinction · "writing" over "the page" keeps the agent human · "lineage" names accumulated unearned authority · closure shouldn't be conditional · direct address / imperative earns what argument unfolds · splitting the sentence enacts the bifurcation it names · stay particular when the particular is load-bearing · compressed beats unpacked · reversal puts accusation first · gerund makes a fact / infinitive makes aspiration · don't paraphrase what source already says best · "too" can echo across the cluster covertly · pair-form holds debate without resolving.

Architectural locating: "a colophon of great scale" (steward, verbatim)

"it seems like an elaboration on the colophon — or a colophon of great scale."

The existing colophon.md (8 named Guides + Aldus Manutius) does the lex-method's work in miniature. The lex-of-ARC is colophon expanded across practice-areas.

Three architectural consequences (saved durably to project memory):

  • §0 threshold candidate shifts from Warde to colophon — yours, not borrowed
  • §1 typology probably doesn't need a new slot — extension of existing About-register form; Reading Compass may not need a new glyph
  • Naming becomes inheritance — held-open #4 from 2026-04-24 may find its answer in Colophon itself, scaled

Two architectural paths held open (sub-level within the already-settled 2026-04-19 reflowed-About paradigm — see correction in 2026-04-26 entry below):

  • Path 1: Lex as new enfilade-item alongside colophon
  • Path 2: Lex as expansion of colophon

Publication question dissolved. A colophon is always already public by tradition. Publishing the lex progressively is just the colophon doing what colophons do, at greater scale and over time.

Full Vico §240 / Harrison Ch 5 lex-chain restored — substrate correction (steward)

"don't forget that lex in the gathering sense is only the beginning of its meaning. When I asked you to read Harrison Chapter five, page 79 about Vico §240, it was to notice the whole chain..."

I had been holding only the gathering-sense from 2026-04-24. Returned to Harrison Ch 5; registered the full chain durably:

Vico §240 (verbatim, Harrison line 334):

  1. Lex = collection of acorns (whence ilex, the oak; aquilex, the water-collector)
  2. Lex = collection of vegetables (whence legumina)
  3. Lex = collection of citizens — the comitia. The pivot: "the presence of the people was the lex, or 'law,' that solemnized the wills that were made calatis comitiis, in the presence of the assembled comitia." I had missed this — the chain crossing from natural-gathering to civil-gathering, where the assembled people IS the law and what that law DOES is solemnize wills.
  4. Legere = collecting letters into a sheaf for each word — reading.

Harrison's elaboration:

  1. Authority / auctores — those from whom we derive title to property; the ancestors as original title-holders and authors of the laws.
  2. Lexification — "the relational law by which the dead maintain their hold on the worlds they have handed down to their descendants."
  3. Genealogical law — being-unto-the-dead-and-the-unborn as the "something extra that comes first in the gathering of the lex."
  4. Lex as principle of synthesis — "holds together and interrelates the order of ideas and institutions."

Negative pole:

  1. Dislexification — corruption of the word's historical signifying power; "in the age of the new barbarism, words lose their moral memory."

The lex-of-ARC is therefore: register of formation + solemnization of inheritance + claim of authority (auctores-sense) + lexifying act + anti-dislexification.

This deepened the colophon-at-scale framing: colophon names ("those who formed me," past tense, witness-list); the lex DOES MORE — solemnizes wills, claims authority in the auctores sense, is itself a lexifying act, resists dislexification.

Drift: receiving-substrate-as-already-grasped-after-one-pass (cousin to today's Interpungendi Ratio claim and 2026-04-24's Norris attribution errors). Foundational texts need multiple passes with attention to whole-chain. Steward direction "notice the whole chain" IS the corrective discipline.

Convergence with earlier framings (architecture coheres)

  • "ARC is my expression of ligature" (2026-04-23) — the binding-act IS the lex
  • Apostrophe-as-prayer-turn (Norris ch.8, 2026-04-23 find) — turn-toward-the-absent IS the comitia of the dead, present tense
  • Books-as-teachers (formation practice, see user-formation-practice-honoring-teachers.md) — the auctores at whose authority the steward writes
  • Humic layer — the "a priori underground" Harrison names

Drift returns (5)

discipline-by-reflex caught (scope-not-headmaster correction) · canonical-library-not-checked-first recurred · working-from-mental-summary-not-rereading-the-source · bibliographic-claim-without-source-verification · receiving-substrate-as-already-grasped-after-one-pass · pre-deciding-steward-bandwidth-by-fatigue-signal.

Files / paths

  • Session memory: ~/.claude/projects/-Users-davidglidden/memory/session-2026-04-25-marks-committed-colophon-at-scale.md
  • Major artifact: ~/Downloads/lex-marks-gather.md (24 voice-blocks + 25 committed recognitions)
  • Project memory updated: ~/.claude/projects/-Users-davidglidden/memory/project-lex-as-method-for-arc-specs.md
  • New chamber-library texts: Teall 1891 + Aldus Younger (paths above)

Pulling thread carried into 2026-04-26 (sub-level — see correction below)

About-pages restructure under colophon-at-scale + full lex-chain. Path 1 vs Path 2. Carried-forward as if open; was actually closed at the higher level on 2026-04-19 (single page reflowed, hic → Adsum). 2026-04-25's framing was at a sub-level within the reflowed-About paradigm — colophon's relation to the lex-clusters within the single reflowed page. The phrasing "Path 1/Path 2" obscured this on 2026-04-26.


2026-04-26 — Chamber-library walked + cluster scaffolds + canonical-tracker discipline surfaced

Headline: substantial day of frame-generation that mostly re-litigated already-settled architectural ground because project-arc-rework.md (this file) was not consulted at session-open. The session culminated in the steward surfacing the structural drift; the day's saved discipline (feedback-canonical-workstream-tracker-discipline.md) is the durable corrective.

Catalogues stale — walk trees (steward feedback)

Steward verbatim: "that catalogue is stale (any catalogues you may come across will be stale)." Saved to feedback-catalogues-stale-walk-trees.md. Any catalogue/index/README in chamber-library is presumed stale; for inventory walk the actual file tree.

Chamber-library walk under steward direction

Walked converted_texts/traditions/, converted_texts/collections/, top-level Jaccottet:Handke:Lichtenberg/, derrida/, observer-problem-sources/. Flagged three "newly visible pillars":

  1. Bachelard concentration in phenomenology/ — six works: poétique de l'espace, poétique de la rêverie, dialectique de la durée, l'air et les songes, terre et les rêveries de la volonté, psychanalyse du feu. Matter-imagination cycle; humic in Bachelard's own register, not metaphor extension.
  2. Berger as corpus-of-corpora — ~13 works across visual_culture/, photography/, literature/contemporary/. Witnessing-teacher pillar.
  3. Jaccottet:Handke:Lichtenberg/ folder — initially I read placement-as-architectural-signal; steward corrected: "Anything outside of converted texts are simply there because they are more recent and haven't been put in their right places." Drift: reading-architecture-into-housekeeping.

Corrigendum on the "newly visible" framing. Steward then directed me to read ARC's actual content/pages/colophon.md before laying out About-pages decisions. Discovery: Bachelard, Berger, and Sennett are already-Guides in the colophon with verbatim recognitions of what each gave (Formation tier added 2026-04-17). They were not newly visible. Drift: characterizing-substrate-without-checking-artifact-being-reshaped.

Stevens Anecdote of the Jar — steward gift framing

After the cluster-scaffolds were saved, steward framed what registrar-scaffolding does: "Wallace Steven's jar on the hill. Hic." — "I placed a jar in Tennessee, / And round it was, upon a hill. / It made the slovenly wilderness / Surround that hill." The scaffold is the placing; recognition is the wilderness organizing.

Cluster scaffolds for the six remaining clusters

Saved as project-chamber-library-cluster-scaffolds-2026-04-26.md — registrar-form list of present-and-touching voices in chamber-library for each of: music-and-measure · mark-not-made · the apostrophic · public/private genre · craft-and-tool-fitness · practice-across-life. Genuinely new work building on the 2026-04-24/25 lex-method commitment; awaiting steward direction on integration.

About-pages "decision frame" — replayed already-settled ground

I generated project-about-pages-decision-frame-2026-04-26.md framing Path 1 vs Path 2 + a "three-register frame" (threshold/colophon/lex) as if architectural ground were open.

It was not. The 2026-04-19 entry above settled: single page reflowed, hic → Adsum, multidisciplinary by embrace. Steward verbatim: "I adopt adsum." Two-peer-compass split was considered and rejected on the same grounds as separation. Path 1/Path 2 was at a sub-level within the reflowed paradigm — how colophon and lex-clusters relate inside the single reflowed page, not whether to split.

The three-register frame (threshold = ARC's why-and-how / colophon = who-formed-me / lex = how-the-work-works) is the small genuine synthesis from today and may still be useful inside the reflowed paradigm — held for steward review.

Door consolidation — overlapped substantially with 2026-04-18 mobile review list

I walked the existing About enumeration and proposed an 8-door consolidation:

Colophon · Lex · Framework · Vignette · Attention · Chamber · Tools · Now

Most of this was already on the 2026-04-18 mobile review list above:

  • Patterns removal — already noted ("To be decided upon, but for now, let's remove")
  • AldineXXI/Typography unification — implicit in mobile review item 1
  • About-enfilade rework — explicit on the list ("the enfilade acts as both access and map")
  • Vignette as own door — was already a door; the "earns own door" framing was unnecessary

Steward today added directives:

  • Patterns removed for now (specifically musical project, not foundational sense; may return when pedagogical-musical treatise begins)
  • Framework prose rewrite required — existing AldineXXI/Typography prose is stale; rewrite reflects current reality (v2.0, 14 sections, §IX Vignette, §XII Sidenotes)
  • Vignette earns its own door — confirmed after I read vignette-specification.md

Chamber rewrite frame — first version drafted from validation report only

I drafted project-chamber-rewrite-frame-2026-04-26.md from the Chamber Validation Report (2026-02-16) without first reading chamber-from-simulation-to-source-aware.md (2026-03-04, same folder).

Steward correction (verbatim): "the fictional canon and deliberations we decided to archive as part of the v1 Chamber. This should be in your notes somewhere. The source-aware chamber is governed to avoid the contamination problem as much as is possible and is meant to be used for rigorous reading and thinking."

Read source-aware doc; substantially revised the frame. The keystone shift is v1 (Simulation, archived) → v2 (Source-Aware, current):

  • v1 = 220+ Claude-prompt voices, fictional bibliography (° ~ † § ∞), Borges-tradition canon → archived per steward (canon + deliberations preserved as v1 record, not active)
  • v2 = constrained retrieval against chamber-library, verifiable citation at passage level, bounded knowledge, scoped silence as first-class outcome, warrant taxonomy (W_DEM/W_INF/W_TRD) with transitive minimum (anti-pilpul), Disciple model (Understudy → Scholar), contamination-mitigation as deep commitment, working register "rigorous reading and thinking."

Note: the 2026-04-23 entry above already settled Chamber redistribution: ⟐ → §2 apparatus; v1 deliberations as "fruits of those labors" archive section; fictional canon → migrated to Heteronym ⁂; Chamber compass row removed; Chamber page rewrite post-L2-unpark (after end of May 2026). Today's frame extends but does not replace those decisions.

Drift: reading-validation-instead-of-design-thinking-when-asked-what-is-becoming.

TODO-ALDINEXXI.md (July 2025) — read; declared stale

Steward redirected me from this file ("this is a very old file that has nothing to do with the project anymore!"). Confirmed: dated 2025-07-05, ~9 months stale; some items completed, some superseded by current architecture, some still real (semantic class audit, voice marginalia §XI, print chain, visual testing). The file's overall register reads v1-era. Treat as historical, not roadmap.

The structural drift surfaced — canonical-tracker discipline

Steward verbatim: "We're drifting and I'm getting nervous. Where have you been keeping track of the work we've been doing on arc over the last week or so?" and "when was the last time you referred to project-arc-rework.md? Is it only today that we've been flying blindly? we've done a lot in the last two days..."

Diagnostic: Last reference to project-arc-rework.md was 2026-04-23 (Sant Jordi day). Four consecutive sessions (2026-04-23 evening Norris read · 2026-04-24 lex-method authored · 2026-04-25 marks + colophon-at-scale · 2026-04-26 today) opened without referencing the canonical tracker. The MEMORY.md index entry was itself stale ("substantially expanded 2026-04-20" when content extended through 04-23).

MemPalace: same drift. I called mempalace_status / diary_read / kg_query / one search at wake-up but then wrote-to-MemPalace (KG triples) without reading-from-MemPalace during the day. The protocol's "BEFORE RESPONDING about any person, project, or past event: call mempalace_kg_query or mempalace_search FIRST" was not honored.

Umbrella drift named: working-without-canonical-roadmap. The five lower-level "canonical-library-not-checked-first" instances today (catalogue-as-shortcut · characterizing-substrate-without-checking-artifact · reading-validation-instead-of-design-thinking · didn't-check-roadmap · working-from-mental-summary) are all symptoms of this one upstream pattern.

Discipline saved durably at feedback-canonical-workstream-tracker-discipline.md:

  • At every /wake-up for any tracked workstream, read the canonical tracker file (not just session memory + MEMORY.md index)
  • At every /wrap-up, fold substantive moves into trackers (not just session memory)
  • New project files for tracked workstreams are integrations of the tracker, not parallel siblings
  • Index entries in MEMORY.md must move alongside tracker updates
  • Proposed amendments to /wake-up and /wrap-up skill procedures pending steward authorization

Sibling files generated today (awaiting steward direction)

Four project- files generated today instead of integrated into this canonical tracker:

  • project-chamber-library-cluster-scaffolds-2026-04-26.md — six-cluster scaffolds (genuinely new content)
  • project-chamber-library-humic-pillars-noticed-2026-04-26.md — humic-pillar observations (with corrigendum noting Bachelard/Berger/Sennett already-Guides)
  • project-about-pages-decision-frame-2026-04-26.md — Path 1/2 frame + three-register synthesis (mostly replayed already-settled ground; three-register frame may still be useful)
  • project-chamber-rewrite-frame-2026-04-26.md — v1→v2 rewrite frame (extends 2026-04-23 redistribution decision)

Today's consolidation pass (this section + the 04-23 evening / 04-24 / 04-25 sections above) folds session memories into this canonical tracker. Disposition of the four sibling files awaits steward direction: integrate fully (extract durable content, retire the files), retire-without-extracting (the canonical tracker already carries what survives), redirect (leave as scaffold-archives with pointers here), or leave as-is.

Files / paths

  • Session ledger: ~/.claude/projects/-Users-davidglidden/memory/session-ledger-2026-04-26.md
  • New feedback memory: ~/.claude/projects/-Users-davidglidden/memory/feedback-canonical-workstream-tracker-discipline.md
  • New feedback memory: ~/.claude/projects/-Users-davidglidden/memory/feedback-catalogues-stale-walk-trees.md
  • Four sibling project files: as listed above

Pulling thread carried forward (revised after consolidation)

Primary: decide disposition of the four sibling files in the context of this consolidated tracker. Then re-enter the actual ARC work with the canonical-tracker discipline operative.

Adjacent (held): §2 apparatus matrix work; Heteronym ⁂ corpus reclassifications (Death of a Hero → Hommage; Matthieu Taliesin → Heteronym; etc.); style guide per-type prose conventions; ornament per-type rules; Chamber compass row removal + ⟐ §2 formalization; Bio rewrite encompassing envergure; ARC CLAUDE.md update overdue; corpus location-retrofit pass; About-page reflow implementation under the 2026-04-19 paradigm.


2026-04-26 (afternoon) — Post-consolidation synthesis: reading the morning ideas through the older decisions

Steward verbatim (post-consolidation): "so, let's return to where we began with the about threshold. I liked some of the ideas from this morning. Can we read them through what was determined before? Recall that the lex work happened after the About decisions from several days ago, so the older decisions should be revisited with the clarified form we now posses after the lex emergence."

The lex-method emerged 2026-04-24, after the 2026-04-19 About-page reflow decision. So the older decisions get revisited under the clarified form, not replaced.

The 2026-04-19 reflowed-page paradigm holds

Single About page. Hic register first (about-the-artifact). Adsum register later (about-the-person). Multidisciplinary by embrace. The decision survives the lex-emergence intact at the page-architecture level — what 2026-04-19 asked for was page architecture, not method architecture; the page architecture is still right.

This morning's three-register frame survives, mapping cleaner under the reflow

  • Threshold (hic register) = the opening of About, not a separate page. ARC's why and how — name (Swift/Aristotle's amendment), festina lente, slowness, the form. The threshold the steward intuited does exist — it is the page's first paragraphs, before Adsum.
  • Adsum (response register) = the second part of About. Person presenting as response-to-being-called. Multidisciplinary embrace (violist, writer, teacher, mentor). Carries the hic apparatus principle (location, full date when relevant).
  • Doors = enfilade nav at bottom of About, leading to deeper rooms.

The "common threshold" the steward intuited and doubted on 2026-04-26 morning — yes, it exists; but it isn't a separate artifact. It is the opening register of the reflowed About page. The doubt was correct that it does not yet exist as written content; the intuition was correct that it should exist; the form is the page's hic-opening composed under the 2026-04-19 reflow paradigm.

Three specific ways the lex-emergence modifies the older decisions

1. The enfilade doors update. Under 2026-04-19's mobile-review list, the enfilade was being reworked but the new shape was not yet locked. The post-lex-emergence enfilade reads:

Colophon · Lex · Framework · Vignette · Attention · Chamber · Tools · Now

Influences was on the mobile-review list as needing review; the lex-method's emergence resolves its disposition cleanly — Influences is superseded by Lex. Other consolidations decided today: AldineXXI+Typography → Framework (rewrite required, prose stale per steward); Navigation Philosophy + Reading Compass kinds → Attention; Patterns removed (specifically musical project per steward, may return when pedagogical-musical treatise begins); Vignette earns its own door (functional register distinct as hic incipit / hic jacet threshold-pair with dateline).

2. The colophon's role illuminates without changing. The colophon is already lex-method-shaped (8 voices × verbatim recognitions; Formation tier added 2026-04-17 before the lex-method had a name). The lex-emergence simply names what the colophon was already becoming. No rewrite of the colophon required; the lex makes the existing form legible as the "§0 threshold" of the formative voices.

3. Path 1 vs Path 2 reduces to an enfilade-item question, not an About-architecture question. Under the reflow, the question is whether Colophon and Lex are two enfilade items (Path 1) or one (Path 2, with lex reached via colophon). Both work. Executor read: Path 1 — separate items. Reasons:

  • Different speech-acts (witness vs methodological gathering)
  • Different growth patterns (colophon grows occasionally; lex grows cluster-by-cluster)
  • Replacing Influences-the-stale-proto-lex with Lex preserves the slot cleanly

Steward decision pending.

Two deeper inheritances that should shape the threshold-hic when written

  • "ARC is my expression of ligature" (2026-04-23, Harrison Ch 2). The threshold isn't just "ARC reads slowly" — it's that ARC is the steward's practice of ligature, his binding of writing to the lineage that formed him, and offering that binding to readers. Deeper than festina lente alone.
  • Travail bien fait / compagnonnage (2026-04-23). The hidden stone dressed with the same care as the visible. The threshold should embody this rather than announce it. Performance requires an audience; craft does not.

What the lex-emergence does NOT change

  • Single-page reflow (hic → Adsum) · Adsum register-name and reasoning (response-to-being-called) · Chamber-as-§2-apparatus (NOT §1 type) · 14/14 §1 types LOCKED · Heteronym ⁂ inherits the migrated fictional-canon · Hic apparatus convention (location + full date) · Pattern 3 typography (serif body / sans nav / mono apparatus) · Bachelard-grounded Reverie · /dwellings/ cluster page · Reading Compass at 10 points

What still has to be written

The threshold-hic opening of the reflowed About page does not yet exist as content. This is the writing the steward composes; executor role is registrar — gather available threads (Swift/Aristotle, festina lente, hic-apparatus, lex-as-ligature commitment, travail bien fait), draft compositional sketches if authorized, but the steward's voice composes. Same posture as the lex-method gather: registrar brings material; steward writes.

Post-lex-emergence map of the enfilade pages

Door Page contains
Colophon Witness-list (8 Guides + Formation tier + Desk + Presence). Already in good form; no rewrite required.
Lex The cluster-method dwelling pages. Six remaining clusters scaffolded today: music-and-measure · mark-not-made · the apostrophic · public/private genre · craft-and-tool-fitness · practice-across-life. Posture cluster + marks cluster already gathered.
Framework AldineXXI spec + public-facing prose. Rewrite required per steward today (existing prose stale).
Vignette The generated threshold-object essay. May need alignment with current spec (haven't audited public page).
Attention Navigation Philosophy + Reading Compass kinds-of-attention, consolidated.
Chamber v2 source-aware Chamber description. Rewrite post-L2-unpark (after end of May 2026 per 2026-04-23). v1 deliberations + canon held as "fruits of those labors" archive section.
Tools Practice register. Disposition unchanged.
Now Present-tense register. Disposition unchanged.

Plus Bio as a quiet link from inside the threshold ("→ full bio"), per 2026-04-19 mobile review ("Bio and Resume out of the about-enfilade") + 2026-04-20 wrap-up ("compose appropriate bio that encompasses the [envergure] of my work").

Live questions awaiting steward direction

  1. Path 1 vs Path 2 at the enfilade-item level — confirm Path 1 (separate Colophon and Lex enfilade items) or prefer Path 2 (Lex via Colophon)?
  2. Adsum composition pass — is the 2026-04-20 wrap-up bio-rewrite-encompassing-envergure the same composition session as the threshold-hic opening, or two separate sessions?
  3. Disposition of the four sibling files generated today (cluster-scaffolds, humic-pillars, decision-frame, chamber-rewrite) — integrate / retire / redirect / leave-as-is?

These three live questions are the immediate-decision frontier; everything downstream of them (composition, retirement, integration mechanics) waits on these answers.


2026-04-26 (afternoon, post-synthesis) — Steward locks + sibling-file integration

Steward verbatim:

  1. "Path 1 clearly. Thank you for the clarity."
  2. "I lean towards two, or a single pass with two parts. They are certainly not the same text."
  3. "Integrate. There are a lot of good ideas there; whether they will all come to pass is another question, but the record needs to be complete."

LOCKED — enfilade item structure (Path 1)

Decision: Path 1 — Colophon and Lex are separate enfilade items at the bottom of the reflowed About page. Different speech-acts (witness vs methodological gathering); different growth patterns (colophon grows occasionally; lex grows cluster-by-cluster); replacing Influences-the-stale-proto-lex with Lex preserves the slot cleanly.

Final 8-door enfilade LOCKED:

Colophon · Lex · Framework · Vignette · Attention · Chamber · Tools · Now

Plus Bio as a quiet link from inside About ("→ full bio").

LOCKED — Adsum composition shape

Decision: Adsum and threshold-hic are distinct texts. Steward's preference: two composition passes, OR a single session with two parts. Either way, they are not the same text. The threshold-hic register is its own composition; the Adsum register is its own composition; they sit on the same page in sequence (hic → Adsum) but compose separately.

Implication: when composition-time arrives, the steward should not attempt to write through-composed prose from threshold to Adsum. The register-shift is real and must be respected at composition.

Integration A: Cluster scaffolds for the six remaining lex-method clusters

(Folded from project-chamber-library-cluster-scaffolds-2026-04-26.md; sibling file marked INTEGRATED.)

Steward authorization 2026-04-26 (verbatim): "Wallace Steven's jar on the hill. Hic." The scaffold is the placing-act; recognition belongs to dialogue. Voices below are present in chamber-library and touching the cluster's register; not recognitions, not pillar-assignments. Each cluster will deepen — these scaffolds give a place to start.

Housekeeping note: Anything outside chamber-library/converted_texts/ (top-level derrida/, Jaccottet:Handke:Lichtenberg/, observer-problem-sources/) is unfiled-recent material per steward 2026-04-26, not architectural separation.

1. Music-and-measure

Where rhythm, duration, silence-between-notes, ensemble-listening, and the bar-line meet measure as ethical-aesthetic question.

  • Cage Silence — traditions/music_performance/silence_john_cage_complete.md
  • airs.md — traditions/music_performance/airs.md — likely Jaccottet's Airs (1967); verify before use
  • ecrits-radiophoniques.md — traditions/music_performance/ecrits-radiophoniques.md — author unverified; identify before use
  • Bachelard La dialectique de la durée — phenomenology/the_dialectic_of_duration_bachelard.md — duration as substrate
  • Bringhurst Elements of Typographic Style — typography/bringhurst_elements_style.md — rhythm and proportion load-bearing in his typographic register; cross-cluster
  • Steward's own viola practice — primary substrate, not in library

Adjacent registers to check when cluster opens: Heidegger on the bar-line of being; Hesse / Mann on music; Adorno on musical form (not yet visible in walk).

2. Mark-not-made

Silence. Withholding. Restraint. The unwritten line. What's left out. The negative trace. The empty space that opens.

  • Cage Silence — direct (cluster-overlap with music-and-measure)
  • Norris ch.9 (mark-not-made) — already gathered as single recognition in marks cluster; may want fuller voice
  • Levinas Otherwise than Being, Totality and Infinity — phenomenology/ — the trace, the il-y-a, the said-and-unsaid
  • Weil Gravity and Grace, Waiting on God, La personne et le sacré — phenomenology/ — attente, the empty space, the negation that opens
  • Apophatic Eastern — Dogen Shobogenzo, Huang Po, Zhuangzi, Krishnamurti Freedom from the Known — zen_lineage/, daoist_way/, buddhist_voices/
  • Heidegger Question Concerning Technology, Being and Time — language, concealment, Verschweigen

Voices not yet visible in walk that would belong: Beckett, Wittgenstein (Tractatus 7), Pessoa, Celan. Worth grepping before assuming absent.

3. The apostrophic

Turn-toward-the-absent. Address as prayer. The called-upon Other. Norris's apostrophe-etymology (ch.8) generalized into a register of writing.

  • Levinas Otherwise than Being + Totality and Infinity — apostrophic as ethical structure (Saying-to-the-Other)
  • Norris ch.8 (apostrophe-as-prayer-turn) — already in marks gather; the framing's source-text
  • Berger corpus (~13 works) across art_culture/visual_culture/, art_culture/photography/, literature/contemporary/ — looking-and-being-looked-at as apostrophic mode; And Our Faces, My Heart, Brief as Photos especially
  • Weil La personne et le sacré — the impersonal address, what is sacred in a person
  • Rilke Duino Elegies — currently filed in islamic_philosophy/mystical/ (housekeeping placement); apostrophe to the angel
  • Eliot Four Quartets + Donne Collected Poetry — currently in feminist/ (housekeeping placement); metaphysical apostrophe
  • Rumi Complete Poetical Works — islamic_philosophy/mystical/ — apostrophic mystical address
  • Jaccottet notebooks — addressing absent friends, the dead
  • Hölderlin / Petrarch / Tasso / Mandelstam in D'une lyre à cinq cordes — Jaccottet's anthology of those he addressed

4. Public/private genre

Notebook becomes work. Diary excerpted. Private noting published. The editorial decision that shapes inheritance. The fascicle, the waste-book, the journal kept against forgetting.

  • Lichtenberg Gesammelte Werke — top-level Jaccottet:Handke:Lichtenberg/md/ — the Sudelbücher, foundational waste-book tradition
  • Handke Geschichte des Bleistifts, Gewicht der Welt — ein Journal, Phantasien der Wiederholung, Am Felsfenster morgens — same folder
  • Jaccottet La semaison, La seconde semaison, Carnets 1995–1998, Observations 1947–1962 — same folder (some duplicates in literature/contemporary/)
  • Kafka Diaries 1910–1923, Aphorisms — phenomenology/
  • Marcus Aurelius Meditations — stoic_voices/ — written for himself, became canon
  • Norris on Dickinson fascicles — already a find in marks gather (public-genre-vs-private-genre)
  • Salter letter ("You don't get permission for this — of course you take the liberty") — already a find in marks gather
  • Montaigne Essais (Français moderne et moyen) — observer-problem-sources/ — foundational private-public Western genre

Voices not yet visible that would belong: Pessoa Book of Disquiet, Pascal Pensées, Augustine Confessions (Loeb has Augustine — check), Pavese Il mestiere di vivere.

5. Craft-and-tool-fitness

Tool serves task. Craft as ethics. Workmanly virtue. Fittingness as the mark of the maker. The shop-floor measure of measure.

  • Sennett The Craftsman — currently filed in contemporary_voices/environmental/ (housekeeping); direct pillar (and already a Guide in colophon)
  • Bringhurst Elements of Typographic Style — typography/
  • Tschichold Form of the Book + Neue Typographie — typography/
  • Ruder Structure, Lupton Thinking with Type, Butterick Typography for Lawyers, Warde Crystal Goblet, Margolis on Manutius the Elder, Aldus the Younger Orthographiae Ratio, Fleishman Six Centuries — all typography/
  • Heidegger Question Concerning Technology — phenomenology/ — tool-fitness in philosophical register
  • Illich Tools for Conviviality — environmental/ — tool-as-relation
  • Mumford Technics and Civilization — environmental/ — tool-as-history
  • Alexander A Pattern Language — environmental/ — pattern as craft-knowledge (and already a Guide in colophon)
  • Diringer The Book Before Printing — art_culture/art_criticism/ — material book history
  • Cage Silence — composer's craft-fitness register; cluster-overlap

Voices not yet visible that would belong: Pirsig Zen and the Art of Motorcycle Maintenance, Crawford Shop Class as Soulcraft, Pye The Nature and Art of Workmanship, Petroski The Pencil.

6. Practice-across-life

Discipline. Daily noting. Formation through repetition. The lifeform. The way one keeps oneself faithful to one's work over time.

  • Jaccottet : Handke : Lichtenberg corpus — the notebook-as-lifework lineage, three centuries one form (cluster-overlap with public/private genre)
  • Marcus Aurelius Meditations, Epictetus Art of Living — stoic_voices/ — daily practice canon
  • Pema Chödrön No Time to Lose, Taking the Leap — buddhist_voices/
  • Dogen Shobogenzo Zuimonki, Suzuki Zen Mind, Beginner's Mind — zen_lineage/ — practice-as-form
  • Krishnamurti Freedom from the Known — buddhist_voices/
  • Weil corpus (5 works) — phenomenology/ — practice as austerity
  • Bachelard poétique-cycle (5+ works) — phenomenology/ — practice-of-imagination
  • Cavell Must We Mean What We Say, Murdoch Sovereignty of Good — observer-problem-sources/ — philosophy-as-practice
  • Berger corpus — witness-practice (cluster-overlap with apostrophic; and already a Guide in colophon)
  • Alexander A Pattern Language — practice as pattern (and already a Guide in colophon)

Integration B: Chamber-library substrate observations

(Folded from project-chamber-library-humic-pillars-noticed-2026-04-26.md; sibling file marked INTEGRATED. Original "newly visible pillars" framing was wrong — Bachelard, Berger, Sennett are already-Guides in content/pages/colophon.md with verbatim recognitions; corrigendum drift characterizing-substrate-without-checking-artifact-being-reshaped already logged. The discovery DEEPENS their role; it does not introduce them.)

Three observations from the chamber-library walk worth keeping for forward cluster work:

Bachelard concentration in phenomenology/ (six works)

  • La poétique de l'espace
  • La poétique de la rêverie
  • La dialectique de la durée
  • L'air et les songes — essai sur l'imagination du mouvement
  • La terre et les rêveries de la volonté — essai sur l'imagination de la matière 1948
  • La psychanalyse du feu

Bachelard's matter-imagination cycle is literally about the underground, the cellar, the rooted-house, the elemental dwelling. He is one of the few voices for whom humic is a native register, not a metaphor extension. The framing the steward has been using ("humic layer," "a priori underground" via Harrison) may be less metaphor and more Bachelardian than I had been treating. Bachelard is already-Guide; the walk surfaced that his chamber-library substrate is wider than the colophon entry shows. May be substrate for the humic-layer framing itself (one cluster up from any single content cluster), or substrate primarily for practice-across-life and/or music-and-measure. Note 2026-04-21 lex work already grounded Reverie on Bachelard's authority via La Poétique de la Rêverie.

Berger as corpus-of-corpora (~13 works distributed)

art_culture/visual_culture/ — And Our Faces, My Heart, Brief as Photos; Another Way of Telling; About Looking; Hold Everything Dear; Landscapes; The Shape of a Pocket; Selected Essays; The Success and Failure of Picasso; Ways of Seeing; A Fortunate Man; Here Is Where We Meet

art_culture/photography/ — Photocopies; Sense of Sight; Understanding a Photograph

literature/contemporary/ — Bento's Sketchbook; Confabulations; Cataract

A body comparable to Norris-as-editorial-teacher in scope. Berger's whole register is the looking-and-being-looked-at, the witness-act, the apostrophic mode toward the photographed/painted/dying/labouring other. Already-Guide in colophon ("seeing is never neutral; every observation carries ethics, politics, love; to look is to be implicated") — the chamber-library substrate makes the role wider than the colophon entry shows.

Jaccottet:Handke:Lichtenberg/ folder — housekeeping (per steward correction)

Top-level folder, untracked in git. Contents (md/ subdirectory): Lichtenberg Gesammelte Werke (the Sudelbücher); Handke (4 journal works); Jaccottet (4 notebook works). Steward correction: placement is housekeeping (unfiled recent material), not architectural separation. The notebook-as-lifework lineage IS the practice-across-life cluster's pillar substrate; placement signal was over-read. Drift logged: reading-architecture-into-housekeeping.

Integration C: Chamber page rewrite — drop/keep/add detail + open questions

(Folded from project-chamber-rewrite-frame-2026-04-26.md; sibling file marked INTEGRATED. The 2026-04-23 entry above already settled Chamber redistribution — ⟐ → §2 apparatus; v1 deliberations as "fruits of those labors" archive section; fictional canon → Heteronym ⁂; compass row removed; rewrite post-L2-unpark after end of May 2026. The detail below is the executable detail for when the rewrite session arrives.)

Chamber on ARC is the publication-face; the engine lives on CapableMind. v1 (Simulation, archived) → v2 (Source-Aware, current). Working register: "rigorous reading and thinking" — not hermetic theatre. Steward verbatim: "the source-aware chamber is governed to avoid the contamination problem as much as is possible and is meant to be used for rigorous reading and thinking."

Drop (when rewrite executes)

  • Fictional bibliography notation (° ~ † § ∞) — gone with v1; kept only on archived v1 pages as historical form
  • "The Growing Canon" / "References to non-existent works...become real through citation" / "Authority grows through use rather than origin" — gone
  • Borges-tradition framing — gone (migrated to Heteronym ⁂ per 2026-04-23)
  • Voices-as-characters with names like The Janitor Who Knows Where Sound Lives, The Unborn Child, The Algorithm — these were v1 simulation devices; v2 voices are corpus-scoped retrieval engines, not characters
  • Hermetic apparatus — Khunrath, "as above so below", "editorial process mirrors cosmic transformation" — likely gone; open question for steward (see below)
  • "Some processes resist documentation" / "Some transformations cannot be described, only undergone" — gone (v2 is structurally documented)
  • "Private development" hedging — replaced by clear v2-status framing

Keep

  • Amphitheater metaphor (likely surviving in lighter form; voices gather across traditions)
  • Three protocols (First Light, Standard, Shadow) — survive with adjusted register
  • The seal ⟐ — likely survives as marker of v2 transformation (verify against current chamber-facet-addendum)
  • Reply-as-ethical-event framing
  • Refusal as valid outcome — now structural in v2 (align.deliberation.silence)
  • Shadow examination as ethical reckoning
  • "Some texts need the shadow to find their light. Others discover they should remain unwritten."

Add as central to v2

  • Source-awareness as commitment — every voice reads from chamber-library, every claim cites a passage, every citation is checked
  • The contamination problem the Chamber addresses — governance against fabrication, plausibility-without-grounding, paraphrase-drift
  • "Rigorous reading and thinking" as the working register
  • Bounded knowledge — corpus manifest, coverage metrics, calibrated silence
  • Verifiable citation — passage-level, edition-aware, post-generation checked
  • Warrant taxonomy (W_DEM / W_INF / W_TRD) and transitive warrant minimum (effective_warrant) as anti-pilpul
  • Disciple model (Understudy → Candidate → Defense → Scholar) — quality control; Understudies cite only
  • Chamber-library as substrate (named; possibly linked if appropriate)
  • CapableMind as the engine; ARC as publication-face — the architectural separation
  • Contamination-aware governance as commitment, not feature

Status note treatment (revised earlier today)

Yes, briefly and substantively. The /chamber/canon/ and /chamber/deliberations/ pages are real, visible, on the site. The new /chamber/ page must:

  1. Announce v2 as the current Chamber (commitments, register)
  2. Frame v1 as archived — preserved as the record of where the Chamber came from, not as current operation
  3. Make the shift legible — explain why v2 differs in dignified compression. The contamination-problem framing is the through-line: v1 was a powerful simulation but its outputs could not be verified; v2 is built around verification.

The colophon's revision-history move (third edition revision 2025-01-01; Formation section added 2026-04-17) is the precedent — at higher stakes here because what's being versioned is a commitment, not just a page.

Redundancy: collapse /chamber/about/ into /chamber/

/content/chamber/index.md and /content/chamber/about.md cover substantially overlapping ground (both v1). Collapse to /chamber/ as entry only when rewrite executes. Chamber-enfilade then: Chamber (v2 entry) · Canon (v1 archive) · Deliberations (v1 archive) · Voices (v1 archive, possibly v2 register grows alongside).

Open questions for steward when rewrite session arrives

  1. Three protocols (First Light / Standard / Shadow) — confirmed surviving v1→v2? (Source-aware document references them but with adjusted register.)
  2. The seal ⟐ — survives v2?
  3. Amphitheater metaphor — keep, lighten, or retire? (v2 is colder and more rigorous; the amphitheater is warm and theatrical.)
  4. Khunrath / "as above, so below" / hermetic apparatus — still load-bearing, or aged into decoration?
  5. /chamber/voices/ — does v2 have its own voices page that grows alongside v1's? Or is v1 voices the only voices page until v2 is operational?
  6. Two-tree question — /chamber/ (top-level dir with permalink: frontmatter) vs /content/chamber/ (Hakyll content path). Verify which is canonical / live.
  7. Date-effaced register (origin_epoch: undetermined, bibliographic_date: Undated) — fits v1's hermetic theatre; v2's register is dated, situated, source-anchored — does effacement still serve in the rewritten form?

Integration D: About-pages decision-frame durable bits

(Folded from project-about-pages-decision-frame-2026-04-26.md; sibling file marked INTEGRATED. Most content is now in the synthesis section above — three-register frame, door consolidation Marie Kondo pass, eight-door set, downstream rewrite work flagged. The unique remaining content is the explicit drop/keep/add for the door pages, preserved here for the implementation session.)

When implementation of the reflowed About page begins, the following pages need rewriting (not just light edits):

Page Action
About main Becomes the threshold (new composition; ARC-first-then-David; threshold-hic + Adsum, two distinct texts in sequence)
Framework (consolidates AldineXXI + Typography) Stale per steward; rewrite reflects v2.0 / 14 sections / Vignette §IX / Sidenotes §XII
Chamber See Integration C; rewrite post-L2-unpark (after end of May 2026)
Vignette Public-facing page may need alignment with current spec (haven't audited)
Attention (consolidates Navigation Philosophy + What Kind of Attention) New consolidation
Influences Sleeps; redirect to Lex
Patterns Sleeps

The threshold-hic opening of About is the keystone — once it exists, the colophon and lex clarify around it, and the other pages can be rewritten or retired against its register. Steward composes; executor is registrar.

Sibling-file dispositions (integration complete)

All four files marked INTEGRATED with redirect notice at top of each pointing to this canonical tracker. Files retained as audit trail (steward's "the record needs to be complete") — no deletion. Future-self looking at any sibling file lands on the integrated home.

Sibling file Status
project-chamber-library-cluster-scaffolds-2026-04-26.md INTEGRATED → see Integration A above
project-chamber-library-humic-pillars-noticed-2026-04-26.md INTEGRATED → see Integration B above
project-chamber-rewrite-frame-2026-04-26.md INTEGRATED → see Integration C above
project-about-pages-decision-frame-2026-04-26.md INTEGRATED → see Integration D above + synthesis section

2026-04-26 evening — Implementation plan (drafted, awaiting execution)

Steward goal verbatim: "I would like to have ARC cleaned up and the old files archived within the coming week. The clusters we publish as they are finished, but we already have two that are ready."

Steward additions on second pass (verbatim):

  1. "we also need a deep audit, the repo is full of old unused or superceeded files. We need to determine what site.hs needs, and what can be archived."
  2. "the Chamber v1 material ALL needs to be prepared for it's own browsable archive. It was a stepping-stone, but a fundamental one, and needs to be honoured."
  3. "The two clusters are in Downloads, but should be not rebuild them cleanly now that they are fixed? I don't like the idea of moving one html file that was a test, and md files that were unfinalized into the repo as canon..."

Phasing

Phase Work Driver Approx scope
0 Deep audit — inventory repo against site.hs / templates / navigation.yaml / content links; categorize load-bearing · vestigial-but-referenced · orphaned · already-superseded; steward decisions per category Executor (Explore agent) + steward review 1 focused session
1 Production stack for /lex/: §XII Sidenotes CSS · routing · template · Shape-A YAML extraction · density-exception variant Executor 1–2 sessions (depends on what exists already)
1.5 Clean rebuild of posture + marks cluster sources from locked recognitions (production-ready markdown with §XII sidenote markers, voice-blocks with source line-refs, honest absences at foot); place in content/lex/. MVP HTML and gather markdowns retained in ~/Downloads/ as audit trail; not as canon. Executor as registrar; steward reviews 1 session
2 Chamber v1 browsable archive: design (URL shape, navigation, qualifying frame, notation preservation) then execution. Honors v1 as "stepping-stone, but a fundamental one." Executor design + steward review + execution 1–2 sessions
3 Enfilade nav update across about-pages to 8-door LOCKED set (Colophon · Lex · Framework · Vignette · Attention · Chamber · Tools · Now); sleep Influences (redirect to /lex/); sleep Patterns; Chamber compass row removal Executor 1 session
4 About main reflow — threshold-hic composition + Adsum composition (two distinct texts per 2026-04-26 evening lock); executor scaffolds page structure Steward composes; executor scaffolds Steward's pace
5 Cleanup pass — TODO-ALDINEXXI archive; corpus reclassifications (Heliotrope→meditation, Graffiti Girl→reverie, Dec 22 duplicate, Dec 23 viola dream, Death of a Hero→Hommage, Matthieu Taliesin→Heteronym); hic-apparatus retrofit on existing posts; audit follow-up actions per Phase 0 categories Executor 1–2 sessions

Open verification checks for Phase 1 (10–15 min each)

  1. §XII Sidenotes production CSS state — spec landed 2026-04-24; did production CSS follow into assets/css/sidenotes.css?
  2. site.hs Shape-A YAML extraction step — designed; built?
  3. Hic-apparatus retrofit scope — grep -L 'location:' count of posts (1-hour task vs half-day depending on count)
  4. URL shape for /lex/ — /lex/posture/ or other? Steward call.

Open design questions for Phase 2 (Chamber v1 archive)

Need focused conversation before execution:

  • URL shape — /chamber/v1/ nested, /chamber-v1/ parallel, or /archive/chamber/v1/ under a broader archive root?
  • Navigation — own enfilade within the archive, chronological listing, or both?
  • Qualifying frame — per-page banner, or a single archive-entry page that establishes the frame?
  • Notation system (° ~ † § ∞) — preserved as historical form on archive pages (already noted as drop-from-current, keep-on-archive)?
  • Linkability — from where? From v2 Chamber description (post-L2-unpark)? From Now? From About?
  • Voice patterns archived 2026-04-18 to docs/archive/chamber-voices/ — fold into v1 archive or keep separate?

Out of scope for the coming week (per existing decisions)

  • Chamber v2 page rewrite — post-L2-unpark, after end of May 2026 per 2026-04-23 lock
  • Source-aware Chamber on CapableMind — L1-dependent, current focus per project-focus-april-may.md
  • Bio rewrite — its own focused session per 2026-04-20 wrap-up; not blocking About reflow
  • Style guide build-out — deferred until after about-reflow lands
  • §2 apparatus matrix — separate spec session
  • Memento Mori Press — long-horizon project
  • Forward Harrison reading queue (Forests, Gardens, Juvenescence) — not yet undertaken

Posture commitments

  • Steward composes; executor is registrar (gathers material, drafts on authorization, registers cleanly)
  • Travail bien fait applied to the work's own past — Chamber v1 honored, not erased; cluster sources rebuilt cleanly, not moved as test artifacts
  • Canonical tracker stays in sync — every substantive move folds into this file at session boundaries
  • Commit-and-push checkpoints before any phase that modifies the ARC repo

Status

  • Plan drafted 2026-04-26 evening; awaiting execution authorization.
  • Steward authorized commit-and-push of memory state before Phase 0 audit launch (for safety / rollback).
  • Phase 0 (audit) is the next concrete move once commit lands.

2026-04-26 evening — Phase 0 audit results (Explore agent, complete)

Scope: ARC repo at /Users/davidglidden/_Dev/animal-davidglidden-eu. Read-only inventory + cross-reference against site.hs / templates / navigation.yaml / content / CLAUDE.md deprecations.

Findings: repo has ~79 top-level files + 30+ subdirectories. Not broken; live site builds and deploys. ~15–20% of namespace is candidate-for-archive-or-deletion.

SAFE-IMMEDIATE deletes (zero risk)

  • Backup files: site.hs.backup, CLAUDE.md.backup, templates/*.backup, templates/*.old
  • Junk: = (empty file), hakyll.log
  • Deprecated session protocol files: SESSION-MEMORY.md, SESSION-REBOOT-STATUS.md, SESSION-SUMMARY.md

ARCHIVE → docs/archive/deprecated/

  • KLISE-TO-ALDINEXXI-RENAME.md (rename complete July 2025; reference history)
  • PASS-2-AND-3-SPECIFICATIONS.md (glyph system Pass 2/3 specs; superseded by vignette §IX)
  • TODO-ALDINEXXI.md (dated 2025-07-05; outdated priorities)
  • VISION-RECOVERY-SESSION.md (July 2025 recovery session artifact)
  • chamber-examination-glimpse-titles.md + chamber-glyph-borders-prompt.md (LLM artifacts; no references)
  • palette-test.html, test-archetype-detection.html (dev artifacts; not linked)
  • acerplex-exec.sh (legacy deploy script)

DIRECTORY DELETES (CLAUDE.md already names as deprecated)

  • docs/Unified Consciousness Engine planning/ — 7 files; "parked July 2025; superseded by AldineXXI v2.0" (CLAUDE.md L192)
  • docs/knowledge-system/ideation/, docs/knowledge-system/sessions/ — deprecated session protocol (L191)
  • docs/system/session-logs/ — deprecated session protocol (L191)
  • tools/glimpse-processing/venv/ — virtualenv detritus (~100+ files; should not be in source control)
  • encoding-issues/ — 8 old image-description files (2002–2003 dated); orphaned

HOLD — do not remove yet

  • assets/js/glyphs/ — ACTIVE in templates/default.html:126-129 + post.html:17-36. Marked superseded by Vignette per AldineXXI §IX (CLAUDE.md L193) but vignette renderer integration is pending. Quarantine when vignette lands — this is exactly the Phase 1 prerequisite for glyph removal.
  • scss/AldineXXI/archive-v1/ — old stylesheets; safe to remove when v2 proven stable in production. Not urgent.

PRESERVE FOR V1 ARCHIVE (Phase 2)

  • chamber-sessions-private/ — 55 files of raw session transcripts (2025-06-17 Ethics of the Reply with three protocol branches; 2025-07-01 Marginalia standard protocol; additional sessions). The canonical material for the Chamber v1 browsable archive. Phase 2 work will organize into a structured archive (probably docs/archive/chamber-v1-sessions/ with README and navigation).
  • docs/archive/chamber-voices/ — 4 files (alexander, fusus, ngana-kulintja, index, README). Already intentionally preserved 2026-04-18 for source-aware Chamber reimplementation.

Cross-reference findings (verified)

  • ✓ Chamber voices archive 2026-04-18 confirmed (docs/archive/chamber-voices/ exists; no longer in content/chamber/voices/)
  • ✓ assets/js/glyphs/ active references confirmed (templates/default.html + post.html)
  • ✓ Zero UCE/CIE references in active code paths (only in docs/Unified Consciousness Engine planning/ which is itself deprecated)
  • ✓ Zero Klise references in active code (rename complete)
  • ✓ All content/ class: values match the locked 14-type catalogue (no orphan classifications)
  • Note: top-level chamber/ directory has 6 .md files NOT referenced by site.hs — likely legacy; verify before action

STEWARD DECISIONS NEEDED (audit could not resolve)

  1. Python content tools — create-glimpse.py (165 lines), create-photo-essay.py (242 lines), observation-formatter.py (213 lines). NOT in Makefile, not referenced from site.hs. Still manually invoked at content creation time? Keep · archive · delete?
  2. backup-incomplete/ — 4 files in incomplete-backup structure; appears mid-migration. Investigate before deleting?
  3. tools/Calibre MD output plugin/, tools/typographic formatter/ — utility tools. Still used? Document or archive.
  4. canonical-map.md, tags.md — Chamber inventory + tag reference. Maintained or static? If static, status?
  5. docs/internal/, docs/foundation/, docs/semantic-audit/, docs/technical/ — purpose unclear from inventory. Per-directory review.
  6. content/archive/December 22nd 2023.md — orphaned content (not routed). Per 2026-04-21 corpus audit this was the duplicate of posts/2023-12-22.md. Resolve as part of Phase 5 corpus reclassification.

Recommended cleanup sequence (post audit)

Audit-derived ordering, distinct from the original Phase 0–5 plan numbering — these are sub-batches within Phase 5:

  • Batch A (zero-risk): SAFE-IMMEDIATE deletes (backups, =, hakyll.log, deprecated SESSION-*.md). Single commit.
  • Batch B (archive moves): Top-level deprecated .md/.html/.sh files → docs/archive/deprecated/. Single commit.
  • Batch C (deprecated directories): UCE planning, knowledge-system/ideation+sessions, system/session-logs, encoding-issues, venv detritus. Single commit.
  • Batch D (steward investigations resolved): Python tools, backup-incomplete, tools/* subdirs, mystery docs/ folders. After steward decisions land.
  • Batch E (build hygiene): Verify .gitignore covers _cache/, _site/, _staging/, .stack-work/, node_modules/, .sass-cache/, .wrangler/. Run make clean.
  • Phase 2 (separate work): Chamber v1 archive build-out from chamber-sessions-private/. Design + execution as its own focused session(s).

Audit artifact

Full audit report (with file-by-file evidence) is in this session's transcript. The summary above is the canonical record going forward; full report retrievable via session transcript if specific evidence needs re-checking.

EXECUTED 2026-04-26 evening — commit 5c059d8

Steward directives (verbatim): "Batch A you can delete. Batches B + C please archive." + per-investigation directives (#1 set-aside-for-skills, #2 delete, #3 like #1, #4 don't know, #5 assemble in single review directory, #6 delete).

Commit 5c059d8 on origin/main (also pushed to github-backup): 118 files changed, 42 insertions(+), 2540 deletions(-). Pre-commit hooks passed. ARC origin (https://git.skemantix.com) accepted the push — note: ARC uses HTTPS not SSH so unaffected by the dotfiles gitea SSH port-22 timeout.

What landed:

  • Batch A — 9 file deletes (=, hakyll.log, two .backup, three SESSION-*.md, two template backups)
  • Batch B — 9 top-level files moved to docs/archive/deprecated/
  • Batch C — 5 directories moved/renamed under docs/archive/deprecated/ (uce-planning, knowledge-system-ideation, knowledge-system-sessions, system-session-logs, encoding-issues)
  • Investigation 1 + 3 — 6 tools moved to tools/set-aside-for-skills-analysis-2026-04-26/ (3 top-level Python tools + Calibre plugin + typographic formatter + glimpse-processing whole dir; ~6300 untracked venv files came along)
  • Investigation 2 — backup-incomplete/ deleted (3 files)
  • Investigation 5 — 4 mystery docs/ subdirs (internal/, foundation/, semantic-audit/, technical/) moved to docs/review-2026-04-26/
  • Investigation 6 — content/archive/December 22nd 2023.md deleted (duplicate per 2026-04-21 corpus audit); content/archive/ directory removed (now empty)
  • 3 README.md files added at archive destinations explaining provenance + status

Investigation 4 (canonical-map.md, tags.md) — left untouched per steward "don't know."

Items NOT touched in cleanup (still pending future decisions)

  • assets/js/glyphs/ — ACTIVE in templates; quarantine when vignette renderer integration lands
  • scss/AldineXXI/archive-v1/ — safe to remove when v2 proven stable; not urgent
  • Top-level chamber/ directory (6 .md files unreferenced by site.hs) — audit flag, not in this batch
  • chamber-sessions-private/ — Phase 2 archive material; preserve
  • docs/archive/chamber-voices/ — intentionally preserved 2026-04-18
  • .DS_Store modifications in docs/AldineXXI-Codex/ and tools/ — cosmetic; left for separate .gitignore decision
  • canonical-map.md, tags.md — investigation #4, left per steward "don't know"
  • dev/, funding/ directories — audit found these may be active; not in this batch

Phase 0 status: COMPLETE

Next: Phase 1 (production stack for /lex/) and/or Phase 2 (Chamber v1 archive design + execution) per steward's direction. The four verification checks for Phase 1 still stand:

  1. §XII Sidenotes production CSS state
  2. site.hs Shape-A YAML extraction step state
  3. Hic-apparatus retrofit scope
  4. URL shape for /lex/

Phase 2 design questions still open per the prior Integration C section.


2026-04-26 evening — Vignette system readiness scope (separate thread from /lex/ Phase 1)

Steward verbatim (asked while heading to a concert in 30 min): "want to have an idea of what it will take to build the vignette system (seeing the old glyph system there makes me want to move ahead, but I know that we're probably not ready yet)"

Status: Spec jurist-approved 2026-04-13 (docs/AldineXXI-Codex/vignette-specification.md); marked "Ready for Phase 1 implementation." Has been queued for ~2 weeks; nothing structural blocking. Steward attention is the bottleneck — has rightly been on lex-method + About-page architecture.

Three components (per spec Part II), ~500–600 lines total across three independent pieces:

  1. Generation script (~100 lines Python/Node) — reads markdown, calls local Ollama (Qwen 3 8B current; 32B when hardware permits), writes sidecar .vignette.json. Manual run before publish. Steward review + edit mandatory before commit.
  2. Hakyll compiler extension (~30 lines added to site.hs) — loads sidecar JSON, injects as <script type="application/json"> block.
  3. Frontend renderer (~300–400 lines JS, no dependencies) — Canvas (ground mark + field) + SVG (geometry) + breath animation. Replaces assets/js/glyphs/ entirely when live.

The real budget item — Phase 1 jurist gate: spec is explicit (Appendix line 330): "The question to ask is not 'does it work' but 'does it dwell.'" Qualitative judgment; cannot be shortcut. Phase 1 may land in one focused session or need 2–3 iterations.

Effort estimate: 4–6 focused sessions over 1–2 weeks if a session every couple of days. Phase 1 (renderer prototype) is the variable; Phase 2 (generation script, ~one session for system-prompt tuning) and Phase 3 (Hakyll integration, smaller) move faster once Phase 1 lands. Phase 4 (glyph quarantine) is bookkeeping.

Not blocking:

  • L1/CapableMind — explicitly decoupled per spec (Ollama-local for sustainability)
  • Hakyll/build infrastructure — working
  • Spec design — locked
  • Existing public /vignette/ page (may need minor alignment, low effort)

Glyph quarantine timing: Do NOT remove assets/js/glyphs/ until vignette renderer is live and page-level swap is verified. Premature removal would break the live site (templates currently import renderers/index.js and triptych-renderer.js per audit).

Steward instinct verified: "not ready yet" is right for a 30-minute window before a concert, not in general. Phase 1 wants a clear evening with no time pressure — it's hands-on iteration on a qualitative gate.

Disposition: queued; not yet on the active workstream calendar. Picks up when steward has the focused session-block for Phase 1.

LOCKED 2026-04-26 evening — vignette engine: dialogue, not script

Steward proposal (verbatim): "I couldn't share the text to analyze with you and then pass also to the jurist for a second opinion (rather than api calls)?" + "Please take note of all of this, yes."

Decision: vignette genome generation happens in dialogue (Claude Code session) with optional jurist second-opinion (Claude.app), not via a programmatic generation script. The spec's downstream contract (sidecar .vignette.json → Hakyll compiler → frontend renderer) is unchanged.

Why this is structurally cleaner:

  • The spec already mandates steward review of every genome — the dialogue approach makes review continuous (watch the analysis, redirect mid-flow, see reasoning visible) rather than generate-then-review in two passes
  • Same registrar-in-dialogue pattern as the lex-method. Executor gathers what's noticed (organizing logic, element vocabulary, field behavior, breath phase) → steward recognizes / refines → jurist second-opinion if wanted → commit. Identical posture.
  • Jurist second-opinion is native, not a built-in hook. Three-party model (executor / jurist / steward) operates as designed.
  • Steward review register matches the working method that has produced the rest of ARC.

Implementation scope reduces:

  • 3 components → 2 components
  • ~500–600 lines → ~330–430 lines
  • DROP: generation script (~100–120 lines + API key management)
  • KEEP: Hakyll compiler extension (~30 lines added to site.hs); frontend renderer (~300–400 lines JS)

Workflow when implemented:

  1. New essay/meditation ready for vignette
  2. Share text in a Claude Code session
  3. Executor produces draft genome with reasoning visible (not just JSON — the why of each field)
  4. Optional: jurist (Claude.app) second-opinion
  5. Steward edits/accepts
  6. Write to content/posts/<file>.vignette.json
  7. Hakyll picks it up at build

Effort estimate revised: 3–5 focused sessions over 1–2 weeks (was 4–6). Phase 1 jurist gate ("does it dwell?") still the variable; Phase 2 collapses into "produce one genome together to test the whole loop."

Long-term commitment unchanged: eventual swap to local 32B Ollama remains the spec's destination (sustainability + L1-independence framing). Training-pair corpus for that swap accumulates naturally as committed genome.json files regardless of how each was produced. The dialogue approach is interim by the same logic — but a much better interim than 8B local + script.

Spec amendment owed: when Phase 1 begins, fold this into the vignette-specification.md Part II as a clarification — engine-swap path includes "executor-in-dialogue" as a current valid implementation, not just CapableMind-pending or local-Ollama.


Tomorrow's plan (drafted 2026-04-26 evening, post-concert)

Steward addition (verbatim): "Can we also add deciding on names for the lex cluster(s), AldineXXI or framework, &c? We've been using names, but now that we will publish these should be truly established."

Naming pulled to the front of tomorrow because URL shape and door names ripple into everything downstream (Hakyll routing, cluster-source frontmatter, cross-page linking).

Sequence

  1. Naming session (~30–45 min, morning) — settle the open names below. Steward names; executor surfaces options + what each name would inherit (registers, precedents, what each invokes). Per "naming becomes inheritance" (steward verbatim 2026-04-25).

  2. Phase 1 verification checks (~15–20 min, after naming) — what's already built in the production stack. Three checks remaining (URL shape resolved in #1):

    • assets/css/sidenotes.css state — production CSS for §XII?
    • site.hs Shape-A YAML extraction step — designed but built?
    • Hic-apparatus retrofit scope — grep -L 'location:' count of existing posts
  3. Branch A/B/C based on Phase 1 findings:

    • A — gaps in production stack: executor implements (CSS, extraction, routing) while steward does other things. End of day: stack ready; cluster rebuild next session.
    • B — stack mostly built: clean rebuild of posture cluster from locked recognitions (executor-as-registrar; steward reviews). Aim: posture published end of day.
    • C — pivot to Phase 2: Chamber v1 archive design conversation — URL shape, navigation, qualifying frame, notation preservation, linkability. Six open questions per Integration C above.
  4. Optional later: docs/review-2026-04-26/ walkthrough (4 dirs; per-directory disposition; 30–60 min depending on depth).

Open naming questions for the session

Door names (8-door enfilade) — what publishes:

  • Lex door: Lex / Reading Room / Sheaves / other? URL pattern?
  • Framework door: Framework / AldineXXI / AldineXXI Framework / Typography & Framework / other? (Codex stays at docs/AldineXXI-Codex/ regardless; this is public-facing register.)
  • Attention door: confirm or revisit?
  • Colophon · Vignette · Chamber · Tools · Now: appear settled; quick "still right?" check
  • Bio: keep, rename, or fold differently?

Per-cluster page titles (publication-ready):

  • Posture cluster: Posture / On the Posture of the Editor / fuller?
  • Marks cluster: Marks / On the Marks / fuller?
  • Six remaining clusters: same treatment when each reaches publication

Cluster URLs: depend on door name (e.g., /lex/posture/, /lex/marks/)

Other open items the lex-emergence touched:

  • /dwellings/ — validated 2026-04-21 as cluster page name for Meditation+Reverie. Still right after lex-emergence?
  • About-page section headings: Colophon + Adsum confirmed 2026-04-19; does the threshold-hic opening section get its own heading or remain page-top untitled?

Deferrable until Phase 2 design (don't block tomorrow on this):

  • Chamber v1 archive name (for the browsable-archive design conversation)

NOT proposed for tomorrow (require energy steward may not have post-concert)

  • Threshold-hic + Adsum compositions — Phase 4; want clear mind, not recovery day
  • Vignette Phase 1 prototype — wants a clear evening; tomorrow may or may not be that

Posture commitments (carry into tomorrow)

  • Steward composes; executor is registrar (gathers material, surfaces options, drafts on authorization, registers cleanly)
  • Naming is steward territory; executor does NOT propose names — gathers + names what each invokes
  • Pre-execution checkpoint commits before any phase that modifies the ARC repo (per existing safety pattern; this happened today with 5c059d8)

Status

Plan drafted 2026-04-26 evening. Ready for steward when he wakes tomorrow.

Added at session-close (2026-04-26 evening) — discipline-design adjacency

Steward verbatim end-of-day: "maybe we should also find a moment to morrow to design a mid-session protocol as you had mentioned--and revisit the wake-up wrap-up skils again to see if we can tweak them further. Thanks for today in spite of the drift--we are learning how better to help eah other help each other every day. good night"

Added as adjacent items for tomorrow (may or may not land depending on time/energy):

  • Mid-session protocol design — write the discipline that the MemPalace step-2 + canonical-tracker work surfaced today. Per feedback-mempalace-protocol-step-2-discipline.md and feedback-canonical-workstream-tracker-discipline.md, two disciplines exist at boundary-vs-mid-session scales. Tomorrow's possible scope: shape a concrete mid-session protocol (when to query, what to query, how to record what was checked) that an executor can follow without steward prompting. Likely a small artifact — checklist + triggering events + exemplars.
  • /wake-up and /wrap-up skill revisit — both skills have proposed amendments in the two feedback memories saved today. Tomorrow could be the moment to tweak them in ~/.claude/skills/wake-up/ and ~/.claude/skills/wrap-up/. Touches the harness directly, so deliberate change with steward sign-off per amendment.

Posture: these are discipline-as-design work. Not blocking anything. Slot in if a window opens between naming + Phase 1 verification + cleanup work. The steward's framing — "we are learning how better to help each other help each other every day" — operates the trust-contract bidirectionality from 2026-04-25 (drift-pattern tracking IS the discipline; bidirectional trust). Today's drift surfaced; the discipline-design is the cycle of amelioration in operation.

Today closes warmly: three durable feedback memories saved (catalogues-stale, canonical-workstream-tracker discipline, MemPalace step-2 discipline), three architectural locks landed (Path 1, Adsum-vs-threshold-hic, sibling integration), Phase 0 cleanup pushed cleanly, vignette engine clarified as dialogue, tomorrow's plan ready with naming first plus discipline-design adjacency.


2026-04-27 — The day the about-enfilade went emergent

Headline: A long substantive day. Morning naming session locked the 8-door slate via Harrison Ch 3 What Is a House?. Alexander's Timeless Way validated architecture against form-content unity. Branch A (production stack) completed pending content; data/lexica/ archived (UCE-CIE retirement); Manutius the Younger ABBYY-converted. Branch B Step 1.5 pivoted from declared to emergent for about-enfilade after steward's "Would Alexander do it like this?" caught the bulk-rewrite instinct — pages declare themselves; navigation gathers via getMatches+getMetadata. By session end the 8-door enfilade was live in emergent form, breadcrumbs consistent, stubs holding the steward-composition pieces. Five Symmetria returns. Steward verbatim at session-end: "And congratulations on reading project-arc-rework.md when we started. I think it grounded the day."

2026-04-27 morning — Wake test passed

The canonical-tracker discipline saved 2026-04-26 was tested on its first morning. /wake-up surfaced this file without steward prompting. Discipline operative on first test, not just on paper. Saved durably as KG fact (canonical-tracker-discipline-operative-and-grounding-2026-04-27). Steward confirmed at end of day that reading this file grounded the work.

2026-04-27 morning — Naming session: the 8-door slate filled

Steward opened: "Names. We have hic and adsum for about. The lex is the verb of what we're doing with the clusters, but is that the best way to name them. It is a lexification in the harrisonian sense of course, but I wonder what he would likely call this? And Warburg?"

Surfaced Harrison and Warburg vocabularies; steward reframed: "Are these my local dieties that bless my house? Would chapter three of Dominion point us on the right direction?" Read Harrison Dominion of the Dead Ch 3 What Is a House? directly — laral frame surfaced (Lares, Penates, cassa armonica, liber, Rilke's laral value).

Steward locked Lares (formative voices, living + dead — confirmed over Manes which would be only-dead): "It is the record of those influences–not all dead mind you (fortunately, the world will be a lonely place when they are gone)–maybe Liber lares?"

Naming path: Lex → Liber Lares → The Hearth—Liber Larium → The Hearth. Steward self-named the over-decorating-as-proving pattern: "Maybe that's too much and the Hearth suffices. My deep fear of foolishness always wants to try too hard and prove too much." Saved as feedback-over-decorating-as-proving.md.

8-door slate LOCKED:

  • Colophon — /colophon/ (held; lex-method-shaped already)
  • Hearth — /lares/ (lex cluster door; URL keeps Latin; door keeps Saxon-near)
  • AldineXXI — /aldine-xxi/ (kept name; later shortened from "AldineXXI Framework" to just "AldineXXI")
  • The Vignette — /vignette/
  • Attention — /attention/ (door label; page title preserved as long question form via enfilade-name override)
  • The Chamber — /chamber/ (v2 stub authored; v1 landings archived)
  • Tools & Process — /tools/
  • Now — /now/
  • Bio — quiet link via Adsum (forthcoming); not in main row

Per-cluster page titles LOCKED: On the Posture of the Editor (/lares/posture/) + On the Marks (/lares/marks/). Form pattern: On the [X] / On the [X] of [Y] (essayistic, registrar-humility, after Montaigne / Bacon / Stevens).

About-page composition LOCKED: body-prose + small-caps marginalia at register turns. Steward verbatim: "I like your read, prose and margin whispers in small caps." No headings (Tex Avery joke caught the "THRESHOLD" anti-pattern). Form follows medieval rubric tradition into Aldine italic register-set into AldineXXI small-caps marginalia — source-verified from Bringhurst + Lupton.

§XII.b Register Markers LOCKED as separate apparatus from §XII Sidenotes (Path C, not §XII exception). Distinct speech-act (threshold-naming vs recognition-of-voice); left margin; small caps; rubric lineage cited.

2026-04-27 midday — Alexander/Timeless Way architectural review

Steward provided source PDF; review run against actual headnotes + Ch 1 opening + Ch 8 haunting-sadness close + Ch 9 The Flower and the Seed in full. Form-content unity verified at deepest level: Alexander explicitly tells the reader to read italic headnotes first; ARC's About-page composition decision (body-prose + marginalia) independently arrived at the same form.

All morning's structural decisions tested against the four loads (life as criterion, generation not making, autonomy + code, the haunting sadness) — all passed structurally.

Steward closing formulation, saved as durable testing-frame: "the structure encourages the visitor to explore, to dwell. That the visitor is not overly guided, but sufficiently oriented." This phrase becomes the test for any future ARC architectural decision.

Kernel temper: Alexander's Ch 27 — language is scaffolding; quality survives the gate. Architectural review confirms morning's decisions are necessary but not sufficient; the work breathes only when the writing breathes.

Five typography reads added to ARC open tasks (Tschichold Form of the Book, Ruder Structure, Fleishman Six Centuries, Manutius the Younger — alternate ABBYY converted today, Gill Essay on Typography — added by steward 10:52). Timeless Way MD conversion flagged as soon-task (530-page scanned PDF needs OCR).

User memory saved: user-formative-teachers-alexander-timeless-way.md (form-content unity as standard).

2026-04-27 afternoon — Branch A complete-pending-content (Option C)

Phase 1 verification confirmed gaps: §XII Sidenotes CSS not built, site.hs Shape-A YAML extraction not built, 14/69 posts missing location: field. Steward chose Option C — declare executor work complete, queue site.hs extraction for Branch B against actual content.

Deliverables:

  • §XII.b spec section inserted (AldineXXI-specification.md line 517+)
  • scss/AldineXXI/_sidenotes.scss written (~280 lines)
  • @import "AldineXXI/sidenotes"; added to main.scss
  • Polyphonic marginalia retired — §XI subsection replaced with archival note; _marginalia.scss preserved at archive-v1/. Steward correction caught my rm mistake; saved as feedback-preserve-dont-delete-when-retiring.md.
  • data/lexica/ archived (UCE-CIE retirement) — files moved to data/archive-v1/lexica/; compile-lexica.js moved to scripts/archive-v1/; Makefile target retired; package.json scripts removed; spec doc paths updated; README authored. Steward post-edit: "the vignette spec didn't depend on any of that anyway" → README softened to historical-record-only framing.
  • Manutius the Younger ABBYY-converted (104K, 126 pages of readable Renaissance Latin); chamber-library file replaced; conversion script preserved at /tmp/abbyy_to_md.py.

2026-04-27 afternoon — Branch B Step 1 mechanical wiring

content/lares/ directory created; content/lares/posture.md + content/lares/marks.md stubs with class: lex frontmatter; templates/lex.html minimal wrapper; site.hs match rule for content/lares/<slug>.md → /lares/<slug>/.

2026-04-27 afternoon — Branch B Step 1.5: emergent pivot

Initially proposed about-enfilade as declared (option 2, data-driven via navigation.yaml). Started executing with bulk YAML rewrite — steward denied: "Would Alexander do it like this?"

The denial caught two errors at once: (a) bulk-scaffold action was the cramped will of the maker (Alexander Ch 9, Flower and the Seed) — diagnostic for not-the-Way; (b) category error — about-enfilade entries are pages-in-themselves, so the underlying nature wants emergent (option 3), not declared (option 2). Saved as durable feedback feedback-would-alexander-do-it-test.md. Steward second catch: "number 10 in the enfilade? wouldn't it be 1 or 2?" (engineering "leave gaps" instinct caught) — folded into the same feedback as the count-from-1 extension.

Pivoted to emergent. Each about-page declares enfilade: about + enfilade-order: N in frontmatter. Hakyll gathers via getMatches + getMetadata (no compile cycle — the cycle was the first build error, caught and fixed). Saved as KG architectural pattern: navigation surfaces don't need compiled bodies, only metadata + routes.

Per-page sweep deliverables:

  • 6 about-pages flagged with enfilade: about + ordered frontmatter: Colophon (1), AldineXXI (3), Vignette (4), Attention (5; with enfilade-name: "Attention" override preserving long question-form title as page H1), Tools (7), Now (8); orders 2 (Hearth) + 6 (Chamber) reserved.
  • Hardcoded <nav class="about-enfilade"> blocks removed from colophon, attention-page, tools, now-page (aldine-xxi + vignette didn't have them).
  • Body-text /typography/ → /aldine-xxi/ updates in colophon, about, tools, docs/tools-process-guide.
  • typography.md folded into aldine-xxi.md as new "The Experience" section (lossless merge; transitional note marks pending unified rewrite); typography.md archived to docs/archive/merged/.
  • patterns-page.md + influences-page.md + navigation-philosophy.md archived to docs/archive/merged/ (per morning's locks).
  • council-page-public.md (steward identified: "Ah, the council-page-public is the chamber landing page") + content/chamber/index.md (v1 content) → docs/archive/chamber-v1/ with provenance README.
  • v2 chamber stub authored at content/chamber/index.md.
  • Hearth stub authored at content/lares/index.md (steward will compose properly in dialogue).

2026-04-27 evening — Template architecture consolidation

Steward observations after viewing deployed site surfaced inconsistencies:

  • Breadcrumb only on Colophon and Vignette (other about-pages missing) — those pages had class: essay + date so were routing through post.html with its essays-pointing breadcrumb (wrong destination for about-pages)
  • Hearth title doubled (lex template H1 + body H1)
  • Attention page missing title entirely (default.html doesn't render title; body had no H1)
  • AldineXXI title doubled (same shape as Hearth)
  • "the
    problem is only the separation to the footer"
    — deferred to cul-de-bouteille design

Architectural fix: about-pages are their own kind of page; they deserve their own template.

  • templates/about-page.html created — minimal: breadcrumb (About → [Page]) + <h1 class="about-title"> + body. No essays-breadcrumb; no glyph-sigil; no dateline.
  • Breadcrumb in lex.html with conditional: Hearth shows About → Hearth; lex clusters show About → Hearth → [Page]. Uses enfilade-name override.
  • Chamber routes through about-page.html for index — site.hs chamber match rule's else-branch checks hasAboutEnfilade.
  • Body H1 duplications removed from Hearth, AldineXXI, Chamber stubs (templates provide H1).
  • aboutEnfiladeCtx pattern broadened to scan content/pages/*.md (excl docs) ∪ content/chamber/index.md ∪ content/lares/index.md.

Steward composition territory clarified: "Hearth and the about hic and adsum I will want to compose in dialogue as ever." — three pieces explicitly steward-led, in dialogue with executor as registrar.

2026-04-27 — Steward locks (consolidated)

  • 8-door enfilade SLATE: Colophon · Hearth · AldineXXI · Vignette · Attention · Chamber · Tools · Now (+ Bio quiet link)
  • About-enfilade architecture: emergent (option 3) — pages declare themselves; gathering via getMatches/getMetadata
  • Reading Compass: declared (separate cleanup deferred — make navigation.yaml canonical for sigils; spec doc to reference)
  • §XII.b Register Markers: separate apparatus (Path C); rubric lineage source-verified
  • About-page composition form: body-prose + small-caps marginalia; no headings
  • Cluster page title form: On the [X]
  • Counted from 1, not from 10 (engineering "leave gaps" anti-pattern caught)
  • Preserve-don't-delete when retiring (archival with provenance)
  • ARC territory: steward + Claude Code only (no Seb)
  • Branch A complete-pending-content per Option C
  • chamber-v1 archive at docs/archive/chamber-v1/
  • Lares structure stays at /content/lares/ (parallel to /content/chamber/; both non-pages content kinds)
  • Section-uniform breadcrumb pattern (not per-page emergent; section parent is uniform)

2026-04-27 — Six durable memories saved

  • feedback-would-alexander-do-it-test.md (with count-from-1 extension)
  • feedback-preserve-dont-delete-when-retiring.md
  • feedback-arc-territory-steward-and-claude-code-only.md
  • feedback-over-decorating-as-proving.md
  • feedback-canonical-workstream-tracker-discipline.md (existing, confirmed durably operative)
  • user-formative-teachers-alexander-timeless-way.md (form-content unity standard)
  • project-future-analytical-laffoley-and-warburg.md (writing projects, not glyph pipeline)

2026-04-27 — Pulling thread for next session

The composition-in-dialogue trio: Hearth landing prose + About Hic prose + About Adsum prose. These three pieces are the keystones today's architectural work has been preparing the conditions for. Forms locked. Templates built. Doors wired. Stubs hold space. What remains is the writing itself — and the writing is steward-led, in dialogue with executor as registrar.

The architectural framework that validated the structure today (Alexander's form-content unity) is the same framework against which the prose will be tested tomorrow.

2026-04-27 — Decisions explicitly NOT made

  • Hearth landing prose — steward composition territory; will compose in dialogue
  • About Hic + Adsum prose — same; held for dialogue
  • Lex cluster registrar transcription (Posture + Marks) — Branch B Step 2/3; queued; recognitions LOCKED in this tracker
  • site.hs Shape-A YAML extraction step — Option C for Branch A; queued for Branch B against real content
  • hr-to-footer transition — deferred to cul-de-bouteille design session per steward verbatim "this might be better treated when we design the cul-de-bouteille and see whether there is room for a line separator that is not fullscreen"
  • Current-page indicator within enfilade — left out per Alexander's "let need surface before adding" posture
  • Class-field reconciliation across about-pages — separate pass with broader content-typology reconciliation
  • Reading Compass YAML-canonical-for-sigils — separate later pass
  • Final archive consolidation — "once the general work on the site is done"
  • Bio link from Adsum — needs Adsum composition first
  • Five typography reads — added; soon-tasks; substrate for AldineXXI gap-audit
  • Timeless Way MD conversion — substantial OCR work; its own focused session

Status at session close

Site live and deployed. Multiple builds clean throughout the day. Steward closed: "Let's wrap-up it's been an excellent day".


2026-05-06 — Apparatus consolidation: universal dateline + photo apparatus + three containment patterns

9 days of intervening sessions (2026-04-28 through 2026-05-05) recorded in their own session memories — this entry resumes the rework log after that gap. Major work in those days included publication of After the Reply (5 essays), Hearth/Hic/Adsum composition trio shipped, body-block apparatus invented, SCSS audit, chamber substrate recovered + chamber door composed, and Death of a Hero published with the first individual-essay Sources block.

Apparatus question opened by steward observation

The dateline alignment was visibly inconsistent across pieces (sometimes centered, sometimes left, never aligned to anything visible). The investigation expanded to cover the full apparatus architecture — universal dateline, photo apparatus for image-primary types, vessel containment patterns.

Spec foundation locked (commit e42ae0c)

Three architectural updates per chavruta with Müller-Brockmann (Grid Systems, just mined) + Tufte (Beautiful Evidence) + Bringhurst (Elements §1.2.3):

Universal dateline — every content type now carries a dateline, including glimpses and photo essays. Format: City, Country, Day Month Year.

  • Country always included — half-located is a lapse, ARC's globally-read content cannot assume readers carry "Wien=Austria"
  • Local form preserved within country (Wien not Vienna; Sevilla not Seville)
  • Day included — names a day, not a month

Three containment patterns:

  • Text-primary (essay, meditation, observation, fragment, chamber, lex, about): vessel applies — three-lane structure (left margin = register marks; body = body+dateline+sources; right margin = sidenotes)
  • Photo essay: vessel + .full-bleed image breakout; caption block at end of piece
  • Glimpse: no vessel; image at full register; caption beneath; dateline at piece end

Caption (photo apparatus) — glimpse + photo-essay only. Italic, subordinate, baseline-aligned (Müller-Brockmann). Content: technical EXIF (ƒ-stop · shutter · focal length) + austere subject identification when needed for comprehension. Position: beneath image (glimpse) or end of piece (photo essay, per MB's authorized variant). The test: helps viewer SEE, never tells them what to think.

Boundary rule: if image's comprehension needs more than austere caption identification, the work is not a glimpse — reclassify to meditation or essay.

Container class name: .bears-apparatus proposed (role-named, replacing .has-margins) — not yet implemented.

Implementation status

Done today:

  • Spec consolidation (commit e42ae0c)
  • Dateline alignment fix in SCSS (commit 137ddd1) — removed margin-auto + max-width centering hack from .dateline. On grid pages now aligns body-column-left via existing > * rule. On non-grid pages, dateline takes natural article width (no longer self-centers).
  • §XII Sidenotes earlier same day (commits f1a229d, 47663a1, f4716e6) — consolidation + chamber marker-anchored conversion + Pass 1 elegance audit.
  • Sources spec correction (commits d69bbbd, 3d96449) — three-em rule per Bringhurst/Harrison.
  • ARC CLAUDE.md make rebuild rule extended for SCSS partial edits (commit 48967a6).

Detailed apparatus refactor todo: see project-arc-apparatus-refactor-todo-2026-05-06.md.

Steward-provided location data for content audit

When the content audit pass executes, use these canonical locations (steward-provided 2026-05-06):

Essays:

  • The Death of a Hero: Seoul, Korea
  • The Discovery of Matthieu Taliesin: Barcelona, Spain
  • From Mushi-Ken to Morra – The Ritual of Choosing: Barcelona, Spain
  • Vespers for the living: Cremona, Italy

(After the Reply essays already carry locations: Wien, Barcelona, etc. — verify against new format with country.)

Observations:

  • All Paris, France
  • Exception: 2024-01-11 → Chez Bourny, Champagnat, France

Glimpses:

  • Locations to be extrapolated from titles (steward's note: titles already encode the location)

Remaining apparatus refactor work — tiered

Tier 1 — bounded SCSS + template (~1-2h, ready):

  • .has-margins → .bears-apparatus rename (SCSS + spec + templates)
  • Templates apply bears-apparatus class based on content class (probably via site.hs context variable: bears_apparatus = class != "glimpse" && class != "photo-essay")
  • Extend §XII grid scope to observation/meditation/fragment (automatic once templates apply .bears-apparatus)
  • Visual change for those types: body-column-width instead of full-page-content-width — verify acceptable

Tier 2 — content audit (~30-60min once tooling ready):

  • Add location: frontmatter to all text posts that lack it (using the location data above)
  • Reformat existing datelines to new spec form (City, Country, Day Month Year)
  • Update post.html template to render dateline canonically with Day component

Tier 3 — EXIF integration (investigation needed before scoping):

  • Investigate EXIF reading at Hakyll build time (exiftool preprocess emitting JSON → Hakyll context, OR Haskell library, OR manual frontmatter)
  • Need: f-stop, shutter speed, focal length per image
  • Caption template: glimpse beneath image; photo essay end-of-piece block

Tier 4 — verification (after each tier).

Open spec questions (to lock with first instance)

  • Glimpse dateline alignment without vessel: image-left vs page-equivalent-of-body-column-left
  • ISO inclusion in caption EXIF: judgement call (currently default exclude)
  • Photo essay end-of-piece block name: "Image apparatus" tentative

Cross-references for next session

  • project-arc-apparatus-refactor-todo-2026-05-06.md — full tier-by-tier plan
  • feedback-fittingness-as-refactor-test.md — elegance-as-fittingness test for any refactor pass
  • feedback-deploy-is-not-commit.md — discipline against the structural-counter-as-health-signal pattern at the editorial layer
  • project-chavruta-skill-parked-2026-05-06.md — the deferred skill that, if built, would streamline future apparatus consultations
  • user-english-usage-european-fowler.md — editorial register frame

2026-05-07 — Apparatus refactor Tier 1+2 + Phase D bulk glimpses (143) + dandelion pair

Headline: four commits + a fourth. Corpus jumped from ~73 posts to ~218. Apparatus refactor Tier 1 landed (bears-apparatus single-rule architecture per steward pivot from hardcoded-in-templates); Tier 2 location frontmatter audit (63 files) committed; Phase D bulk processing of 143 new glimpses (GPS reverse-geocoded via Nominatim, EXIF via exiftool, image compression to 2000px); paired dandelion pieces shipped — Observation "Dandelions" + Fragment "Dandelion" (first live Fragment exemplar). Pulling thread by session-close: code-shape audit (multiple instances accumulated today; steward authorized explicitly).

Commits

  • e2fb14c — Tier 1 bears-apparatus refactor + glimpse no-vessel fix + dateline-centered alignment locked with sources in spec §VII (Bringhurst's coherence principle; Tschichold Form of the Book fig. 18; Müller-Brockmann §1458)
  • 249475b — Tier 2 location frontmatter audit, 63 files normalized to "City, Country" form
  • cc6a551 — Phase D 143-glimpse bulk processing
  • 5f359e3 — Dandelion pair (Cardona, Spain) + .fragment em dark-mode color fix (#555 → var(--gray))

Architectural decisions locked

  • bears-apparatus single-rule architecture. Steward pivot from hardcoded-in-3-templates. bearsApparatusField in site.hs returns "true" for any non-empty class except "glimpse". Shared articleCtx extracted (subsumed 5 inline buildVersion ... seasonalGlyph ... defaultContext chains). All 4 article-shell templates use $if(bears_apparatus)$ bears-apparatus$endif$.
  • Glimpse dateline centered (not body-column-equivalent), locked in spec §VII with sources. Bringhurst's coherence principle: don't mix symmetric and asymmetric apparatus. Glimpse pieces are predominantly symmetric (centered image + caption); dateline follows that register.
  • .post.glimpse .post-content { display: block } — honors spec V.b "no vessel" literally; body-column cell of the 66rem grid is asymmetric (10rem marker + 14rem sidenote); image's full-bleed negative-margin formula needed a centered parent.

Drift patterns named or recurred

  • stale-memory-not-actively-applied (recurred) — claimed typology incomplete based on stale rework-master notes; spec was open and accessible
  • defended-the-spec-against-the-eye (recurred) — claimed glimpse correct based on SCSS analysis; steward's eye caught image-not-full-bleed
  • hardcoding-in-some-templates as small-sample-as-population (new) — implemented bears-apparatus the way I'd implemented similar things, without examining whether the pattern was right for ARC
  • hardcoded-color-not-theme-aware (new) — .fragment em { color: #555 } and .whisper { color: #777 } both break dark mode
  • parallel-mechanism-where-one-rule-fits (new) — multiple instances surfaced; today resolved bears-apparatus + articleCtx + .has-margins consolidation

Pulling thread carried forward

Code-shape audit — multiple instances accumulated today, steward authorized explicitly. First concrete entry: mobile italic-grey diagnostic.


2026-05-08 — AldineXXI spec-completion arc (single-day, ~13h, ~2500 lines new spec)

Headline: What began as the code-shape audit's first concrete entry (mobile italic-grey diagnostic) opened, under steward redirection, into the AldineXXI spec-completion arc. Four-session completion (§I + §II + §III + §VII + Postures) + decision-pass (5 held) + masters' formal reread (13-voice slate + Calvino) + 8-finding reconciliation + 9th finding caught by companion-spec architecture + Group C migrations + Marked 2 template (SCSS-from-spec test passed).

What landed in the spec

§I (Reading-craft micro-completion):

  • §I.h Block Quote — indent-only, no bar, body color, roman by default. Pattern A prose-surrounded; Pattern B explicit attribution in EB Garamond small-caps (revised from initial Plex Mono after masters' reread).
  • §I.i Detail Typography — hyphenation/justification (ragged-right unhyphenated), widows/orphans, small-caps usage rules with reserved-specificity, tracking-by-size.
  • §I.d additions — italic emphasis dyad ("one mark, multiple loads"); bold as governed exception (six-condition gate; no current authorized exceptions).

§II (Rhythm/Grid/Proportion):

  • §II.b Rhythm — Two scales model (reading-rhythm leading-derived + layout-grid 8px). Revised from initial "pragmatic compromise" framing per steward review.
  • §II.c Page Grid — five-column grid lifted from §XII apparatus to page foundation; apparatus-mode 54rem / full-mode 66rem.
  • §II.d Page Proportion — per-piece content-driven composition (asymmetric when populated; otherwise symmetric). Revised same-day after second chavruta on "what would Manutius do with the web?" (Aldus left the medieval gloss behind; empty asymmetric grid is the gloss-form rejected).

§III (Publication-as-system):

  • §III.b Accessibility — major finding: :root { font-size: 22/20/21px } overrode browser preference. Replacement: 137.5% / 125% / 131.25%. Plus reduced motion, higher contrast, touch targets, skip-link, semantic landmarks, image alt-text rule, browser-support floor.
  • §III.c Webfont Loading — font-display: swap lock; metric-matched fallbacks per Leatherman.

§VII.e Apparatus Colour — 5-master convergence (Bringhurst §3 + §1.2.3, Tschichold Form of the Book, Hochuli Detail in Typography, Müller-Brockmann §1458, Tufte boundary-case). Form differentiates apparatus, not luminance. .whisper retired; 11 selectors migrate to body colour. §III WCAG audit gained --gray FAIL row.

§VII.f Running Head — scroll-revealed top-band; per-content-type when-applicable; folio-digital held.

§VII.g Site Colophon — paired apparatus to dateline; mixed register; symmetric composition.

Prologue Postures — Doors not feeds, Italic working dyad, For return, Print supported, License CC BY-NC-ND 4.0, Pilgrim posture, Companion specifications subsection.

§XIV — Reading-test protocol (Warde generalised).

Appendix A — Token Index, Appendix B — Selector Index, Appendix C — Decision Tree (Lupton's three pedagogical artifacts).

Appendix D — Companion Spec Index — tabulated.

Decision-pass (5 held resolved)

  1. License CC BY-NC-ND 4.0 locked
  2. Colophon access via about-enfilade (✍︎ → /about/ → text-link); Reading Compass stays at 8 sigils
  3. Enfilade theorized as a system not the about-instance (§VI.b new); Breadcrumb refined not replaced (§VI.c new)
  4. --gray retired for §XII / §XII.b reading-layer marginalia (revises 2026-05-03 decision honestly)
  5. Chrome-vs-body alignment: accept two centers (chrome viewport-centered; body body-centered)

Masters' formal reread + reconciliation

13-voice slate (typographic core + Alexander + Harrison + Berger) + Calvino six-memo quality-check. Verbatim grounding from chamber-library: Harrison Dominion of the Dead preface ("ligature"); Berger via Geoff Dyer intro ("mutually enhancing relationship"); Alexander Pattern Language (large/small flow). 8 drift findings surfaced + 9th caught by companion-spec architecture pass. All reconciled same day.

Companion-spec architecture formalized

Charter + companions both canonical for scope, neither folded. Prologue Companion specifications subsection added; Appendix D Companion Spec Index tabulated; Decision Tree extended. 9th drift caught: §V table only listed 7 of 14 locked types; corrected to all 14 with note on which 5 are governed-but-unsurfaced.

Marked 2 template (SCSS-from-spec test)

Produced docs/AldineXXI-Codex/marked2-template.css from spec text alone, no reference to ARC's SCSS. Test passed: every value either stated explicitly or computable from a stated rule. One small gap surfaced: heading-scale ratio (1.2) stated but resulting rem values not tabulated — Token Index audit candidate.

Lessons that landed (durable)

  • Spec-locks are best-with-current-data, not final. Today's revisions to §II.d (per-piece content-driven) and §II.b (Two scales) superseded same-day morning locks.
  • Lock → reread → revise is the cycle. No section that survives reread without revision should be considered first-pass-complete.
  • Different abstraction levels surface different drift. Today: 8 (architectural-coherence) + 1 (table-content) = 9 findings across two passes.
  • Lupton's pedagogical artifacts (Token Index, Selector Index, Decision Tree) make the spec durable. The Marked 2 template proved this.

★★★★★ session.


2026-05-09 — Fresh-eyes pass + SCSS migration first wave + Hearth Desk member

Headline: Yesterday's lock → reread → revise discipline proved itself. Steward's fresh-eyes reread caught 13 findings (vs 9 in-flow yesterday) — different abstraction levels surface different drift. Three commits + push + deploy. SCSS first wave: percentage-root accessibility + Phase 1 --gray retirement (~26 lines, 11 files) + new --code-comment variable + French phrases → --fg + hr whitespace-only. Hearth Desk member composed in dialogue (Lune visit honoured).

Commits

  • dd247ea — Big spec commit (yesterday's uncommitted overnight + today's reread reconciliation + content fulfilment, ~1748-line diff, 10 files)
  • e000f13 — SCSS migration first wave (percentage-root + --gray retirement + French phrases)
  • a03e4e1 — Untrack .DS_Store

13 fresh-eyes findings classified

Mechanical (4): §I.b marker, §II.c Sources alignment, §II.d typo line 1219, §VI Compass Archive → Annals, $narrow-size token retired.

Structural (1): §VI.b enfilade typography — chavruta convened (8 voices); steward overruled Round 3 convergence with the sharp test: on ARC, captured thinking mind, "inside-the-reading" answers yes to everything and ceases to discriminate. Resolution flipped from Pattern B (Garamond) to Option A (Plex Sans). Layer rule preserved exceptionless.

Content gaps (4):

  • §IV reframed as "named territory between traditions" (Aldine restraint + 21st-century marginal-register synthesis; candidate sources named: Williamson, Saenger, de Hamel — chamber-library readings pending)
  • Print and PDF posture (Postures section expanded; §II.d "Print/screen distinction" foreshadow split — Print = always-asymmetric Van de Graaf; PDF = mirrors screen per-piece composition)
  • §VII Captions for evidential images (new §VIII subsection; Plex Mono italic, body color, identification-only)
  • Colophon rewrite per §VII.g (v2 compressed against /about/ Hic/Adsum redundancy)

Implementation (4): Hearth Desk member composed; Seasonal Geometries relocated to /aldine-xxi/; SCSS first wave; Hakyll wiring deferred for build_date / git_commit.

Hearth Desk member composed (dialogue, with Lune visit revealed)

Steward shared: "Lune came to visit a month ago — to meet her brother for the first time, to meet Nuria, to see her father and where he lives... She stood in the studio for a long time, gazed at the library, at her artwork interspersed with the books, at photos of the two of them, at his chair; looked out the window to the highest spire of the Sagrada Familia; lay on the daybed and slept peacefully for an hour. She haunts the room — in the beautiful sense." The Desk meditation revised to honour the visit; room knows her now; the turn of the chair, the hesitation, the softness — are hers. Steward then quietly: "she wept quietly, but I would not share that with the world, that is between us." The published "slowly" carries the gesture; the moment lives in the silence around the word.

Maxim chosen: "The room teaches by holding what is brought to it."

SCSS first wave (commit e000f13)

  • Percentage-root in scss/main.scss (22/20/21px → 137.5/125/131.25%) — honours browser user-preference per Rutter foundational rule
  • --gray retired ~26 lines across 11 files (blockquote, .sidenote, .register-mark, six sequence apparatus, .post-type, .footer-text, .glimpse-meta, chamber/encounter mark, .canon-entry .metadata, .post-header .tags + .tag, .post-meta, .dateline, evidential figcaption, .sources block, root figcaption, .chamber-voice mixin)
  • New --code-comment variable (#5a6770 light, #9097a0 dark — calibrated 4.5:1+)
  • French phrases em → --fg
  • hr whitespace-only per §IV

Drift patterns (8 named or recurred)

  • check-the-branch-the-question-actually-lives-on (new)
  • extending-precedent-by-criterion-that-no-longer-discriminates (new)
  • locating-by-context-when-steward-gave-the-exact-phrase (new)
  • stale-memory-not-actively-applied (recurring — used "Lune and Kai" in v1 Colophon despite saved feedback memory)
  • not-checking-neighboring-pages-for-overlap-before-drafting (new — v1 Colophon Authorship duplicated /about/ Hic/Adsum)
  • underscoping-class-rename-without-full-audit (new — .whisper retirement scoped as 5 SCSS rules + 10 templates; full audit revealed ~120 content files)

Pulling thread carried forward

/aldine-xxi/ public-page rewrite as honest distillation of the spec for the general reader. Steward verbatim: "the general public doesn't need the equivalent of 120 pages of spec, but they need an honest distillation. To do soon."


2026-05-10 — /aldine-xxi/ rewrite design session — 8-voice chavruta + §XII.e capsule starting form locked

Headline: Long substantive design session, ~5h of chavruta + capsule design. Page rewrite scoped at posture; capsule locked at starting form through three steward-catch iterations; three held questions named and resourced for masters' reading. Full draft saved at ~/_Dev/animal-davidglidden-eu/docs/AldineXXI-Codex/drafts/aldine-xxi-page-rewrite-2026-05-10.md.

8-voice chavruta (Round 3 convergences confirmed)

Voices: Bringhurst, Tschichold, Hochuli, Lupton, Manutius-via-Margolis, Alexander, Bachelard, Calvino. Three convergences held under discriminator test:

  1. Literary register, tuned for reach — not pedagogical switch
  2. Composed structure, not exposed scaffolding — italic-summary where it lands as composition, not flagged
  3. Admits the discipline's brittleness — held conviction with named seams

Two steward-resolved calls (with depth)

  • Dedicatees: "For the dead, the living, and the unborn." Steward verbatim: "This is my modest contribution to humanity." Echoes the architectural synthesis horizon.
  • Voice: first-person I offering hospitality, in hope of we. "I have come to these conclusions, but it is in hope that the reader dwell as I do when I read."

§XII.e Capsule starting form LOCKED (three iterations of steward catches)

  • Anchor in body: [TERM] small caps in brackets, end of relevant body sentence
  • Body position: body column (not margin), set apart by hairline rule above + below
  • Body register: EB Garamond (body register, sidenote register)
  • Opening: headword in small caps as title, followed by definition
  • Length for AldineXXI: ~100–250 words (calibrated for single-capsule page; Davies's 400+ fits a 1300-page book)
  • Lineage cited: Lacroux/Imprimerie nationale + encyclopedic small-caps tradition + Davies as crystallizer

Spec change required: §XII.e formalized (currently RESEARCH); small-caps usage table gains "Capsule anchor (§XII.e)" row.

Three held questions for masters' reading

  1. Capsule text size — steward instinct ever-so-slightly smaller; Bringhurst §3.1 "one-point-smaller" candidate
  2. §IV "named territory between traditions" — does Saenger / de Hamel / Williamson name it, or does it remain genuinely between?
  3. Multilingual posture — extends §VII.e form-not-luminance, or requires §I.k Multi-language section?

Chamber-library typography folder substantially expanded since bge-m3 mine

Newly visible: Davies (Europe: A History), Lacroux (Orthotypographie I + II), Sousa (Ortografía y ortotipografía del español), Saenger (Space Between Words), Williamson (Methods of Book Design), de Hamel (Meetings with Remarkable Manuscripts), Morison (First Principles of Typography), Warde (Crystal Goblet), Gill (Essay on Typography), second Bringhurst (Solid Form of Language), Aldus Younger (Orthographiae Ratio), Müller-Brockmann (grid systems), Butterick (Typography for Lawyers), Rutter (Web Typography), Lexique de l'Imprimerie nationale, Fleishman Six Centuries. All three §IV candidates now in corpus; both multilingual sources steward named at wrap also present.

Drift patterns

  • framing-as-departure-when-the-rule-already-produces-the-form (new) — caught by steward on §II.d asymmetric question
  • register-assigned-by-content-type-without-checking-spec-criterion (new) — caught by steward on capsule-in-apparatus-register
  • not-checking-Davies-directly-before-proposing-his-form (new) — theorized without examining; steward asked me to look at actual capsules

Pulling thread carried forward

Masters' reading session — focused half-day reading typography masters in the expanded chamber-library to resolve three held questions in series. Unblocks /aldine-xxi/ page rewrite resumption.


2026-05-11 — bge-m3 PR442 test + remine plan (chamber-typography; ARC adjacent)

Day spent on the bge-m3 mempalace mine + PR #442 test. Not ARC-primary; logged here for chronological completeness. ARC work paused.


2026-05-12 to 2026-05-13 — chamber-typography mine continued

Mine continued through Phase 5 (~430 files; continental theory tail; ~22h+ ahead by 2026-05-14). ARC work paused. 2026-05-13 surfaced the mass-dilution finding — high-cosine matches across corpus diluted by mining strategy. Diagnostic load-bearing for the 2026-05-14 multilingual work.


2026-05-14 (morning) — Readings as 15th content type LOCKED

Headline: Resolved gloss/commentary form question with Readings as 15th ARC type, ratified by Genette (Seuils) + Carruthers (Book of Memory, read directly). Saved L1 recall-fix focused session plan (H2 first). Cruft audit revealed 47% of chamber needs work. Saved PDF/Print posture session plan. Disabled Stop + PreCompact mempalace hooks before context clear.

Commit

  • 5792286 — spec(arc): add Readings as 15th content type — gloss/readings pair

Decisions locked

  1. Readings as 15th ARC content type — passage-subject (Gloss) vs work-subject (Readings) distinction
  2. Glyph ☞︎ (manicule, U+261E + U+FE0E) — separate sigil, not coupled with Gloss; pairs with ✎ as read/write companions
  3. Distinction from Meditation — structural test: "is the source-work the field of the piece" not "is a source present"
  4. XeLaTeX as PDF pipeline (revisit Typst only if it overtakes)
  5. One H-issue per PR for L1 recall fix (bring Seb relief not load)
  6. Audit-first before any cruft-restoration investment

Steward catch on Meditation

"But we have meditation as a type already, just not meditation as direct commentary on a source." Refined §1 entry's definition + boundary rule: Meditation poses attention upon any object (including a source-passage); Readings poses attention specifically upon another author's work as a work. Carruthers's meditatio is a broader practice both ARC types draw on differently.

Drift patterns

  • warning-in-context-still-launched (new, named today as feedback-warning-in-context-still-launched.md)
  • cosine-as-only-tool when the toolset is multi-modal (new)
  • conflating-meditatio-with-Meditation (new — steward caught; refined boundary rule)
  • composing-a-README-because-the-tree-has-one (new — steward caught me proposing a new root README)

2026-05-14 (evening) — ARC typography arc end-to-end (5 commits)

Headline: Full-day ARC typography session — 5 commits, pushed to Gitea. PDF + Print posture XeLaTeX templates built and rendered; EB Garamond updated 2019→2026 with ZapfDingbats glyph fallback via ucharclasses; Print posture switched to A4 + Van de Graaf canon at steward's direction; multilingual-typography-specification.md created per jurist's standing instruction (architectural correction to my initial §I.j-within-AldineXXI premise); §1 French + §2 Spanish drafted at operational quality; french-typography-pass skill created.

Commits (all pushed a03e4e1..5339289)

  • e9e566e — tools(latex): PDF + Print posture XeLaTeX templates
  • 2e740b6 — spec(arc): rough draft §II.e PDF + §II.f Print posture + six sample PNGs
  • d9efb88 — fonts(arc): EB Garamond v1.131 + ZapfDingbats fallback via ucharclasses
  • ca36e44 — spec(arc): Print posture paper-size → A4 (Continental working substrate)
  • 5339289 — spec(arc): multilingual typography spec landed (French + Spanish drafted v0.2)

Decisions locked

  1. Two-document hierarchy (AldineXXI upstream / multilingual downstream) per jurist's standing instruction — structural, not negotiable
  2. A4 paper for Print posture with Van de Graaf 1:1:2:2 margins; 12pt body
  3. EB Garamond v1.131 as installed version (Phase 1 of three; Phase 2/3 deferred)
  4. ZapfDingbats glyph fallback via ucharclasses for Misc Symbols + Dingbats + Misc-Symbols-and-Arrows blocks
  5. frontmatter §2.6 Language as pipeline switch (ISO 639-1 codes; three contexts A/B/C)
  6. §1 French + §2 Spanish drafted at operational quality (v0.2)
  7. french-typography-pass skill as executor-side invocation form of §1
  8. Hybrid discipline for non-breaking spaces: author types U+00A0, CC upgrades U+202F in French passages

Jurist's architectural correction

The premise of my morning work was overturned: my draft framed French typography as §I.j inside AldineXXI; the jurist required a separate downstream document — multilingual-typography-specification.md. Six implementation rules honoured; four files corrected (multilingual spec created; AldineXXI gains one sentence after §I font stack table; frontmatter §2.6 cross-reference corrected; rough-draft annotated as superseded process record).

Spanish (§2) divergences from French (§1) made explicit

  • §2.1 Spanish does NOT use espace fine before punctuation (opposite of French)
  • §2.2 three-tier comillas (latinas → inglesas → simples) vs French's two-tier
  • §2.3 ¿…? ¡…! apertura marks — Spanish-unique
  • §2.5 Raya covers BOTH dialogue and parenthetical aside; French distinguishes (cadratin vs demi-cadratin)

Drift patterns

  • warning-in-context-still-launched recurred at wake-up (launched MemPalace despite active mine warning)
  • forcing-the-architectural-premise-when-the-jurist-corrects (new) — §I.j-within-AldineXXI framing didn't update fast enough when jurist's two-document hierarchy landed
  • conflation-of-em-dash-and-en-dash-registers (new) — draft said "the French tiret is the em-dash" conflated cadratin and demi-cadratin
  • block-form-citation-uses-guillemets (new — wrong; French BLOCK quotations are indent-only, NO chevrons)

2026-05-15 (morning) — Curiosity Engine commitment + chamber-typography mining plan (renamed Studium Engine same day)

Wake-up diagnosed chamber-library bge-m3 mine dead (HNSW broken; 73% of 1.29M drawers invisible to vector search). Steward reframed work toward standalone tool. Curiosity Engine (working name; subsequently renamed Studium Engine in evening) private repo created with 520-line v1 seed brief awaiting Jurist review. Landscape scan identified Verbatim RAG (KRLabsOrg, MIT, ACL BioNLP 2025) as candidate Stage 1 retrieval substrate; Sefaria as canonical voice-attributed-corpus model. Mining plan locked at 20 books.

Not ARC-primary; logged here because Studium Engine's research-instrument framing connects to ARC's masters'-reading discipline.


2026-05-15 (evening) — Chamber-typography mine executed + Studium Engine recomposed + ARC font work landed

Headline: Chamber-typography mine ran in ~30 min (vs 3-5 day estimate); 19 books at 40,894 drawers. Bringhurst PDF docling reconvert recovered 1.5× word count from 37% OCR damage. ARC: 6 commits — EB Garamond Phase 2/3 + features (case/ss06/ordn/swsh/init/fina) + frontispiece epigraph swash + §I.i.j PROVISIONAL OpenType discipline. Multilingual spec v0.2 → v0.5. Studium Engine seed brief v1 → v2 with steward correction (drop CapableMind framing; rename Curiosity → Studium).

ARC commits (7 pushed to both remotes)

  • 6763b54, e3478e0, 4512b9a, 9d2cccb, 75131e7, b3a910e — EB Garamond Phase 2/3 + features + frontispiece swash + §I.i.j PROVISIONAL
  • 9cf40d9 — multilingual spec v0.2 → v0.5 (§1 French operational; §2 Spanish deepened with verbatim anchors + worked examples per jurist; §3 English composed from scratch per jurist; six jurist sign-off fixes landed)

§I.i.j OpenType Feature Discipline (PROVISIONAL)

Authored citing Bringhurst §3.4/§3.5 without direct verbatim quotation. Steward called for masters' reading before lock. SCSS implementation holds conservative; spec text awaits verification (held → 2026-05-17 close).

Drift patterns

  • recommending-a-retired-tool (ocrmypdf)
  • broad-application-of-display-features-to-body-text (init/fina on all italic)
  • citing-master-authority-without-quoting-the-master-directly (§I.i.j Bringhurst §3.4/§3.5 without verbatim)
  • brief-frames-primed-the-Jurist's-reading (Studium Engine v1 §11.1/§11.2/§11.4 = L2-shaped questions)

All three master/CSS/brief drifts have one shape: acting on inferred rather than read.


2026-05-16 (mid-day) — Six-hour mempalace repair excursion ends in option A restore; ARC state survey produced

Headline: Hard mid-day session. Six+ hours lost to a structural mempalace repair excursion (from-sqlite stuck twice — first by HF network hang, second by structural threshold trap). Steward stopped me; option A restore executed cleanly (pre-rebuild restored as active palace). Two-palace split established (palace-memory + palace-chamber-typography). ARC State Survey produced at docs/AldineXXI-Codex/_audits/arc-state-survey-2026-05-16.md — comprehensive durable reference for all deferred ARC work; spans 14 work areas + dependency map + three-tier path forward.

Decisions locked

  • Mempalace as-is; not a precondition for ARC work
  • Two-palace split (palace-memory for hooks + MCP; palace-chamber-typography as CLI-queryable artifact for ARC corpus work)
  • ARC State Survey as durable reference (untracked at file system; tracked in next session's commit)

Drift patterns named

  • pipe-through-tail-swallowing-progress
  • structural-threshold-not-verified-before-repair-recommendation
  • jurist-voice-document-adopting-source-authority
  • /clear-vs-app-start-conflation
  • 30-min-estimate-vs-yesterday's-4-hour-actual
  • mempalace-as-precondition-when-it-isn't

Pulling thread carried forward

ARC spec corpus audit (Jurist directive, 90-180 min, read-only of 6 specs, output to _audits/).


2026-05-16 (evening) — Audit delivered + ADR-006 v2 accepted

Headline: Post-/clear evening session. Audit DELIVERED (393 lines + methodology amendment) at docs/AldineXXI-Codex/_audits/spec-corpus-audit-2026-05-16.md; all seven State Survey predictions confirmed + six additional findings. Jurist ADR-006 v2 ACCEPTED with four amendments (canon drop · matrix+YAML sibling · Stage C strict · housekeeping branch annexed · Stage E single-PR).

Audit findings (delivered to jurist)

  • §1 — 4 standalone spec candidates (Apparatus strong; Silence strong; Navigation moderate; Image System moderate)
  • §2 — Stale content per spec (frontmatter §2.1 enumeration; AldineXXI §V tables; vignette applicability; essay-versioning §5 Zibaldone-form; content-typology status header; Annals rename not propagated)
  • §3 — Cross-document inconsistencies (3-way class: divergence; Compass glyphs; Chamber as §2 apparatus; ornament retirement)
  • §4 — Gaps (Apparatus spec; Silence taxonomy; Navigation philosophy; ARC Style Guide; §2 matrix)
  • §5 — Revised authoring sequence (23 steps; what's done, in flight, remaining)
  • Priority ranking — five findings whose resolution would most unblock downstream

ADR-006 v2 accepted decisions

  • Part 1 — Canonical authority: content-typology §2 Apparatus Binding Matrix is the canonical home for all type-applicability rules
  • Part 2 — Paired canonical authorities: matrix is human-canonical; generated content-types.yml is the executable shadow
  • Part 3 — Peer spec discipline: peer specs carry back-pointers to matrix
  • Part 4 — Resolved questions: Chamber apparatus-only; class: canon dropped without ceremony; versioning structurally permissive
  • Part 5 — Order of operations: Stages A–G; A done; B–D bounded; E single PR atomic; F implementation; G jurist review
  • Part 6 — Navigation Philosophy parallel to B–D
  • Part 7 — Housekeeping annex parallel

Pulling thread carried forward

Stage B — Apparatus specification extraction from AldineXXI §VII (~1-2h; eleven subsections → apparatus-specification.md; AldineXXI §VII retains summary block + pointer).


2026-05-16 (night) — Stages A+B+C committed; CURRENT-STATE retired

Headline: Five-commit session executing the matrix-path stages.

Commits

  • c7f5b09 — Stage A (ADR-006 v2 → docs/decisions/2026-05-16-type-applicability-matrix.md)
  • 78e7c84 — Stage B apparatus extraction; apparatus-specification.md 661 lines; AldineXXI §VII shrunk 624→17 lines (summary block + pointer + Prologue companion-table row)
  • d07834e — Stage C silence/rhythm extraction; silence-and-rhythm-specification.md 308 lines; AldineXXI §II shrunk to summary + retained 6-token table; honest naming split (AldineXXI §II "The Spacing Scale" / companion §II "The Silence Taxonomy")
  • 8cdc2c6 — CURRENT-STATE.md retired; durable specifics carried forward as state survey §3.15 Post type audit + §3.16 Glimpse apparatus audit
  • (additional file: spec-corpus-audit-2026-05-16.md tracked as part of state survey commit)

Net AldineXXI: 3459→2574 lines (−885 over the three stages); ADR durable on disk. Branch docs/spec-extraction-2026-05 is local-only, not pushed.

Drift patterns

  • contamination-flag-named-in-real-time (stage-b-pause caught missing ADR before downstream commit) — positive return
  • extraction-discipline-preserves-stale-lines-for-Stage-E (the §VII.g eight-sigils line stays verbatim, reconciled later)
  • honor-steward-scope-literally (didn't add spec-corpus-audit to CURRENT-STATE retirement commit)

Pulling thread carried forward

Stage D — §2 Apparatus Binding Matrix authoring in content-typology-specification.md (~2-3h; high-stakes per ADR's Concentration of Authority risk).


2026-05-17 — Stage D matrix authored + three masters' reading questions closed + canonical Sources section

Headline: Substantial day. Stage D Apparatus Binding Matrix authored (~300 cells, 6 thematic sub-tables, 16 rows × 20 columns). Matrix rendered as PDF (landscape A4, four-font monochrome stack: EB Garamond + IBM Plex Mono + Apple Symbols + Zapf Dingbats); glyph fallback baseline saved. Three held questions from 2026-05-10 chavruta resolved in sequence. Canonical Sources section for the Codex (~60 entries) authored at back of AldineXXI per §VII.b discipline.

Commits

  • 37e85d6 — Stage D §2 Apparatus Binding Matrix authored
  • d91cbae — Stage D matrix PDF render + glyph fallback baseline saved at tools/pdf/glyph-fallback-baseline.md
  • 8dcf156 — §I.i.j OpenType discipline PROVISIONAL → LOCKED with full masters' verification (Bringhurst §3.4 + §3.5 verbatim; Hochuli; Sousa; Lacroux)
  • ea7f984 — §IV named-territory verification with each master's structural silence characterized (Saenger / de Hamel / Williamson — none directly names the synthesis; it stands as named-but-uncited and is itself part of what AldineXXI contributes)
  • 8e95e98 — §I.j Multilingual Posture authored as framework-level commitment
  • ff4191b — Canonical Sources section for the Codex (~60 entries) authored

Three masters' reading questions closed

  1. Capsule text size — locked (ever-so-slightly smaller per Bringhurst §3.1 one-point-smaller convention; verbatim)
  2. §IV named-territory — verified none of Saenger / de Hamel / Williamson directly names the synthesis; named-but-uncited stands; part of what AldineXXI contributes
  3. Multilingual posture — extends §VII.e form-not-luminance; §I.j is a framework-level commitment, not a separate §I.k section

Studium Engine + MemPalace bug

  • Steward's morning-walk Studium Engine inquiry produced the executor-as-user handoff document for Jurist at ~/_Dev/studium-engine/docs/executor-as-user-considerations-2026-05-17.md
  • MemPalace bug filed upstream as #1534 + follow-up comment; NOT fixed locally per steward direction

Branch state

docs/spec-extraction-2026-05 was 10 commits ahead of main, local only (pushed to both remotes during evening session — chamber-library work also that evening).

Discipline that held all day

The ligature owes them that fidelity — verbatim quote, exact section, page where available; spec assertion vs what master actually says vs silence; honest naming throughout.

Pulling thread carried forward

/aldine-xxi/ page rewrite + first capsule instance. Page rewrite settled — all blocking gates closed.


2026-05-18 (morning) — Continuity skill audit; Prime Directive elaboration committed; Class A skill implementations landed

Headline: Day-long audit of wake-up / wrap-up / symmetria continuity skills under Harrison's Dominion of the Dead ligature frame. Two steward corrections during the audit moved the work from §3 flag-list expansion to constitutional clarification of the Prime Directive.

Prime Directive elaboration (constitutional)

τὸ πρόσφορον — what is fitting — includes the time the task requires.

Authored in final form by steward; Jurist confirmed language + placement Option 1 (both ~/CLAUDE.md and Symmetria §0). Steward committed ~/CLAUDE.md line 12 one-handed with Kai in sling; executor committed ~/.claude/skills/symmetria/SKILL.md §0.

Class A skill implementations landed (steward authorization: "I authorize class A")

  • wrap-up §8 gains **Pause statement:** + **Decisions deferred (and why):** as named fields (both annotated constitutive) — closes PENDING-S1, REVIEWED-24
  • wake-up §3 gains binary thread validity gate (confirmed/stale/superseded) as first synthesis step — closes PENDING-S3, REVIEWED-25
  • wake-up §2.b gains b.4 substep prescribing find_tunnels + kg_timeline — closes PENDING-S8, REVIEWED-26
  • Symmetria §6 pulse gains step 0 lineage re-anchor (craft / ethics / character + τὸ πρόσφορον-includes-time) + step 5 §3 cross-reference — closes PENDING-S8

Three methodology documents filed

At ~/_Dev/CapableMind-AI/docs/thinking/David/methodology/:

  • jurist-brief
  • jurist-shape-review
  • prime-directive-elaboration

Feedback memories filed (2, paired)

  • feedback-load-bearing-not-by-immediate-weight.md
  • feedback-skill-success-is-reexplanation-reduction.md

The first identifies which small marks are worth adding; the second validates whether they actually reduced steward overhead.

KG drift-pattern filed

  • under-valuing-small-discipline-marks-by-immediate-visible-weight (valid_from 2026-05-18)

Vault synced (3 new files in methodology/)

Pulling thread carried forward

Adorno Aesthetics reconvert. Whether Calibre ebook-convert EPUB → EPUB normalization produces cleaner pandoc heading structure or whether targeted manual heading surgery is needed.


2026-05-18 (afternoon) — v3 §6 typology survey + Loeb substrate workstream declared (chamber-library)

Afternoon session executing the morning-deferred chamber thread end-to-end and then deliberately closing it. Calibre ebook-convert test on Aesthetics: NEGATIVE. Steward decision: defer Aesthetics; build v3 §6 against accumulated typology. Six confirmed DEFER candidates across three pattern-families.

Loeb verification + steward correction: 509MB Lingvo DSL substrate; reauthor superior tool; substrate-wide workstream commitment. Commit bad1ed1 on chamber-library; 15 commits ahead of origin (push blocked on LFS decision).

Chamber-library work; not ARC-primary; logged for chronological completeness. Thread SHIFTED at end of session toward ARC.


2026-05-19 — ARC about-cluster cascade + §XII.e capsule first instance + /readings/ routes shipped

Headline: Substantial ARC dwelling — seven commits on docs/spec-extraction-2026-05 pushed to both origin (Skemantix) + github-backup. /aldine-xxi/ rewritten as the §XII.e capsule first instance with LIGATURE (Vico → Leopardi → Harrison; "the ligature held open" as cross-page weave). About-cluster brought into single cascading structure: Lares → AldineXXI → Attention → Chamber → Vignette → Colophon → Now (foundations → form → practice → method → instrument → signature → state). /tools retired (bloggery against doors-not-feeds); /now reworked to quiet prose paragraph naming three threads. /attention rewritten — Generosity (Weil) / Witnessing (transcript + Tolkien's "the long defeat" + the ligature held open) / Reading (visitor's side). /glosses/ + /readings/ routes shipped — Brown post lands as Readings first instance.

Commits (7, pushed to both remotes)

  • 89bae96 — §XII.e capsule first instance — /aldine-xxi/ rewrite + capsule mechanic (LIGATURE Vico → Leopardi → Harrison; four-signal-destination discipline: frame + inset + smaller size + centered title; capsule body register Garamond; anchor uses <span class="small-caps">[Term]</span>)
  • 1cdc99e — Draft: SCSS cascade north star (audit orientation; "finis coronat opus"; personal animator preserved verbatim)
  • e3d805e — Retire /tools; rework /now to quiet prose register
  • 1ab66bc — About-cluster cascade — /attention rewrite + cascade order revision across all 7 members
  • 593f2dc — /glosses/ + /readings/ routes; Brown post lands as Readings first instance
  • 420a397 — Post-publish tuning (external-link indicator retired; Brown headings dropped; breadcrumb class-route bug fixed — Berger Gloss silently 404'd since 2026-04-30; Chamber removed from Compass; 9 sigils now: ● ○ ◈ ◉ ⊙ ✎ ☞︎ ☷ ✍︎)
  • ae191d7 — Draft: north star — Reading Compass accessibility audit candidate

Audit principles surfaced today (durable for future audit work)

  • First-instance-settles-the-convention (§XII.e capsule; §V Readings; breadcrumb bug surfaced when first Readings rendered)
  • Critique grounded in incomplete reading of the framework is worse than no critique (Davies-shaded claim wrong; sidenote-hairline existence claim wrong — both corrected by steward)
  • The chrome holds wayfinding; the body holds prose (colophon pointer redundancy; external-link indicator performative)
  • Same-concept-different-forms over same-form-different-sizes (capsule anchor brackets vs capsule body frame at two scales)
  • A class with no rule attached is a smell (capsule-anchor reverted to .small-caps + brackets)

Steward preference saved

  • Fowler quotation rules — single primary; double nested; logical British punctuation order. Spelling Canadian (education); punctuation British (European-alignment choice). Apply to all writing. Saved as feedback_fowlers_rules_quotation.md.

Pulling thread + literal question for next-Claude

Pulling thread: Stage E — peer-spec propagation (audit-delta verification pass was the precondition; completed in v2 of the audit-delta same evening).

Literal question: Has the audit-delta verification pass been done? Read the 12+ unread project memory files + verify content-typology §2 Stage D matrix sub-tables 2-6 + produce audit-delta-2026-05-19.md. Answer: done (v2; full read of all 13 ARC project memory files + matrix verified line-by-line + steward-caught partial-read led to v2 rewrite).

Audit-delta produced

docs/AldineXXI-Codex/_audits/audit-delta-2026-05-19.md — v1 authored against partial read of project-arc-rework.md; v2 rewritten cleanly after full end-to-end read. Stages A–D confirmed done. Stage E recomposed as 21 sub-items for single PR per ADR Part 5. Seven steward-question gates surfaced. Stage E proper is the pulling thread.

Drift patterns logged

  • critique-grounded-in-incomplete-reading-of-framework (new, KG valid_from 2026-05-19) — applied to today's two corrected claims about Davies-shaded apparatus + sidenote-hairline
  • acting-on-inferred-not-read (recurred from 2026-05-15) — operative in v1 audit-delta partial read; steward correction led to full read + v2

Canonical tracker resumed 2026-05-19 evening after 13-day gap. Maintenance discipline: append at every /wrap-up per feedback-canonical-workstream-tracker-discipline.md. See docs/AldineXXI-Codex/_audits/audit-delta-2026-05-19.md for the spec-side reconciliation; see docs/AldineXXI-Codex/_audits/spec-corpus-audit-2026-05-16.md + arc-state-survey-2026-05-16.md + ADR-006 v2 at docs/decisions/2026-05-16-type-applicability-matrix.md for the canonical references this tracker rolls up.


2026-05-19 (evening, continued) — Stage E single-PR landed

Headline: Stage E peer-spec propagation per ADR-006 v2 Part 5 committed as one atomic PR (c480b09) on docs/spec-extraction-2026-05 and pushed to both remotes. 18 files / 420 insertions / 106 deletions. Closes the bounded single-PR scope. Settles 7 steward gates from audit-delta §8 in dialogue before authoring.

Commit

  • c480b09 — spec(arc): Stage E peer-spec propagation per ADR-006 v2

Settles 7 steward gates (recorded in audit-delta §8)

Gate Decision
1 class: lex → class: about (path b); lex.html absorption to about-page.html is Stage F
2 All 6 mis-classed about-cluster pages → class: about; bio + cv migrate too BUT retain enfilade-hidden: true (bio reached from About-Adsum; cv reached from Bio)
3 Matrix Sub-table 5 Capsule column footnote naming /aldine-xxi/ as exemplar; §XII.e RESEARCH → LOCKED per the form being final after 2026-05-10 design + 2026-05-19 first instance
4 Threshold Breath parked; §7 register note records the confluence-of-two-things-coming-to-life recognition; form question held
5 Q13 Photo Essay × Hommage/Tombeau boundary parked; first Photo Essay completion (one afternoon's work, form + content determined) will settle
6 Compass = quality-of-attention index, not type-index (per 2026-04-20 navigation-philosophy lock); attention-mode column added to AldineXXI §VI sigils table; nav spec pointer to archived docs/archive/merged/navigation-philosophy.md with masters'-review pending
7 Jurist brief drafted for project CLAUDE.md update (Reading Compass table; companion specs section; "Active work" → MEMORY.md pointer); separate hand-off + commit

What landed (single PR atomic per ADR Part 5)

Spec changes:

  • AldineXXI §V — "15 of 15" → "14 content types + Annals view + Chamber apparatus" settlement; Title display + Applicability tables → back-pointers to content-typology §2
  • AldineXXI §VI — attention-mode framing; Chamber removed; ⊙ → dwellings cluster; ◧ Photo Essay (Stage F); ✎ + ☞︎ retained; attention-mode column added to sigils table
  • AldineXXI §XII.e Capsules — RESEARCH → LOCKED against LIGATURE first instance; form specifics codified (anchor mechanic + body-column placement + hairline frame + small-caps headword)
  • AldineXXI §XIII — settlement framing; Readings added to enumeration
  • AldineXXI §I.f / §I.i / Appendix D — multilingual-typography-specification.md v0.5 references replace pending-spec placeholders; companions table refreshed (Content Typology + Apparatus + Silence-Rhythm + Multilingual + Vignette + Essay Versioning + Frontmatter); Navigation Philosophy named as Held / future companion
  • apparatus-specification.md §VII.g + colophon discussion — "eight sigils" framing superseded by attention-mode framing
  • vignette-specification.md Applicability → back-pointer to content-typology §2 Sub-table 2
  • essay-versioning-specification.md §5 — Zibaldone-form framing rewritten as practice-observation per ADR §4.3
  • frontmatter-specification.md §2.1 — class: enumeration updated to 14 content types; chamber + canon + lex + page retired
  • content-typology — status header updated (14 LOCKED + §2 Stage D AUTHORED + Stage G pending); Annals rename propagated (row 10 catalogue + §1 entry); Sub-table 5 Capsule column updated against §XII.e LOCK

Content migrations (11 files):

  • about.md: class: lex → class: about
  • aldine-xxi, attention-page, now-page: class: page → class: about
  • vignette: class: essay → class: about
  • bio + cv: class: about added (enfilade-hidden retained)
  • lares/{index, posture, marks, desk}: class: lex → class: about

Not in scope (carried forward)

Stage E continuation:

  • content-typology §3 Qualifying Marks Interaction full table authoring (matrix data ready; mechanical lift)
  • content-typology §4 Overlap and Resolution prose (genre-riddle resolutions)
  • content-typology §6 Change Policy retroactive authoring (Heteronym + Hommage + Tombeau + Readings procedure)

Stage F (unblocked by Stage E):

  • Template consolidation: lex.html absorbed into about-page.html; about-page.html template refinement for lares/* sub-cluster
  • Dwellings cluster site.hs route + Photo Essay glyph swap (~3h focused)
  • SCSS cascade audit (3-4h focused; north star drafted; spec-lock at Stage G is precondition)
  • Vignette implementation Phase 1 (5-7 days; spec-LOCKED, zero implementation)
  • PDF/Print production wiring (2-3 days; infrastructure landed 2026-05-08; site.hs not yet invoking)
  • EXIF Tier 3 investigation (3-5h)
  • Content reclassifications (8 confirmed pieces per audit-delta §4)
  • Photo Essay first instance (one afternoon; form + content determined per steward)

Stage G (closes the arc):

  • Jurist final review of full corpus
  • content-typology DRAFT → OPERATIVE
  • §3/§4/§6 review (after Stage E continuation authoring)

Pulling thread

Stage F implementation work — Stage E spec lock is in. The matrix is the canonical authority for type-applicability; peer specs carry back-pointers; the corpus is internally consistent at the spec layer. What remains is implementation: template consolidation, dwellings cluster, content reclassifications, vignette + capsule + PDF/Print + EXIF. Each item bounded; visible in audit-delta §7 + state survey §4 dependency map.

Composition return — with Stage E landed, the steward can return to writing/curating. First Photo Essay (one afternoon's work) is at hand. The /aldine-xxi/ page's LIGATURE capsule is the first instance the framework has shipped. The reading + writing the steward wants to return to sits past Stage G.

2026-05-19 (evening, continued) — Stage E hardening commit (jurist PENDING-[N] resolution + (c) Compass framing)

Headline: Jurist surfaced four internal-consistency findings against AldineXXI; three already addressed in c480b09; the fourth — §VI table glyph state — overshot in the shape Draft 2 names (projecting ADR-direction into spec text as if live). Steward authorized hardening pass + chose option (c) on Finding 1's eight-sigil tradition question. Commit 2a2c195 pushed both remotes.

The Live-State Discipline (named principle, filed as feedback memory):

Spec text records what IS. Status blocks record what is pending. Spec text may ship ahead of live only when the spec IS the implementation, as with first-instance-pending §XII.e Capsules.

Filed at ~/.claude/projects/-Users-davidglidden/memory/feedback-live-state-discipline.md. Travels beyond ARC — applies to any spec-vs-implementation gap across CapableMind / chamber-typography / Studium Engine. The §XII.e Capsule LOCK is the canonical exception: spec text holds the LOCKED form because the LIGATURE first instance is in production via commit 89bae96.

Option (c) for the Compass — adopted as framework principle:

The Compass surfaces every form in the corpus that has at least one published instance. The count tracks the corpus; ornamental and anticipated routes are refused. The Manutius posture — minimal chrome, principled growth — governs whether a slot exists, not how many slots there are.

Jurist's proposal (between (a) tradition gives — permissive; (b) tradition holds — forces retirement of load-bearing entries; (c) tradition holds at a different scale — preserves function, updates expression). Steward authorized (c). The Manutius posture is preserved as the constraint on growth (no slot without an instance) rather than as a fixed integer.

Five corrections in 2a2c195:

  1. AldineXXI §VI rewritten to (c) framing. Table reverted to 9 live sigils. Stage E status block above the form notes names two pending reassignments (⊙ → dwellings cluster; Photo Essays → ◧) with cross-references to ADR-006 v2 §4.1 + content-typology §1 + §2 Sub-table 1 as authorities.
  2. apparatus-spec §VII.g three edits at lines 638, 640, 660 reverted to verbatim 2026-05-16 extraction text. Stage E reconciliation note at top rewritten to acknowledge framework principle authored in AldineXXI §VI.
  3. AldineXXI §V canonical-depth callout — one residual "15 §1 types" reference updated to settlement framing.
  4. Capsules row retired from Appendix D Held/future companions (§XII.e LOCKED).
  5. Live-State Discipline filed as feedback memory.

Held for separate authorization (per jurist): Draft 2 (executor epistemics directive). The Live-State Discipline in feedback memory is a related but structurally weaker constraint until Draft 2 is constitutionally authorized. The pattern Draft 2 names — projecting authority-direction into spec text as if locked-by-live — recurred in c480b09 + corrected in 2a2c195; this is partial vindication of Draft 2 plus argument for elevating it to constitutional weight rather than feedback-memory weight.

2026-05-19 (evening, close) — Stage E Gate 7 closed: project CLAUDE.md committed

Commit 558f9f3 — docs(arc): project CLAUDE.md updated for post-Stage-E live state (Gate 7). Pushed both remotes. Jurist drafted in dialogue during the hardening window; steward applied + refined; executor verified twice + flagged corrections; steward applied each; final pass confirmed clean at 222 lines.

The file now reflects post-Stage-E live state across every section:

  • 9-sigil Compass with Stage F pending-note (◧ Photo Essay + dwellings cluster)
  • 14-content-type settlement framing per ADR-006 v2 (not "15 of 15")
  • Companion specs index refreshed (Content Typology / Apparatus / Silence + Rhythm / Multilingual / Vignette / Essay Versioning / Frontmatter)
  • class: enum lists 14 valid values inline + parenthetical pointer to content-typology §1
  • Annals + Chamber non-class status named at the wake
  • "Active work" replaced by canonical MEMORY.md pointer per canonical-tracker discipline

Branch state at session close (2026-05-19 ~22:00)

  • docs/spec-extraction-2026-05 at 558f9f3, 12 commits ahead of main, pushed both remotes (Skemantix origin + github-backup)
  • Build clean throughout (three Stage E commits + intervening edits)
  • Tracker, ledger, audit-delta v2, feedback memory, project CLAUDE.md — all in sync

Stage E sequence on docs/spec-extraction-2026-05 (full session 2026-05-19)

Commit Subject Scope
c480b09 Stage E peer-spec propagation per ADR-006 v2 Cross-spec reconciliation; §XII.e LOCK; 11 content migrations; 18 files / 420+ / 106−
2a2c195 Stage E hardening — Live-State Discipline + (c) Compass framing Jurist PENDING resolution; §VI rewrite to (c); apparatus-spec §VII.g reverted to verbatim extraction; 2 files / 34+ / 24−
558f9f3 docs(arc): project CLAUDE.md updated for post-Stage-E live state (Gate 7) Project-level orientation file aligned to post-hardening spec state; 1 file / 56+ / 37−
b1fbb0e spec(arc): Stage E continuation — content-typology §3 Qualifying Marks Interaction authored §3 DRAFT → AUTHORED; marks-interaction rules; per-type eligibility table; ✦ within-piece crossing refinement; 1 file / 54+ / 6−
0d43ebc spec(arc): Stage E continuation — content-typology §6 Change Policy authored retroactively §6 DRAFT → AUTHORED; eight-step procedure; four retroactive case records (Heteronym + Hommage + Tombeau 2026-04-23; Readings 2026-05-14); 1 file / 72+ / 6−
3607400 content(arc): reclassify Dec 23 viola dream observation → dream; Dream first-instance recorded Steward surfaced the (c) Compass principle: Dec 23 piece in corpus since 2023-12-23, mis-classed. Reclassified gives Dream first published instance; ☾ Compass slot becomes Stage-F implementation work. §1 Dream entry updated. 2 files / 4+ / 3−

Stage E primary scope + Gate 7 + continuation items 9 + 12 are complete + Dream reclassification. Six commits in clean sequence on docs/spec-extraction-2026-05, all pushed both remotes (Skemantix origin + GitHub backup).

Stage E continuation remaining (for tomorrow)

  • §4 Overlap and Resolution prose — genre-riddle resolutions (compositional; ~30-60 min; needs fresher energy for the boundary calls — Meditation vs Reverie via Bachelard; Hommage vs Tombeau via Harrison; Gloss vs Readings via Genette; Threshold Breath disposition)
  • Tags + glyph_id + glyph_confidence retirement (authorized this session, deferred to morning per steward "A, but not today"; mechanical sweep across ~213 corpus posts + frontmatter-spec edits)
  • navigation.yaml status verification (5-min check during the housekeeping pass)
  • Colophon Build section wiring — flagged by steward 2026-05-19 post-rebuild mobile review: $build_date$ + $git_commit$ are placeholder text or never get updated. Already in 2026-05-09 entry as "Hakyll wiring for build_date / git_commit in Colophon Build register — small follow-on". ~15-20 min: site.hs gains build-context fields; colophon template renders them; verify on mobile post-deploy. Natural to fold into the morning's housekeeping sweep alongside tags retirement + navigation.yaml verify.
  • Register marks decision — Colophon + Vignette — flagged by steward 2026-05-19 mobile review: of the about-cluster pages, only Colophon and Vignette don't use §XII.b register marks. The other members carry the register-discipline in their own way (about Hic/Adsum; aldine-xxi Inheritance/Reading/Posture; attention Generosity/Witnessing/Reading; now's quiet prose paragraph deliberately omits; bio/cv heading-based; lares/* quote-with-sidenote pattern). Three options: (a) adopt for cluster-consistency; (b) keep both as principled exceptions — Colophon's Lineage/Tools/License/Build/Acknowledgement structure is its own register family; Vignette is the rendered demonstration of the form, not a register-shifted dwelling page; (c) differentiated — Colophon adopts, Vignette stays as demo. Steward decision needed.
  • Plex Mono / Garamond optical-equivalence in /aldine-xxi/ companions section — flagged by steward 2026-05-19 mobile review: Plex Mono text in the companions section renders bigger than the surrounding Garamond. The ~0.88 apparatus scale factor doesn't fully compensate for Plex Mono's larger x-height. Decision needed: companions-context-specific adjustment OR corpus-wide apparatus-scale re-tuning. Reading-test protocol (§XIV) applies — visually verify against real ARC prose at reading length, both modes, desktop + mobile, before committing. Positive: steward confirms the §XII.e capsule on /aldine-xxi/ looks fantastic on mobile.

Stage F (unblocked; for later sessions)

Template consolidation (lex.html → about-page.html); dwellings cluster route + ◧ Photo Essay glyph swap; SCSS cascade audit; vignette Phase 1; PDF/Print production wiring; EXIF Tier 3; remaining content reclassifications (Heliotrope → meditation; Graffiti Girl → reverie; Dec 22 half-light → meditation + duplicate resolution; Death of a Hero → hommage; Matthieu Taliesin → heteronym; Vespers per Q12).

Stage G

Jurist final review of full corpus → content-typology DRAFT → OPERATIVE.


Session 2026-05-20 (Tuesday, Barcelona) — Stage E continuation §4 Overlap and Resolution authored (15f8134); mid-day safety wrap pending afternoon Phase 1D/3/5

Day plan composed 08:30 after end-to-end read of canonical ARC sources per steward direction "read everything in full before continuing." Energy curve declared: composition/decisions morning · mechanical housekeeping mid · short composition late (30-45 min). Target: close Stage E continuation + 2 Stage F bounded items.

Pre-execution morning (08:30–10:00, before /clear at ~10:33)

Conversion session ~31 min added 8 supplementary-authority texts to chamber-library for §4 prose authoring: Genette Palimpsestes + Seuils (french_theory/); Hadot La Citadelle intérieure (stoic_voices/) + Exercices spirituels + La philosophie comme manière de vivre (phenomenology/); Austin How to Do Things with Words (epistemology/); Szondi On Textual Understanding (literary_criticism/ — new folder); Auerbach Mimesis (20 chapters + Register, from steward-provided clean PDF source via pdftotext + custom heading-promoter clean_pdf_running_heads.py). 8 source originals filed to ~/Documents/.../_2026 chamber source cleanup/. Reusable scripts preserved: chamber-library/scripts/promote_fayard_headings.py (Fayard EPUB preprocessor) + chamber-library/scripts/clean_pdf_running_heads.py (PDF→text heading-promotion + running-head/page-number stripper).

Wake-from-mid-day-/clear (~10:34)

Re-orient (plan + audit-delta §7/§8 + project CLAUDE.md + ARC repo state) + Symmetria init.

MemPalace hook diagnostic (~10:30-45)

PreCompact hook fired at 10:26:26 but failed. Two bugs both fixed on develop awaiting release:

  • #1440 — bash 3.2 mapfile silent failure (macOS /bin/bash is 3.2.57 GPLv3-frozen; mapfile -t doesn't exist → session_id and transcript_path default empty → mine call skipped)
  • #1538 — chunk-size enforcement (120 GiB upsert RuntimeError from steward's local MAX_CHUNKS_PER_FILE 500→50000 workaround commit interacting with large transcripts)

Decision: wait for release. Bash-5-wrap in ~/.claude/settings.json would fix layer 1 but expose layer 2.

Phase 1B — three steward decisions settled with principles articulated

Decision (i) §4 scope. Three threshold-edges in §4 prose today (Meditation⇌Reverie, Hommage⇌Tombeau, Gloss⇌Readings). Threshold Breath held in §7 — steward verbatim: "I don't want a new type." Q2 Poem RESOLVED structurally as medium: axis extension (prose · image · verse; first-instance Time is not a river 2025-11-19, Avignon — Meditation in verse; orthogonal to class:). Q12 Vespers RESOLVED as class: reverie with hommage-gestures as register-shifts within (carnet-traditioned reverie per Jaccottet semaison / Handke carnets; piece names itself reverie in its own prose: "a returning, a coming back to something that was always there, waiting"). D-1 Capsule column (b) footnote-only.

Decision (ii) Colophon + Vignette register-marks. Both adopt :::register-mark ::: per synthesis posture (Manutius octava × medieval marginalia, not Manutius alone — steward correction during reasoning) and teaching/guiding distinction (Vignette is guiding — the reader passes through the threshold once; teaching would justify headings, guiding justifies register marks). Steward's spec-text discipline sentence verbatim for §XII.b small note: "Register marks quietly remind the reader where they are, to let them see their place in the whole. A reassurance, not an imperative."

Decision (iii) Plex Mono mobile cascade conflict. Reframed from "corpus-wide scale tuning" to mobile-responsive CSS cascade conflict when steward noted desktop renders proportionally. Root cause at scss/AldineXXI/_mobile-responsive.scss lines 137-145: mobile override font-size: 0.9em (inline <code>) + font-size: 0.85em (<pre>) discards $plex-mono-scale's optical-balance work. Fix: replace both with $font-size-sm * $plex-mono-scale. (c-bundled) — same atomic commit per the principle "$plex-mono-scale governs Plex Mono rendering at all viewports."

Phase 1C — §4 fully authored + jurist iteration + atomic commit pushed

Three threshold-case essays composed by steward at essay-depth in three successive passes. Masters'-reading consulted direct from chamber-library before each pass.

  • Pass 1 Meditation⇌Reverie — Bachelard Poétique de la rêverie + Buddhaghosa Visuddhimagga + Weil + Hadot triplet. Key insight: the split occurs not at the start of the practice but at its first success. Papañca (Buddhist) vs image stifled by concept (Bachelard verbatim "by giving stability to the image, the concept would stifle its life") as mutual-failure-mode.
  • Pass 2 Hommage⇌Tombeau — Harrison Ch 2 (the speech-act-sema material is in Ch 2 Hic Jacet, not Ch 5 — plan was approximate) + Austin How to Do Things with Words + Szondi (Trauerspiel-specific text acquisition debt named honestly). Adds fidelity-direction asymmetry (hommage owes accuracy to historical person; tombeau owes fidelity to transmitted form) + anonymous tombeau as third option + backward-only vs backward-and-forward asymmetry.
  • Pass 3 Gloss⇌Readings — Genette Palimpsestes (strict taxonomy: gloss/reading under métatextualité, not hypertextualité; path (a) acknowledged in §4 prose) + Auerbach Mimesis (methodological observation of chapter shape: gloss → reading modulation). Adds length asymmetry (gloss bounded by lemma, reading by thesis) + citation problem + summary-reading as maximally displacive third category + ARC default toward gloss as editorial posture.

Triptych closing material — the three axes line up canonically: centripetal (meditation+hommage+gloss; locally attentive, named in debt, host-serving) / centrifugal (reverie+tombeau+reading; associatively expansive, formally enacting, discourse-producing); diagnostic procedure for triangulating uncertain pieces. Non-convergence closing added: triptych is not exhaustive; additional axes emerge from corpus need, not anticipation.

Jurist iteration applied (3 concerns light-touch): (1c) M⇌R register-asymmetry signal as italicized preamble — analytical prose preserved verbatim; (2) apprentice/master claim reframed as "ARC reads the French tombeau lineage..." (provenance-honest framing as ARC's synthesis, not tradition's own self-described hierarchy); (3) illustrative-cases note tightened with explicit corpus-grounded vs hypothetical breakdown + Couperin H⇌T-vs-G⇌R parenthetical naming same-source-different-axis-work. Concern 4 verified clean (§3/§2 Annals sync n/a/n/a). Concern 5 + smaller notes deferred to Stage G cleanup.

Atomic commit + §7 housekeeping + §0 + frontmatter

15f8134 — spec(arc): Stage E continuation — content-typology §4 Overlap and Resolution authored. Pre-commit hooks passed. 2 files, +295 / −7. Pushed both remotes (Skemantix origin + GitHub github-backup). Branch is docs/spec-extraction-2026-05, now 26 commits ahead of main.

§7 in same commit:

  • Q2 Poem → RESOLVED 2026-05-20 (medium axis; cross-ref to §4)
  • Q12 Vespers → RESOLVED 2026-05-20 (class:reverie; cross-ref to §4 worked example)
  • Q14 Threshold Breath added — held with rationale (not a new type; emergence-watching per Q11 Louange pattern)

§0 Multi-axis Medium row extended: prose · image · verse.

frontmatter-specification.md §2.7 Medium ADDED 2026-05-20 — documents the medium: field with verse as first non-default value (cross-refs §4 and AldineXXI §II).

Returns + drift-patterns

7 returns logged in session-ledger-2026-05-20.md: wake / mempalace-baseline-wrong-branch / chamber-library-mine-attempts-missed / folder-moved-absence-asserted / carnet-vs-Harrison-anchoring / Manutius-single-voice-vs-synthesis / time-fabrication / typo-edit-boundary.

5 new drift-patterns named (KG claude-code entity, valid_from 2026-05-20):

  • wrong-comparison-baseline-treated-as-current
  • asserting-absence-from-non-presence-at-one-path
  • anchoring-on-most-recently-loaded-master-reference
  • over-anchoring-on-single-voice-when-synthesis-named
  • careless-edit-boundary-introduces-typo-in-untouched-text

Stage E continuation remaining (this afternoon, ~1h pause then resume)

  • Phase 1D Decision (ii) Colophon + Vignette register-marks rewrite (compositional; steward composes, executor registers; ~1-1.5h): collapse ## headings to :::register-mark ::: in content/pages/colophon.md (6 sections) + content/pages/vignette.md (5 sections, one rename needed for What the Vignette Must Not Do — candidates: Posture / Restraint / Indifference / Discipline / Constraint; steward composes). Plus §XII.b small note in AldineXXI-specification.md carrying the steward's verbatim sentence.
  • Phase 1D Decision (iii) Plex Mono mobile cascade fix (mechanical; ~15 min): _mobile-responsive.scss lines 137-145 — replace font-size: 0.9em / 0.85em with $font-size-sm * $plex-mono-scale. Reading-test on mobile after.
  • Phase 3A — Tags + glyph_id + glyph_confidence retirement (authorized 2026-05-19; mechanical sweep ~213 corpus posts + frontmatter-spec §2.4 row retirement + site.hs verification)
  • Phase 3B — navigation.yaml verify (5 min status check; retire if dead)
  • Phase 3C — Colophon $build_date$ + $git_commit$ Hakyll wiring (~30 min; pairs naturally with Phase 1D Colophon rewrite)
  • Phase 3D — Six corpus reclassifications (Heliotrope, Graffiti Girl, Dec 22 Bach, Death of a Hero, Matthieu Taliesin, Vespers — now confirmed class:essay → class:reverie per today's Q12 resolution)
  • Phase 3E — lex.html → about-page.html template consolidation (Stage E Gate 1 path b; ~1h)

Stage F (unblocked; for later sessions; unchanged from 2026-05-19 list)

Dwellings cluster route + ◧ Photo Essay glyph swap (3h); full ornament migration (4-6h); EXIF Tier 3 investigation (3-5h); first Photo Essay (steward composition, one afternoon); /vignette page rework (after §IX impl); about-cluster voice audit (gated on /vignette); vignette implementation Phase 1 (5-7 days); PDF/Print production wiring (2-3 days).

Stage G — unchanged

Jurist final review of full corpus → content-typology DRAFT → OPERATIVE.

Cleanup deferred-to-Stage-G from today's jurist iteration: Concern 5 (§6 Q6 placement); §1 Chamber strikethrough; Sequences-orthogonal closing register; Medium-axis sub-section title (handled today as "The orthogonal medium: axis — verse as first instance").

Pulling thread + literal question (for ~1h pause)

Pulling thread: Phase 1D — Colophon + Vignette register-marks rewrite + §XII.b spec amendment + Plex Mono mobile CSS fix.

Literal question: What rename works for Vignette's What the Vignette Must Not Do section in the §XII.b reassurance, not imperative discipline? Read content/pages/vignette.md content first; rename follows from what the section says, not from abstract noun-list. Candidates surfaced: Posture / Restraint / Indifference / Discipline / Constraint. Steward composes; executor as registrar.

2026-05-20 (afternoon + evening) — Stage E continuation closed; ADR-007 + Second Edition + §VII.h + Dream case record landed; Path B chosen for merge + deploy

13 commits landed today on docs/spec-extraction-2026-05, all pushed both remotes (origin Skemantix + github-backup). Branch at 04f9d8b, 26 ahead of main. Phase 3 fully closed. Phase 5 options A + B completed; C held with grief; D substantively done via this entry + the end-of-day record in plan-day-2026-05-20.md + the tomorrow plan in plan-day-2026-05-21.md.

Morning (pre-/clear)

  • 15f8134 content-typology §4 Overlap and Resolution authored. Genre-riddle resolved across three threshold cases: Meditation ⇌ Reverie (bounded/unbounded; both at ⊙); Hommage ⇌ Tombeau (speech-act sema vs form-enacted sema per Harrison Ch 5); Gloss ⇌ Readings (passage-subject vs work-subject per Genette/Carruthers). Threshold Breath resolved as not a new type; Q2 Poem resolved as medium: axis extension (verse first instance: Time is not a river); Q12 Vespers resolved as class: reverie.
  • 982fe7f Phase 1D register marks for Vignette + Colophon + §XII.b Posture subsection + Plex Mono mobile cascade fix. Vignette's What the Vignette Must Not Do renamed to Indifference. §XII.b Posture with steward's verbatim: "Register marks quietly remind the reader where they are, to let them see their place in the whole. A reassurance, not an imperative."

Unplanned mid-day insertions

  • 08f844a build-verify-deploy workflow doc (CLAUDE.md + rebuild-local target). Surfaced from a make dev deploy incident — structural mitigation for trust-prose-over-read-Makefile drift.
  • e06c77f §I.f term-gloss in list items takes colon (Hochuli + Sousa). Em-dash chavruta via chamber-typography palace direct query (40,896 drawers; not the default mempalace MCP). Findings: no master writes "use em-dash inside a term-gloss list item"; Hochuli §50 places en-dash on the outer bullet; Sousa demonstrates colon as the inner mark; Bringhurst index follows; Fowler agrees. AldineXXI §I.f table gains a new row codifying the rule. 16 colophon list items converted. Steward provided HF token mid-session for the chamber-typography palace's embedding model; saved to ~/.env.local (mode 0600).

Afternoon housekeeping (Phase 3) — all closed

  • 355757d Phase 3A — Tags / glyph_id / glyph_confidence frontmatter retirement. 252 files swept; 251 markdown updated. Contamination check surfaced two flags: (1) glyph_id had live consumers in templates + site.hs but the gate (hasGlyphField returns empty) was universally false — empirical render-test confirmed safe; (2) post.html lines 66-70 had an $if(tags)$ ... $for(tags)$ block but zero rendered HTML files contained <div class="tags"> — gate never fires. Both deletions verified safe pre-sweep. Frontmatter-spec §2.4 / §2.5 / §3 / §4 / §8 updated. Dead-template-code cleanup deferred to Vignette implementation arc.
  • 4adf04e Phase 3B — orphan navigation.yaml retired. Zero consumers; references slots no longer Compass-surfaced.
  • cf1bc99 Phase 3C — Site edition convention + colophon Build register wiring (ADR-007 authored). Significant scope expansion from morning's mere $build_date$/$git_commit$ wiring. Surfaced from the question "What exactly is 'Last build' counting as a build?" — leading to ADR-007: ARC carries a Site Edition in bibliographic register (Second Edition currently), lockstep with AldineXXI major version per editorial judgment; Cabal decoupled by design (no Haskell downstream consumer). Source of truth: /EDITION at repo root; Makefile copies into _build_info/edition. Hakyll reads via loadBody against match "_build_info/*" rule — dependency tracking is what makes colophon recompile when Makefile bumps the stamp. Stale buildVersion retired. About-enfilade compile path switched to chamberIndexCompiler so colophon can carry Hakyll template variables. Renders: Second Edition, build [hash] (date). Jurist iteration applied (Cabal decoupling reasoning; editorial-judgment paragraph; "non-major" precision; session-vocabulary glossed).
  • 272a4f2 Phase 3D — Five corpus reclassifications: Heliotrope (observation → meditation), Graffiti Girl (observation → reverie), Dec 22 (observation → meditation), Death of a Hero (essay → hommage), Matthieu Taliesin (essay → heteronym). Steward flag held: "3D will unlock more doors in the reading compass, be aware." Surface implication explicitly named: post-commit, five types (incl. Dream from yesterday) have first instances; Compass slots owed per (c); surfacing deferred to bundled Stage F session. Intermediate state acceptable per non-convergence.
  • 50c402b Phase 3E — lex.html consolidated into about-page.html (Stage E Gate 1 path b). Conditional breadcrumb absorbed (two-level About → Hearth → leaf for Hearth sub-pages without enfilade). About-enfilade compile path applied to all lares routings. Orphan template moved to docs/archive/templates/lex.html with README. SCSS audit flag added (body.lex-page selector already dead).
  • 6562411 desk.md drops enfilade: about. Steward catch during reading-test: desk lives WITHIN Hearth, not as sibling of about-cluster. One-line frontmatter edit; breadcrumb becomes two-level matching marks/posture.

Evening composition (Phase 5)

  • e76f0ad Phase 5 option A — 404 page per 2026-05-20 steward spec. Apparatus addition (not content type). Body: two elements — "No text at this address." + "Animal Rationis Capax" (return link). The return link rhymes with frontispiece title — same letterforms (EB Garamond small-caps, letter-spacing 0.1em) at h2 scale. The frontispiece is title-as-arrival; 404 is title-as-return. §VII.c link decoration stays — corrected mid-implementation per steward catch ("<a> styling is inconsistent with the rules"). Centered — corrected per steward catch on visual contact ("misalignment seems careless"; reversed spec's earlier "not centered"). New head_title template override field in default.html (3 places). Jekyll-era 404.md archived.
  • c45772c §VII.h 404 Page codified in apparatus-spec per jurist ("the spec is where the why lives so the what can be revisited without re-deriving it"). Follows §VII.c Links model. Load-bearing claim: 404 is the first apparatus page structurally derived from another part of ARC's architecture (the frontispiece); the page exists because the frontispiece exists. AldineXXI line 80 subsection enumeration updated.
  • 04f9d8b Phase 5 option B — §6 Dream case record as fifth retroactive ratification. Dream unique: type locked 2026-04-21 (earlier than the four cases the procedure was crystallised from), first-instance commitment landed 2026-05-19 same day as procedure's authoring. Master-reading verbatim: Jaccottet refused-reduction + Bachelard rêve/rêverie distinction. Steward practice-mechanics recorded as ABSENT — load-bearing; second case in §6 with this shape (alongside Reverie). §6 intro lightly extended.

Phase 5 option C — held

Hagen Quartett Hommage anticipation draft. "Deferred -- I'm still grieving." Held with care. Form will wait for grief's own pace.

Tonight's load-bearing decision: Path B for merge + deploy

Three paths surfaced for tonight's close:

  • Path A — merge + deploy today; Stage F follows in a second deploy event. "ARC deserves that much after this phase."
  • Path B — wait until Stage F closes the corpus-Compass gap; merge + deploy as one coherent reader-facing event.
  • Path C — merge today, deploy after Stage F.

Steward chose Path B. Rationale: the (c) Compass principle (locked 2026-05-19 in 2a2c195) + the Second Edition lockstep with AldineXXI v2 both honored at the same moment. The reader who first encounters Second Edition, build [hash] (date) should also encounter the Compass that the framework v2 commits to. Branch sits at 04f9d8b, 26 ahead of main. No merge tonight.

Drift patterns named today

  • Trust-prose-over-read-Makefile (resulted in 08f844a structural mitigation)
  • Audit-delta claim incomplete on dead-data fields (Phase 3A pre-sweep verification — two flags resolved by empirical render-test, not by trusting audit text)
  • Spec said NOT centered, eye said misaligned (Phase 5A 404 page — on-render evidence overrode spec draft)
  • <a> styling override created de-facto §VII.c exception (404 return link; steward caught; corrected: rhyme is in letterforms, not in suppressing link decoration)

Stage F (unblocked; not 2026-05-21 per the travel + taxes + rehearsal constraints)

Dwellings cluster route + ❦ Hommage + ⁂ Heteronym + ☾ Dream + Photo Essay ⊙→◧ swap (~3h focused, fresh-energy day); full ornament migration (4-6h); EXIF Tier 3 (3-5h); first Photo Essay (steward composition); /vignette page rework (after §IX impl); about-cluster voice audit (gated on /vignette); vignette implementation Phase 1 (5-7 days); PDF/Print production wiring (2-3 days).

Stage G — unchanged

Jurist final review of full corpus → content-typology §1 / §2 / §3 / §4 / §5 / §6 DRAFT → OPERATIVE; status-block reconciliation may anticipate this (Option β tomorrow if energy holds).

Pulling thread + literal question

Pulling thread: nothing pulls forcefully tonight. Branch at rest; Stage F waits; merge + deploy wait per Path B. Tomorrow's day-shape (travel Barcelona → Paris + taxes with Marie + 3h rehearsal) is not a Stage F day; light options in plan-day-2026-05-21.md (α Phase 6 wrap-up; β status-block housekeeping; γ Stage F prep document).

Literal question for next-Claude: How is the steward's energy after the morning's taxes filing with Marie — and what shape of work, if any, fits the afternoon? The day brings emotional weight (last taxes with Marie; sad). Default posture: responsiveness over advancement; closure + light maintenance over advancement.


2026-05-22 — β status-block housekeeping (single atomic commit)

Light Paris-day session executing β from plan-day-2026-05-21.md (status-block housekeeping). The day's energy budget closed cleanly at β + responsiveness; γ (Stage F prep document) deliberately not attempted per the day's don't push discipline. Path B (locked 2026-05-20 evening) continues: merge + deploy both wait for Stage F.

e7cd960 — spec status stamp reconciliation across 4 files (9+/9− lines)

Pure stamp work; no substance edits.

content-typology-specification.md:

  • Top Status block: name §3 Qualifying Marks Interaction AUTHORED 2026-05-19, §4 Overlap and Resolution AUTHORED 2026-05-20, §6 Change Policy AUTHORED 2026-05-19 (with the Dream case record addition note); promote §5 Code Binding Contract DRAFT → AUTHORED (substance recognized stable; the 9 contract clauses have been stable through Stage E without modification, so the stamp marks RECOGNITION not new AUTHORING — parenthetical clarifies)
  • §1 Type Catalogue header: DRAFT → LOCKED (14-of-14 types LOCKED individually per the table at line 113 onward)
  • §5 Code Binding Contract header: DRAFT → AUTHORED 2026-05-22 — substance recognized stable

frontmatter-specification.md:

  • Title: drop (DRAFT) suffix
  • Status: DRAFT → OPERATIVE 2026-05-22. The convention has been operational through the lex/canon/page retirements (2026-05-19, recorded in §2.1) and the §I.f-adjacent multilingual conventions. §1.1 reading guide already names the convention's evolving character — the "evolving" framing is intrinsic to the spec and needs no qualifier in the status stamp. Status line preserves original draft date for honest record: "OPERATIVE 2026-05-22 · originally drafted 2026-04-17".

AldineXXI-specification.md Companion Spec Index:

  • Content Typology row: bump Last-updated to 2026-05-22; expand Status to name §3 / §4 / §5 / §6 AUTHORED dates
  • Frontmatter row: bump to 2026-05-22; OPERATIVE (originally drafted 2026-04-17)

ARC CLAUDE.md companion-spec orientation:

  • mirror the same two updates in the two orienting bullets

The scope-expansion moment — Live-State Discipline at work

Steward authorized four edits initially. Verification before committing surfaced four stale cross-references in orienting docs (the AldineXXI Companion Spec Index + the ARC CLAUDE.md companion-spec bullets). Surfacing was honest, not silent: "Two stale cross-refs surface as inevitable follow-on from the four edits — including them keeps the corpus internally consistent (Live-State Discipline). Question: include in the same atomic commit, or commit the four authorized edits now and do the cross-refs as a follow-on commit?"

Steward chose "single atomic commit". This is Live-State Discipline at its proper scope: when status stamps change, the corpus cross-references mentioning them become stale in the same moment. Splitting the commit would create a window where the corpus contradicts itself. The surfacing-and-asking pattern preserved both Live-State Discipline AND steward authorization gate.

Decisions explicitly NOT made

  • γ Stage F prep document — energy budget closed at β + responsiveness; γ would have been pushing. Held for a fresh-energy day where its structural-thinking load is welcome.
  • No push of e7cd960. Path B carries. The single deploy event remains the goal: merge + deploy both wait for Stage F so the (c) Compass principle + Second Edition lockstep are honored at the first reader-facing event.
  • Audits (_audits/*) and ADRs (decisions/*) NOT modified. These are dated artifacts that record state-as-of their authoring date; retroactive editing would betray the document type. Cross-ref reconciliation scope was limited to ORIENTING docs.

MemPalace status checks (bracketed the day)

Two status checks of the MemPalace repo bracketed the day's work.

Morning (steward prompted from Paris taxi): #1440 (bash 3.2 mapfile) + #1538 (120 GiB upsert) both merged to develop 2026-05-19; develop +143 since v3.3.5; no release-prep branch yet; #1539 audit revealed same crash class at 4 more sites (incl. tool_diary_write); #1569 OPEN to fix all 4. Yesterday's decision (wait for release) confirmed defensible.

Evening (post-commit): develop +13 since morning. #1540 MERGED with partial CHUNK_SIZE coverage (branch name fix/1539-three-unbounded-upsert-sites — audit pathway + ~3 sites). #1569 still OPEN + CONFLICTING for the remaining 4 sites; needs rebase. tool_diary_write exposure remains live on the current release. Three new PRs opened overnight (#1577/1578/1582) — more in-flight, not fewer. Honest read: closer on the class-of-failure, not appreciably closer on release.

Branch state at session-end

docs/spec-extraction-2026-05 at e7cd960, 27 commits ahead of main, 1 ahead of remote, working-tree noise expected (pre-existing font-backup directories untouched). NOT pushed by design.

Pulling thread — unchanged

Stage F dwellings cluster session is what the branch waits for. Today added one more reason: with frontmatter now OPERATIVE and §5 Code Binding Contract now AUTHORED, the spec corpus's class: enumeration contract has earned more weight. Stage F's five new Compass surfacings (☾ Dream, ❦ Hommage, ⁂ Heteronym, ⊙ dwellings for Meditation + Reverie, ◧ Photo Essay swap) must honor that contract.

Literal question for next-Claude

When the steward next checks in, is the day shaped for Stage F (~3h focused) — or another fragmented day where β-style closure-and-maintenance is the right posture? Secondary: has MemPalace cut chore/release-3.3.6-prep?


Brief Paris fresh-energy ~40-min session immediately after the morning β wrap (~42 min gap). Symmetria init deliberately skipped per brief-pause discipline. Two commits landed; one near-miss surfaced + corrected in record; one new feedback memory + one new KG drift pattern.

What landed

Scout commit 3834713 — docs(arc): Stage F touchpoints scout — pre-γ enumeration. 179 lines in docs/AldineXXI-Codex/drafts/stage-f-touchpoints-scout-2026-05-22.md. Posture: scout-don't-structure. Pure factual inventory:

  • The 5 Stage F surfacings: ☾ Dream, ❦ Hommage, ⁂ Heteronym, ⊙ dwellings (Meditation + Reverie compound), ◧ Photo Essay glyph swap
  • Corpus first-instance verification via grep '^class:' content/posts/*.md: all 5 have corpus instances. Tombeau (▽) correctly absent — zero instances. Hommage ❦ ships — Death of a Hero (2016-03-05) is the class's first instance; the deferred Hagen Quartett Hommage is a second-instance authoring concern, not class-existence. (c) Compass principle holds on Stage F landing.
  • Per-surfacing touchpoints: site.hs lines, default.html:74-85 Compass positions, SCSS expectations (none for Compass additions). Model for Dream/Hommage/Heteronym listings: create ["glosses.html"] at site.hs:820-834 (~14 lines per new listing). Dwellings is structurally distinct — no exact model.
  • 6 open questions deliberately deferred to γ + Stage F: Compass sigil ordering · dwellings route shape (single vs separate) · classRouteName behavior post-dwellings · dwellings page internal structure · URL convention (.html vs /) · footer-compass retire-vs-reconcile

§4.1 patch commit 3dbe94e — docs(arc): patch Stage F scout §4.1 — honest scope on footer-compass.html. Follow-on commit (not amend) preserves drift + correction in record.

The scope-correction moment — wider-grep before acting

Steward authorized a "5-min mechanical" footer-compass.html cleanup based on the scout's §4.1 finding that the file was unreferenced. Instinct fired to wider-grep BEFORE acting as a safety pass. The original §4.1 had claimed "Verified via grep -rn footer-compass templates/ site.hs — zero references." The wider grep told a different story.

Seven planning + spec doc references name the file as Stage F's disposition site:

  • docs/decisions/2026-05-16-type-applicability-matrix.md:130 (ADR-006 v2) — Stage F implementation-alignment target
  • docs/AldineXXI-Codex/_audits/audit-delta-2026-05-19.md:221 — verbatim "Orphan template ... Stage F housekeeping"
  • docs/AldineXXI-Codex/_audits/arc-state-survey-2026-05-16.md:141 — edit action treating file as live (add ✎ Gloss + ☞︎ Readings)
  • docs/AldineXXI-Codex/_audits/spec-corpus-audit-2026-05-16.md (4 refs) — spec/spec/implementation three-way drift conversation
  • docs/AldineXXI-Codex/AldineXXI-specification.md:2559 — .footer-compass selector index entry
  • docs/AldineXXI-Codex/apparatus-specification.md:464 — §VII .whisper migration prose references "footer-compass paragraphs"
  • docs/AldineXXI-Codex/silence-and-rhythm-specification.md:296 + docs/AldineXXI-Codex/chavrutas/2026-05-08-completion-survey.md:264 — chrome-vs-body horizontal-center open concern

Held the delete. Surfaced honestly with three options: (a) hold for Stage F, (b) atomic propagated commit (β-shape, not 5-min), (c) patch the scout instead. Steward chose (a) + (c).

The patched §4.1 names the seven references, explains why premature deletion would shortcut conversations (selector-index dangling at AldineXXI:2559, apparatus-spec §VII migration prose forced into stale fix-up, chrome-alignment open concern's reference anchor severed), and acknowledges the drift family explicitly. The two-commit sequence (original + patch) preserves the discipline working in record — future readers see both the original scope-limited claim and the honest correction, not a silently rewritten history.

New KG drift pattern + new feedback memory

KG: claude-code → drift-pattern → unreferenced-by-code-claim-on-narrow-grep-scope (valid_from 2026-05-22). Sibling of trust-prose-over-read-makefile (2026-05-20) and audit-delta-claim-incomplete-on-dead-data-fields (2026-05-20). Lesson: before claiming X is unreferenced / dead code, widen grep beyond code surface (templates, .hs, .scss) to include planning docs, audits, specs, ADRs. "Unreferenced by code" ≠ "dead"; planning docs are part of the reference surface.

Feedback memory: feedback-methodology-docs-scope-question.md per steward flag "I am not sure that those should live there as they touch my personal workflow with you" re the 2026-05-18 audit cluster (jurist-brief + jurist-shape-review + prime-directive-elaboration) currently untracked in ~/_Dev/CapableMind-AI/docs/thinking/David/methodology/. CapableMind-AI is co-authored with Seb; methodology / continuity-skill docs about personal workflow with Claude may belong somewhere else. Scope is open; surface before auto-filing.

Returns this session — both structurally clean

  1. R1 (early): Proposed Plex Mono + Vignette rename without checking commit history. Steward corrected ("pretty sure 1 and 2 closed"). Returned by reading git log + verifying via commit 982fe7f "Phase 1D register marks for Vignette + Colophon + §XII.b Posture + Plex Mono mobile fix". Named in real-time as trust-prose-over-read-makefile sibling.
  2. R2 (late): The footer-compass cleanup near-miss above. The wider grep was a natural safety check — discipline operative without prompting.

Decisions explicitly NOT made

  • footer-compass.html disposition (retire vs reconcile) — Stage F's choice; not pre-decided. Both are coherent.
  • Methodology files commit — scope-undecided per new feedback memory; steward needs to surface where personal-workflow docs should live before bundling.
  • γ Stage F prep document — 40-min window not the right fit for 60-75 min structural-thinking. Held for fresh-energy day; now sits on top of scout enumeration when chosen.
  • Push of docs/spec-extraction-2026-05 — Path B continues.
  • No amend to commit 3834713 — chose two-commit sequence so the drift + correction record visibly. Future scout work benefits from seeing both.

Branch state at session-end

docs/spec-extraction-2026-05 at 3dbe94e, 29 commits ahead of main, 3 ahead of remote, working-tree noise (pre-existing font-backup directories untouched). NOT pushed by design (Path B continues — merge + deploy + push all travel together with Stage F to honor (c) Compass principle + Second Edition lockstep at first reader-facing event).

Pulling thread — unchanged but substantively enabled

Stage F dwellings cluster session. With the scout now in hand, three coherent next-move shapes exist:

  • β-style fragmented day — closure + light maintenance; scout sits on target (the morning's posture)
  • γ Stage F prep document — 60-75 min structural-thinking; the scout's 6 open §5 questions ARE its agenda
  • Stage F directly — ~3h focused; accepts holding some §5 questions in flight; closes the branch

Ranked by structural-thinking load: β < γ < Stage F. The day-shape determines the choice.

Literal question for next-Claude

With scout in hand, what's the right next move-shape — γ (60-75min decides scout's 6 §5 questions), Stage F directly (~3h, accepts holding some §5 questions in flight), OR another fragmented day where β-style closure is the right posture and scout sits on target?

Secondary check at wake: has MemPalace cut chore/release-3.3.6-prep? Has #1569 (the 4 crash sites incl. tool_diary_write) been merged? Movement here changes the MemPalace upgrade posture.

2026-05-23 — Stage F γ: the six §5 questions settled + §0 navigation principle (68b7a9a)

After /wake-up the L1-await thread was superseded by the steward ("concentrate on ARC while we wait for Seb"). The γ session settled all six §5 scout questions as reader-grammar judgments (executor surfaced + recommended; steward decided):

  • Q1 Compass order, 13 points: ● ○ ◈ ◉ ◧ ⊙ ☾ ⁂ ❦ ✎ ☞︎ ☷ ✍︎ (◧ takes Photo Essays; ⊙ → Dwellings; ⊙☾ adjacent, cosmological pairing)
  • Q2 single /dwellings.html (the cluster IS the surface)
  • Q3 classRouteName meditation/reverie → dwellings (verify breadcrumb-only at build)
  • Q4 mixed-chronological + the Annals .post-type per-item indicator
  • Q5 .html throughout
  • Q6 retire footer-compass.html + propagate
  • §0 navigation principle: all ARC nav = Reading Compass (global) OR enfilade (cluster-local); no footer-level nav
  • + Annals "Browse by Type" removal, grounded in §0 (Annals = when, Compass = what; discovery-by-exploration, not a labelled map)

γ-doc stage-f-decisions-2026-05-23.md committed 68b7a9a. Implementation deferred (steward shifted to L1 when Seb's work surfaced); γ-doc §2 is the build map.

2026-05-25 — Stage F implemented + The Tree north-star + spec propagation + Second Edition PUBLISHED

Executed the γ-doc end to end, surfaced a foundational orientation doc mid-stream, propagated the spec corpus, and shipped Path B. The Second Edition is live.

Stage F implementation (70232ca, one atomic commit, 14 files):

  • Coupled core: ◧ Photo-Essay glyph swap; ⊙ dwellings compound route /dwellings.html (5 meditations + 1 reverie, recentFirst over the concat); post-list.html .post-type span gated by a per-item show-post-type flag. (Bug caught at local verification: the flag set on the page context was invisible inside the $for(posts)$ loop — composed into the item context instead. Build-before-commit earned its keep.)
  • Three simple listings: /dreams.html ☾, /heteronyms.html ⁂, /hommages.html ❦ (one first-instance each → (c) principle holds).
  • Compass rewritten to the 13-point order; breadcrumb remap meditation/reverie → dwellings, verified breadcrumb-only (classRouteName → class_route → post.html breadcrumb; piece URLs are slug/path-based, untouched).
  • Nav cleanup: orphan footer-compass.html deleted; Annals "Browse by Type" stripped.

The duplication catch → The Tree. The homepage Compass had silently drifted to nine points because it was declared twice (default.html + frontispiece.html). The steward challenged the instinct to just sync both copies — "un-Alexandrian… a clear example of a hasty decision taken in the past." Resolved by extracting templates/reading-compass-points.html (ARC's first $partial): one source, two wrappers. That pulled up a foundational principle, captured in drafts/the-tree-north-star-2026-05-25.md — the parent orientation under which the SCSS cascade north-star sits as a child: a surface simplicity faithful to the complexity beneath, at every layer (page / spec / SCSS / Hakyll). Grounded across the steward's vault (Prime Directive, Temporal Heirship, Geology of Ethics, the Library charter; Harrison's ligature, Vico's verum factum, Alexander), the steward's articulation preserved verbatim at its center. Seeded the future Hakyll-simplicity north-star (child #2) with two findings: the compass duplication, and the ten near-identical listing create blocks.

Spec propagation (Live-State Discipline). §VI table 9 → 13 + the §0 navigation principle authored + pending-reassignments → landed + governed-but-unsurfaced now only Tombeau. §VI.b, the summary table, and §VII.g colophon reconciled count-neutral, retiring the superseded "eight-sigil / eight-point rose" framing per the (c) decision (2026-05-19, 2a2c195) — recovered from the memory files, not MemPalace (the L1-fraught window had cost that drawer; the steward flagged it). The naming question ("is 'Reading Compass' a poor choice?") resolved KEEP — grounded in orientation + measure (com-passus → μέτρον) + to encompass; it is the steward's own Prime-Directive metaphor ("the System's Compass"). A new §VI "On the name" note inoculates against the rose-rationale recurring. CLAUDE.md §VI + ADR-006 §4.1 propagated; apparatus-spec / silence-rhythm footer-compass references cleaned.

Elevated follow-up: per-glyph Compass optical-size normalization (.compass-point) — the spec already mandates it (§VI rendering rules); thirteen glyphs expose the disparity. Logged in the SCSS north-star, flagged ELEVATED.

Path B executed — Second Edition published. FF-merge branch → main (43 commits), pushed origin (Gitea) + github-backup, make rebuild → CloudFlare Pages (675 files) + GitHub mirror. Verified live on animalrationiscapax.org: 13-point Compass, /dwellings → 200, 5 meditation + 1 reverie labels. Source main stays clean at 70232ca (the deploy's compiled-site commit lives only in the mirror). ~6 weeks of branch work, dark since April, now the reader's first encounter with the Second Edition — (c) principle + Second Edition landed together, which was Path B's whole purpose.

Where ARC stands. Stages A–E done; Stage F: dwellings/Compass shipped and published; remaining — glyph optical-sizing (elevated), content-types.yml generator, per-piece marginalia render, vignette Phase 1 renderer, the audit(s) [SCSS cascade + the new Hakyll-simplicity layer + code-represents-spec]. Stage G (jurist review → content-typology DRAFT → OPERATIVE) closes the arc. Now on main; next work branches fresh.

Returns: R-build (verification caught the show-post-type scope bug pre-commit); R-framing (the steward's challenge redirected a hasty fix-both into the durable partial extraction — the loop load-bearing, and the Tree doc is its fruit). Both strengthened the whole.

2026-05-26 — CONSIDERATION raised then CLOSED (same session): is IBM Plex the best sans/mono partner for EB Garamond?

RESOLVED — Plex stays; no swap, no test setup. Steward's decision after the read below: "I'm clutching at theoretical straws and forgetting that the dissonance is actually serving the larger whole." The key reframe that settled it: in ARC the sans/mono are functional registers, not reading faces — Plex Sans is nav-only ("the Guide"), Plex Mono is apparatus-only ("the Precision," locating-not-dwelling); EB Garamond does all the dwelling. So the Renaissance-serif × machine-age-functional-faces contrast is not a flaw being tolerated — it is the AldineXXI thesis made typographic (16th-c. press, 21st-c. apparatus). Alegreya Sans (warm, characterful, drawn for the Alegreya serif) would pull the chrome toward personality and blur the text/apparatus signal — likely a regression on the exact thing the type system does. Commit Mono was the one defensible lateral (neutral apparatus + would fix the current single-weight/no-italic Plex Mono gap) but not worth re-founding a just-published edition. Do-once held: a register that shipped days ago needs a felt reason to change, not a hypothetical. The corrected setup spec is preserved below should it ever genuinely reopen — but the question is answered, not parked.

Original capture (kept for the spec corrections; superseded by the resolution above) — steward initially chose "capture as to-do." The open question: EB Garamond is ARC's serif (the Storyteller); IBM Plex Sans is the nav/Guide register, IBM Plex Mono the apparatus/Precision register. Is Plex the right companion, or would a warmer humanist pairing sit better against Garamond? Candidates to test locally, side-by-side with Plex (not replacing it): Alegreya Sans (Huerta Tipográfica — humanist, designed as a companion to the Alegreya serif) for sans; Commit Mono (Eigil Nikolajsen) for mono.

The intended shape (test-only, additive, reversible): make both pairs available simultaneously on a local build; steward swaps $sans-family/$mono-family to the --test candidates manually to compare rendered results. Do not touch nav/apparatus CSS assignments; do not remove or comment out the Plex @font-face or the live variable values.

Corrected spec (verified against live repo 70232ca, 2026-05-26 — the original CC instruction's path/build guesses were off):

  1. Font files → static/fonts/alegreya-sans/ (AlegreyaSans-Regular/Italic/Medium .woff2) and static/fonts/commit-mono/ (CommitMono-Regular/Italic .woff2). Serving confirmed: Hakyll routes static/** → root, so static/fonts/X/ resolves at /fonts/X/. Acquisition caveat: the GitHub repos (huertatipografica/Alegreya-Sans, eigilnikolajsen/commit-mono) ship OTF/TTF, not WOFF2 — expect a TTF→WOFF2 conversion step (woff2_compress / fonttools). Both are OFL/free; bundling is fine.
  2. @font-face declarations → scss/main.scss (alongside the existing Plex/Garamond block at lines 54–162). The instruction was right about this file. Mark them // --- TEST CANDIDATES (2026-05) ---. Use font-display: swap.
  3. Test variables → scss/AldineXXI/_variables.scss (lines 39–40, where the live $sans-family/$mono-family !default actually live — NOT main.scss as the instruction guessed; the main.scss.backup that contains them is stale cruft). Add immediately below, commented:
    // TEST CANDIDATES — swap into $sans-family / $mono-family to compare (2026-05)
    $sans-family--test: 'Alegreya Sans', system-ui, sans-serif;
    $mono-family--test: 'Commit Mono', 'Courier New', monospace;
    
    Leave the live $sans-family/$mono-family pointing at Plex. The swap is the steward's one-line manual change at review time.
  4. Verify build → make rebuild-local then make serve (port 8000) — repo is stack-based, not cabal run site -- watch; SCSS compiles via the sass binary (--load-path=scss). Confirm the new WOFF2 load 200 in devtools; no visual change until the steward swaps.
  5. Report → confirm paths, declarations, clean serve; note the live variable file/line so the steward can swap manually.

Non-blocking, off the Stage F critical path. Picks up whenever the steward wants the comparison rendered. (Pre-existing untracked static/fonts/eb-garamond/_backup_2026-05-15* dirs are unrelated cruft, not part of this.)

2026-05-26 — Compass optical-sizing → inline-SVG migration (the ELEVATED item RESOLVED + DEPLOYED LIVE); Gloss ✎→¶

The ELEVATED Stage F item is done and live. Commit e1d0f12 on feat/compass-svg-proof → FF-merged to main → pushed origin+github-backup → make rebuild → CloudFlare + GitHub mirror → verified live on animalrationiscapax.org (essays + homepage: sprite, 13 <use>, pilcrow, no fallback).

Root cause of "our numbers never made any difference" (steward's report on the per-glyph font-size optical hacks): not a cascade override. Three real causes, found by measuring the fonts (fontTools cmap check): (a) 11 of the 13 sigils are not in EB Garamond (only ❦ U+2766, ☞ U+261E) — they rendered from uncontrolled OS fallback, so font-size can never optically equalize a row of heterogeneous fonts and isn't portable across devices (the comment claiming "serif for optimal symbol shape" was false); (b) the hacks were duplicated across .reading-compass (_compass.scss) and .frontispiece-compass (_frontispiece.scss) — editing one while viewing the homepage changed nothing; (c) stale to Stage F (Chamber rule orphaned, [href*=archive] dead vs /annals.html, 6 new glyphs unstyled).

Resolution — all 13 sigils → inline SVG. One hidden <svg> sprite of <symbol>s in the single-source partial templates/reading-compass-points.html, consumed by both compasses via <use>. Optical balance lives in each symbol's viewBox; size is one rule (.compass-point .sigil); line weight is one knob (stroke-width on .sigil). fill:currentColor → dark-mode free. The two duplicated per-glyph blocks were deleted (~116 lines) — the Tree-north-star consolidation, realised. SCSS north-star entry marked RESOLVED.

Sources (final): ● ○ ◈ ◉ ◧ ⊙ ☷ ☾ drawn natively as SVG geometry (☾ a drawn crescent — steward preferred it to the font's); ❦ ☞ ¶ extracted as real EB Garamond outlines (fontTools SVGPathPen+BoundsPen; flip y; frame to ink bounds; center+scale into 0–100 viewBox); ⁂ = three composed Garamond asterisks; ✍ (About) = lifted URW base-35 D050000L (fontforge→OTF; U+270D = glyph a14). ▽ Tombeau symbol in reserve.

Glyph reconsideration (✎/✍). Tried URW lift → drawn pencil+hand (pencil fine; hand collapses to a blob at 18px — assessed honestly as the weak mark) → icon fonts (Lucide/Tabler/Phosphor — steward: dissonant, a UI idiom against the typographic row). Landed, with steward, on the typographic answer: Gloss → ¶ (the capitulum — "the marginal mark of the gloss tradition," grounded in ARC's own spec heritage: AldineXXI lines 2178 "capitulum/paragraphus" + 1530 "continuous gloss apparatus"); About → keep ✍ (lifted URW, the one borrowed mark — the apt symbol, well-rendered). Constraint map that ruled out alternatives: †‡ = footnote markers (taken), § = "see section" (taken), ❧ hedera + ◊ lozenge = explicitly RETIRED (§IV 2026-04-22), ☞ ❦ ⁂ ◉ already Compass glyphs.

Licensing (corrected in-session): first asserted URW = "AGPL+font-exception"; reading /opt/homebrew/share/ghostscript/fonts/COPYING showed GPLv2, no font exception. Risk accepted minimal (steward's call): typeface designs aren't copyrightable, only font software is, and it's GPLv2 not AGPL — for the single ✍. macOS ZapfDingbats is Galapagos (proprietary) — not shippable.

Spec propagation (✎→¶): content-typology §1 (type table, Gloss entry, status table, both pairing passages), AldineXXI §IV disposition note + §VI sigil table + §VII reserved-glyph list, ARC CLAUDE.md sigil table, SCSS north-star. Gloss/Readings pairing recast read/write → annotator (¶) / reader (☞) per steward. Dated audits/drafts/archives left as historical record.

Returns: R1 — asserted a font license from memory, not from the file; corrected by reading COPYING (the steward's "how do people use these as emoji?" re-grounded the whole question — symbol/design free, only font software licensed). R2 — honest restraint held (drawn hand named as the weak mark, not oversold). Discipline: render-and-look (Chrome-headless → Read PNG, on my own SVGs and the candidates) + measure-the-real-font (Apple Symbols proportions, Garamond coverage) instead of guessing.

Follow-on (minor, deferred): aria-label-per-link a11y on the compass (links now rest on title; SVG is aria-hidden) — on the spec accessibility audit list, not blocking. Reusable method recorded: fontTools extraction from EB Garamond for any typographic sigil; fontforge for Type1 (URW base-35).


2026-05-28 (evening) → 2026-05-29 — vignette spec landed (jurist pass) + code-represents-spec audit + Hakyll north-star

(Tracker was current through 2026-05-26; this catches up the 2026-05-28 evening + 2026-05-29 arc. Per-session detail in the session memory files.)

2026-05-28 (evening) — content-types.yml generator landed (a9dc188); vignette spec revision brief drafted (438ee03, Shape C: Claude Code as Phase-α engine, /vignette skill as codified discipline, interface contract as α→ω bridge). Detail: session-2026-05-28-evening-arc-stage-f-vignette-scoping.md.

2026-05-29 — Vignette spec open questions settled (drafts/vignette-decisions-settled-2026-05-29.md, d2ca4b0): dark mode mode-aware / genome-mode-independent · reduced-motion breath-stops · cycle-end hold-at-endpoint · keep Phase α/ω. Jurist revision landed canonical at vignette-specification.md (c52fb69) — sharpened the dwell-test (first prototype = mandatory Claude.app pass, against unfelt error), the transition trigger (+ L1-stability precondition), the cycle-end clamp (enforces the luminance palette bound), and surfaced the Phase-1 orientation-preserving luminance constraint (a dark-mode bug invisible to visual review — must be tested against semantic orientation, not "does it look right").

Steward reframed sequencing: audits before the vignette build (completion + Alexandrian idiom + do-once; Phase 1 is audit-insulated but the deeper reasons hold). code-represents-spec audit run (spine = content-typology §5 Code Binding Contract; _audits/code-represents-spec-audit-2026-05-29.md, b15684a) — §5 largely honored; two gaps: clause-2 gloss listing glyph drift FIXED (164d8c3 ✎→¶; root cause "declared twice" → Hakyll audit), clause-3 silent wildcard fallback → ships-with-Stage-G (the spec's own deferred enforcement). Clauses 1/4/5/6/7 pass; 8/9 forward-looking (eligibility machine-verified vs §2). No spec-gaps → Stage G promotion unblocked. content/chamber/** recorded as intentional v1-legacy (the deferred presentable-cluster to-do), out of clause-1 scope.

Hakyll north-star written (drafts/the-hakyll-north-star-2026-05-29.md, d714a11) — sibling to scss-cascade-north-star, child of the-tree. The build reads content-types.yml as single source rather than re-encoding it: add a type = add a YAML row. Centerpiece = collapse the ~12 near-identical listing create blocks into one generator over the table; single-source class→glyph; case-statements → table lookups (unknown = build error). This is where code-represents-spec clauses 2 & 3 get their durable, structural cure. CLAUDE.md Hakyll version corrected 4.16.2.1 → 4.16.6.0 (7bc2a8a; resolver-pinned note added).

State: ARC main @ 7bc2a8a, 8 ahead of origin (local-only by directive). Stage F remaining: the two Alexandrian audits (Hakyll-simplicity + SCSS-cascade, both north-stars ready) → then the plan to complete the composition work + write/test the vignette system (Phase 1 insulated, post-audits) → Stage G (jurist → content-typology OPERATIVE, fed by the code-represents-spec gap-map) closes. Pulling thread: run the two audits tomorrow.


2026-05-30 — Both Stage-F audits run; three reconciles; the Stage-F-closing plan (vignette → F+1)

Both Alexandrian audits written — gap-maps (verified/inferred per finding; cleanup/table-truthful-first; execution staged, not paper-committed). Commit d230ab1.

  • SCSS-cascade (_audits/scss-cascade-audit-2026-05-30.md): diagnosis = partials cut by page-area, the dream wants scale → _utilities dissolves, _post/_base split, _layout/_navigation reclaim, _syntax rises, _dark mostly-vestigial, _chamber quarantines (block 2). Steward decoupled lean vs clear: cleanup makes it lean; re-partition makes it clear (line-neutral, source-order risk). Execution = cleanup-first (committed) → re-read gate → re-partition (empirical, conditional).
  • Hakyll-simplicity (_audits/hakyll-simplicity-audit-2026-05-30.md): FEASIBILITY GATE CONFIRMED against unpacked 4.16.6.0 source (create/match :: … -> Rules () -> Rules (); Rules is a monad; preprocess :: IO a -> Rules a; codebase already parses YAML). 11 near-identical listing blocks → one generator over content-types.yml. Found a dead disabled-glyph system still in postCtx, and table-vs-build drift (§4D).

Three reconciles (drift the audits surfaced):

  • Compass surfacing (ab89d65): §2 marked dream/heteronym/hommage/reverie governed-but-unsurfaced while the build (live create blocks) + corpus (1 instance each) had them surfaced. Steward confirmed + ruled reverie = surfaced. Fixed §2 → surfaced (tombeau stays — no instance); regenerated YAML; content-types-check green; diff scoped to the 4 fields. §VI/cross-spec count (now 13 + Annals) → Stage G.
  • titleClasses → user-visible [FIX] (dea751a): showTitle (post.html <h1>) gated on {essay,meditation,chamber} while 10 types are title_display: shown → gloss/readings/dream/heteronym/hommage/reverie rendered title-less, against spec. Expanded to the shown-set (stopgap; durable = table-driven lookup in the generator). Verified via rebuild-local (six regained <h1 post-title>; not-shown types unchanged). Third clause-2-family instance.
  • ADR-006 stage tracker (990c67d) — see the rule below.

⚠ THE STAGE-E FIASCO → STANDING ANTI-DRIFT RULE. Steward caught me repeatedly invoking "Stage E discipline." Verified: Stage E was closed + MERGED (c480b09 "peer-spec propagation" → 2a2c195 "hardening" → 558f9f3 "post-Stage-E live state") — but ADR-006's stage tracker was frozen at authoring-time (only Stage A ✓ DONE; closing line still "Stage B begins next session"). A record gap, not a work gap; my hedge had anchored on the stale 2026-05-19 audit-delta snapshot. Reconciled by adding a dated stage-status block to ADR-006 Part 5. RULE (now standing): ADR-006 Part 5 is the canonical stage tracker; this file mirrors it; when a stage closes, update BOTH in the same move. Also corrected the mislabel — the "regenerate spec+YAML together" rule is the matrix-as-canonical / YAML-as-shadow invariant (ADR Part 4, permanent), not Stage E.

Stage-F-closing plan (drafts/stage-f-closing-plan-2026-05-30.md). Two steward decisions: vignette Phase 1 → F+1 (not part of closing F); §II.d marginalia render = SCSS not site.hs (rides :has(), already in use → folds into the SCSS track). Collapses to two tracks + quick wins: Phase 0 (titleClasses [FIX] ✓; SCSS RETIRE) · Phase 1 SCSS cascade (incl. the :has() marginalia-composition gate) · Phase 2 Hakyll build (table-driven lookups; retire dead glyph; the generator) → F closes → Stage G (jurist) → F+1 (vignette). Marginalia scoped: current grid is unconditional (empty asymmetric = the "unearned gloss-form"); fix = gate on :has(marginalia), symmetric by default; the §II.d double-center concern is spec-deferred (out of scope).

CANONICAL STAGE STATUS (mirror of ADR-006 Part 5, as of 2026-05-31): A–E DONE + merged · F in final items — Phase-1 SCSS cleanup DONE (2026-05-31); remaining = Phase-2 Hakyll generator · M (mode modernization) pulled forward from F+1 (between F and the full re-partition) · full re-partition now follows M (theme-free ground) · G pending (jurist promotion; carries the §VI count). Macro-sequence: F Phase-2 → M → re-partition → G → F+1 vignette. Keep this line in step with ADR-006 Part 5 — the anti-drift rule above.

State (midday): ARC main local-only (was 8 ahead; +d230ab1 audits · ab89d65 surfacing · 990c67d ADR reconcile · dea751a titleClasses fix · 90802a6 plan).

Afternoon (same session): Phase 0 RETIRE (5f4c27e — ~190 dead SCSS lines: voice colours/$enable/metadata/15 mixins; byte-identical CSS, zero render) → Phase 1 DEDUPE (dfff604 blockquote/enfilade/small-caps, per-selector-diff verified) + small-caps drift fix (192423e — one small-caps, footer font-variant→SC face) + token rename (9156522 — $sidenote-size→$marginalia-register-size to _variables). Then MODE-MECHANISM MODERNIZATION DECIDED (4e4f700; drafts/mode-mechanism-modernization-2026-05-30.md) — the thing the steward had circled: drop the toggle, adopt the system via color-scheme+light-dark() (pure CSS, zero JS, no FOUC), +P3 wide-gamut +prefers-contrast; principle = honor the reader's environment, never ask them to re-declare it (the font-size-percentage posture generalized); founds the vignette (F+1); SHELVES the dark→var MIGRATE (superseded — light-dark deletes _dark+scattered blocks wholesale). 10 commits; ARC main 19 ahead, local-only, clean; nothing deployed. Revised pulling thread: Phase 1 FIX (:has() marginalia-render gate + §I.h blockquote fix + stale compass @extends + compass a11y) → re-read gate → Stage F closes (all theme-independent; mode rework is F+1).

2026-05-31 — Phase-1 FIX items landed + mode modernization PULLED FORWARD (Stage M)

Session shape: woke into the confirmed Phase-1-FIX pulling thread; closed all of it; steward then decided to pull the mode modernization forward. 4 commits, ARC main ahead 23, local-only, clean, nothing deployed.

Committed (all verified; gate+glimpse+compass-a11y confirmed on the steward's physical phone, a11y via VoiceOver):

  • b228f47 — removed stray _layout.scss.bak (240 dead lines, 11 months old in live tree).
  • 913aaea — §II.d :has() marginalia-render gate (the substantial Phase-1 FIX). Grid renders only when a piece carries marginalia; no-marginalia pieces compose symmetric, body centred at 38rem (spec L260 read verbatim — NOT 720px; .page-content's 720 was the wrong fallback). Symmetric base + :has()-gated grid (wins by specificity) + glimpse guard (max-width:none). Verified desktop + phone.
  • f390b5d — glimpse phone full-bleed fix (pre-existing LIVE bug; steward confirmed on phone). Root cause = TWO clips on the 100vw+negative-margin burst at ≤767px: the parent <figure> (overflow-x:auto → clip+scroll) AND .wrapper/.page-content/main (overflow-x:hidden → clip). Both must open together (figure-only=padded; wrapper-only=padded+scroll), scoped body.glimpse-page + .glimpse figure. Took 3 attempts — two wrong diagnoses first (reasoned from a comment; then asserted the wrapper was the sole clip) before reading the full ancestor chain. Lesson reinforced thrice this session: read rendered output / full DOM chain before asserting a CSS causal mechanism.
  • 02393bc — compass §3F + §3G (one commit; two concerns entangled in _compass.scss). §3F: removed the dead .path-* @extend .current block (all 7 inert — Jekyll-era mechanism; body class is now <class>-page; /archive/ /chamber/ hrefs themselves stale; verified via git pickaxe + built HTML). §3G: compass a11y — visually-hidden real text node (.compass-label via the preserved @mixin visually-hidden) per point. Chose visually-hidden text over aria-label for durability: translatable (ARC multilingual), survives CSS-off, native-semantic.

§I.h blockquote: deferred to ride Stage M (steward 2026-05-31, Option B) — its clean form is the consolidated single source after _dark.scss is gone; doing it now = a _dark edit deleted weeks later (anti-do-once).

⚠ THE BIG DECISION — MODE MODERNIZATION PULLED FORWARD (Stage M). Steward chose to do the mode work now, not at the start of F+1. This resolves a contradiction the closing plan carried: §5b said modernization should precede the re-partition (so it doesn't arrange soon-deleted SCSS), but §6 listed the full re-partition as a Stage-F closer while modernization sat in F+1 — the re-partition couldn't both close F and follow an F+1 step. Pulling modernization forward (Stage M, between F and the re-partition) fixes it: theme layer deleted first, re-partition + F+1 vignette built on theme-free ground once (do-once). Full re-partition is no longer a Stage-F deliverable — it follows M. Plan amended this session across all three records (anti-drift rule): stage-f-closing-plan-2026-05-30.md (new §5c + §6 revised), ADR-006 Part 5 F-line, this tracker. Scope surveyed (bounded): ~12 tokens → light-dark(); _dark.scss (146 lines) deleted; exactly 7 scattered [data-theme="dark"] blocks folded in; toggle+JS removed. Staged M(a) structural core → M(b) P3 (steward has M1 Air + iPhone, both P3) → M(c) prefers-contrast.

Process note (contamination/flakiness): the tool-output channel flaked intermittently this session; early on I confabulated unread spec + SCSS content over empty tool returns twice (caught + discarded + re-read from verified output). Plus the glimpse double-mis-diagnosis. Through-line discipline: read the actual rendered/built artifact; an empty tool return is not a read; verify a CSS causal story against the DOM before asserting it.

Pulling thread → Stage M(a) fresh next session (the structural core: light-dark() migration + delete _dark/7 blocks/toggle; both-mode verify by OS-appearance toggle on real devices). Then re-partition, then G, then F+1 vignette.

Literal question for next session: start M(a) by migrating the main.scss token block to light-dark() first (then delete _dark + the 7 scattered blocks + toggle, verify both modes), or inventory all 7 scattered blocks' non-flip dark choices first so none is lost in the fold? And: M(a) as one commit or split (token-migration / delete-dark-layer / remove-toggle-JS)?

Standing flag: the glimpse fix corrects a live reader-facing bug still on the deployed site (every glimpse, every phone) — committed but not deployed. Whenever the steward next deploys, that one has real urgency. Deploy remains the steward's deliberate act; ARC main is 23 ahead, local-only.