“Most of our research is published openly” is easy to say and easy to fake. So here’s the actual mechanism, because open by default only works if it’s the path of least resistance internally.
Every project at LegionEdge starts with a publication decision, not a publication review. The default is open: specs, datasets, weights, and write-ups ship to the public registry unless there’s a specific, documented reason not to. Flipping the default changes behavior more than any policy memo — nobody has to champion openness case by case.
The registry is the enforcement layer. Internal tooling reads from the same registry entries the public sees, so keeping something private means maintaining a private fork of your own infrastructure. Friction points the right way.
What stays closed? Customer data, always. Unreleased product work, until it ships. And safety-relevant capabilities research where publication would do more harm than good — we document the reasoning in the registry entry even when the artifact itself is withheld.
The result is that openness isn’t a launch event here. Protocol specs, the W0rkTree core, our datasets, and our benchmark suites are public because that’s where our own tools look for them. The future of AI should be built together, and this is the plumbing that makes the slogan true.
