David F GliddenandClaude Opus 4.8
3f9a89b00c
Basic Memory v0.21.6 first sync over the live memory dir (steward-authorized live-dir trial, Option A 2026-06-06): adds permalink: to frontmatter, refolds long YAML description lines, strips final newlines. Bodies untouched — verified via full diff classification. From this commit forward, any diff in claude/memory shows only what Basic Memory or the session writes. Trial design: MemPalace untouched as incumbent; git status check on this dir at every wrap; end-of-day evaluation (recall quality, sync robustness, rebuild-from-files, malformed-file behavior). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2.5 KiB
name, description, type, originSessionId, permalink
| name | description | type | originSessionId | permalink |
|---|---|---|---|---|
| ARC link treatment — one rule, two named exceptions | Predictability principle for ARC link styling — single global treatment per spec §VII.c, with avatar-link and Reading Compass as the only exempt elements | feedback | 8d9ac240-47df-4578-aec1-a9dd32965027 | claude-memory/feedback-arc-link-treatment-one-rule-two-exceptions |
ARC link treatment follows one rule, two named exceptions — captured by steward 2026-05-02 during the §VII.c link-spec drafting + SCSS migration session.
"the avatar and reading compass are the only links that need special treatment. The rest should be predictable and crafted with care"
Why: Predictability is the principle. A reader's eye trained by reading one ARC piece should know what a link looks like in any other. Multiple competing link treatments across contexts (catalogue/wholeform variant, apparatus quiet-nav variant, button variant, etc.) fragment the reader's intuition and require re-learning per page. The discipline of one treatment is also the discipline of care — every link gets the same considered typography rather than ad-hoc per-context decisions.
How to apply:
- The TWO exceptions are documented in spec §VII.c "Exceptions" subsection:
.avatar-link— wordmark in page header; underline would compete with wordmark typography- Reading Compass (per §VI) — eight-sigil navigation; underline would be redundant beneath glyphs
- Everything else (in-text, apparatus, catalogues, navigation) follows §VII.c (Pompeian-red hair-thin underline, body-color text, native
text-decorationper Rutter / Bringhurst transferred). - When you encounter a context-specific link rule that diverges from §VII.c, the question is NOT "is this a different valid pattern?" but rather "is this (a) legacy material destined for an archival collection where preservation overrides current-spec alignment, or (b) a cascade artifact to be reconciled?" Don't propose new sub-spec sections for the divergence; reconcile it or archive it.
- The earlier impulse (mine, 2026-05-02) to spec multiple sub-variants (§VII.c.ii catalogue, §VII.c.iii quiet-nav, §VII.c.iv button) was over-elaboration. Resist that pattern. The simpler frame — one rule, two exceptions, everything else predictable — is correct.
Related: care-over-traffic (work answers to itself; quality + predictability + accountability matter even at low traffic); the broader "would Alexander do it like this?" discipline against unnecessary elaboration.