Skip to content
QuanuXPublic

About

Symphony is the flagship offering from QuanuX. A fully open source operating system designed for autonomous quantitative trading, research, and infrastructure. Architected as the first Vector-Graph-Application "VGA", Agent-first // humans welcome. Symphony Beta launch 11/16/26. Documentation in 35+ languages https://docs.quanux.org/symphony

Resources

Security policy

Stars

2 stars

Watchers

0 watching

Forks

Latest commit

 

History

768 Commits

Folders and files

Repository files navigation

QuanuX Symphony — Open-Source VGAA quantOS for Quantitative Research, Trading Systems, and Sovereign Infrastructure QuanuX Symphony VGAA Capabilities, Domain Vectors, and Public Beta 0.2.0-beta.2 Platform Profiles QuanuX Symphony Monorepo Ownership, Verification Assurance Gates, and Source Integrity

QuanuX Symphony

A quantOS for quantitative research, trading systems and infrastructure.

Install the Public Beta · Start from source · Explore the components · Platform targets · Report a problem

Symphony is developed through VGAA — Vector-Graph Application Architecture. Its vectors organize quantitative data, replay, hardware and infrastructure knowledge, and explicit administrative control, with independently installed modules implementing those capabilities. Native engines and SDKs perform the domain work; qxctl gives people and agents a common way to inspect, validate and administer the components they select.

Build the environment your work needs. Users can compose programs, introduce modules and integrate approaches beyond those anticipated here. Published tools retain their specific operating contracts; your strategy logic, provider choices, hardware and deployment topology remain under your control.

Important

Public Beta available: Symphony 0.2.0-beta.2 supplies clean CI-built binaries, independently maintainable packages, SDK exports and optional corresponding source on four profiles. The feature freeze remains in force: current work covers defects, hardening, packaging, qualification, documentation and release operations. Native credential/provider limits remain explicit below; installing the beta does not activate a provider or qualify a user's live deployment.


00 // VGAA TOPOLOGY & MODULE BOUNDARIES

System Topology Overview

flowchart TD
    subgraph Control["Administrative & Knowledge Spine (Cold / Freezing Path)"]
        QX["qxctl (Go 1.26.5 CLI)\nStructured Grammar · Exact Owner Invocation"]
        KSC["Knowledge Session Coordinator & Maestro\nBounded Sessions · Lifecycle Plans · Engine Presence"]
        VAL["symphony-validator & C++ Foundation\nSKVI · SCLV · SACV · SODV · SSFV · SAV · SEV"]
    end

    subgraph Governance["Identity, Authorization & Audit"]
        SSIAG["SSIAG\nPolicy Dispatch & Provider Bindings"]
        STAV["STAV & Accordare Producer\nAppend-Only Audit Commitment"]
    end

    subgraph Infra["Cloud, Hardware, Nodes & Operations"]
        SCVSHV["SCV · SHV · DuckDB Connectors\nCloud & Traceable Hardware Graphs"]
        SNVSOV["SNV (5 Node Engines) · SOV\nNode Evidence · Local Handoff & Scoped SSH"]
    end

    subgraph Quant["Quantitative Research & Connection Owners"]
        SQV["SQV C++ SDKs & Engines\nCapture · Metadata · Flow · Conversion · Replay"]
        SBV["SBV Native Backtest Engine\nBounded Research · Optional Go Client"]
        CONN["SOOV (FIX) · SCABV (IBKR) · SRRAPIV (R API+ C++)\nExplicitly Scoped Connection Classes"]
    end

    QX --> KSC & VAL
    QX --> SSIAG & STAV
    QX --> SCVSHV & SNVSOV
    QX --> SQV & SBV & CONN
    SSIAG --> STAV
Loading

01 // RELEASE MAINTENANCE & SOURCE CHECKPOINT

Published beta maintenance notes

The 0.2.0-beta.2 downloads include three lifecycle repairs:

  • Dependency replacement is scheduled before a new dependent is introduced.
  • A verified completed scoped-close retry returns its recorded completion without rewriting durable state.
  • Installed SSIAG and Accordare owner binaries can reinstall under exclusive target custody. Existing ownership and active-use refusals still apply.

