ORAM keeps the Python engine as the source of truth. New app, daemon, or plug-in work should route through structured ORAM actions instead of bypassing the parser/router boundary.
uv sync --extra dev --extra web
uv run pytestcd apps/macos
swift build- Add provider credentials through
oram_security.CredentialStore. - Never log provider keys.
- Register engines by capability in
oram.engines.registry. - Add tests proving state, logs, archives, and metadata do not contain secrets.
ORAM is MIT licensed. New dependencies should be compatible with that release model or clearly documented as a separate boundary.