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

# Symphony Vectors and Delivery Phases

> Understand Symphony's enduring semantic ownership domains (vectors) vs chronological delivery phases, plus the Contract Quad and current vector status.

Symphony organizes its architecture around two ideas: **vectors** are enduring semantic ownership domains, and **phases** are chronological delivery campaigns. A component first researched in one phase does not make that phase its permanent owner. Vectors keep meaning stable while implementation evolves.

## What is a vector?

A vector is an enduring bounded semantic-ownership domain whose canonical contract owns that domain's meaning and permitted operations. Each vector receives a **Contract Quad**: `INTENT.md`, `MANIFEST.md`, `SKILL.md`, and `SPEC.md`, plus focused companion surfaces it actually needs. The vector declares its canonical surfaces and delegation graph, SKVI maps each current surface exactly once, and obsolete companions are superseded through governed evolution rather than lingering as contradictory context.

## Vector status

| Vector                                               | Status                                                | Page                                            |
| ---------------------------------------------------- | ----------------------------------------------------- | ----------------------------------------------- |
| **SKV** — Symphony Knowledge Vector                  | Implemented: Phase 1 foundation with indexed surfaces | [/skv/overview](/symphony/symphony/skv/overview)         |
| **SKVI** — Source indexing                           | Implemented: inspect/check/propose engine             | [/skv/skvi](/symphony/symphony/skv/skvi)                 |
| **SCLV** — Change ledger                             | Implemented: append-only ledger checks                | [/skv/sclv](/symphony/symphony/skv/sclv)                 |
| **SACV** — API contract governance                   | Implemented: OpenAPI 3.2.0 checks                     | [/skv/sacv](/symphony/symphony/skv/sacv)                 |
| **SODV** — Official documentation/release governance | Implemented: local release-ledger checks              | [/skv/sodv](/symphony/symphony/skv/sodv)                 |
| **SSFV** — Feature identity/administration           | Implemented: structural feature checks                | [/skv/ssfv](/symphony/symphony/skv/ssfv)                 |
| **SAV** — Accordare composition                      | Implemented: freezing-path evaluation                 | [/skv/sav](/symphony/symphony/skv/sav)                   |
| **SEV** — Evolution                                  | Implemented: impact/disposition planning              | [/skv/sev](/symphony/symphony/skv/sev)                   |
| **SSIAG** — Secure Identity and Access Governance    | Implemented: cgo-free Go foundation                   | [/governance/ssiag](/symphony/symphony/governance/ssiag) |
| **STAV** — TOPS audit protocol                       | Implemented: per-TOPS append-only ledger              | [/governance/stav](/symphony/symphony/governance/stav)   |
| **SOV** — Ops Vector                                 | Emerging: provisioning, Habitat, Nest delivery        | [/vectors/sov](/symphony/symphony/vectors/sov)           |
| **SCV** — Cloud Vector                               | Implemented: eight C++ source-knowledge engines       | [/vectors/scv](/symphony/symphony/vectors/scv)           |
| **SNV** — Node Vector                                | Emerging: SNIV, SNRV, SCIV, SCNV composition          | [/vectors/snv](/symphony/symphony/vectors/snv)           |
| **SQV** — Quantitative Vector                        | Emerging: SOOV FIX architecture subvector             | [/vectors/sqv](/symphony/symphony/vectors/sqv)           |
| **SHV** — Hardware Vector                            | Implemented: C++ source, catalogue, profile engines   | [/vectors/shv](/symphony/symphony/vectors/shv)           |
| **SIV** — Intelligence Vector                        | Emerging: SMCV optional Markdown; SAIV reserved       | [/vectors/siv](/symphony/symphony/vectors/siv)           |

## Contract Quad and companion surfaces

Every vector receives:

1. **INTENT.md** — purpose and scope
2. **MANIFEST.md** — identity, declared surfaces, delegation graph
3. **SKILL.md** — safe use and operational guidance
4. **SPEC.md** — normative behavior and boundaries

Companion surfaces such as `SLANG.md`, `NAMESPACES.md`, registries, schemas, and profiles remain governed artifacts outside the four-member structure. They route or specialize owner truth but cannot expand their own authority.

## Evidence-based integration

A deferred engine has no fabricated receipt. A proposed API has no invented registry entry. An unpublished contract has no SODV completion claim. This is evidence-based integration, not ceremonial duplication.


## Related topics

- [Quickstart: Explore QuanuX Symphony](/symphony/symphony/quickstart.md)
- [Symphony Quantitative Vector: Framework Contracts](/symphony/symphony/vectors/sqv.md)
- [Symphony Architecture](/symphony/symphony/concepts/architecture.md)
- [QuanuX Symphony Documentation](/symphony/symphony/index.md)
- [Symphony Ops Vector: qxctl Operations Control](/symphony/symphony/vectors/sov.md)