The feature freeze covers these defect repairs. The earlier 0.2.0-beta.1 release retains its original artifacts and verification record.

The immutable Symphony beta.2 source checkpoint records the merged source at 8a6889597eef3d2713f48bf6962456f989188e18. The distributed native binaries retain their actual build source, bae2e817120467561ae051c1b08cf61be3436bac; the intervening documentation and merge commits do not rebuild or relabel them.


02 // ECOSYSTEM STEWARDSHIP & INSTALLATION BOUNDARY

Identity

QuanuX is the ecosystem and steward of official source truth. Symphony is its open-source quantOS. A user’s private Symphony/TOPS installation retains its own declared and observed state; that state does not become official QuanuX source truth.


03 // AVAILABLE REPOSITORY WORKFLOWS

What you can do today

Workflow Available in the repository Where to start
Inspect and administer an installation Query contracts, versions, command identities, installed engines, lifecycle state, and protected selections through a Go CLI with structured output. qxctl
Work with quantitative data Use C++ SDKs for capture, metadata, flow, integer conversion, retained stores, replay and checkpoints; inspect retained state through installed owner engines. SQV contracts · Installed dependency recipe
Develop a dedicated Rithmic integration Inspect exact SDK/adapter bindings and maintenance impacts; build the non-Windows native SRRAPIV runtime with an explicitly supplied SDK. Native mapping, runtime tests and live vendor qualification remain separate evidence. SRRAPIV contracts · Native runtime
Run bounded backtest research Build a signal census, run native evaluations, retain results, and exercise cancellation and recovery through SBV and the optional Go adapter. Installed SBV scenario · Go adapter
Build traceable hardware knowledge Retain source captures, replay a selected catalogue, evaluate requirements, query a graph, and preview publication with explicit provenance. Hardware starter
Inspect cloud and Node evidence Use cloud/provider source-knowledge engines and five Node engines for supplied identity, resources, cluster relationships, names, and composition. SCV source knowledge · SNV qualification
Add relational graph indexing Use the optional native DuckDB connectors for retained SCV and SHV graphs. Both connectors have installed qualification on all four MVP targets. Connector workflow · Exact dependency map
Govern local administration Apply exact authorization policy, maintain append-only audit evidence, inspect lifecycle plans, and recover bounded administrative operations. SSIAG · STAV · Operator runbooks

Note

The SBV launch scenario uses deliberately synthetic market events, a small CPU workload, and same-host process transport. It verifies that path, including uncertainty and recovery; it does not establish strategy performance, live trading readiness, or distributed performance. Cloud knowledge does not provision a cloud account, and a hardware catalogue does not install a driver.


04 // SUPPORTED OPERATING-SYSTEM PROFILES

Platform targets

The Public Beta profiles are:

Target Architecture Current qualification boundary
macOS 15 Apple Silicon / ARM64 Native installed SDKs, Go modules, retained inspection, package lifecycle, and DuckDB connectors; Apple provider contract tests remain distinct from operational Keychain access.
Ubuntu 24.04 LTS x86_64 / amd64 Native installed SDKs, Go modules, retained inspection, package lifecycle, and DuckDB connectors.
Ubuntu 24.04 LTS ARM64 / aarch64 The same selected Linux qualification on the supported ARM Linux profile.
Ubuntu 26.04 LTS x86_64 / amd64 Native installed SDKs, Go modules, retained inspection, package lifecycle, and DuckDB connectors.

The published beta record binds the selected artifacts to four-platform installer, first-use, Codex client and maintenance qualification, including native Mac PKG installation/removal. Earlier source/build campaigns, such as PR #184, remain historical evidence for their own revisions. The published release record identifies the qualified bytes; a later source build or CI run does not silently replace them.

Note

DGX Spark: Ubuntu ARM64 is the current qualification substitute. Physical DGX Spark, its DGX OS image, NVIDIA drivers, and GPU behavior are not yet qualified. Intel macOS checks provide supplemental development evidence. Native Windows is unsupported, and no native Windows port is planned; WSL and remote Linux access are separate Linux environments.


05 // BINARY PACKAGES & INSTALLER CHANNELS

Install the Public Beta

