Part 15 of 16
The platform
The four systems and where the lines are drawn: what the closed ones do, what they guarantee, and what a receipt does not prove.
- The platformThe four systems that make up CueCrux: the Crux Daemon, Crux Engine, CoreCrux and FeatureCrux, which are open, which are closed and why, and a router from what you want to do to the chapter that cover
- Crux EngineReference for the hosted CueCrux platform service: the /v1 response envelope, all 22 error types with their status and retry semantics, the five auth mechanisms, retrieval, answers, ingest, capability
- CoreCruxReference for the proprietary retrieval and event-storage engine: the complete Community Edition versus CoreCrux capability split, its contract surface and auth model, behavioural descriptions of hybr
- FeatureCruxThe internal control plane that resolves which runtime behaviours apply to a tenant and request and records each decision for audit: what it records, how it fails, its auth posture, and why it is not
- How they fit togetherExplanation of the whole CueCrux platform as one picture: Crux Daemon, Crux Engine, CoreCrux and FeatureCrux, what runs where, which contracts are shared, and what stays yours in each of the four depl
- Assurance and complianceWhat a CROWN receipt proves and what it does not, what can bypass capture, the enforcement state of every trust control, the honest status of all ten compliance documents, and what you can verify your