Outcomes over implementation.
Lead with what the reader gets. Mechanism belongs in documentation.
Nine rules we build by.
These principles guide how Aarmatix builds, writes, and makes tradeoffs for Aarmos. Product behavior and technical procedure remain with their canonical product and documentation owners.
Evidence over assertion.
Material claims about governed execution should be grounded in evidence at the level that evidence supports.
Portability over lock-in.
Evidence should remain independently verifiable without dependence on an Aarmos service.
Enforce before you explain.
On enforcing paths, governance is evaluated before governed execution. Evidence explains what followed.
One idea per surface.
A page that defends one idea is remembered. A page that defends five is not.
Subtraction is a feature.
New primitives must unlock a customer or simplify the story. Otherwise, defer.
Boring where it matters.
Production infrastructure should feel predictable, not clever.
Write for the person on call.
Write clearly for the reader working through a consequential moment.
Record history; don't rewrite it.
Governance changes extend the evidence history rather than rewriting what was previously recorded. Retention and storage remain separate concerns.