Skip to main content
The Symphony Official Documentation Vector (SODV) governs how knowledge inside the SKV framework becomes official public documentation and release records. Its engine is an independently installable C++ process that performs local append-only release-ledger checks and produces disposable release inventories. SODV does not publish anything itself.

​
Operations

  • Inspect and check: validate release-ledger shape and continuity.
  • Verify: check caller-supplied observations of published state.
  • Propose: accept provider-neutral release proposals.
  • Recover: perform non-mutating recovery.
  • Project: emit disposable release inventories.

​
What SODV does not do

  • SODV has no network access.
  • SODV publishes nothing to GitHub, Mintlify, package registries, or any other surface.
  • SODV creates no tags and cannot declare a release complete.
  • SODV does not rank providers or favor a publication path.
Publication happens through separate authorized tooling that consults SODV evidence.

​
Completed SODV publications

stav-protocol-go v0.2.0

github.com/QuanuX/Symphony/libraries/stav-protocol-go at tag libraries/stav-protocol-go/v0.2.0.

stav-append-authority v0.1.0

github.com/QuanuX/Symphony/modules/stav-append-authority at tag modules/stav-append-authority/v0.1.0.

stav-append-authority v0.2.0

github.com/QuanuX/Symphony/modules/stav-append-authority at tag modules/stav-append-authority/v0.2.0.

qxctl vector commands

Run qxctl sodv ... to inspect, verify, propose, and project.
Every SKV engine is read, query, validate, and propose only. Canonical apply is disabled until each engine’s SSIAG, expected-state transaction, qxctl safeguard, STAV event, recovery, and negative-test contracts are complete.
Last modified on September 24, 2026