Naming Conventions
The Dev4rno ecosystem uses a deliberate, thematic naming system. This isn’t vanity — it’s a mnemonic architecture that makes 19 organisations and 340+ repositories navigable by a single person.The Philosophy
“If you can’t remember its name, you won’t remember to maintain it.”Every name in the factory serves three purposes:
- Identity — immediately tells you what wing of the factory you’re in
- Memorability — sticks in your head without a lookup table
- Searchability — unique enough to grep across the entire estate
Organisation Naming
Organisations follow a{name}-{suffix} pattern where the suffix signals the type:
| Suffix | Meaning | Examples |
|---|---|---|
-hq | Headquarters / primary hub | choco-hq, chronicle-hq, cookr-hq |
-tools | Developer tooling | sparki-tools, nestr-tools, clari-tools |
-io | Platform / service | so1-io, smo1-io, tektree-io, msx-io, v01t-io, featr-io |
-ai | AI/ML focused | traceo-ai |
-dev | Developer community | reactr-dev |
-me | Personal / identity | skyflow-me |
-craft | Protocol / low-level | aphelion-craft |
-cloud | Infrastructure / ops | devarno-cloud |
Repository Naming
Within organisations, repositories follow product-specific conventions:choco-hq (The Factory)
Wonka-themed names referencing the factory metaphor:- golden-ticket — entry points, landing pages
- factory-floor — internal tooling and automation
- conveyor — CI/CD pipelines and workflows
- oompa — worker services and background jobs
- wrapper — SDK wrappers and client libraries
chronicle-hq (The Editor)
Named after document and time concepts:- editor — core editor package
- relay — real-time sync service
- schemas — protobuf definitions
- app — web application
aphelion-craft (The Protocol Layer)
Named after celestial/orbital concepts with a-node suffix:
- fork-node — CRDT merge engine
- vest-node — verifiable audit ledger
- tnp-node — temporal navigation protocol
- aegis-node — access control
- timechain-sdk — client SDK
Domain Naming
Domains are grouped by brand identity. Each brand owns a TLD family:| Brand | TLD Pattern | Examples |
|---|---|---|
| Choco | choco.{purpose} | .gold, .codes, .tools, .press |
| Chronicle | {name}chronicle.{tld} or chronicle.{purpose} | openchronicle.net, chronicle.engineer |
| Null0 | null.{noun} | .limited, .investments, .builders |
| Product | {brand}.{tld} | devarno.cloud, so1.io, sparki.tools |
Thematic Consistency
The Wonka metaphor isn’t limited to names — it extends to:- Commit messages — factory floor language (“conveyor fix”, “golden ticket deploy”)
- Branch naming —
factory/{feature},golden/{fix} - Release names — major releases get Wonka character codenames
- Internal docs — “The Factory Floor” blog, “Golden Ticket” onboarding