Start with the release downloads and installation and verification guide. Conda packages are published under QuanuX/beta on Anaconda. Downloadable .sh installers for all four profiles and a macOS Apple Silicon .pkg are hosted on Cloudflare. Choose the exact profile and its verified package list, including the correct Ubuntu version.

Each profile has 59 independently maintainable default packages plus optional corresponding source. SDK headers, libraries and CMake exports remain with their module owners. Standard installation uses clean CI binaries; compiling the repository is optional. User profiles, credentials and hardware/workflow state are created on the user's system rather than copied from the publisher's machine. Codex is the primary qualified client; the existing Claude, Antigravity and generic adapters remain available with their own documented boundaries.

Modules can be installed, changed, swapped and removed independently through the documented owner flows. Conda manages delivered package files; application selection, retained runtime files and service lifecycle remain explicit owner operations. The beta qualifies packaging revision upgrade/rollback and same-candidate recovery. Install beta.2 into a new private prefix and retain an existing beta.1 environment separately. Upgrade or rollback between distinct native releases is not yet qualified; installing a package does not migrate existing retained runtimes or active profiles.

Verify the detached publisher signature before installation. This beta uses a pinned self-signed publisher key; the Mac PKG has no Apple Developer ID signature or notarization. The guide explains verification and the separately available Mac shell installer. No system trust changes or automatic live-service activation are part of installation.


06 // SOURCE BUILD & FIRST-RUN VERIFICATION

Get started from source

Start with the CLI to explore the repository without enrolling a service or contacting a provider. Use a reviewed source revision and the exact Go toolchain declared in tools/qxctl/go.mod, currently Go 1.26.5.

From the repository root:

repo=$(pwd -P)
umask 077
work=$(mktemp -d "${TMPDIR:-/tmp}/symphony-first-run.XXXXXX")
(cd tools/qxctl && GOWORK=off GOTOOLCHAIN=local GOENV=off \
  GOPROXY=https://proxy.golang.org GOSUMDB=sum.golang.org \
  go build -mod=readonly -trimpath -o "$work/qxctl" ./cmd/qxctl)
"$work/qxctl" version --json
sh tests/launch-acceptance/source-smoke.sh "$work/qxctl" "$repo" "$work/evidence"

This builds a development CLI, reports its executable identity, reads the invariant registry, and checks refusal of a missing repository. It does not establish repository semantic validity; that requires the separately installed validator. An ordinary local build reports 0.1.0-dev and unavailable source-stamp fields. A release build must bind its exact source, dependency map, and build recipe separately.

Next, choose the path you need:

Full native qualification uses CMake 3.31+, a profile-selected C++26 compiler and platform SDK, and exact external dependencies. The installed CI recipe selects Xcode 26.3’s Apple compiler on macOS, Clang 18 on Ubuntu 24.04, and Clang 21 on Ubuntu 26.04; exact compiler/runtime versions are recorded per run. Individual projects may have lower CMake minimums. Go, native package, SDK, schema, and owner-interface versions are independent; the dependency map records their exact relationships.

Modules install independently into explicit prefixes with owned-file receipts and guarded removal. Keep old and new versions side by side until compatibility is verified. Installation does not activate a provider or authorize an operation. For the published binary packages and their exact maintenance scope, use the Public Beta installation guide.


07 // PROVIDER ADAPTERS & CREDENTIAL QUALIFICATION

Provider and credential status

Provider integration has several layers: a parser or SDK, a bounded session/acquisition path, credential authority, an actual provider connection, and operational acceptance. A passing fixture test proves only the layer it exercises.

