Integration — Koali Spaces
Koali Spaces is an optional presentation/composition subsystem hosted by kOA-Linux deployments when selected by profile/product configuration.
Boundary
Koali can compose admitted Konnaxion, Orgo, UCKK, SemantiK Architect and Kristal-related application surfaces, but it does not acquire their business or epistemic authority.
Owner applications retain internal route and domain ownership beneath Koali outer namespaces such as /apps/<owner>/....
Lifecycle distinction
Space activation / module admission / surface readiness
≠
Runtime Pack verification / activation
Koali's lifecycle adapter must request owner/broker lifecycle actions rather than invoking privileged process control directly from the renderer/browser.
Kristal presentation rule
A Koali view of Kristal/Runtime Pack material must preserve relevant status, certainty, authority and Reader Policy labels. Rendering does not compile, validate or recognize authority.
Current evidence
The supplied Koali maturity report is a historical 2026-09-06 baseline with a later notice documenting a successful real Konnaxion pilot on 2026-09-08. Two current Koali reference pages still describe first Konnaxion onboarding as pending. Digital Ecosystem records this as a product-documentation drift to be corrected in Koali Spaces, not as evidence that every ecosystem integration is production-complete.