Skip to main content
The Symphony Change Ledger Vector (SCLV) records changes made to SKV surfaces over time. Its engine is an independently installable C++ process that performs deterministic append-only ledger checks and produces disposable projections. The ledger is written only after a material source change is complete.

​
Operations

  • Inspect and check: validate ledger shape, continuity, and evidence.
  • Propose (v3): accept caller-declared, provider-neutral proposals for new records.
  • Recover: perform non-mutating recovery of interrupted or ambiguous state.
  • Project: emit disposable inventories of ledger state on request.

​
Admission and retirement

Every admitted SCLV record binds current indexed evidence at the time it is written. Later legitimate retirement of a surface preserves the immutable historical provenance without forcing deleted current prose back into SKVI. History remains history; current truth remains current.

​
What SCLV does not do

  • SCLV does not create or approve source changes.
  • SCLV does not rewrite existing records; it is append-only.
  • SCLV does not publish anything. Public projection belongs to SODV.
Every current SKV engine is read, query, validate, and propose only. Canonical apply is disabled until each engine’s full authority and audit contracts are complete.

SKVI

Indexes current canonical truth that SCLV records bind to.

SODV

Governs official public projection of ledger information.

SEV

Evolution cases assess changes before SCLV records them.

qxctl vector commands

Run qxctl sclv ... for inspect, check, propose, and recover.
Last modified on September 24, 2026