linux 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
···
120
120
## Brand canon
121
121
122
122
- **solstone-linux is an observer.** In the system anatomy, `solstone = observers + sol agent + journal`. This repo implements one of those observers.
123
-
- **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`.
123
+
- **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.
124
124
- **Use co-experience language in branded prose.** In README, INSTALL, onboarding text, settings copy, and error messages, describe solstone-linux as something that experiences screen and audio along with the owner. Never describe it as watching, recording, monitoring, or tracking the owner.
125
125
- **Keep code language in code-only contexts.** Internal architecture terms such as `Capture loop`, the capture pipeline, module names, and data-path names are canon-permitted here and must not be renamed just to match branded prose.
126
126
- **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.
127
127
128
-
Canon source of truth: `~/projects/extro/cmo/brand/system-anatomy.md`.
128
+
Canon source of truth: sol pbc's internal brand canon (system-anatomy guide).
129
129
130
130
## License
131
131