12.09 — Ecosystem coherence#

Six repos, several languages, several technologies, several licenses, several deployment platforms. At first glance, heterogeneous. On a second read, rigorously coherent: every piece serves exactly the same bet.

1. Overview: six repos, one ethic#

┌────────────────────────────────────────────────────────────────────────┐
│         THE ECOSYSTEM AS A COHERENT WHOLE                              │
└────────────────────────────────────────────────────────────────────────┘

  ┌──────────────┐    The framework. ROP, strict types, refusal of pytest
  │   ocarina    │    plugin. ONE single runtime dep. Auditable in an
  └─────────────┬┘    afternoon. — PROVES that rigor is lightweight.
                │
                │
                ▼
  ┌─────────────────┐ The reference of use. Project adapters. Canonical
  │ ocarina-example │ patterns. Shows how to narrow the framework's API
  └─────────────┬───┘ surface for your context. — PROVES the framework is
                │     usable "by anyone".
                │
                ▼
  ┌─────────────────────────┐ The AI bet. Co-written by Claude 99%. CURA
  │ ocarina-with-ai-example │ Healthcare as SUT. Findings sourced down to PHP.
  └─────────────┬───────────┘ — PROVES AI + Ocarina can do real senior-tester
                │               work.
                ▼
       ┌──────────────┐ The deliberately chaotic SUT. The playground.
       │  igoristan   │ — PROVES you can test a pathological app without
       └────────┬─────┘   cheating.
                │
                ▼
       ┌────────────────┐ The coordination backend. Vercel Edge,
       │ tests-workers  │ Upstash Redis, deliberate anti-precision.
       └────────┬───────┘ — PROVES you can do distributed coordination
                │           without a proprietary platform.
                │
                ▼
       ┌───────────────────┐ The public documentation. VitePress + FR/EN/RU
       │ ocarina-holy-book │ + LLM-first (llms.txt, CLAUDE.md, skills).
       └───────────────────┘ — PROVES you can write docs that serve human AND
                               AI, without a third-party platform.

2. One repo = one type of challenge#

RepoType of challengeBet proven
ocarinaBuild a small and deep frameworkRigor isn’t a gas factory
ocarina-exampleDemonstrate canonical usageYou can actually write rigorous tests like this
ocarina-with-ai-exampleMake a human and an AI collaborateAI is the bridge, not the DSL
igoristanBuild a chaotic SUTNot a demo on a twenty-HTML-line site — a demo on a real mess
tests-workersBe the substrate testers coordinate through“You can be stateless on the code side”
ocarina-holy-bookDocument for humans and AIDocumentation is first and foremost raw data for LLMs

Remove one of these repos and the ecosystem loses an argument. The six are solidary.

3. Cross-cutting invariants#

License#

RepoLicense
ocarinaMIT
ocarina-exampleMIT
ocarina-with-ai-exampleMIT
ocarina-holy-bookMIT
igoristannone (public demo)
tests-workersISC (Vercel scaffold default)

MIT everywhere except special cases. The license is permissive to the maximum in every case.

Signature#

Each README ends with:

