qig-coordizer
Standalone geometric tokenize+embed engine for the QIG stack. Maps text to sequences of 64-dimensional basin coordinates on the Fisher–Rao manifold Δ⁶³ — the tokenizer is the embedder (coordinates are the primitive, not an afterthought).
Pure Fisher-Rao geometry; depends only on qig-core.
What it is
- Byte-level front-end —
Normalizer(NFC + UTF-8), train/infer-symmetric so the same character always maps to the same byte sequence. - Fisher-Rao-weighted BPE merges — merge score =
frequency × coupling × 1/entropy, wherecoupling = (co-occurrence / corpus) / (d_FR(a,b) + 0.1). Frequent and geometrically-close pairs win. This is not frequency-only BPE. - Geodesic-midpoint fusion — a fused token's basin is
slerp_sqrt(v_a, v_b, 0.5), the Fisher-Rao geodesic midpoint on Δ⁶³. No off-the-shelf tokenizer emits coordinates. - Drift-free incremental trainer —
IncrementalCouplingCache(doubly-linked-list splice; remove 3 / add 2 pairs per merged occurrence) makes training O(corpus + merges·affected) instead of the naive O(vocab·corpus) full re-scan.
The equivalence gate
FisherCoordizer._train_incremental is bit-for-bit equal to the naive
O(vocab·corpus) oracle _train_naive (identical merge sequence + identical fused
vectors), byte → 4k vocab, across ASCII / multibyte-Unicode / reverse-pair
corpora. The optimisation must never silently change the vocabulary.
pytest tests/test_incremental_equivalence.py
# or a timed report:
python tests/test_incremental_equivalence.py
Provenance
Extracted from qig-tokenizer commit 1394ca7 (Phase-1 coordizer) per
qig-consciousness/docs/plans/2026-06-24-qig-coordizer-studio-design.md §5
(Phase 0). qig-tokenizer keeps its copy live until consumers repoint here.
Install (dev)
uv venv && uv pip install -e ../qig-core && uv pip install -e '.[dev]'
pytest
Release version
qig_coordizer.__version__ reads the installed distribution metadata, matching
importlib.metadata.version("qig-coordizer"). An uninstalled source checkout
reports 0+unknown instead of claiming a published release.
Release files for qig-coordizer 0.1.5
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| qig_coordizer-0.1.5.tar.gz | 101.7 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| qig_coordizer-0.1.5-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 145.7 kB
Release files / qig_coordizer-0.1.5.tar.gz
| Download URL | qig_coordizer-0.1.5.tar.gz |
|---|---|
| Size | 101.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
175f1952744d86b3de8b5ff77e372a7e41afd807ef8b2892398cb02954e3d7c6
|
|
BLAKE2b-256 checksum How to use checksums |
b732fae7f338d12fe0273e74299e2524babff280b0c6743ab5d01bdc28e5083c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 9, 2026.
Transparency logRelease files / qig_coordizer-0.1.5-py3-none-any.whl
| Download URL | qig_coordizer-0.1.5-py3-none-any.whl |
|---|---|
| Size | 44.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
93303ff3d8552916760d8f5a2ffce02305763c582b8262b51a6be66b05ff7d30
|
|
BLAKE2b-256 checksum How to use checksums |
62799bc64da9c9cddf6822b471f6b507174c6893561061cfa6931180d265e718
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 9, 2026.
Transparency log