Skip to main content
The Symphony Knowledge Vector (SKV) is the canonical framework for Symphony’s declarative platform knowledge. It preserves architectural truth, module boundaries, contracts, doctrine, and compatibility knowledge in a structure that humans, validators, qxctl, CI, and agentic tools consume consistently. SKV is not a runtime; it is the shared knowledge layer that every vector routes through.

​
The Contract Quad

Every semantic owner in SKV publishes a Contract Quad:
  • INTENT.md: purpose, scope, and non-scope
  • MANIFEST.md: canonical surfaces and delegation
  • SKILL.md: safe usage procedure for callers
  • SPEC.md: normative behavior
Schemas, registries, profiles, ledgers, and other artifacts stay outside the four-member Quad and remain governed by the same owner.

​
Companion surfaces

Two SKV-owned companions route across every vector:
  • knowledge/SLANG.md maps each platform term to the exact contract that owns its semantics.
  • knowledge/NAMESPACES.md records identity-family ownership without dictating grammar, allocation, lifecycle, or individual identities.
Neither companion is a fifth Quad member, a new vector, or a runtime service.

​
Interpretation rule

Current contracts describe current truth. Append-only SCLV and SODV records preserve what was known, authorized, or completed at their recorded point in time. When contract state, implementation evidence, and the latest applicable record disagree, the disagreement is drift for review. Tooling must not silently invent a reconciliation.

​
Sub-vectors

SKVI

Indexes each current canonical surface exactly once.

SCLV

Append-only change ledger for completed material source changes.

SACV

Bounded OpenAPI 3.2.0 governance and compatibility diffs.

SODV

Governs official QuanuX publication and release records.

SSFV

Feature identity, freshness, and administration assurance.

SAV

Accordare composition and three-axis compatibility evaluation.

SEV

Evolution cases, disposition planning, and novelty checks.

Governance

SSIAG identity and STAV audit governance for authorized mutations.
Every current SKV engine is read, query, validate, and propose only. Programmatic canonical apply is disabled until each engine’s SSIAG permission, expected-state transaction, qxctl safeguard, STAV event, recovery, and negative-test contracts are complete.
Last modified on September 24, 2026