Skip to main content
The Symphony Cloud Vector (SCV) owns private semantic knowledge about offsite hardware resources and the provider realities that shape your clusters, training, research, and data work. It maps provider offerings, regions, infrastructure domains, constraints, and observed availability without ranking providers or imposing boundaries on what you may attempt.

​
Provider coverage

SCV covers the following providers and resource types:
  • AWS
  • Azure
  • Google Cloud Platform
  • DigitalOcean
  • Cloudflare
  • User-owned hardware (where comparison with offsite resources is required)

​
Installed engines

SCV knowledge is delivered through eight independently installable C++ engines. You install only the ones you need:

scv-engine

Core SCV engine for provider resource knowledge and graph construction.

scev-engine

Cloud evidence engine for bounded capture and corpus semantics.

scev-cf-engine

Cloudflare-specific evidence engine.

schv-aws-engine

AWS-specific hardware and resource knowledge engine.

schv-azure-engine

Azure-specific hardware and resource knowledge engine.

schv-do-engine

DigitalOcean-specific resource knowledge engine.

schv-gcp-engine

GCP-specific hardware and resource knowledge engine.

scv-graph-duckdb-connector

Optional relational graph connector using DuckDB for retained SQL indexing.

​
Portable provider packages and composition

SCV exposes portable provider packages through qxctl. You retain control over requirements, provider permissions, recipe alternatives, and execution decisions. qxctl supports retained workflows and protected graph selection, so you can replay exact evidence without re-querying providers.

​
Optional DuckDB connector

The scv-graph-duckdb-connector adds a bounded relational projection of immutable native graphs. DuckDB is the user-selected default SQL database. You may select dedicated graph engines in the future through additional adapters.

​
Privacy and sovereignty

An installed SCV knowledge graph belongs to your private installation. User-supplied accounts, balances, permissions, and contractual constraints are used only through explicitly enabled observation surfaces. Private facts do not enter official Symphony source truth.

​
How SCV relates to other vectors

SOV

The operational control plane that acts upon SCV evidence. SOV does not rewrite provider meaning.

SNV

Records the identities of physical Nodes and clusters that result from SCV-informed provisioning.

SHV

Owns detailed hardware capability knowledge for components SCV references.

​
Versioned interface increments

SCV releases are additive and exact-versioned. Earlier installations remain invocable at their exact scopes. Current increments include native operations, corpus snapshots, interpretation profiles, portable provider packs, composition workflows, obligation tracking, and evidence bundles. Each increment preserves prior routes, defaults, and records.
Last modified on September 24, 2026