Quickstart
Find the shortest reading path for the platform, its contracts, and qxctl.
Platform doctrine
Understand user ownership, caller authority, evidence, and hot-path protection.
Architecture
See how Nodes, Habitats, Nests, vectors, engines, and qxctl fit together.
qxctl CLI
Explore Symphony’s administrative and query command surface.
Explore the documentation
- Node, Habitat, and Nest defines the physical resource, its exact software conditioning, and the user-purpose workload.
- Vectors and phases distinguishes enduring semantic ownership from delivery campaigns.
- Symphony Knowledge Vector explains canonical contracts, companion surfaces, and indexed knowledge.
- Vector engines describes the independently installed, out-of-process engines.
- Caller authority and hot-path isolation state two essential operating boundaries.