--- name: ARC rework landscape (reawakening 2026-04-16) description: 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. type: project originSessionId: 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. ## 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. ## 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. ## 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.