personal memory agent
coding standards: trust system path resolution principle
Never set _SOLSTONE_JOURNAL_OVERRIDE from application code. Cross-refs
environment.md for the full explanation.
+1
+1
muse/coding/reference/coding-standards.md
+1
muse/coding/reference/coding-standards.md
···
38
38
- **Conciseness & Maintainability**: Clear code over clever code
39
39
- **Robustness**: Minimize assumptions that must be kept in sync across the codebase, avoid fragility and increasing maintenance burden.
40
40
- **Self-Contained Codebase**: All code that depends on this project lives within this repository—never add backwards-compatibility shims, fallback aliases, re-exports for moved symbols, deprecated parameter handling, or legacy support code. When renaming or removing something, update all usages directly. For journal data format changes, write a migration script (see [docs/APPS.md](docs/APPS.md) for `maint` commands) instead of adding compatibility layers.
41
+
- **Trust system path resolution**: Never set `_SOLSTONE_JOURNAL_OVERRIDE` or bypass `get_journal()` from application code, agent prompts, subprocess environments, or service files. The env var exists only for tests and Makefile sandboxes. See `reference/environment.md`.
41
42
- **Security**: Never expose secrets, validate/sanitize all inputs
42
43
- **Performance**: Profile before optimizing
43
44
- **Git**: Small focused commits, descriptive branch names. Run git commands directly (not `git -C`) since you're already in the repo.