Vela is version control for scientific state: a Git-native protocol and CLI for recording what is claimed, submitted, checked, decided, corrected, and safe to do next.

The core loop is deliberately small:

init → submit → verify → decide → replay

Work can happen in any native tool. A Submission retains bounded producer evidence. A Verification Record reports one scoped check. Only an authorized Decision changes Standing, and strict replay derives the current state.

• Vela Core owns Protocol 1, the Rust CLI, canonical bytes and roots, replay, schemas, conformance, and signed releases. v0.977.6 is current. Signed v0.977.5 remains immutable history.
• Problems owns the public discovery and hosted-work product at problems.science. Its read projection and WebMCP tools cannot change scientific Standing.
• Workbench owns local activity, native runs, evidence preparation, and explicit handoff to Vela's Submission boundary. It holds no Repository authority.
• Math is the reference mathematics authority Repository: exact Sources, Claims, Verifications, Decisions, and replay state under one local trust root.
• www is the static source for the vela.space front door.

vela.space is the static public front door. Problems, Workbench, Math, and Core remain separate because discovery, activity, scientific authority, and protocol execution have different owners.

Git preserves bytes and ancestry. Native scientific tools preserve their own domain meaning. Vela owns only the exact transition from bounded evidence and scoped checks into locally governed, correction-aware Standing.

A Repository exists because there is an independent scientific authority, not because there is another topic. A Frontier is a derived query over unresolved state; it owns no history, trust root, or protocol identity. Sources preserve external provenance, and Problems names bounded questions.

The Observatory was the historical name for a derived read surface. Problems now owns the public read product. No current Observatory application is deployed at app.vela.space.

The former topic repositories are archived historical evidence and are not part of the current product topology:

• Erdős Problems
• Formal Conjectures
• Quantum Codes
• Sidon Sets

Verifier success, a model output, a Git commit, and a Web badge are evidence or publication facts, not acceptance. No model belongs in the human Decision or repository-authority path.

Workbench source and unsigned macOS builds are qualified, but public signed distribution remains blocked on a Developer ID identity and notarization credentials. The unsigned artifact is qualification evidence, not an installable release substitute.

These repositories are the current Vela source-state and product surfaces. The wider autonomous-science direction, including the intended programme-level Frontiers layer, is maintained in the programme vision and repository map.

Those programme documents do not make Vela Core a scheduler or workflow engine, and they do not imply that a unified Frontiers product already exists. The private vela-web and topic-frontier repositories remain archived historical custody.