Integration Implemented source capability Required before an operational launch promise
SSIAG general credential integration (L14) Internal one-shot guard, policy-bound dispatch, durable exact-owner admission snapshots, intent/outcome journal, STAV commitment and reconciliation. General permission-backed lease lifecycle/audit wiring, native recipient/provider admission and protected delivery, and the actual native consumer bridge remain incomplete. The separate Cloudflare route below does not enable these general paths.
Cloudflare native credential use Opt-in private-store provider and /v1/cloudflare/use: exact native peer/executable and target binding, one-shot secret delivery, sensitive-result import and committed STAV intent/outcome. Local native/SSIAG fixtures qualify this boundary. Actual selected deployment and live-provider qualification remain open. This explicit private-file provider is not an OS keychain or hostile same-user isolation; it does not complete the general L14, Apple/Linux or FRED/Databento bridges.
Apple Keychain Independently installed Swift metadata adapter, native peer/code checks, signed-bundle and session-readiness observations. Data-protection Keychain item/access-control operations, deployment identity and login-context qualification, and protected credential use. Metadata readiness does not open the Keychain.
Linux credentials SSIAG's portable authorization and journal foundations. The separately identified Linux Secret Service provider and native delivery integration. Headless identities need their own explicit profile.
Databento DBN decoding and replay, reference/quote support, and quote/request/attempt-bound historical acquisition composition. Actual SSIAG bridge, authorized account and entitlements, bounded request/spend approval, and real success/refusal/recovery evidence.
FRED / ALFRED Bounded native request and response handling with series/vintage/page identity and caller-supplied credential-use integration. Operational credential bridge and authorized installed-provider qualification, including partial pages and refusal paths.
IBKR Client Portal Read-only session admission, authenticated-status/account checks, bounded data reads and expiry/refusal handling through an explicit Gateway transport. An externally authenticated Gateway and authorized profile; actual installed session and transport qualification. No login automation or order entry is implied.
IBKR TWS Serialized host-session coordinator and read-only callback collection with generation/request binding, pacing, cancellation and disconnect handling. Authorized SDK 10.45 provenance, concrete vendor socket/EReader/EWrapper/Decimal bridge and actual TWS/Gateway host qualification. Fixture sessions are not vendor SDK conformance.
News Vendor-neutral article ingress, immutable revision/correction binding and capture. An authorized caller/content source and installed retention qualification. No news vendor, scraper, feed subscription or fetching of article URLs is selected.

The credential integration handoff identifies remaining general L14 implementation, deployment and qualification work. The Cloudflare private-store contract defines its separate implemented route and trust limits. Missing native implementation must be completed before its operations are advertised as supported. Users will qualify supported live-provider paths after packaging; unavailable live test profiles do not block package preparation. Credentials and private provider payloads must remain outside command arguments, logs, public issues, and qualification artifacts.


08 // DOMAIN VECTORS & MODULE INVENTORY

Architecture

The Symphony source is organized as a monorepo for inspectability, with independently versioned and installable runtime components. A user can select, update, diagnose and remove engines individually. Shared native mechanics do not make the system a single resident process.

Area Components and responsibility
Administrative interface qxctl owns CLI grammar and presentation. It invokes exact installed owners and preserves their response and authorization boundaries.
Knowledge foundation C++ foundation provides bounded framing, JSON, hashes, manifests and receipt mechanics. Validator performs deterministic read-only checks.
Coordination Knowledge Session Coordinator manages bounded sessions, compatibility and lifecycle plans/journals. Maestro records authenticated engine presence; it does not schedule or execute engines.
Identity and audit SSIAG owns authentication/authorization and provider bindings. STAV owns append authority; Go protocol and Accordare producer retain separate roles.
Knowledge governance SKVI indexes declared surfaces; SCLV checks change history; SACV checks API contracts; SODV checks release-publication evidence; SSFV checks feature truth.
Composition and evolution SAV / Accordare resolves and evaluates explicit composition; SEV prepares evolution plans and evidence. Neither silently applies canonical changes.
Cloud, hardware and Nodes SCV, SHV and SNV own their respective source evidence, interpretation and supplied state. Optional DuckDB connectors add retained relational graph indexes.
Quantitative work SQV includes capture, metadata, flow, conversion, retention, replay and source adapters. SBV owns native backtest research, with an optional Go client.
Connection classes SQV's peer owners are SOOV for FIX, SCABV for component-scoped broker/API bindings, and sovereign SRRAPIV for dedicated R API+ C++ integration. Exact module contracts delimit implementation and qualification.
Operations SOV provides bounded local handoff and an optional scoped SSH carrier. These mechanisms do not establish general cloud provisioning or cross-host deployment acceptance.

The machine-readable component/version map and functional qualification manifest enumerate current roots and test selections. A component in that inventory is not automatically selected for the first binary release. Each module's Contract Quad (INTENT.md, MANIFEST.md, SKILL.md, SPEC.md) and INSTALL.md define its actual boundary.


