It's all signal

The move, in one line: everything Euhedron builds is going public. The code, the history, the audit receipts, the process. Your data stays closed. Everything else opens.

1. What just opened

crux is public as of tonight. arclite has been public. commissure is next: the full implementation source, public from this release's tree forward.

One honest note on what stays sealed. We swept the pre-public commit history for publication and the sweep found exactly what it exists to find: real people's numbers, real people's private moments, friends who never signed up to be named in someone else's repo. So the pre-public history stays private. Not to protect the code. To protect them. Development is public from the first public commit on.

Not a showcase repo. Not source-available-but-look-don't-touch. The working repositories, with the development happening in them.

2. Why: it's all signal

The last post argued that a tool should be adversarial to its own flaws. This is the same argument pointed at the company.

A private repo hides two things: the code and the process. Hiding the code protects a moat we don't have and don't want. Hiding the process throws away the most valuable thing we produce.

The night we shipped 0.2.15, the release gate blocked the same candidate over thirty times. Two independent model auditors read every byte of the patch, fresh, every roll. They caught a consent record that contradicted itself. They caught the same rationale drifting across four copies in comments. They caught a whole file rewritten in the wrong indent, riding along as churn. Each catch got fixed at the root and the next roll read the new bytes cold.

That history is not embarrassing. It is the product working. Every defect caught is signal, and signal compounds when it's shared. Keeping it private would be the same defect the first post named in other people's products: eating the evidence instead of using it.

3. Everybody wins

We want competitors. Genuinely. Fork it, study it, build the better version, take the ideas without asking. Friendly competition over honest tools is a race everyone wins, because the thing being competed on is how little the tool lies to you.

We are not doing this for the money. The money matters, the company has to live, but the bet was never that the code is the value. Anyone can read a routing table. What compounds is the corpus you feed it and the judgment the system accretes over it, and that lives on your machine, not in this repo.

So the code opens. If someone ships a sharper fork, the gap section one of the last post described gets narrower for everyone, and we get to read their commits too. Signal flows both ways.

4. What stays closed: yours

The inversion that makes this safe is the same one that makes commissure worth using. The corpus is private by architecture. Your messages, your mail, your photos, your history: local, on your Mac, never in any repo, never in the cloud unless you explicitly push an encrypted snapshot only you can read.

Our code goes open because it holds nothing of yours. Your data stays closed because it is the only thing that was ever actually private. Companies tend to get this exactly backwards: proprietary code, promiscuous data. We are running it the right way around.

5. Nothing is canon

The rulebook that gates every release says nothing is canon and everything can evolve. That applies to the rules themselves, to the architecture, and to this decision. Open is not a ribbon we cut once. It is the default posture until the evidence says otherwise, and the evidence will be public too.

The repos are the argument. Go read them.