> ## 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 Quantitative Vector: Framework Contracts

> SQV owns reusable quantitative and trading-system framework contracts without acquiring user strategy logic. SOOV is its first named subvector for future C++-only FIX architecture.

The Symphony Quantitative Vector (SQV) owns reusable framework contracts for quantitative research, trading-system construction, execution support, and later quantitative engines. Strategy logic always belongs to you. SQV supplies framework surfaces and exact compatibility evidence, but it never determines your instruments, feeds, subscriptions, order logic, or execution model.

## User strategy boundary

You retain complete ownership of strategy logic. SQV does not:

* Select your instruments or data feeds
* Define subscription fields or market depth
* Determine failure behavior or normalization rules
* Write order logic or execution models
* Design your internal modular structure

Symphony gives compatibility evidence and supported operations. It never ranks strategies or imposes platform law on your trading decisions.

## SOOV: Symphony Orchestra Omega Vector

SOOV is the first named subvector under SQV. It represents a future high-performance, C++-only FIX architecture informed by historic QuanuX work. SOOV is planned as a bounded, deterministic messaging layer for trading communication. Detailed FIX behavior is not yet canonical; no FIX session, feed adapter, or broker integration is currently implemented.

## Future scope

SQV is the planned home for ratified quantitative framework components across later delivery phases. Expected areas include:

* Backtesting engines
* Broker C++ APIs
* Indicator libraries
* Quantitative mathematics
* Data-stream architecture

None of these are implemented until their respective contracts are ratified.

## Current status

SQV is a canonical architecture contract only. No SQV or SOOV engine, FIX session, feed adapter, strategy runtime, broker integration, backtester, indicator library, or data-stream component is currently implemented.

## How SQV relates to other vectors

<CardGroup cols={2}>
  <Card title="SHV" icon="cpu" href="/symphony/symphony/vectors/shv">
    Supplies hardware capability evidence that constrains quantitative engine design.
  </Card>

  <Card title="SNV" icon="server" href="/symphony/symphony/vectors/snv">
    Records the Nodes where quantitative workloads execute.
  </Card>

  <Card title="SKV" icon="book-open" href="/symphony/symphony/skv/overview">
    Governs SQV contracts, evolution, and official publication relationships.
  </Card>
</CardGroup>


## Related topics

- [Symphony Knowledge Vector: SKV Framework Overview](/symphony/symphony/skv/overview.md)
- [SACV: API Contract Governance for QuanuX Symphony](/symphony/symphony/skv/sacv.md)
- [SEV: Symphony Evolution Vector for Planned Changes](/symphony/symphony/skv/sev.md)
- [SAV: Symphony Accordare Vector for Composition Evaluation](/symphony/symphony/skv/sav.md)
- [Symphony Validator: Deterministic Read-Only Repository Checks](/symphony/symphony/governance/validator.md)