Architecture
Data Plane (Memory)
Understand direct-core memory operations, policy boundaries, and when low-level lanes are appropriate.
The MuBit data plane exposes low-level memory primitives. It is powerful and intentionally policy-constrained.
Use direct-core methods only when you need an explicitly enabled compatibility lane such as direct semantic search. For most app request paths, control-plane methods are safer and easier to operate. Keeping this boundary clear reduces policy and reliability incidents.
Core route families
| Family | Representative routes |
|---|---|
| Direct retrieval | /v2/core/search |
| Health/auth | /v2/core/health, /v2/core/auth/* |
Policy behavior
/v2/core/searchrequiresMUBIT_CORE_ENABLE_DIRECT_SEARCH.- Other external
/v2/core/*routes should be treated as compatibility-only or policy-denied, not normal SDK adoption paths.
Failure modes and troubleshooting
| Symptom | Root cause | Fix |
|---|---|---|
| Core calls are denied | Direct lanes disabled | Use control path or enable lane deliberately |
| Retrieval behavior diverges unexpectedly | Mixed control/core usage | Define one default retrieval path |
| Operational overhead increases | Broad direct-core adoption | Restrict direct-core to targeted features |
Next steps
- See direct-lane policy contract at Core direct lanes policy.
- See how the runtime fits together at How MuBit works.