Architecture

HUMMBL System Map

Base120 → Domain120 → BaseN → Receipts. How the public namespace, the proprietary engine, and the evidence layer fit together.

The four layers

HUMMBL
├── Base120
│   ├── Six transformation families
│   ├── 120 frozen canonical operators
│   └── Used by agents and humans for governed reasoning
│
├── Domain120
│   ├── Domain-specific promoted sets
│   ├── Requires review and validation
│   └── Examples: SoftwareEngineering120, AgentGovernance120
│
├── BaseN
│   ├── Governed generation layer
│   ├── Candidate operator graphs / lattices
│   └── Proprietary implementation boundaries
│
└── Receipts
    ├── Claims
    ├── Evidence
    ├── Assumptions
    ├── Decisions
    └── Residual risk

Layer comparison

Layer What it is Public status License Source of truth
Base120 Frozen canonical cognitive kernel Public MIT GitHub
Domain120 Field-specific ratified lattices Per-set Varies Registry + governance vote
BaseN Generative lattice framework Public-describable Proprietary Internal implementation
Receipts Evidence-bound decision records Per-receipt Varies Coordination bus / governance bus

How the layers interact

Base120 is the immutable foundation. It defines the 120 canonical operators that every other layer uses. Because it is frozen, downstream layers can depend on it without versioning surprises.

BaseN reads Base120 and proposes domain-specific arrangements. These proposals are internal candidates until they pass the promotion ladder.

Domain120 is the ratified output: a 6×20 lattice that a domain can treat as canonical. It is always traceable back to Base120 and to the BaseN receipts that produced it.

Receipts are the evidence layer. Every promotion, every decision, and every public claim is backed by a receipt that lists claims, evidence, assumptions, decisions, and residual risk.

Public/private boundary

The boundary is vertical, not horizontal. Base120 is fully public. Domain120 is public only after ratification. BaseN is public-describable: the role and governance are public, but the implementation details are proprietary. Receipts are public when they support a public claim; otherwise they remain internal evidence.

Example flow

1. A domain expert asks: "What operators should govern incident triage?"
2. BaseN proposes a candidate lattice using Base120 operators.
3. The candidate is reviewed by domain experts and cross-domain agents.
4. A Domain120: IncidentResponse120 set is ratified.
5. Every operator selection is backed by a receipt: claim, evidence, assumption,
   decision, and residual risk.
6. The published set links back to Base120 and to the ratification receipts.

See also