tmux observer
brand: scrub extro paths from AGENTS.md
Replace internal `~/projects/extro/cmo/brand/...` paths with neutral
phrasing referring to sol pbc's internal brand canon. The substantive
guidance (canon-permitted code vocabulary vs co-experience language for
owner-facing prose) is preserved.
+2
-2
+2
-2
AGENTS.md
+2
-2
AGENTS.md
···
101
101
## Brand canon
102
102
103
103
- **solstone-tmux is an observer.** In the system anatomy, `solstone = observers + sol agent + journal`. This repo implements one of those observers.
104
-
- **The canon lives elsewhere.** Owner-facing terminology comes from `~/projects/extro/cmo/brand/system-anatomy.md`. The companion is `~/projects/extro/cmo/brand/voice-terminology.md`.
104
+
- **The canon lives elsewhere.** Owner-facing terminology comes from sol pbc's internal brand canon (system anatomy + voice terminology guides). This repo's branded prose follows it; the canon itself is not vendored here.
105
105
- **Use co-experience language in branded prose.** In README, INSTALL, onboarding text, settings copy, and error messages, describe solstone-tmux as something that experiences tmux sessions along with the owner. Never describe it as watching, capturing, recording, monitoring, or tracking the owner.
106
106
- **Keep code language in code-only contexts.** Internal architecture terms such as the `Capture Loop` heading, the `capture.py` module, the `~/.local/share/solstone-tmux/captures/` on-disk path, and the `capture_interval` config key are canon-permitted here and must not be renamed just to match branded prose.
107
107
- **Edit with the surface in mind.** If the owner sees the string, follow the canon. If the text is naming code, pipelines, modules, or storage artifacts for engineers, the existing internal vocabulary stays.
108
108
109
-
Canon source of truth: `~/projects/extro/cmo/brand/system-anatomy.md`.
109
+
Canon source of truth: sol pbc's internal brand canon (system-anatomy guide).
110
110
111
111
## License
112
112