Home > Engineering > Top Level Design
The bridge between the Splectrum philosophical framework and its engineering. This document introduces the three pillars and the design commitments that govern all engineering below this level.
Splectrum’s six seed principles (P0–P5) describe properties shared by all languages. The engineering does not implement these principles — it is these principles expressed in another language. The relationship is relational, not representational. Neither side governs the other. The quality gate is low friction at the boundary.
If the seed holds, the engineering that grows from it should look like how reality works.
P0 — being implies language — yields three inseparable aspects. These become the three pillars of the engineering: state, meaning, and cognition. Three fabrics, not three layers. Aspects of the same thing.
The physical layer. Data and data change — carrier, substrate, structure, transitions. Records, contexts, metadata, traversal, and the processes that transform data state. Everything encoded as information. The subject never touches the data world directly — only through the mycelium interface.
Mycelium is decentralised at the data level. No central database, no single source of truth. Subject realities within git repositories. What actually exists is always mycelium fabric expressed as subject realities. The totality of data is only a logical totality — the sum of everything across the fabric.
Mycelium hosts both languages (splectrum) and process (HAICC) as facts in its metadata. It is the stable ground — minimal, universal, unchanged when the layers above evolve.
Constitutive dependencies: git (identity, history, boundary) and AVRO (schema, conformance, protocol, interface).
The logical layer. Meaning languages, concept vocabularies, the mapping surface between them. Splectrum supplies the languages — protocol libraries, schemas, meaning structures. A fabric in its own right, not glue between the other two.
The relational structure that governs how decentralised data and decentralised cognition interact without needing a central authority. P4 — equal standing — expressed as architecture.
P1–P5 as engineering:
Natural language as the carrier language. AI makes this operational. Ambiguity at the fringes is generative — where new meaning enters.
The activation layer. Activity, structured process flows, and process models — the cognition that resolves logical against physical, operating through languages while maintaining genuine human partnership.
The persona is the operational unit. It declares required capabilities. These are tested against available capabilities — human and AI. The conformance determines work division. Optimisation direction: toward AI autonomy. The human retains what AI capability does not yet cover.
Conscious is what is in focus — the work at hand. Subconscious is what supports it — the additional activity needed to achieve the conscious task. AI and human are present in both layers. The persona is the continuous identity across both.
Plasticity is the ability to learn. A capability starts conscious — attended, deliberate. Through practice it moves subconscious — running without attention. The movement IS learning. Learning is architecturally native because the conscious/subconscious design makes it so. The design is compatible with learning by construction.
The subconscious operating pattern is evolutionary: scan, diversify, evolve. Process capabilities dormant in the fabric, woken by data state change. What works reinforces, what doesn’t fades. No orchestration — the data state is the relay. The appearance of orchestration is emergent.
HAICC is decentralised at the cognition level. Human and AI agents as collaborative peers, no central controller.
The three pillars are not independent systems. They meet at defined boundary points:
Mycelium–Splectrum. Protocol libraries place their schemas as facts in mycelium metadata. Splectrum defines the languages. Mycelium hosts them. Schema discovery during traversal is the mechanism — schemas present in context metadata, accumulated naturally as the path is walked. No registry, no injection — facts in the fabric.
Mycelium–HAICC. The process layer sits in the fabric alongside the projection layer. Process definitions, watcher expressions, readiness schemas — all live in mycelium context metadata. The trigger model operates on the fabric: data footprint observation, watcher expressions as get paths, accumulation and readiness as data state facts. HAICC’s process flow uses mycelium’s substrate.
Splectrum–HAICC. Splectrum supplies the languages. HAICC supplies the process flow through them. Protocol libraries (splectrum) define what operations exist. The process layer (HAICC) determines when and how they fire. The persona (HAICC) uses protocols (splectrum) in service of its role. The persona is the why; the protocols are the how.
All three together. A process is triggered by data state change (mycelium), its inputs conform to a schema (splectrum), the persona engages with the ready state (HAICC). The three pillars are simultaneously present in every act.
The design commitments govern all engineering below this level. They are the philosophical framework in engineering language. Each design must conform to them. The quality test is low friction with the framework.
The full set of commitments is maintained in Design Commitments.
| Document | What it covers |
|---|---|
| This document | Bridge between philosophy and engineering. Introduces pillars and commitments |
| Design Commitments | The constraints. Philosophical structure as engineering law |
| Process Models | HAICC: the decentralised evolutionary pattern and its neuroscience grounding |
| Document | What it covers |
|---|---|
| Mycelium | The data fabric. Design, boundary, subject reality, constitutive dependencies |
| Fabric | The base data structure. Records, contexts, navigation, data APIs |
| Subject Reality | The git repo as living subject. Boundary, POV, references, self-contained from birth |
| AVRO Design Scope | Constitutive dependency. Schema, conformance, protocol, interface |
| Git Design Scope | Constitutive dependency. Historicity, identity, boundary, decentralised exchange |
| Area | Status |
|---|---|
| Splectrum engineering design | Early stage. Protocol libraries defined in mycelium process. Language fabric design not yet articulated as its own document |
| HAICC design | Early stage, ahead of splectrum. Persona mechanism, conscious/subconscious, plasticity, and evolutionary model established. Detailed design not yet articulated |
© 2026 In Wonder - The World of Splectrum, Jules ten Bos. The conversation lives at In Wonder - The Conversation.