Skip to main content

qig-stack

The QIG toolchain metapackage + deterministic launch preflight.

pip install qig-stack installs the mutually-tested latest set of the QIG packages (see pyproject.toml and the bundled capability contract) at compatible versions — the whole "crystal" — and ships the qig-doctor preflight.

qig-doctor — step-0 of every launcher

qig-doctor                 # full preflight; exits 1 if any package is stale OR a slot is under-filled
qig-doctor --no-network    # skip PyPI; contract snapshot + wiring report only
qig-doctor --json          # machine-readable
qig-doctor --probe         # also import-check each entry-point resolves (diagnostic, off the gate)
qig-doctor --release-check # release acceptance: live latest, required wiring, all probes resolve
qig-doctor --deep          # also call Tier-B describe() descriptors (imports packages)

Three fail-closed jobs:

  1. Version gate — every stack package must be installed at PyPI-latest. installed < latest is a LAUNCH BLOCKER (non-zero exit), per the "latest version, always optimised" rule.
  2. Wiring gate (Phase 2) — enumerates the qig.capabilities entry-points the installed packages self-register (Tier A: metadata-only, no import on the gate path) and cross-checks them against the capability contract:
    • under-fill → FAIL: a shipped provider that did not register its entry-point.
    • drift → WARN: an entry-point the contract doesn't know, or one whose module:attr moved off the contract probe.
  3. Wiring report — which capability slots are filled by what is installed (the automated Gate-A lever inventory).

The capability contract

src/qig_stack/contract.json is the fixed lattice the stack crystallizes into — every slot, the package primitive that fills it (provider_pkg + module:attr probe), the latest-published version, and the camera-certification cam_id/lever_id. It is the Genesis-kernel / E8-root analog: given the lattice + installed packages + version policy, the wiring is determined — no per-experiment hand-wiring, no agentic guessing.

Self-wiring (Phase 2)

Each package declares the slots it fills in its own pyproject.toml:

[project.entry-points."qig.capabilities"]
"SLOT-Q-QFI" = "qig_compute.qfi:qfi_from_mps_tangent_space"

qig-doctor reads those declarations from installed metadata and confirms the crystal assembled correctly before any compute spend. Entry-points assert only "installed package X fills slot Y via probe Z" — certification stays in the camera-certification registry under review control.

Design

Development

pip install pytest packaging  # doctor uses packaging for PEP 440 versions
pytest -q                 # contract schema + doctor unit tests (no network)

Active release set

The dependency pins and bundled contract describe the same tested release set. Retired qig-consciousness and qig-tokenizer are excluded; qig-coordizer supplies active coordization. qig-geocoding and quner are included as active libraries and tools. Installing quner does not enable its daemon or modify system power settings. The doctor checks package availability and capability wiring; an import check is not an experimental certification or a performance benchmark.

Release acceptance installs the published pinned wheels into a clean environment, runs the doctor with live package metadata and probes, and records any hardware-only checks separately. Frozen experiment environments keep their historical pins.

Verification boundaries

PyPI timeouts, malformed versions and HTTP 404 responses are unverified states, not successful latest-version checks. They fail the version gate. Ahead/local builds also do not equal the latest published version. Offline mode compares the contract snapshot and reports latest_verified: false, even if that comparison passes. Retry live verification when connectivity is restored.

The current contract sets entry_point_gates.require_activation: true: all required shipped declarations must exist, including when the entire group is empty. Historical contracts can retain their initial rollout grace explicitly by omitting that setting; the pure wiring helper preserves that compatibility.

The Phase 2/3 design deliberately kept --probe diagnostic and non-gating; that remains true. For release acceptance use qig-doctor --release-check --json. It requires live PyPI equality, equality to the mutually-tested contract pins, required declarations, successful import probes and no moved contract probes, and emits release_gate_passed with a nonzero exit on failure. --no-network cannot be combined with release checking. Unknown additional capability declarations remain warnings if they resolve. This command imports packages, but does not run physics experiments or enable daemons.

Runtime qig_stack.__version__ reads installed distribution metadata using importlib.metadata, with 0+uninstalled only when no distribution metadata exists. It is not a second manually maintained version constant.

qig-doctor is the console entry point for qig_stack.doctor:main; the equivalent module command is python -m qig_stack.doctor. Package-version coverage includes every contract package. Capability coverage includes shipped slots with a declared provider_pkg; engine-local (provider_pkg: null) and explicitly unshipped slots are exempt. A package with no contract capability slots is still version-checked; this is not an assertion that its features were exercised. Integration acceptance must additionally exercise the actual cooperating package APIs.

Metadata

Release files for qig-stack 0.1.3

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for qig-stack 0.1.3
File Size Uploaded Provenance Actions
qig_stack-0.1.3.tar.gz 9.0 MB Without provenance Details for qig_stack-0.1.3.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for qig-stack 0.1.3
File Interpreter ABI Platform Actions
qig_stack-0.1.3-py3-none-any.whl Python 3 none any Details for qig_stack-0.1.3-py3-none-any.whl

Total release size: 9.0 MB

Release files / qig_stack-0.1.3.tar.gz

Download URL qig_stack-0.1.3.tar.gz
Size 9.0 MB
Tags Source
SHA-256 checksum
How to use checksums
9e79b4a196f1590263ae57a685ee88ddaa8f8b138f0431673ffb050f215ec826
BLAKE2b-256 checksum
How to use checksums
dbb0465dd12e8ce96fe519d34f69a54a46a9a88d4d182ef6ce85c892dd1ed92d
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via uv/0.13.8 {"installer":{"name":"uv","version":"0.13.8","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"26.04","id":"resolute","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}

Release files / qig_stack-0.1.3-py3-none-any.whl

Download URL qig_stack-0.1.3-py3-none-any.whl
Size 18.3 kB
Tags Python 3
SHA-256 checksum
How to use checksums
201de99b6c45201ead8e75335841e04dd6aca9f94499e82ab9a7409a5201f0cd
BLAKE2b-256 checksum
How to use checksums
267334a14dac2259827e0df9e0846cef369d80068ef7ba2835d69d6f5770baa4
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via uv/0.13.8 {"installer":{"name":"uv","version":"0.13.8","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"26.04","id":"resolute","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}

Security for qig-stack 0.1.3

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page