09 // ARCHITECTURAL PRINCIPLES & PHYSICAL MODEL

Doctrine

  • Explicit ownership: domain vectors own meaning; qxctl presents their operations. Derived views retain provenance to their source owners.
  • Evidence before action: exact versions, receipt identities, expected state, bounded requests, and explicit authority constrain supported mutations. An uncertain outcome is reconciled rather than silently retried.
  • Independent deployment: modules retain their own configuration, state, installation, update and removal boundaries. There is no implicit newest-version selection.
  • User-controlled composition: users choose their programs, modules, provider integrations and bus topology, including new approaches beyond the supplied components. Published operations retain their explicit authority contracts; human or agent identity alone grants no authority.
  • A protected hot path: administration and knowledge work are cold or freezing-path capabilities. qxctl is not a mandatory resident trading-loop dependency. Explicitly installed SSIAG/STAV services retain their documented supervision roles.

A Node identifies physical computer resources. A Habitat is the exact OS/package conditioning selected for a Node. A Nest serves the user's chosen purpose; it is not constrained to one strategy, file, process or broker interface. Multiple buses may coexist, and their choice remains explicit. See the architecture, terminology, identity namespaces, and platform governance for precise definitions.


10 // RESERVED SURFACES & NON-GOALS

Emerging Vector Architecture

SIV (Symphony Intelligence Vector) remains an emerging domain. Its optional SMCV Markdown mediation component has no implemented translator or command; SAIV is reserved. SAV continues to mean Symphony Accordare Vector. Prima Parte is a ratified optional Node-local witness concept, not an executable. hotpath-runtime is a proposal-only contract seed. The retired node-troll and bus-troll names are reserved tombstones.

General provider provisioning, Terraform apply, Habitat construction, Nest delivery, bus installation and canonical knowledge apply remain outside the implemented runtime promises. The Linux systemd boot receptor performs report-only lifecycle planning; it does not apply the plan. SACV currently supports bounded OpenAPI 3.2.0 JSON with internal references; YAML and external references return explicit unsupported responses. See its shipped example.


11 // PLATFORM INVARIANTS & MODULAR SOVEREIGNTY

Root-Level Governance Role

The platform governance contract defines shared invariants and modular sovereignty within the knowledge architecture. It does not absorb a vector’s meaning or a module’s runtime authority. Current contracts describe current truth; immutable change and publication records retain historical evidence. Phases describe delivery chronology, while vectors remain the enduring domain owners.


12 // QUALIFICATION EVIDENCE & RELEASE GATES

Verification and release readiness

Symphony's checks cover distinct questions:

Evidence What it establishes
Dependency map verification Source/version consistency, explicit dependency ordering and installed SDK consumption.
Functional qualification Selected native tests, Go race suites, Swift contracts, generated interfaces and installed scenarios on named profiles.
Package qualification Candidate verification and lifecycle mechanics using controlled fixtures.
SDK distribution and removal Receipt-owned headers/exports, installed consumers, refusal and resumable removal preserving unrelated files.
Dependency notice inventory Collected identities and notice material; publisher review and recursive runtime closure remain separate.
CodeQL Static-analysis baseline. C++ uses source-only analysis with documented C++26 coverage limits; a clean scan is not complete security or runtime qualification.
Published beta acceptance Exact published bytes, publisher-pinned signature, four-profile installation/client/maintenance evidence and publisher legal approval/acceptance within the initial-beta scope. Apple notarization, separate human-reviewer independence and live-provider acceptance are not claimed.
Release acceptance procedures Reusable candidate and evidence checkers. Their historical preparation packets and fixture results remain distinct from the published beta's selected artifacts and approval.

Run the source checks with CMake from the repository root:

cmake -P tests/mvp-dependencies/verify.cmake
cmake -P tests/release-qualification/verify.cmake

The published distribution dossier records the current release outcome and scope. The earlier gate checklist and Public Beta preparation dossier retain their original planning and implementation boundaries; pending inputs in those historical records are not the current published release status. Launch ownership names @quantDIY as release approver and rollback primary. Completing source tasks does not itself authorize another publication.

