Quickstart — run Concordance on any laptop

No model, no network, no account. Five minutes. Concordance is pure Rust with no runtime dependencies, so it runs on Linux, macOS and Windows, on both Intel (x86-64) and Apple-Silicon / ARM (aarch64).

1. Get Concordance

Option A — prebuilt binary (fastest)

PlatformArtifactStatus
Linux x86-64concordance-linux-x86_64 (+ .sha256)available now
Linux aarch64 (ARM)concordance-linux-aarch64build from source, or CI follow-on
macOS arm64 (M1/M2/M3) & x86-64signed .dmgCI follow-on (Apple-Silicon runner)
Windows x86-64 & ARMsigned .exe / .msiCI follow-on (Windows runner)

Download the artifact for your platform, verify its checksum, and run it:

# Linux / macOS
chmod +x concordance-linux-x86_64
sha256sum -c concordance-linux-x86_64.sha256      # 'shasum -a 256 -c' on macOS
./concordance-linux-x86_64 about

:: Windows (PowerShell) — verify then run
Get-FileHash .\concordance.exe -Algorithm SHA256
.\concordance.exe about

Option B — build from source (works identically on all three OSes)

Install Rust (rustup), then from the Concordance source tree:

cargo build --release            # default features = egress-free
./target/release/concordance about

On Windows the binary is target\release\concordance.exe. You can also build for a different architecture of the same OS — e.g. a Linux-ARM binary from an x86-64 Linux box:

rustup target add aarch64-unknown-linux-gnu
cargo build --release --target aarch64-unknown-linux-gnu

Building for a different operating system must be done on that OS: a macOS (Apple-Silicon or Intel) binary has to be built on a Mac — or on the project’s Apple-Silicon CI runner — not cross-compiled from Linux (Apple’s SDK is required). Likewise a Windows .exe is built on Windows or cross-built with the mingw toolchain.

You should see the AI-000 tier banner: “No AI model. No network. On-device only. It flags; it does not decide.”

2. Check a document

Point it at a LaTeX file:

./concordance analyze mypaper.tex

You get a JSON report. The part you care about is findings:

  • dangling_refs — a \ref/\cref to a label that does not exist. Fix these.
  • duplicate_labels — the same \label defined twice. Fix these.
  • missing_cites — a \cite key with no bibliography entry. Fix these.
  • unused_labels — a \label never referenced. Usually fine (section anchors); review the theorem-like ones.

3. Fold the report into your editing loop

Re-run analyze after each edit; watch dangling_refs and duplicate_labels go to empty. That is the whole workflow: Concordance flags, you read and fix.

4. Markdown instead of LaTeX

./concordance corpus-md ./docs-folder/

What you will NOT be asked for

No account, no API key, no network egress, no upload. Your document stays on your machine. That is the AI-000 guarantee — see sovereignty-and-tiers.md.