Docs
Architecture, strategy, research, quickstart, MCP reference, license. The developer reading surface.
Everything substantive about IOBOXX, organised by section. Architecture is the meaty read — the 19-component catalogue with one page per load-bearing component as the deep dives land. Strategy and research are the shorter framing reads. Getting started and the MCP reference are for engineers who want to wire it up today. License is the three-layer split that holds the open commons coherent.
New here? The shortest path through the surface is quickstart → memory → MCP reference. If you're evaluating versus other AI-memory systems, start at competitor analysis.
WHATArchitecture
What IOBOXX is and how it works. The architecture overview is the orientation map across all 19 components; the rest are deep dives on the components that already have one. Components without a deep page yet — agents, identity, security, platform top-level, observability, visibility, payments, web3, voice, AR, connectivity, compliance, digital-twin pipeline — are catalogued on the overview with one-liners; their dedicated pages land in future swarm rounds.
Architecture overview
/docs/architectureThe 19-component catalogue. Start here if you want the map of the whole system.
Memory
/docs/architecture/memoryThe substrate the platform converges onto. Object Store + MCP access layer.
Object Store (OODB)
/docs/architecture/memory/oodbThe EAV-typed object substrate — relevance-ordered reads, autohop, agent-curated handoff.
Tensor as substrate
/docs/architecture/memory/tensor-as-substrateWhy memory itself is the primitive — the load-bearing technical claim.
Portability
/docs/architecture/memory/portabilityOpen MCP. Any LLM. IOBOXX is not coupled to a single model vendor.
Data
/docs/architecture/dataWhere memory physically lives. Object Store plus Supabase coexistence.
Vectors
/docs/architecture/vectorsEmbeddings, HNSW, TurboQuant — the retrieval layer over the typed store.
Senses
/docs/architecture/sensesN → 1 / 1 → N upstream extension. How twins sync with systems of record.
BPMN
/docs/architecture/bpmnToken-based BPMN 2.0 engine. SOPs become executable workflows.
Observation surface
/docs/architecture/observation-surfaceThe render layer. 11 ViewKinds. Object cards are the atomic unit.
Mycelium
/docs/architecture/myceliumThe mesh of sovereign brains. Per-twin sovereignty with directional, permissioned grants — N → 1 / 1 → N, never N → N.
Authorization
/docs/architecture/authorizationJWT-claim-driven access. Keycloak roles + Organization membership drive every reducer.
WHYStrategy
Why this. Positioning, the thesis, the load-bearing strategic claims. More strategy pages will land here as the next batches ship.
EVIDENCEResearch
Comparative analysis and the bibliographic foundation. The current page is the first-pass competitor read; deeper papers and the methodology references will follow.
DOGetting started
For engineers who want to wire it up today. Quickstart for the install path; the MCP reference for the tool surface IOBOXX exposes to any LLM.
TERMSLicense
The three-layer license structure — AGPL core, MIT SDKs, proprietary control plane — and why each layer is licensed the way it is.
The other two area landings
The site has two other top-level surfaces beyond /docs. They live alongside this one and are the right entry points if you're not here for the technical read.