Skip to main content
Symphony organizes its architecture around two ideas: vectors are enduring semantic ownership domains, and phases are chronological delivery campaigns. A component first researched in one phase does not make that phase its permanent owner. Vectors keep meaning stable while implementation evolves.

​
What is a vector?

A vector is an enduring bounded semantic-ownership domain whose canonical contract owns that domain’s meaning and permitted operations. Each vector receives a Contract Quad: INTENT.md, MANIFEST.md, SKILL.md, and SPEC.md, plus focused companion surfaces it actually needs. The vector declares its canonical surfaces and delegation graph, SKVI maps each current surface exactly once, and obsolete companions are superseded through governed evolution rather than lingering as contradictory context.

​
Vector status

​
Contract Quad and companion surfaces

Every vector receives:
  1. INTENT.md — purpose and scope
  2. MANIFEST.md — identity, declared surfaces, delegation graph
  3. SKILL.md — safe use and operational guidance
  4. SPEC.md — normative behavior and boundaries
Companion surfaces such as SLANG.md, NAMESPACES.md, registries, schemas, and profiles remain governed artifacts outside the four-member structure. They route or specialize owner truth but cannot expand their own authority.

​
Evidence-based integration

A deferred engine has no fabricated receipt. A proposed API has no invented registry entry. An unpublished contract has no SODV completion claim. This is evidence-based integration, not ceremonial duplication.
Last modified on September 24, 2026