Symphony releases module by module. Existing SODV source publications below are public Go source-module versions, not a platform binary launch. Independent versions and compatibility boundaries remain visible through release preparation.


13 // DEFECT REPORTING, SECURITY & CONTRIBUTIONS

Support and contributing

For non-sensitive defects, open a bug report with the exact component version/source, OS/architecture, reproduction, expected outcome and redacted evidence. For vulnerabilities, use the support-ticket route in SECURITY.md; do not disclose credentials or exploit details in a public issue. Response ownership and intake qualification remain tracked release work; no response-time guarantee is stated.

When changing a component, start with its owning contracts and installation guide. Keep proposals labelled, preserve independent versions and receipt ownership, update the dependency/test maps when their inputs change, and run the affected focused and installed checks. Canonical change recording follows SCLV guidance; historical records are append-only.


14 // FIRST-PARTY LANGUAGE POLICY

Python Doctrine

This Symphony repository's first-party source, generators, schema authoring, tests and acceptance helpers have no Python implementation or dependency. The separate distribution repository documents its Python-based packaging and setup tools. User-authored programs and explicitly selected isolated Habitats are not restricted by this repository policy.


15 // LICENSING & COMMERCIAL TERMS

License

Symphony is licensed under the GNU Affero General Public License v3.0 only (AGPL-3.0-only). Without a separate written agreement, use, modification, distribution and network deployment are governed by that license. Commercial licensing inquiries: licensing@quanux.org.


16 // MACHINE-CHECKED INVENTORY

Repository facts

The following generated snapshot is validated against the owning source contracts. Its feature catalog is intentionally partial; counts are not a claim of complete platform or host coverage.

Machine-checked feature, command and source-publication inventory

Machine-Checked Repository Snapshot

