libraries/; a separate C++ coordinator owns authenticated-session and worktree-reconciliation mechanics. Engines inspect, validate, project, and propose within vector-owned contracts. They do not acquire authority merely by generating content.
Implemented engines
Knowledge Vector foundation
C++ process framing, JSON, SHA-256, snapshots, receipts, and manifest discovery.
Session coordinator
Authenticated sessions, worktree reconciliation, and lifecycle apply coordination.
SCV source engines
Eight C++26 SCV, hyperscaler, edge, and provider source-knowledge engines.
SHV engines
Hardware source, catalogue, profile, partition, publication, and adapter engines.
SKV engine family
The SKV surfaces each have their own engine:- SKVI, SCLV, SACV, SODV, and SSFV engines each implement inspect, check, propose, project (and recovery where applicable).
- SAV and SEV engines are freezing-path C++26 processes for composition evaluation and evolution cases.
Every current SKV engine is read, query, validate, and propose only. Programmatic canonical apply remains disabled until each engine’s SSIAG permission verification, expected-state transaction, qxctl safeguard, STAV event, recovery, and negative-test contracts are complete.
Common guarantees
- Independent installation and uninstallation per module
- No ambient repository crawl; manifest discovery is explicit
- No shared authority; every mutation route is gated by SSIAG plus STAV
- No hot-path residency; engines never inject latency into live workloads
Related surfaces
qxctl overview
Administrative CLI that invokes exact receipt-validated engines.
Maestro
Records docking relationships between engines and receptors.