> ## Documentation Index
> Fetch the complete documentation index at: https://docs.quanux.org/symphony/llms.txt
> Use this file to discover all available pages before exploring further.

# Quickstart: Explore QuanuX Symphony

> A guided route through Symphony's doctrine, architecture, vector contracts, and qxctl administrative surface.

Use this guide to orient yourself before operating Symphony. The documentation separates platform doctrine, user-selected infrastructure, vector-owned semantics, and administrative commands. Exact installation and execution steps belong to the relevant component's current contract.

## 1. Read the operating boundaries

Start with the [platform doctrine](/symphony/symphony/doctrine). It establishes user ownership of strategy and infrastructure, caller-class neutrality, evidence-based compatibility, and protection of the hot path.

## 2. Learn the physical model

Read [Node, Habitat, and Nest](/symphony/symphony/concepts/node-habitat-nest):

* **Node:** the identified physical computer resource.
* **Habitat:** the exact operating system and package conditioning delivered to a Node.
* **Nest:** the user-purpose workload placed into a suitable Habitat.

A cluster's buses and adapters are explicit architectural choices. Symphony does not prescribe a universal provider or strategy.

## 3. Trace ownership of meaning

The [architecture overview](/symphony/symphony/concepts/architecture) shows the relationship between vector contracts, engines, qxctl, and governed evidence. [Vectors and phases](/symphony/symphony/concepts/vectors) explains why a vector remains the semantic owner even as delivery work moves through phases. The [Symphony Knowledge Vector](/symphony/symphony/skv/overview) describes the Contract Quad and its companion surfaces.

## 4. Find the administrative surface

The [qxctl overview](/symphony/symphony/qxctl/overview) introduces the Go administrative and query CLI. Use the qxctl pages for a specific command family, such as [knowledge](/symphony/symphony/qxctl/knowledge), [lifecycle](/symphony/symphony/qxctl/lifecycle), [engines](/symphony/symphony/qxctl/engines), or [validation](/symphony/symphony/qxctl/validate). qxctl provides command grammar and presentation; vector contracts own the operations and their meaning.

## 5. Check the relevant contract and evidence

Before acting on a Node or invoking a vector engine, check the current owner contract, target state, authorization, and available receipt or validation evidence. [Caller authority](/symphony/symphony/concepts/caller-authority) and [hot-path isolation](/symphony/symphony/concepts/hot-path-isolation) explain those boundaries. An emerging surface is not an implicit operational guarantee.


## Related topics

- [QuanuX Symphony Documentation](/symphony/symphony/index.md)
- [QuanuX Symphony Platform Doctrine](/symphony/symphony/doctrine.md)
- [Hot-Path Isolation in QuanuX Symphony](/symphony/symphony/concepts/hot-path-isolation.md)
- [SACV: API Contract Governance for QuanuX Symphony](/symphony/symphony/skv/sacv.md)
- [SODV: Official Documentation and Release Governance](/symphony/symphony/skv/sodv.md)