Principles
- Keep topology authorization in Control and enforcement in the managed DVeMesh daemon.
- Keep Eryon IPC read-only; do not introduce a second peer or routing authority.
- Do not implement custom cryptography or claim cross-host support from mocks.
- Update documentation when a tested behavior or security boundary changes.
- Run focused tests and report skipped or environment-blocked checks honestly.
Testing
Prefer temporary directories and local sockets for automated tests. Never enroll a production identity or run installer mutation against a production host as part of a routine test.
Attribution and licensing
The repository does not establish an Eryon project license. DVeProto and DVeMesh are separate components with their own licensing and attribution terms. Preserve their notices and confirm distribution terms before bundling or publishing artifacts.