This bounded summary is derived from canonical SSFV coverage and routing, the feature-administration profile, the qxctl command registry, and completed SODV publication records. Edit its source contracts, then regenerate; do not hand-edit the values below.

  • SSFV catalog state: partial; registered features: 154; registered owner scopes: 69; ratified nested features: 79.
  • Feature-administration expectations: 427 reviewed surfaces; 416 required, 29 evidence-backed exemptions, 9 prohibitions, 0 unreviewed.
  • qxctl stable command identities: 525.
  • Registered owner capabilities:
    • ssfv:symphony:accordare-stav-producer
    • ssfv:symphony:knowledge-session-coordinator
    • ssfv:symphony:knowledge-vector-engine-foundation
    • ssfv:symphony:maestro-presence-authority
    • ssfv:symphony:native-source-support-cpp
    • ssfv:symphony:platform
    • ssfv:symphony:qxctl
    • ssfv:symphony:sacv-engine
    • ssfv:symphony:sav-engine
    • ssfv:symphony:sbv-engine
    • ssfv:symphony:sbv-go-adapter
    • ssfv:symphony:scabv-ibkr-client-portal-cpp
    • ssfv:symphony:scabv-ibkr-tws-cpp
    • ssfv:symphony:scev-cf-engine
    • ssfv:symphony:scev-engine
    • ssfv:symphony:schv-aws-engine
    • ssfv:symphony:schv-azure-engine
    • ssfv:symphony:schv-do-engine
    • ssfv:symphony:schv-engine
    • ssfv:symphony:schv-gcp-engine
    • ssfv:symphony:sciv-engine
    • ssfv:symphony:sclv-engine
    • ssfv:symphony:scnv-engine
    • ssfv:symphony:scv-engine
    • ssfv:symphony:scv-graph-duckdb-connector
    • ssfv:symphony:sev-engine
    • ssfv:symphony:shv-engine
    • ssfv:symphony:shv-graph-adapter
    • ssfv:symphony:shv-graph-duckdb-connector
    • ssfv:symphony:shv-partition-engine
    • ssfv:symphony:shv-pdf-adapter
    • ssfv:symphony:shv-profile-engine
    • ssfv:symphony:shv-publication-engine
    • ssfv:symphony:shv-source-engine
    • ssfv:symphony:skvi-engine
    • ssfv:symphony:sniv-engine
    • ssfv:symphony:snrv-engine
    • ssfv:symphony:snv-common-cpp
    • ssfv:symphony:snv-engine
    • ssfv:symphony:snv-local-observer
    • ssfv:symphony:sodv-engine
    • ssfv:symphony:sov-cloudflare-adapter
    • ssfv:symphony:sov-stdio-adapter
    • ssfv:symphony:sov-transport-profile-admin
    • ssfv:symphony:sqav-attempt-engine
    • ssfv:symphony:sqav-capture-cpp
    • ssfv:symphony:sqav-databento-dbn-cpp
    • ssfv:symphony:sqav-databento-reference-cpp
    • ssfv:symphony:sqav-fred-cpp
    • ssfv:symphony:sqav-news-api-cpp
    • ssfv:symphony:sqav-request-engine
    • ssfv:symphony:sqdv-checkpoint-engine
    • ssfv:symphony:sqdv-delivery-cpp
    • ssfv:symphony:sqfv-batch-cpp
    • ssfv:symphony:sqfv-flow-engine
    • ssfv:symphony:sqmv-metadata-cpp
    • ssfv:symphony:sqmv-metadata-engine
    • ssfv:symphony:sqpv-inspection-engine
    • ssfv:symphony:sqpv-local-store-cpp
    • ssfv:symphony:sqtv-conversion-engine
    • ssfv:symphony:sqtv-integer-conversion-cpp
    • ssfv:symphony:srrapiv-runtime-cpp
    • ssfv:symphony:ssfv-engine
    • ssfv:symphony:ssiag-foundation
    • ssfv:symphony:ssiag-provider-private-store
    • ssfv:symphony:ssiag.macos-keychain-metadata
    • ssfv:symphony:stav-append-authority
    • ssfv:symphony:stav-protocol-kernel
    • ssfv:symphony:symphony-validator
  • Completed SODV source publications:
    • github.com/QuanuX/Symphony/libraries/stav-protocol-go v0.2.0 (tag libraries/stav-protocol-go/v0.2.0, source 55f8faf26f4f85213ac23cc1de7ba897b2129a4c)
    • github.com/QuanuX/Symphony/modules/accordare-stav-producer v0.1.0-dev (tag modules/accordare-stav-producer/v0.1.0-dev, source f36c3372ee5fb2ab9d1eb059eac30b543185db2d)
    • github.com/QuanuX/Symphony/modules/stav-append-authority v0.1.0 (tag modules/stav-append-authority/v0.1.0, source 55f8faf26f4f85213ac23cc1de7ba897b2129a4c)
    • github.com/QuanuX/Symphony/modules/stav-append-authority v0.2.0 (tag modules/stav-append-authority/v0.2.0, source ed7484d70607aa96e64916dd4e59d3972a61980b)
    • github.com/QuanuX/Symphony/modules/stav-append-authority v0.2.1 (tag modules/stav-append-authority/v0.2.1, source 967c005e21a8f153ed453c79baa09fe2ab549f01)
    • github.com/QuanuX/Symphony/tools/sov-ssh-adapter v0.1.0-dev (tag tools/sov-ssh-adapter/v0.1.0-dev, source 967c005e21a8f153ed453c79baa09fe2ab549f01)
  • Snapshot digest: sha256:968479005d559e6660dc395279638379e775d50e6f88cd7ddda32ae59fd6ed56

Protected local transport profile administration is registered as ssfv:symphony:sov-transport-profile-admin and ssfv:symphony:qxctl.sov-transport-profile-administration. See tools/sov-transport-profile-admin/INSTALL.md; connection execution and Cloudflare session qualification remain separate increments.


QUANUX VENTURES LLC // QUANUX.ORG · DOCS.QUANUX.ORG · QUANUX SYMPHONY // AGENTIC-FIRST · HUMANS WELCOME

About

Symphony is the flagship offering from QuanuX. A fully open source operating system designed for autonomous quantitative trading, research, and infrastructure. Architected as the first Vector-Graph-Application "VGA", Agent-first // humans welcome. Symphony Beta launch 11/16/26. Documentation in 35+ languages https://docs.quanux.org/symphony

Resources

Security policy

Stars

2 stars

Watchers

0 watching

Forks

Releases

Packages

Used by

Contributors

Languages