v0.1.4

One native binary for macOS. No server, no webview, no language runtime, no account — the only thing it asks of the machine is a working graphics driver. Nothing here reports anywhere; it reaches out only when a spec names a remote source, a DuckLake catalog or a spatial source. Everything under examples/ is local and self-contained except examples/remote/, which is where the specs that fetch are kept — with no connection one of those does not open, it exits non-zero having named the network and the URL, and nothing else is affected.

This is an early preview, macOS only, and it is not signed or notarized by Apple. That is the one thing to read before you open either download, because macOS treats an unsigned application downloaded through a browser as suspect and says so in language that sounds like the file is broken. It is not broken; each section below says what to do.

Two downloads, same build. On an Intel Mac, swap aarch64 for x86_64 throughout.

brightfield-v0.1.4-aarch64-apple-darwin.dmg — a disk image holding Brightfield.app. Take this one if you want an application: an icon in the Dock and a double-click launch.

brightfield-v0.1.4-aarch64-apple-darwin.tar.gz — the bare binary beside the example specs, its LICENSE and a README. Take this one for the terminal, for a scripted install, or to keep the whole thing in a folder you control.

Check what you downloaded

Take the .sha256 sidecar next to whichever file you took, then from the folder they landed in:

shasum -a 256 -c brightfield-v0.1.4-aarch64-apple-darwin.dmg.sha256
shasum -a 256 -c brightfield-v0.1.4-aarch64-apple-darwin.tar.gz.sha256

The disk image

Open it, drag Brightfield.app onto the Applications alias in the window, and eject the image.

Because this preview is unsigned, macOS will refuse to open the copy you just installed. Clear the download mark once, and it opens from then on:

xattr -dr com.apple.quarantine /Applications/Brightfield.app

The examples ship inside the bundle, at Brightfield.app/Contents/Resources/examples.

The tarball

Unpack it in Terminal, not in Finder

This build is unsigned, so macOS quarantines anything the Finder's Archive Utility extracts and then kills it the moment you run it — usually with nothing in the terminal but zsh: killed, and sometimes a notification saying Apple could not verify it. The tar command below does not set that mark:

tar -xzf brightfield-v0.1.4-aarch64-apple-darwin.tar.gz
cd brightfield-v0.1.4-aarch64-apple-darwin
./brightfield

If you already unpacked it in Finder, clear the mark from the whole folder — adjust the path for wherever it landed:

xattr -dr com.apple.quarantine ~/Downloads/brightfield-v0.1.4-aarch64-apple-darwin

What you get

./brightfield with no arguments opens on a set of starts that ship inside the binary: the lineage of the EDGAR↔GLEIF crosswalk, and three charts. Or name a spec yourself —

./brightfield examples/bars.yaml

The example specs and the EDGAR↔GLEIF Protocol manifest are in the archive, alongside the binary, its LICENSE (MIT) and a README. The Protocol manifest renders from the manifest alone, without a run:

BRIGHTFIELD_PROTOCOL_OFFLINE=1 ./brightfield examples/protocol/edgar_gleif/arcform.yaml

What it reports

Nothing. No telemetry, no analytics, no update check — nothing in this application reports anywhere, and it needs no network to start, to render, or to open a local protocol.

It reaches out only when a spec asks it to: a remote source, a DuckLake catalog, or a spatial source. In those cases DuckDB downloads the extension it needs from its own extension repository and fetches the data. A spec over local files does neither.

scripts/verify-airgapped.sh in the repository proves that against the packaged artifact — it denies the network, checks that the denial really bites, and only then renders a chart and a protocol graph inside the jail. Run it yourself; it takes a minute. The Intel build is the same source and packaging, cross-compiled.