Revia

An open-source, graph-first language implementation for Agent-authored work

and human semantic governance.

> Source: MPL-2.0 · Research/preview maturity · Not Stable V1.0 or production-ready

Revia turns checked program structure into deterministic machine contracts and human-readable projections. The repository contains the reference toolchain, the native Rust implementation, conformance tests, language documents, and bounded comparison fixtures.

The source tree is available under MPL-2.0. Historical preview and RC1 binaries remain governed by their original licenses: LICENSE-PREVIEW-0.1.md and LICENSE-RC.md. Those historical terms are not changed retroactively by publishing the source.

Current Status

The open development line is a research and preview implementation. Current source includes a bounded native translator/VM, a runnable project template, project and module checks, deterministic semantic artifacts, a bounded Server profile, interface projection, and conformance/experiment infrastructure.

The latest published candidate, v1.0.0-rc.2.2.1, has separate native evidence for Linux x64 and Windows x64. The current main source has additional, passing source-validation and Linux/Windows native CI after that tag; main-branch checks do not silently change the tagged binaries. See development status and compatibility for the version-specific evidence.

At main commit ca268c4, source validation and native Linux x64 and Windows x64 workflows pass, including the native project-surface-check gate and the bound Windows x64 runner artifact-integrity check. This is current-source evidence, not a new release asset.

These capabilities are bounded evidence, not claims of a production backend, complete language implementation, cross-platform equivalence, full A2A/MCP interoperability, or Stable V1.0. See docs/development-status.md and docs/stable-release-gate.md.

Release-license note: The v1.0.0-rc.2.2.1 export includes

LICENSE-RC.md, whose text says it applies only to v1.0.0-rc.1.

Version-specific terms for the RC2.2.1 binaries are unresolved; do not infer

their license from either the source MPL-2.0 or the RC1 license.

Start Here

Choose a path:

• Try Revia: Quickstart and the

• Understand the language: language specifications.
• Inspect implementation status: development status

• Run published trials: experiments index.
• Start a project: project template.
• Contribute: contributor guide.

npm run re -- check examples/hello.re
npm run re -- run examples/hello.re

Run its conformance suite:

npm test

The Rust implementation lives in native/:

cargo test --workspace --offline
cargo fmt --all -- --check
cargo clippy --workspace --offline -- -D warnings

The native CLI is built from native/. The Node toolchain remains a reference and development implementation; its presence does not make Node a semantic requirement of the language.

Repository Layout

doc/             language, syntax, semantics, and execution specifications
docs/            compatibility, integration, release, evidence, and status
examples/        small programs, Agent workflows, and review challenges
experiments/     historical release trials and comparison records
projects/        contributor project template and sample projects
src/             Node reference toolchain and host adapters
native/          Rust translator, VM, CLI, and native conformance tests
test/            Node tests, fixtures, and byte-exact goldens
test-support/    shared test adapters and fixtures
scripts/         development, conformance, and evidence commands
runtime/         historical packaged runtimes and release evidence

The public repository is the source and test authority for the open development line. runtime/ and experiments/ bind evidence to specific versioned candidates; historical evaluation terms do not define the source license.

Design Direction

Revia is built around a checked semantic graph:

• capabilities, effects, errors, and resources are explicit;
• canonical serialization and graph identity are deterministic;
• generated projections are derived from checked interfaces rather than

• protocol adapters remain outside the language core;
• evidence distinguishes measured, verified-only, pending, and

The language and implementation are still evolving. A passing test or bounded experiment must be read together with its stated scope and limitations.

Community

Use GitHub issues for reproducible implementation problems and discussions for design proposals. Do not publish credentials, personal data, private messages, local paths, private infrastructure details, or proprietary material. Security-sensitive reports should use the repository's private security reporting channel.

License

Newly published source is licensed under MPL-2.0. See SOURCE-LICENSE.md for the scope of the source transition and the relationship to historical release assets.