Skip to content

v0.7.0

Choose a tag to compare

View all tags
@github-actions github-actions released this 12 Aug 19:07
· 47 commits to main since this release
v0.7.0
994d332
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

ANNPack packages a documentation corpus into a single immutable, searchable artifact, and gives every retrieval an offline-checkable receipt naming the passage, the artifact, and the source revision it came from.

The browser demo — an OKF bundle compiled and searched in the page over HTTP byte ranges — runs locally via python3 web/serve.py. There is no hosted instance at present.

What this release is

The current ANNPack generation: the v3 container format, exact BM25 retrieval with normative tokenization, and the EVIDENCE-v1 receipt chain. Artifacts are content-addressed and reproducible by this builder across operating systems and toolchain versions.

A receipt establishes that a specific passage existed, unmodified, in a named artifact built from a named source revision — checkable with no artifact, no network access, and no trust in whatever produced the citation. It does not establish that a model's answer follows from the passage.

Installing

Download the binary for your platform below, verify its checksum, and extract:

curl -sSLO https://github.com/Arjun2729/ANNPACK/releases/download/v0.7.0/annpack-aarch64-apple-darwin.tar.gz
curl -sSLO https://github.com/Arjun2729/ANNPACK/releases/download/v0.7.0/annpack-aarch64-apple-darwin.tar.gz.sha256
shasum -a 256 -c annpack-aarch64-apple-darwin.tar.gz.sha256
tar xzf annpack-aarch64-apple-darwin.tar.gz

Every binary here carries GitHub-native build provenance, checkable with gh attestation verify.

From source, with Rust 1.88 or newer:

cargo install --git https://github.com/Arjun2729/ANNPACK --tag v0.7.0 annpack

Bindings

pip install annpack and @annpack/node are thin process bindings: they drive the CLI above and do not parse artifact bytes themselves, so untrusted input stays in the Rust runtime. Both require the binary installed.

Interoperability

Core remains v1.0-draft. Three implementations — the Rust reference, the browser runtime, and a reader written from the specification alone — run the conformance runner on every build. That is evidence the specification can drive a second implementation; it is not independent interoperability, because the spec-derived reader shares an author with the reference. Core loses -draft when a reader written without access to this repository passes the suite.

Full detail in the README and the specifications.

Assets 8
Loading