Q-Office-Suite historical runtime
Historical Windows packaging for a local HTTP interface to Qovaryx text specialists. This repository contains a compiled runtime artifact; it is separate from the model-weight repositories and the compatible Python source packages.
Status — October 3, 2026: Qovaryx is on the back burner. Desktop downloads are paused; there is no current public installer, purchase, or trial. These repositories remain as research references. Published weights are separate from desktop product availability.
Published packaging
The repository contains q_office_suite.exe, its checksum file, and config.json. Configuration records a Nuitka Windows x86-64 build dated June 2, 2026, with nine specialists and a default port of 8788. These are packaging records, not a fresh execution or compatibility test.
The recorded nine-specialist set comprises Q-FinCite, Q-Invoice, Q-CmdSafe, Q-ToolCall, Q-SheetExtract, Q-DocCite, Q-Meeting, Q-Triage, and Q-Coder. The later Q-RAG checkpoint is a separate release; this historical nine-specialist count does not certify support for every subsequent specialist.
Model weights and their tokenizers/configurations must be supplied separately in the format expected by this runtime. The entrypoint source and dispatch implementation are not bundled as an importable bleeding_edge source package. This binary therefore does not satisfy the custom Python import requirements listed on the specialist cards.
Historical interface
The original documentation described /health, /specialists, /ask, and /run/{specialist} HTTP routes on a local server, with environment-based model paths and port configuration. These describe the historical integration contract. Endpoint behavior, security, installation, and dependencies were not rerun or certified during this page cleanup.
Claims that the complete suite fits within 1 GB RAM, runs in under a second on ordinary hardware, or requires no network under every integration have been removed. Hardware requirements depend on the actual model set and workload. Local inference does not remove network requirements of optional licensing, market data, broker, or external-service integrations.
Evaluation scope
The earlier perfect-score table combined small specialist fixtures with a runtime page. It did not establish application-level correctness or production readiness. Read the individual specialist cards and their original evaluation metadata for task-specific scope and limitations.
License
The existing repository metadata records Apache-2.0. Earlier documentation separately described the runtime entrypoint and dispatch as proprietary. This cleanup does not relicense the binary or resolve that distinction; review applicable artifact terms before use or redistribution. Specialist weight licenses are recorded on their own repositories.
Project and support
J.E. Herizon LLC, doing business as JE Horizon.
- Downloads last month
- 316