vela

Release · evaluator path · 0.103.0

A frontier you can inspect from answer to bytes.

The current public release is one focused frontier: Anti-amyloid translation in Alzheimer's disease. It is meant for external readers who want to inspect the state, follow the evidence trail, and reproduce the proof packet from a fresh checkout.

Open the Workbench → Run the thirty-second check → Read the evaluator package → Read the evaluator brief →
frontier · vfr_5076e7b3ff8e6b0f
141
finding bundles
277
canonical events
80
artifacts
122
sources

What to inspect first

Start in the Workbench. The default route loads the anti-amyloid frontier from the hub, then shows the answer layer, imported source records, runtime bridge trail, review decisions, and proof view.

Workbench repository shell 10-minute demo path External runtime bridge Bridge Kit validation BBB reference frontier Proof packet manifest Release marker JSON Live event feed Hub snapshot

Reproduce locally

This sequence builds the binary, pulls the flagship frontier, runs the evaluator CLI path, checks a clean clone, and produces a GitHub-ready release bundle with SHA-256 sums. 

git clone https://github.com/vela-science/vela.git
cd vela
cargo build --release --bin vela
./scripts/test-first-user-release-path.sh
./scripts/clean-clone-smoke.sh
./scripts/package-github-release.sh /tmp/vela-github-release

Correct under agentic load

Vela treats machine-speed source and runtime activity as proposal material, not as trusted state. Accepted events are append-only authority; materialized frontier state is replay output; impact reports are read-only dependency intelligence for reviewers.

integrity
vela integrity projects/alzheimers-bbb-dysfunction-delivery --json
impact
vela impact projects/alzheimers-bbb-dysfunction-delivery vf_ba4f834d6dc506d1 --json
check JSON
state_integrity is included in vela check --json

Release assets

The release bundle is generated from the repository, not copied from the hosted site. It includes the canonical frontier JSON, proof packet tarballs, packet validation output, source freshness report, adapter run records, trust audit, evaluator package, evaluator brief, and release marker.

snapshot hash
b1ecc2128a5e813ddf191e867647fa0cf870bddbe69ede640644034729dccbd7
event-log hash
9a58441d91bf920ffaae0346be604576e27348f5bc756c32fdbb3a8f0677d8e2
release command
./scripts/package-github-release.sh /tmp/vela-github-release
source freshness
source-freshness-anti-amyloid-translation.json
./scripts/check-source-freshness.py projects/anti-amyloid-translation --max-age-days 45 --json

Boundaries

Vela is showing reviewed frontier state. It is not giving medical advice and it is not claiming that registry metadata or agent output becomes truth on import. Those records become source material until review accepts a bounded event.

Release note Evaluator package Carina kernel spec Frontier repo format State integrity Activity is not state BBB core v0.3 BBB frontier manifest BBB lockfile BBB proof latest BBB event manifest BBB replay trace BBB source dossier BBB frontier map BBB transition examples BBB rewrite proposals BBB core v0.4 outcomes BBB review walkthrough Artifact-to-state path Runtime bridge docs