Files
dotfiles/claude/memory/feedback-children-not-named-online.md
T
David F GliddenandClaude Opus 4.7 e9e772d69c memory: bundle accumulated 04-17/26 + lock ARC about-page architecture
Safety checkpoint before deep-audit Phase 0 of the ARC repo. Steward-authorized
commit-everything for rollback safety.

ARC architectural locks (2026-04-26 evening):
- Path 1 enfilade structure (separate Colophon and Lex items)
- 8-door enfilade locked: Colophon · Lex · Framework · Vignette · Attention ·
  Chamber · Tools · Now (+ Bio quiet link)
- Adsum and threshold-hic as two distinct texts on the reflowed About page
  (steward verbatim: "They are certainly not the same text")

ARC consolidation pass (canonical tracker project-arc-rework.md, +~700 lines):
fold 04-23 evening (Norris read), 04-24 (lex-method authored, posture cluster,
§XII Sidenotes, ARC CLAUDE.md cleanup), 04-25 (marks cluster, colophon-at-scale,
full Vico/Harrison lex-chain), 04-26 (chamber-library walk, cluster scaffolds,
canonical-tracker discipline surfaced).

Sibling-file integration: four 2026-04-26 frame files folded into the canonical
tracker (Integrations A/B/C/D) with INTEGRATED redirect notices retained as
audit trail.

New durable feedback memories:
- feedback-canonical-workstream-tracker-discipline (umbrella drift surfaced
  2026-04-26 by steward; proposes /wake-up + /wrap-up amendments)
- feedback-catalogues-stale-walk-trees (steward feedback on chamber-library
  catalogue currency)

Implementation plan drafted for the coming week: Phase 0 deep audit → Phase 5
cleanup, with steward additions on second pass (deep audit; Chamber v1 as own
browsable archive; clean rebuild of cluster sources rather than moving test
artifacts as canon).

Also bundled (untracked accumulation since 04-17):
- ~24 session memory + ledger files for 04-17 through 04-26 work
- ~10 feedback memories (BMF + ARC + working-method)
- 5 project memories (lex-as-method, strunk-white queue, plus today's four)
- 4 user memories (duality-rules, formation-practice, foundation-work, humic-layer)

Steward-side modifications also in this commit: ~/CLAUDE.md, bin/bmf-start.sh,
open-tasks.md, project-focus-april-may.md, session-2026-04-17 — all
pre-existing, not from today's session.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-04-26 14:52:14 +02:00

31 lines
2.7 KiB
Markdown

---
name: David's children are not named directly in public-facing online content
description: 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.
type: feedback
originSessionId: a73f10a9-062b-4360-bfd2-2ae37afd00d1
---
# 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.