11.02 — Auditability “in an afternoon”#
Operational commitment: a human must be able to read the whole framework and understand it in a few hours. No hidden magic.
Commitment#
Holy Book quote (chapter “What is Ocarina?”):
For teams constrained by security policies: the code is small, auditable in an afternoon. Nothing hidden. The only external dependencies live in the post-execution plugins and if one of them doesn’t fit, it can be removed without breaking anything else.
As few dependencies as possible#
dependencies = ["python-docx>=1.2.0"]python-docx is used exclusively by generate_docx_proof (post-execution plugin).
The rest of the framework imports it nowhere.
| Audit | Verdict |
|---|---|
| Which libs are vendor-shipped with Ocarina? | python-docx (+ Python stdlib) |
If the auditor doesn’t trust python-docx? | Disable the DOCX plugin → everything else runs |
Are there hidden deps in requirements-dev.txt? | Yes (Selenium, allure, mypy, ruff, …) but they’re not embedded in the release binaries |
How many SBOM entries for pip install ocarina? | ~2 (ocarina + python-docx) |
Nothing hidden#
The auditor can verify everything:
- The source: public on GitHub MIT.
- The build: standard
hatchlingbuild, reproducible. - The tests: cram + pytest + mypy plugins + syrupy + hypothesis.
- The Allure report: published on GitHub Pages, viewable by anyone.
- The CIs:
main_ci.yml.
No:
- Proprietary build step.
- Third-party artifact download on install.
- Obfuscated code.
- Hidden telemetry.
- External API call to authorize use.
Code is Law#
See ../01-philosophy/04-citations-and-influences.md
Code substitutes for the Law. Lessig, 1999, a wake-up cry. Then picked up by Ethereum, 2015, conversely as political ideal.
For “code to be the law”, it must be readable. Otherwise it’s just “the law is what we don’t understand, but which executes”.
Ocarina is explicitly auditable, hence legislative in the noble sense.
Portability#
Holy Book quote:
In the most extreme cases: Ocarina doesn’t need to be installed.
Copy it, adapt it, run it.
No dependency to audit.
You can literally copy the src/ocarina/ folder into your project and use it as a sub-package. No install.
Use case: an ultra-paranoid client refusing any pip install. Copy. Adapt. It runs.
dsl/ / infra/ / opinionated/ separation#
See ../02-ocarina/02-module-tree.md
| Layer | Audit first |
|---|---|
railway/ | 30 minutes: understand ROP |
custom_types/ | 30 minutes: types and aliases |
dsl/testing_with_railway/ | 1h: the DSL state machine |
dsl/invariants/ | 1h: invariants chain |
dsl/testing/ | 1h: orchestration (Test → Suite → Campaign → Cycle) |
infra/ | 30 minutes: pool, builder, screenshotter |
opinionated/ | 30 minutes: CLI, loggers, plugins, bootstrap |
Total: ~5 hours for a full audit. A quiet afternoon.
Post-execution plugins only#
The only external dependencies live in the post-execution plugins and if one of them doesn’t fit, it can be removed without breaking anything else.
See ../02-ocarina/11-opinionated/05-plugins-reports.md and ../02-ocarina/11-opinionated/06-bootstrap-launcher.md
run_plugins(*plugins, exceptions_logger):
def _run_plugin(plugin: Effect, exceptions_logger: ILogger) -> None:
try:
plugin()
except Exception as exc:
exceptions_logger.exception("The plugin failed.", exc=exc)If python-docx is broken / un-installable: the DOCX plugin raises, we log, the rest continues.
The run still produces:
- The
pretty_print_resultsreport. - The JSON report (
results_to_json). - The
sys.exit(1)on fail.
Only the DOCX will be missing. You can remove the DOCX plugin call from your main.py entirely if you prefer.
Anti No-Code#
See the Holy Book (chapter “First feedbacks”, “Anti No-Code” section):
Code is raw data. Auditable. Inspectable. A white box.
Exactly what AI has known how to work with since its very beginnings.
“White box”: we see everything. No proprietary black box.
The opposition to No-Code isn’t ideological posturing — it’s a demand for auditability. A No-Code workflow is, by definition, non-auditable.
Anti dev-bros#
Holy Book:
Unlike researchers, engineers and their business-school friends rely on mental models. The most “prestigious” schools have taught them one thing: passing big-talk off as “engineering”, whereas those who know call this work programming astrology.
Ocarina rejects the big-talk. The code is what it is, verifiable. No esoteric “patterns” justifying pointless complexity.
Consequence for teams stuck behind security policies#
The auditability pitch is explicitly aimed at them:
For teams constrained by security policies: the code is small, auditable in an afternoon.
A team that can’t pip install <random> can:
- Audit Ocarina (one afternoon).
- Audit project adapters (a few more hours).
- Ask the security team to whitelist it.
- Run without fear.
No Ocarina consultant, no SaaS, no enterprise license. Free.