Skip to main content
The Symphony Hardware Vector (SHV) owns hardware-capability knowledge that helps you understand how physical design can enable, constrain, port, or extend quantitative software. It covers processors, CPU core types, GPUs, NICs and fibre interfaces, motherboards, cache hierarchies, memory, NVMe, and complete system builds. Default curation prioritizes original components and evidenced variants starting from 2018.

​
Scope and coverage

SHV may cover any evidenced physical capability relevant to program design. You control the coverage profile through qxctl. The default date basis is model introduction, not an inferred individual manufacture date. You may expand, narrow, replace, or remove this filter.

​
Implemented engines

SHV knowledge is delivered through multiple independently installable C++ engines:

shv-engine

Core kernel (0.4.0-dev): coverage profiles, retained-source catalogue build/replay, requirement evaluation, deterministic graph projection, and source-backed graph validation.

shv-source-engine

Source identity, relocation plans, byte-capture binding, and source-replayed provenance graphs.

shv-profile-engine

Declaration conformance, portable recipes, and exact local source binding.

shv-partition-engine

Hardware partition and component mapping operations.

shv-publication-engine

Protected caller catalogue heads, original-source replay, and durable snapshot recovery.

shv-graph-adapter

Generic C++ graph port and in-memory portable reference adapter for lossless exchange.

shv-graph-duckdb-connector

Optional DuckDB relational projection of hardware graph evidence.

shv-pdf-adapter

Bounded PDF extraction and documentary assertion revalidation from original bytes.

​
Source revision and provenance

The shv-source-engine implements stable source identity, explicit relocation plans, pure transition validation, actual-byte capture binding, and source-replayed provenance graphs. These are read-only operations. Core curation prioritizes original component identity and evidenced variants. Protected source activation is handled separately; the pure source engine does not grant authority.

​
Graph exchange and storage

The shv-graph-adapter supplies a generic C++ graph port for lossless exchange and structural queries. Durable storage is implemented through the DuckDB SQL default. No dedicated graph database is currently selected.

​
PDF evidence boundary

The shv-pdf-adapter extracts qualified documentary assertions from explicit PDF tables and revalidates them from original bytes after generic graph exchange. General PDF coverage remains separate scoped work.

​
Remaining work

A broad hardware atlas, automated source acquisition, multi-source conflict aggregation, additional vendor-specific database drivers, custom plugin loading, and Composer integration remain later work. Broad component mappings and durable vendor drivers are also open.

​
How SHV relates to other vectors

SNV

Records the Nodes that contain the hardware SHV describes.

SCV

References provider hardware offerings that SHV characterizes in detail.

SOV

May act on SHV evidence when provisioning or conditioning Nodes.
Last modified on September 24, 2026