Architecture
Use this section for cross-cutting platform concepts.
Guideline:
Architecture docs should describe real current behavior and stable design constraints, not speculative product brainstorming. Each page says what is implemented today and what is only planned.
The platform
Section titled “The platform”- Project Model: what a Project is, and the scopes of the dashboard.
- Platform OS and Project Recipes: the control plane, the Projects it runs, and how a recipe is locked.
- Recipe Runtimes and Managed Apps: recipes that ship their own runtime, and who may load one.
- Fabric and Placement: how a Project is placed on a Node, and what is not operational yet.
- Execution Backends and Traffic: native and container execution, Kubernetes, and the proxy choice.
- Zelavis Edge: public ingress and safe proxy switching.
- Updating Without Downtime: what an update interrupts today, and the plan to make it invisible.
Services and the marketplace
Section titled “Services and the marketplace”- Service Model: apps, plugins and frontends, and how they load.
- Marketplace Allow-List: what an installation may install, and why the list can be fetched from anywhere.
- Endpoint-Backed Capabilities: every capability is an endpoint first.
Access and assistants
Section titled “Access and assistants”- Access Control: principals, permissions and scoped grants.
- Assistant Runtime: the Admin Agent, its tools and its limits.