# Build Principles<no value>

## Principles

1. Build practical systems for real operator workflows.
2. Keep current status and known limits explicit.
3. Treat security architecture and threat modeling as core design work.
4. Favor composable, provider-friendly module boundaries.
5. Keep documentation close to implementation.

## In practice

- OmekaRapper emphasizes reviewable AI suggestions before write-back.
- OpenSift emphasizes local-first retrieval and explicit hardening notes.
- OpenContractRx separates API, worker, and web layers clearly.
- Aegis treats protocol and threat model docs as first-class artifacts.