Bellweather Audio Core Is Public Source

This is not "open source as a growth funnel," nor is it some claim that this is "the audio library the world needed" - it is closer to a public notebook. If the work is visible, I have to be accountable to it and sit with it long enough to see whether it holds water.

That part matters...because as they say, "embarrassment is the most under-explored emotion," and if someone can overcome THAT awkwardness, then they just gained the wildest superpower. Tech is SOOO urgent, self-righteous, and serious that there is rarely time to sit with an idea until it matures. Bellweather Audio Core is my attempt to chill tf out on the instant-disposal cycle for one narrow piece of the work. Put it somewhere public. Make the claims runnable. Let future-me look back and laugh, wince, or learn.

I don't know exactly what this will become or where it will go - all I know is this is a record of where my thinking was in 2026. That is enough of a reason to publish it.

That distinction matters enough to say plainly. Bellweather Audio Core is not a prebuilt Barometer download. It does not ship installers, signing artifacts, notarized packages, licensing services, update services, or unreleased product DSP. Those belong to the product and delivery systems around Bellweather's commercial work.

The public release is useful for a different reason. It gives C++ audio developers a readable, buildable source tree for the pieces that can stand on their own: metering, DSP primitives, audio types, ports, FFT support, and RT-safe infrastructure. Barometer is included as source-built JUCE reference code so the architecture is not presented as a diagram with no real integration behind it.

A framework boundary is easy to claim and harder to make visible. If the repo only contained small isolated modules, it would be clean but less instructive. If it contained the full product system, it would be broad but less honest about what is actually reusable.

Barometer gives the release a middle path. It shows the reusable core adapted into a JUCE plugin while keeping JUCE at the edge where it belongs. In that shape, the reference build does not turn the source release into a product download. It makes the adapter boundary answerable.

Audio metering is a poor place for vague confidence. LUFS, true-peak, loudness range, sample-rate behavior, and real-time processing constraints all have to survive contact with repeatable checks. Otherwise the public claim is only a paragraph with a professional vocabulary.

That is why the release includes standards-oriented metering tests and downstream-consumer public-surface checks. The goal is not to make the repo look complicated. The goal is to let a reader move from claim to source to build to test without needing to trust Bellweather's tone of voice.

The shortest native path is the library preset: clone the repo, run cmake --preset library, cmake --build --preset library, then ctest --test-dir build-library --output-on-failure. The landing page exposes those commands as copyable reference blocks, including split lanes for public-surface, metering-conformance, JUCE-separation, and Docker proof.

Spending more time on a project does not automatically make it successful. It does not guarantee adoption, usefulness, originality, or taste. The uncomfortable part is that spending less time does not automatically disqualify something either. We are living in that tension now.

So quality has to mean something more specific than effort. For this release, it means the public surface is narrow enough to inspect, the claims can be checked by someone else, and the exclusions are stated without trying to turn absence into mystery.

That is the standard I want this repo to be judged against: not whether it is the biggest possible thing, but whether it is honest about what it is, disciplined about what it is not, and useful enough that another developer can run it without needing the surrounding Bellweather machine.

The website has always needed to do more than describe products. It has to explain the standard underneath them: what Bellweather considers evidence, what we treat as release discipline, and where we draw the line between public proof and private implementation.

Bellweather Audio Core fits that pattern, but with a more personal edge. The repo gives developers the source. The landing page gives them a runnable reference surface. This note gives the release its posture: evidence first, no product-download ambiguity, and no claim that cannot point back to code or tests.