Cambium — Official Naming and Architecture
Purpose
This document locks the core naming system for the platform and defines how the major pieces relate to each other.
The goal is simple: stop naming drift now, so product, architecture, docs, and code all point at the same thing.
Canonical Product Name
Cambium is the name of the overall platform.
Use Cambium when referring to: - the full product - the platform/company-facing system - the orchestration substrate as a whole - the long-term ecosystem vision
Short definition
Cambium is a nature-based orchestration platform for resilient agent systems.
Why this name fits
In a tree, cambium is the thin living layer that enables growth. It is not the leaves, not the bark, not one branch. It is the generative layer that allows the organism to keep developing.
That is the right metaphor for the platform: - it enables growth rather than merely controlling tasks - it supports many higher-order structures - it sits beneath visible workflows and coordination patterns - it is living infrastructure, not a static dashboard
Canonical Internal Architecture Names
These names are the official first-layer architecture vocabulary.
1. Cambium
Role: The whole platform
Cambium is the complete system: runtime, policy, memory, coordination, resilience, governance, and interfaces.
If someone asks, “What are we building?” the answer is Cambium.
2. Hypha
Role: The orchestration engine
Hypha is the core execution and coordination engine inside Cambium.
It is responsible for: - agent orchestration - routing work - handling signals and state transitions - coordinating policies, thresholds, and execution flows - supporting adaptive rather than purely linear workflow behavior
Working definition
Hypha is the living orchestration engine inside Cambium.
Why this name fits
Hyphae are the branching filaments of fungi. They explore, connect, transport, and form larger networks. That maps cleanly to an engine that routes work, context, and coordination through a living system.
3. Loom
Role: The workflow surface
Loom is the primary human-facing workflow and composition surface.
It is responsible for: - designing and inspecting flows - visualizing execution state - shaping reusable patterns - exposing the system to operators in a way that feels legible and controllable
Working definition
Loom is the workflow surface of Cambium.
Why this name fits
A loom turns many threads into a coherent fabric. That is exactly what the workflow surface does: it helps humans shape and inspect many moving parts without pretending the whole system is a rigid assembly line.
4. Quorum
Role: The collective coordination and decision layer
Quorum is the threshold, governance, and confidence layer inside Cambium.
It is responsible for: - gating sensitive actions - aggregating signals and confidence - enabling threshold-based approval - coordinating distributed decisions without requiring one central manager for everything
Working definition
Quorum is the collective decision layer of Cambium.
Why this name fits
Quorum already carries the meaning we want: action becomes legitimate when enough aligned participation or confidence exists.
Relationship Between the Names
The clean mental model is:
- Cambium = the platform
- Hypha = the engine
- Loom = the workflow surface
- Quorum = the collective coordination layer
Or in one line:
Cambium is the platform. Hypha runs it. Loom shows and shapes it. Quorum helps decide what it is allowed to do.
Architecture Stack
Platform level
Cambium - the umbrella system - the brand - the architectural whole
Core runtime level
Hypha - orchestration runtime - execution graph / adaptive routing layer - signal handling and policy-aware coordination engine
Interaction level
Loom - workflow editor - operational console - topology and state visibility layer
Governance level
Quorum - threshold rules - collective approval logic - confidence and escalation system
Official Positioning
Cambium should not be framed as: - a task manager for agents - a conventional workflow builder - just another agent framework - a manager dashboard for bot employees
Cambium should be framed as:
a nature-based orchestration platform for building resilient, adaptive, governable agent systems
If we want the stronger internal version:
an ecological operating substrate for autonomous organizations
That second line is powerful, but the first is the safer default for docs and outward-facing explanation.
Architectural Philosophy
Cambium is based on a different assumption than most orchestration systems.
Most systems are built on a bureaucratic metaphor: - managers - tasks - org charts - approvals - reporting lines
Cambium is built on a living-systems metaphor: - adaptation - signaling - resource flow - resilience - environmental coordination - threshold-based collective behavior
That distinction matters.
The point is not to make the interface sound poetic. The point is to build software that is better suited to: - many-agent coordination - fault tolerance - recovery after failure - policy-aware autonomy - system health under changing conditions
Naming Rules
These are the naming rules to keep things clean.
Rule 1: Use Cambium as the umbrella every time
Do not casually use Hypha or Loom as if they are the whole platform.
Wrong: - “We’re building Hypha.” - “Loom is the platform.”
Right: - “We’re building Cambium.” - “Hypha is the orchestration engine inside Cambium.” - “Loom is the workflow surface inside Cambium.”
Rule 2: Keep Hypha technical
Hypha should refer to runtime, engine, orchestration, routing, and execution behavior. It should not become a vague synonym for “the cool part.”
Rule 3: Keep Loom human-facing
Loom should refer to interface, workflow design, inspection, visualization, and operational control.
Rule 4: Keep Quorum decision-focused
Quorum should refer to thresholds, collective approval, confidence, governance, and escalation logic. It should not be overloaded to mean “community” in general.
Rule 5: Avoid creating extra poetic names too early
Three strong sub-names is enough for now. More names too early will make the platform feel mystical instead of clear.
Suggested Default Product Description
Use this when we need one short paragraph:
Cambium is a nature-based orchestration platform for resilient agent systems. Hypha is its orchestration engine, Loom is its workflow surface, and Quorum is its collective coordination layer. Together they support adaptive execution, visibility, governance, and recovery for autonomous software systems.
Suggested One-Sentence Version
Cambium is a nature-based orchestration platform; Hypha is the engine, Loom is the workflow surface, and Quorum is the decision layer.
What This Means for the Build
The product should be designed so that: - Cambium is the repo and platform identity - Hypha is the runtime/core engine package or service name - Loom is the app/UI package or workflow console name - Quorum is the policy and threshold decision subsystem
That gives us a naming system that is clear enough for code, docs, product, and future marketing without collapsing into fluff.
Final Lock
The official architecture naming is:
- Cambium — the platform
- Hypha (the orchestration engine
- Loom)— the workflow surface
- Quorum (the collective coordination layer)
This is the naming baseline going forward.