vela-science/vela

<p align="center" <img src="assets/brand/vela-readme-hero.jpg" width="960" alt="Vela connects exact scientific evidence, verification, decisions, and standing through Git history." </p

<h1 align="center"Vela</h1

<p align="center" <strongVersion control for living science.</strong </p

<p align="center" <a href="https://www.vela.space"Website</a · <a href="https://app.vela.space"Observatory</a · <a href="docs/QUICKSTART.md"Quickstart</a · <a href="docs/ARCHITECTURE.md"Architecture</a · <a href="docs/PROTOCOL.md"Protocol</a · <a href="docs/THREATMODEL.md"Security</a </p

---

Research already has tools for code, papers, data, proofs, and computation. Vela tracks the missing state between them: what is claimed, what exact evidence bears on it, what was independently checked, what a named Frontier decided, what was corrected, and what the next researcher can safely inherit.

Vela is an open scientific-state and compounding layer. Its product loop is:

map -> target -> run -> verify -> commit -> compound

Work can run anywhere. Checks remain scoped. Only an authorized Decision changes Standing. The accepted result, correction, or retained failed route then becomes a stronger starting point for the next person or agent.

Its long-range direction is a federated inheritance layer for science: different workbenches can produce evidence, different verifiers can report scoped checks, and each Frontier can decide and replay its own state without a hosted authority or universal ontology.

With Vela you can:

• inspect one scientific state from exact Git bytes and full roots;
• map an unresolved gap into bounded work without receiving authority;
• submit portable, authenticated evidence;
• retain verifier observations without treating them as acceptance;
• make one exact authorized Decision; and
• replay how every Claim reached its current Standing and what can safely

happen next.

How it works

workbench
   │
   ├── Attempt ── Submission ─────────────┐
   │                                      │
verifier ── Verification Record ──────────┤
                                          ▼
                                 pending Proposal
                                          │
                                authorized Decision
                                          │
                                          ▼
                                    Event + Standing

▼ read-only Observatory

Vela keeps four boundaries explicit:

1. **Git preserves bytes and ancestry.**
2. **A Submission preserves producer intent and evidence.**
3. **A Verification Record reports one scoped check.**
4. **Only an authorized Decision changes Standing.**

A verifier pass is not scientific acceptance. Git publication is not
scientific acceptance. A signature proves control of a key over exact bytes;
it does not prove that a Claim is true.

Install the released CLI from crates.io: