personal memory agent
docs: AGENTS.md §13 system-anatomy canon pointer
Phase A of the system-anatomy canon shipped in the extro repo
at cmo/brand/system-anatomy.md.
Add AGENTS.md §13 to direct in-repo coding agents writing
owner-facing strings to that canon for UI copy, settings,
README/INSTALL prose, error messages, and onboarding.
Keep internal architecture vocabulary unchanged: observe/,
the capture pipeline, and com.solstone.capture stay as-is;
capture remains a code-only word.
+18
+18
AGENTS.md
+18
AGENTS.md
···
310
310
- **Not a runtime guide for cogitate talents.** Runtime CLI restrictions on talents live in `talent/journal/references/cli.md` § Talent CLI Boundaries. If you're tuning what a talent can or cannot call, look there, not here.
311
311
- **Not the journal-layout reference.** `talent/journal/SKILL.md` + its `references/` is the cogitate-audience entry point. This file describes *how those commands are implemented*, not *which ones talents can't call*.
312
312
- **Not an operations manual.** For debugging a live system see `docs/DOCTOR.md`; for service management, the `make install-service` family.
313
+
314
+
## 13. Owner-facing copy: the system-anatomy canon
315
+
316
+
- **The trinity.** In owner-facing copy, name the system in canonical order: `solstone = observers + sol agent + journal`.
317
+
- **The canon lives elsewhere.** The source of truth is `~/projects/extro/cmo/brand/system-anatomy.md` in the extro repo. The companion is `~/projects/extro/cmo/brand/voice-terminology.md` for owner / keeper / partner voices.
318
+
- **Ban surveillance verbs in branded surfaces.** Never use "capture", "watch", "record", "monitor", "track", or "collect" in template copy, settings labels, error messages, onboarding text, or README / INSTALL prose. Prefer "observe alongside", "experience along with", or "take in what you take in".
319
+
- **`capture` is code-only.** Keep it in module names such as `observe/`, function names, OS subsystem identifiers such as `com.solstone.capture`, and internal architecture diagrams. That is intentional and aligned with the canon.
320
+
- **Name artifacts for owners, not pipelines.** In branded prose, say "raw media", "the originals", or "observations". Never say "raw captures" or "screen captures" in owner-facing strings. Code-side artifact names stay as-is.
321
+
- **`sol` is one thing.** `sol` is the running software; there is no homunculus behind it. Use two registers for one entity: `sol` in conversation, `sol agent` in technical contexts.
322
+
- **`keeper` is a surface-specific edge case.** `voice-terminology.md` makes `keeper` the role noun for `sol` in product copy generally. The `solstone-swift` surface bans `keeper` because the mobile UX uses the owner's chosen identity, default `sol`. When writing copy for a specific surface, follow that surface's terminology covenant.
323
+
- **Edit with the right mental model.** Internal architecture vocabulary in this repo stays as-is: `observe/`, the capture pipeline, and screen capture log subsystems remain correct code language. Apply the canon to owner-facing strings only: UI copy, settings text, install / README prose, error messages, and onboarding. If an owner sees it, follow the canon; if it's code or internal docs about pipelines, `capture` is fine.
324
+
325
+
| Surface | Terminology rule |
326
+
|---------|------------------|
327
+
| Code surfaces | `capture` is fine in code, module names, function names, subsystem ids, and internal architecture docs. |
328
+
| Branded surfaces | `capture` is banned. Use owner-facing phrasing such as "observe alongside", "experience along with", "take in what you take in", "raw media", "the originals", or "observations". |
329
+
330
+
Canon source of truth: `~/projects/extro/cmo/brand/system-anatomy.md`.