Design Principles

Govern, do not orchestrate

Orlo governs meaningful steps. It does not aim to become a general-purpose workflow engine.

Deterministic where possible

Validation and control logic should be deterministic and auditable.

Keep the boundary honest

Public packages should stay reusable and free of platform-specific coupling.

Fast gate, deep audit

Hot-path governance must stay bounded in latency. Richer auditing and history can go deeper without blocking the execution path.