From .rqmod
to evidence pack.
ResilQ Studio turns post-quantum cryptographic risk into a developer workflow: write one declarative model, validate constraints, compile to audit artefacts and optionally emit a SpinQ/OpenQASM experiment.
audit "critical-infra-pilot" {
targets = ["10.0.0.0/24", "edge.example.lt"]
layers {
transit { tls, ssh, dnssec, certs }
use { openssl, jwt, hsm, runtime }
rest { luks, tde, backups, kms }
}
score qars_ni {
mosca { t_protect="24mo"; t_data="10y"; t_quantum="96mo" }
}
backend quantum {
provider = spinqit; emit = qasm2; max_width = 3
}
}The user-facing workflow for RQmod models.
Studio is the product layer above the compiler: an editor, validator, artefact explorer and dashboard bridge for ResilQ IR, audit jobs, QARS-NI scoring, CBOM evidence and optional SpinQ/QASM2 experiments.
Describe intent, not scripts.
Declare assets, layers, policies, evidence requirements and scoring windows in one readable source file.
Make limits first-class.
Runtime, evidence, max QPU width, output formats and sovereign deployment rules are validated before anything runs.
Generate build artifacts.
Emit ResilQ IR, payloads, QARS-NI input vectors, CBOM skeletons and optional QASM2 jobs.
Inspect IR before execution.
Security teams can review normalized ResilQ IR, generated payloads, QARS input and build warnings before any audit is submitted.
Ship repeatable evidence.
Generated JSON, CBOM, QASM and manifest files are stable enough for review, signing, SOC ingestion and sovereign deployment pipelines.
One visual system.
The web page and VS Code/VSCodium extension share Omarchy-compatible ResilQ Dark syntax colors.
One small language for audit, risk and quantum experiments.
The language is intentionally narrow. Production audit logic stays deterministic; quantum backends remain optional, explicit and bounded by backend profiles so QARS-NI remains authoritative.
Audit blocks
Targets, credentials, callbacks and Transit / Use / Rest coverage.
Score blocks
QARS-NI, Mosca windows, layer weights and remediation profiles.
Backend blocks
SpinQit, local simulation, QASM2 export and future bridge adapters.
Evidence blocks
JSON, PDF, CBOM, signed manifests and SOC/GRC output contracts.
// Minimal grammar shape
audit "name" {
targets = ["cidr", "host"]
layers {
transit { tls, ssh, dnssec, certs }
use { openssl, jwt, hsm, runtime }
rest { luks, tde, backups, kms }
}
constraint {
max_runtime = "72h"
evidence = signed
local_changes = forbidden
}
output { formats = [json, cbom, pdf, qasm] }
}.rqmod source
Human-readable audit, scoring, backend and output declaration.
Parser + validator
Syntax checks, semantic checks and backend capability checks.
ResilQ IR
Stable JSON representation consumed by CLI, UI and adapters.
audit job
Webhook-ready payload for Transit, Use and Rest cryptographic discovery.
QARS-NI, CBOM
Risk vectors, scoring input and evidence inventory outputs.
QASM2 / SpinQit
Optional quantum experiment path for bounded demonstrations.
From model to audit artifacts in one command.
The MVP command is deliberately simple: validate, compile and emit. It creates the exact artifacts a dashboard, SOC connector or sovereign deployment can ingest.
# Validate and compile
resilq-q validate examples/critical-infra-pilot.rqmod
resilq-q compile examples/critical-infra-pilot.rqmod --out build/critical-infra-pilot
# Optional QASM2 / SpinQit experiment
resilq-q emit qasm2 examples/bell-spinq.rqmod --out build/bell-spinq.qasm
resilq-q run examples/bell-spinq.rqmod --backend spinqit-basic --out build/bell-runLinux-first workflow, SpinQ-ready backend abstraction.
RQmod treats quantum execution as a clearly marked experiment path. The default production path remains deterministic risk analysis; the quantum path emits bounded QASM2/SpinQit jobs for demonstrations, education and future QPU adapters.
Runtime target.
Run the CLI, parser, IR emitter, Jupyter notebooks and static docs in a Linux-first, container-friendly environment.
MVP backend.
Use `spinqit-basic` or QASM2 export first. Keep physical QPU access behind a later bridge profile.
Physical QPU isolation.
A future `spinq-local-bridge` can connect Quantum Linux to a controller host without contaminating the production scoring path.
Omarchy-compatible ResilQ Dark, adapted for the web.
The web page uses the same vocabulary as the VS Code/VSCodium theme: deep navy background, electric cyan keywords, amber numbers and constraints, violet types/layers, green strings and red diagnostics.
#0A0F1F#F4F6F5#06B6D4#F59E0B#8B5CF6#10B981Syntax colors are semantic.
Keywords
`audit`, `layers`, `score`, `backend`, `constraint`, `output`.
Types and layers
`transit`, `use`, `rest`, `quantum`, `qars_ni`.
Numbers and durations
`1024`, `0.30`, `72h`, `24mo`, `10y`.
Strings and targets
`"10.0.0.0/24"`, `"vault://prod/ssh"`, `"edge.example.lt"`.
build/
├── resilq-ir.json
├── audit-job.json
├── qars-input.json
├── cbom.json
├── spinq.qasm
├── -curl-preview.sh
└── manifest.jsonDesigned for dashboards, SOCs and sovereign deployments.
RQmod does not stop at pretty syntax. The important output is a repeatable artefact set that can be signed, reviewed, sent to an callback, exported as evidence or stored for audit history.
Install ResilQ Studio in five minutes.
The Studio starter is a self-contained Python 3.10+ package with zero runtime dependencies. The same workflow runs on Quantum Linux, Ubuntu, Fedora, Arch and Windows 10/11 — pick a platform tab below.
Quantum Linux · Ubuntu · Fedora · Arch
The reference target is Quantum Linux. Any Linux with Python 3.10 or newer works the same way: create a virtual environment, install the starter, run the validator and compile an example model.
Prerequisites
Python 3.10+, pip, git, unzip. All available from the distribution package manager.
VS Codium / VS Code
Optional. Install the bundled .vsix theme to highlight .rqmod files.
# 1) Install prerequisites
# Debian / Ubuntu / Quantum Linux base
sudo apt install -y python3 python3-venv python3-pip git unzip
# Fedora
sudo dnf install -y python3 python3-pip git unzip
# Arch / Manjaro
sudo pacman -S --needed python python-pip git unzip
# 2) Get the Studio starter
curl -LO https://rqmod.com/downloads/resilq-studio-starter-v0.2.0.zip
unzip resilq-studio-starter-v0.2.0.zip
cd resilq-studio-starter
# 3) Create an isolated environment and install
python3 -m venv .venv
source .venv/bin/activate
pip install --upgrade pip
pip install -e .
# 4) Verify with a real audit model
resilq-q --help
resilq-q validate examples/critical-infra-pilot.rqmod
resilq-q compile examples/critical-infra-pilot.rqmod \
--out build/critical-infra-pilot
# 5) Optional · Omarchy ResilQ Dark theme
codium --install-extension \
downloads/resilq-omarchy-dark-vscode-v0.1.0.vsix
# or: code --install-extension downloads/resilq-omarchy-dark-vscode-v0.1.0.vsixWindows 10 · Windows 11
Use Windows PowerShell 5.1 or PowerShell 7. Install Python via winget, then create a venv exactly like on Linux. The CLI behaviour, IR shape and artefact set are identical across platforms.
Prerequisites
Python 3.10+ from winget or python.org, Git for Windows, PowerShell 5.1+.
Execution policy
Run Set-ExecutionPolicy -Scope CurrentUser RemoteSigned once if venv activation is blocked.
# 1) Install prerequisites (PowerShell as user)
winget install --id Python.Python.3.12 -e
winget install --id Git.Git -e
# 2) Download and unpack the Studio starter
Invoke-WebRequest `
-Uri https://rqmod.com/downloads/resilq-studio-starter-v0.2.0.zip `
-OutFile resilq-studio-starter.zip
Expand-Archive resilq-studio-starter.zip -DestinationPath .
Set-Location resilq-studio-starter
# 3) Create an isolated environment and install
py -3 -m venv .venv
.\.venv\Scripts\Activate.ps1
python -m pip install --upgrade pip
pip install -e .
# 4) Verify with a real audit model
resilq-q --help
resilq-q validate examples\critical-infra-pilot.rqmod
resilq-q compile examples\critical-infra-pilot.rqmod `
--out build\critical-infra-pilot
# 5) Optional · Omarchy ResilQ Dark theme
code --install-extension `
downloads\resilq-omarchy-dark-vscode-v0.1.0.vsixExpected first output.
After compile, the build/critical-infra-pilot/ directory contains resilq-ir.json, audit-job.json, qars-input.json, cbom.json, spinq.qasm and manifest.json.
Run from a checkout.
If you prefer not to install, run the CLI module directly: PYTHONPATH=src python -m resilq_q compile examples/critical-infra-pilot.rqmod --out build/x. Same on Windows with $env:PYTHONPATH="src".
Sovereign deployments.
The starter has no runtime dependencies, so the .zip + a Python interpreter are enough for offline installation in sovereign or audit-only environments.
Where the RQmod language goes next.
v0.1 is a deliberately narrow MVP: a single audit block, a regex-based parser and one backend stub. The roadmap turns RQmod into a stable, formally specified domain language with first-class tooling, while keeping QARS-NI deterministic and authoritative.
Formal grammar & diagnostics.
Replace the regex parser with an EBNF/PEG grammar, add line/column diagnostics, fix semicolon and trailing-comma edge cases, and publish spec/rqmod-grammar.ebnf.
Modules, imports & profiles.
import "common/mosca.rqmod", let bindings, and extends "base.rqmod" so org-wide audit profiles can be shared without copy-paste.
Schema-first validation.
Wire the existing rqmod-ir.schema.json into runtime validation, add --strict, custom rule plugins, and a contract suite that round-trips every example through parser → IR → re-emit.
LSP, formatter, tree-sitter.
Language Server (completion, hover, go-to-symbol, live diagnostics), resilq-q fmt, a tree-sitter grammar for GitHub/Neovim, and pre-commit hooks.
Real SpinQit + multi-backend.
Replace the SpinQit Basic mock with the real adapter, add Qiskit/Cirq emitters for QASM2, and introduce a spinq-local-bridge profile for physical QPU controllers.
Signed evidence & CycloneDX 1.6.
Cosign-signed manifests, finalized CycloneDX 1.6 cryptoProperties mapping, IR → .rqmod decompiler for round-trip review, and a public registry of backend profiles.
What RQmod will not become.
RQmod is not a general quantum programming language. The quantum path stays bounded and non-authoritative; QARS-NI scoring stays deterministic; the parser stays small. RQmod competes with audit DSLs, not with Qiskit, Cirq or Classiq.
IR is the contract.
The .rqmod surface is allowed to evolve, but ResilQ IR (resilq-ir.json) is the stable boundary that downstream dashboards, SOC connectors and signing pipelines depend on. Every grammar change is required to round-trip through IR without semantic loss.
Start with the Studio starter, source and theme.
This page is packaged with the full ResilQ Studio starter, source-only archive, generated build artefacts, VS Code/VSCodium theme and example `.rqmod` files.
ResilQ Studio Starter
Compiler, examples, themes and generated build artefacts.
Starter source package
Repository-friendly package without the generated build directory.
Build outputs
IR, audit job, QARS input, CBOM, QASM and run-result package.
VS Code / VSCodium theme
Omarchy-compatible ResilQ Dark syntax highlighting for `.rqmod` files.
tree-sitter-rqmod
Tree-sitter grammar with Omarchy-compatible highlights.scm for Neovim, Helix and GitHub Linguist.
critical-infra-pilot.rqmod
A complete Transit / Use / Rest audit model with QARS-NI and backend constraints.
SHA-256 checksums
Checksum file for the Studio starter and related packages.