> ## 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.

# QuanuX Symphony Documentation

> Start with Symphony's platform doctrine, architecture, knowledge vectors, and qxctl administrative CLI.

Symphony is a modular, agentic-first trade operating system. These docs describe its current contracts and boundaries: how infrastructure is modeled, how vectors own meaning, and how qxctl administers supported operations. Start with the platform doctrine before using any administrative surface.

<CardGroup cols={2}>
  <Card title="Quickstart" icon="rocket" href="/symphony/symphony/quickstart">
    Find the shortest reading path for the platform, its contracts, and qxctl.
  </Card>

  <Card title="Platform doctrine" icon="book-open" href="/symphony/symphony/doctrine">
    Understand user ownership, caller authority, evidence, and hot-path protection.
  </Card>

  <Card title="Architecture" icon="diagram-project" href="/symphony/symphony/concepts/architecture">
    See how Nodes, Habitats, Nests, vectors, engines, and qxctl fit together.
  </Card>

  <Card title="qxctl CLI" icon="terminal" href="/symphony/symphony/qxctl/overview">
    Explore Symphony's administrative and query command surface.
  </Card>
</CardGroup>

## Explore the documentation

* [Node, Habitat, and Nest](/symphony/symphony/concepts/node-habitat-nest) defines the physical resource, its exact software conditioning, and the user-purpose workload.
* [Vectors and phases](/symphony/symphony/concepts/vectors) distinguishes enduring semantic ownership from delivery campaigns.
* [Symphony Knowledge Vector](/symphony/symphony/skv/overview) explains canonical contracts, companion surfaces, and indexed knowledge.
* [Vector engines](/symphony/symphony/engines/overview) describes the independently installed, out-of-process engines.
* [Caller authority](/symphony/symphony/concepts/caller-authority) and [hot-path isolation](/symphony/symphony/concepts/hot-path-isolation) state two essential operating boundaries.

These pages describe current documented surfaces. Follow the linked contracts and implementation evidence for the exact state of a particular component.


## Related topics

- [Quickstart: Explore QuanuX Symphony](/symphony/symphony/quickstart.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)