Built by [@mojo-molotov](https://github.com/mojo-molotov)
Fueled by figatellu and Квас.

Offbeat and uniform signature — a Zone-H / IRC convention (04-zoneh-irc-efnet.md).

Three Git conventions#

ConventionManifestation
Conventional Commitscommitlint + commitizen (Igoristan, Holy Book, ai-example)
Pre-commit hooksHusky (JS) or pre-commit Python (ocarina, ocarina-example)
No .no-verifyNo hook bypass. If it breaks, fix it.

Three CI/CD conventions#

ConventionManifestation
Fast PR-gatelint + typecheck (or check-coding-style)
Manual E2Eworkflow_dispatch only, never on PR
if: always() upload artifactsKeep all traces

Three code conventions#

ConventionManifestation
Strict type checkermypy strict (Python), tsc --build strict (TS)
Linter in select = ["ALL"] or equivalentruff ALL (Python), eslint --max-warnings 0 (TS)
No silent # noqaAlways justified, always local

4. Coherence of stack choices by context#

ContextChoiceWhy coherent
Python frameworkPython 3.14+ with PEP 695Modern strict typing
Demo siteReact 19 + Vike + TailwindReference 2026 frontend stack; no useless debt
Lightweight backendVercel Edge + Upstash RedisStateless, low-cost, low-tech, deployable in 30 seconds
DocumentationVitePress (not Docusaurus, MkDocs, Sphinx)Vite-based, aligned with the SUT frontend, hand-built LLM-friendly aspects
PDF generationReportlab + AI to orchestrateAgentic workflow

5. Coherence of tone#

The tone is uniform — different per medium but aligned:

MediumTone
ocarina READMESober technical, factual
ocarina-example READMETechnical with touches of humor ("figatellu and Квас")
ocarina-with-ai-example READMEHonest and demonstrative ("99% Claude / 50% intelligence")
igoristan READMEMinimalist ("Welcome to the Empire")
tests-workers READMEDirect API documentation
Holy BookPamphlet, strong identity, underground quotes
CLAUDE.mdStrict rules, past examples, firm vocabulary

The Holy Book is the hottest point. READMEs are cold.

This difference is deliberate:

  • README = technical surface. Must be usable with as little noise as possible.
  • Holy Book = philosophical surface. Must be felt.

As in the underground zine: the cold technical doc exists, but the real voice lives in the separate manifesto.

6. Cross-repo coherence via shared secrets#

See ../00-big-picture/04-repo-relations.md

A single secret (IGOR_API_KEYAPI_SECRET) governs all OTP interactions between:

  • ocarina-example (consumer).
  • tests-workers (server).
  • igoristan (UI that passes it).

Not three secrets, not a permissions matrix. One. The bare minimum.

Auditable in an afternoon”.

7. Coherence of bugs#

Deliberate failureWhereWhy
Math.random() < 0.9 on useAuthigoristanForce retry on the Ocarina side
Math.random() < 0.3 on the random-error pageigoristanForce use of transient_errors
Math.random() < 0.3 on donkey-sausageigoristanForce match_page
1/5 chance of Error('lol') on CorsicamonigoristanForce retry on the Ocarina side
OTP timestamp stripped of mstests-workersForce fine coordination between parallel tests
Random .catch-me-if-you-can elementigoristanForce use of Watcher
Heroku eco-dyno that sleeps (CURA)externalForce CI warm-up
Chrome BFCache restores no-storeexternal (Chrome)Force the cross-browser matrix
Chrome password manager catches inputsexternal (Chrome)Force a custom create_drivers_pool adapter

8. Coherence of refusals#

RepoSpecific refusal
ocarinaasync/await, pytest plugin, text DSL, “stylish” contributions
ocarina-exampleMocks (uses the real Igoristan), e2e on PR (expensive, manual only)
ocarina-with-ai-exampleActive security tests, hacks, JS-clicks to bypass, gross workarounds
igoristanUnit tests (everything is external e2e)
tests-workersGitHub CI (Vercel suffices), server-side framework (direct .ts handlers)
ocarina-holy-bookAlgolia (static Pagefind)

9. Coherence with the political stance#

See ../11-independence/03-explicit-refusals.md and ../01-philosophy/05-political-stance.md

The author refuses:

  • Stylish” contributions
  • Misaligned PRs / issues
  • Democratic code governance
  • async/await
  • Vendors
  • Proprietary platforms
  • Big-talk engineering

The ecosystem materializes these refusals:

  • No GitHub auto-merge bot
  • No Discord, no Slack
  • No Patreon / GitHub Sponsors / OpenCollective funding / no sponsor request
  • No SLA, no paid support
  • No sponsored talks
  • No merchandising

10. Meta-coherence: the primer itself#

Trait of the primerAligned with
Markdown only, powered by HugoAnti-No-Code, anti-SaaS, anti-Devs
Cross-referenced multi-filesComposition, not monolith
ASCII diagramsNo proprietary tooling
Free, no paywallCode is Law
Unfiltered pedagogyEverything is explained, RTFM