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.8 KiB
name, description, type, originSessionId, permalink
| name | description | type | originSessionId | permalink |
|---|---|---|---|---|
| David's children are not named directly in public-facing online content | Steward principle — Kai, Lune, and any future children of David's are not named directly in any content that publishes online (ARC essays/posts/descriptions, anywhere outward-facing). The body of his Kai-9-month meditation exemplifies the discipline ("watching an infant," not the name). Applies to all ARC work and any other public-facing surface. | feedback | a73f10a9-062b-4360-bfd2-2ae37afd00d1 | claude-memory/feedback-children-not-named-online |
David's children are not named directly online
Rule: Do not name David's children (Kai, Lune, or any future children) in public-facing online content — essays, posts, descriptions, frontmatter description fields, dedications-as-text, anywhere that would publish to ARC or any external surface. Use generic referents instead: "an infant," "my son," "the child" — or leave the dedication implicit, in the writer's knowing only.
Why: Steward verbatim 2026-04-20: "i don't want to name my children directly online—it feels like a betrayal of their unconditional trust." The children have not consented and cannot meaningfully consent to being named in a public record. The trust they extend is unconditional; declaring them in a public space would convert that trust into material the writer benefits from. The dedication can be real without being declared.
How to apply:
- Body text of public pieces: Use generic referents. The Kai-9-month meditation does this naturally — "There is everything to learn from watching an infant grow into the world."
- Titles, descriptions, slugs, dedications-as-text: Same. No first names. No "for [name]" dedications visible to the reader.
- Datelines: No "[name]'s nine-month day" or similar. Date and place only. (I almost added this on 2026-04-20 and was caught.)
- Frontmatter: No first names in
description,tags,themes. The frontmatter publishes alongside the piece. - Code, comments, commits: Same principle for anything in a public repo.
Where naming IS fine:
- Private conversation between steward and Claude
- Memory files (these are private)
- Private notes, journals, the steward's own non-published writings
- Personal communications (email, in-person, etc.)
Don't ask each time. This is a standing rule. Apply it without asking; flag it only if there's genuine ambiguity about whether something is public-facing.
The piece teaches the principle. The Kai meditation is dedicated to him and honors the rule by not naming him. The dedication lives in the writer's heart and in the absent-presence of the unnamed infant. That model — dedication-without-declaration — is what to honor across all his work involving the children.