The World of SPLectrum
Home > Vocabulary > SPLectrum > Engineering
Engineering vocabulary
Terms native to SPLectrum’s engineering — the fabric, the runtime, the artefacts that realise the seed in software.
Sub-games
- HAICC — Human-AI Creative Collaboration, the subject-internal dynamic.
Terms
Mycelium — the data fabric. Where things exist. The substrate through which a subject accesses the data world. Structure, records, contexts, metadata, traversal. The engineering cornerstone.
SPLectrum — the language fabric. What languages are available and how they relate. Meaning. Supplies the languages — protocol libraries, schemas, meaning structures. The relational structure that governs how decentralised data and decentralised cognition interact.
Namespace tree — every language that participates in the fabric gets its own namespace tree — its own way of organising identity, its own structure for naming what it knows. The fabric weaves these trees together. The pivot between any two trees is the readable-as principle.
Interaction surface — the entity’s exposed interface. Where language lives. The surface through which a subject is known — by its imprint on the fabric, not by looking inside.
Protocol — the engineering artefact of a language game.
Persona — continuous identity across conscious and subconscious. Declares required capabilities, tested against available capabilities — human and AI — to determine work division. A subject may have multiple personas.
JIT implementation — physical implementation goes only as far as capability requires. The logical design describes how the system must look. The physical materialises where and when a capability is needed. The gap between logical and physical is not a deficit — it is the natural state of a design that materialises through use.
Barified — adapted for the Bare runtime. An external module stripped of Node.js assumptions and made compatible with Bare’s minimal API surface.
Constitutive dependency — a dependency that is part of the architecture. Forked, barified, maintained locally. Vendored into the runtime repo as a git subtree. As much SPLectrum code as any other module.
Platform dependency — a dependency that is the platform. Maintained by the platform vendor (Holepunch). Sourced from GitHub, pinned to release tags. Becomes constitutive if it needs modification. The boundary is permeable.