Reference
Security boundary
What is intentionally public and what remains private.
Updated 2026-07-16 · KE Dev OS Wiki
Public
Product identity, fixed capability names, commercial requirements, public demo content, and the isolated Desktop preview may be public.
Private
Source code, private runtime topology, filesystem paths, provider credentials, internal prompts, private Brain content, deployment secrets, and unrestricted dispatch surfaces are not part of the public contract.
Release posture
Schema, entitlement, product, payment, and provider-spend gates fail closed until an owner explicitly releases them. Public copy is never release authority.