Fux
Deterministic knowledge retrieval for AI-assisted codebases — rank from a small git-carried index, fetch content from the systems that own it, verify at answer time.
Status (2026-08-10): T0 slice —
ingest+askwork on this repo.src/fux/exists. From a configured directory:fux ingest # builds the committed .fux/index/*.jsonl fux ask "your question" # scans it, ranks with BM25F, cites the source fileNo accelerator yet (scan-only, ~100–200 ms class queries — correct M1 behavior, not a bug) and no dense/graph query lanes (M2/M3). The v0.26 engine and its docs are archived under
archive/v0.26/, reference-only. The new architecture is specified indocs/paper/the-fux-index-paper.md(§4–§6 knowingly stale until M6) and built againstdocs/PLAN.md.The pruning gate closed (2026-08-09): FAIL. Keeping only each document's top-k terms was measured, twice, against a corpus that could actually test it — no selector came within 35.9 points of preserving candidate recall at a 6 % budget. The committed index carries full postings, permanently — ADR-0003.
The idea
- Sources own content. Repo docs stay in git; Confluence pages stay in
Confluence. Fux never keeps a durable copy (except explicit per-source
snapshotpolicy). - Git carries the index — doc-major, sharded, human-readable JSONL;
full per-document postings, dense binary codes, an extracted link graph,
and a source ledger, one line per document, sorted and content-sharded so
git itself diffs and merges it —
docs/compare/index-format.compare.md. - Answers verify themselves. Rank in the index, fetch the cited
documents live (through a version-keyed cache), re-score passages on the
fetched bytes, cite the fresh sha. (The refer plane is M4; M1's
askcites straight from the committed index.) - Laws: $0 default · stdlib-only · byte-deterministic · offline by default · one ADR per feature, every rule referenced.
Reading order
docs/paper/the-fux-index-paper.md— architecture + falsifiable predictionsdocs/compare/index-format.compare.md— the committed format, measureddocs/PLAN.md— milestones M0–M8docs/adr/0004-index-format.md— the frozen M1 schemaexamples/playground/PLAYGROUND.md— a 20-doc fixture corpus to try it ondocs/WORKLOG.md— the running build log
License: MIT.
1 maintainer
Release files for fux-engine 0.30.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| fux_engine-0.30.0.tar.gz | 7.5 MB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| fux_engine-0.30.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 14.5 MB
Release files / fux_engine-0.30.0.tar.gz
| Download URL | fux_engine-0.30.0.tar.gz |
|---|---|
| Size | 7.5 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
0a151ffb1220b7ce52c0beadc893b08ba5c04df5d31304b138b7d4fe8ca5eed4
|
|
BLAKE2b-256 checksum How to use checksums |
3616e89dae85b6600579240c12a34e6f981bc4352b969702cd1bed3a97797eba
|
| 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 Aug 10, 2026.
Transparency logRelease files / fux_engine-0.30.0-py3-none-any.whl
| Download URL | fux_engine-0.30.0-py3-none-any.whl |
|---|---|
| Size | 7.0 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
a26ad91e26a217834943ed41a75126ff1d63ceafaf26c310941345f54c62aad3
|
|
BLAKE2b-256 checksum How to use checksums |
cf17ae359225d8d0777c2969342add27cc90a3d91810272e349108e6269e1165
|
| 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 Aug 10, 2026.
Transparency log
