Vela · open protocol · v0.720.0

Version control for scientific state.

Vela turns papers, evidence, review events, and code into a frontier your team can inspect, fork, and replay.

Inspect the live frontier Source on GitHub

live vfr_37aec80d874a0239 1,256 findings 2,778 signed events 32/32 witnesses reproduce updated June 30, 2026

erdos-problems sidon-sets benchmark-state quantum-codes formal-conjectures-lean
Day chart five live frontiers schematic

01 The gap

Science is gaining machine‑speed production without machine‑speed trust.

AI proof search and automated labs can propose results faster than any referee can read them. Whatever the record cannot re‑check, it quietly loses.

Vela is the missing state layer: a shared, receipt‑backed record of what is verified, what failed, what supersedes what, and what it costs to re‑check, built so the receipts verify themselves offline.

  1. Activity is not state.
  2. Accepted events are state transitions.
  3. Replayed frontier state is canonical.
  4. Everything else is a projection.

02 Replay

A frontier you can replay.

Frontiersidon-sets

at HEAD · 8 events
  • vf_a1 Sidon set · n = 20 replicated
  • vf_b2 Sidon set · n = 22 replicated
  • vf_c3 Golomb ruler · order 13 contradiction
  • vf_d4 Sidon set · n = 24 inferred

8witness reproduces · n = 22

Plate I A signed event log folds into one canonical state. Drag it back and the same events rebuild the same frontier, every time. The history is the object you trust, not any single paper.

03 Proof

Verified, not proposed.

Where the gate is machine-checkable, the record ships the verifier beside the claim. Re-run any of these yourself, with no model and no trust in the search that produced them: the standalone checker.

  1. OEIS A309370 Improved Sidon-set lower bounds Approved Blair comments for n = 8–22 (e.g. a(16) ≥ 505); extensions to n = 24 in review. approved in OEIS
  2. OEIS A321531 Exact new terms, rook-placement directions a(11) = 28, a(12) = 33, a(13) = 38, proven optimal by an exhaustive verifier. approved in OEIS
  3. Erdős frontier Reproduces from a clean clone 1,256 problem records; 32 of 32 witnesses re-verify under the frozen exact checkers. reproducible

From a clean clone

vela · core flow constellate-science / vela
git clone https://github.com/constellate-science/vela-frontiers cargo install --git https://github.com/constellate-science/vela vela-cli vela reproduce frontiers/sidon-sets vela check frontiers/sidon-sets --strict

Three independent reducers, in Rust, Python, and TypeScript, replay the same event log to byte-identical state; that agreement is the protocol's proof of itself. The reducers, the changelog, and the contributing guide live beside the code in the repository, where they stay in sync.

04 Constellation

Map the frontier.

Every domain has an atlas, every atlas has frontiers, every frontier has open questions.

vf_

Finding

One signed result, carrying its evidence and state.

vfr_

Frontier

The reviewable state of one open question.

vat_

Atlas

A living, versioned map of one domain.

✦

Constellation

The cross-domain picture the atlases make together.

Plate II The four scales of the record. A finding is one signed result; a frontier holds one question's state; an atlas maps one domain; the constellation is the picture they make together.

Vela · open source · v0.720.0

The record should be something you can run.

Inspect the live frontier Source on GitHub
Anchor copied