Qorx

Qorx 1.0.4a Community Edition

Qorx 1.0.4a Community Edition is a Rust source line for local context resolution. It defines a small domain-specific language, checked .qorxb protobuf bytecode, named resolver steps, branches, runtime assertions, a Forth-inspired qstk stack tape, and qorx:// handles that resolve against local state.

The project is early. This page is written for Rust reviewers who want more than a repository link.

What it is

A .qorx file describes a mode, an objective, an evidence budget, and optionally a handle:

QORX 1
let question = "which files explain how Qorx keeps local evidence outside the model prompt?"
pack evidence from question budget 700
cache evidence key question ttl 3600
strict answer from evidence limit 2
assert supported(answer)
emit answer

The Rust implementation parses that source, checks symbol references, lowers it to QIR, compiles it to a bytecode envelope, and resolves it through local index/cache/provenance state.

qorx qorx-check goal.qorx
qorx qorx-compile goal.qorx --out goal.qorxb
qorx goal.qorxb

Why Rust

Qorx uses Rust because the runtime contract matters. The parser, bytecode envelope, cache, and receipt paths all handle local state that should return clear errors rather than guess.

The useful Rust pieces are ordinary ones:

• explicit error paths through anyhow and typed domain errors
• deterministic hashing for evidence chunks and receipts
• structured CLI commands with stable output modes
• tests around parser/runtime contracts instead of only end-to-end examples
• source builds through Cargo

What changed in 1.0.4a

Version 1.0.4a keeps the small-binary release gate and adds production-facing adapter hot swap:

• a local adapter manifest for TypeScript, Python, Rust, Go, parser, compressor, provider, or team runtime tools;
• manifest reload without rebuilding the Qorx binary;
• adapter status in qorx adapters and the science report;
• package-channel metadata for public distribution.

Version 1.0.4 added clarity and operator-facing readiness work:

• problem-first README wording
• a practical first .qorx example
• use std... imports for the first standard-library surface
• qorx-check, AST output, and QIR output for language files
• source-level cache policies for stable local resolver outputs
• assert supported(...) for fail-closed evidence checks
• if supported(...) then emit ... else emit ... branches
• qstk, a Forth-inspired bytecode stack tape inside .qorxb
• README-visible benchmark numbers
• shorter terminology for compact UI/log surfaces
• qorx doctor --json
• Windows release build verification

The current public main branch is Community Edition. Build it from source:

cargo build --release

What needs review

The question is whether the local resolver contract is worth keeping.

Useful review questions:

• Is .qorx a small language, or should it be described as a configuration format?
• Is .qorxb useful outside the CLI?
• Does local context resolution reduce repeated prompt payloads in real workflows?
• Are cache, receipt, and provenance contracts clear enough?
• What should change before people treat Qorx as production tooling?

Scope

Qorx is not a hosted AI service, a general-purpose language, a Forth implementation, or a general compression system. It cannot reconstruct arbitrary unknown files from a tiny message. It only works when the workflow has a Qorx source file, bytecode file, evidence pack, or handle that a resolver can use.

That is the narrow claim. It should be tested as a Rust runtime and CLI, not as a magic context shortcut.

Qorx Ayie is the supported local product. Qorx Ayie Starter gives new accounts 5,000 included Ayie/Cloud requests across Windows, macOS, and Linux before subscription. Edge adds signed installers, tray UX, daemon management, provider routing, account activation, and managed local-vault behavior.

This site is open source. Improve this page.