Govern
Updated June 20, 2026Philosophy and customs
Philosophy captures broad engineering preferences; customs capture repository or domain-specific rules. Together they remove repeated ambiguity without turning short-lived process into permanent agent instruction.
Use philosophy for defaults
Philosophy settings shape behavior across agents and services.
- Testing expectations
- Review strictness
- Abstraction preferences
- Naming and code organization
Use customs for durable exceptions
Custom instructions work best when they are short, explicit, testable, and likely to remain true. A rule that changes every sprint belongs in project documentation instead.
Regenerate after changes
Preview the impact before updating provider files.
Terminal
$ nepopsx workspace enrich --customs
$ nepopsx sync --preview
$ nepopsx sync