Vericairn

Vericairn is a local-first creation and operations platform. It helps you, alone or as an organization, carry work from an intention to a reviewed, delivered and maintained result, with its decisions, sources and history kept as records you own: by default in a git repository beside your work, or in a store on one machine, with hosted options planned. People and agents do the work, and nothing is released until you accept it. Software is its first domain, and the one that ships today.

Status: pre-1.0, Community edition (Apache-2.0). The current published release is 0.8.4, from October 28, 2026. Latest release · NuGet · Install · Limitations · Support · Roadmap

Vericairn's official destinations are vericairn.com, vericairn.org, the Vericairn organization on GitHub and the dotnet-vc and Vericairn packages on nuget.org. Other sites using the name are not Vericairn's.

Who it helps today

A developer, alone or in a small team, who builds and ships software with coding agents such as Codex and Claude Code, and wants to know afterwards what each agent was asked to do, what it did, what was checked and who accepted it.

What you do with it

You write a work order: what to build, its scope and the question that decides when it is done. You assign it to an agent with an exact brief. Vericairn's worker runs Codex or Claude Code on that brief in a workspace repository of its own, within a spending cap recorded before the run, and a coding agent that supports MCP can work in the estate through Vericairn's MCP server. You review the result and accept it or ask for another attempt. A release is built as a draft on GitHub Releases and published only after you accept it.

The outcome is the release you accepted and an estate: the records, in your git repository by default, of every work order, brief, run, result, review, decision and release behind it. dotnet vc status and dotnet vc progress show where it stands.

Why records, reviews and acceptance

An agent's report that work is done is a claim, not evidence. In Vericairn each step is a record with a content hash and, from an admitted device, a signature. A review names the exact result it read and an acceptance the exact hash it accepts, so a changed result needs a new review and acceptance, and nothing is released until you accept it. Later, you can still see what was asked, what was done, what was checked and who decided.

Vericairn's own development runs this way: its work orders, reviews, decisions and releases are records in a Vericairn estate, and every release ships only after its operator accepts it.

Begin

With the .NET 10 SDK and git on Linux, macOS or Windows:

dotnet tool install --global dotnet-vc
mkdir my-venture && cd my-venture && git init
dotnet vc estate init --name "My Venture" --slug my-venture \
  --purpose "Build and ship one product with coding agents." \
  --operator-name "Your Name" --organization "Your Organization"
dotnet vc status

estate init records you as the operator and the estate's charter, and writes a manifest that pins the exact Vericairn build you run, by its source commit; add --release to pin the published release itself, verified against its checksums. status shows the new, empty estate. The operator's guide continues from there: your device and its key, a work order, an agent's run, its review and acceptance, and a release. The install guide also covers the self-contained archives for machines without the .NET SDK, checking a download, Workbench and the MCP server.

In a .NET 10 project, dotnet add package Vericairn adds the SDK, the typed client of Vericairn's API; see the SDK guide.

Limits that affect your start

• Pre-1.0. Commands and record formats still change between releases. Upgrading an estate is forward-only, and when a release changes the record format, every writer and clone of the estate moves to it together.
• Unsigned builds. The archives are developer builds without code signing or notarization. Verify each download against the release's SHA256SUMS, as the install guide shows.
• Platforms. The command line is qualified on Linux x64, macOS on Apple silicon and Windows x64. The other archives are provided but unqualified, and Workbench is not qualified on any platform.
• Agents. The worker runs only exact coding-agent versions, configured on each machine: the release's baselines, or another version a person qualifies there. Live runs have qualified one Codex configuration, which the software guide describes. Spending caps are soft: unknown usage is charged at the cap.
• Not built yet. Remote, the phone client, and every entry of the planned catalog below.
• Support. Help is self-service, with no promised response time.

The limitations and platforms guide gives every current limit, and the release index gives the current release's readiness disclosures and security notices.

Planned

• Remote, the phone client for accepting releases and steering work, in 0.9.0, with a community build guide for every planned catalog entry and a way to request the implementations you need most.
• The first creator domains in a 0.10.x series: websites and web applications, then books, book series and world building, courses and video, and crowdfunding.
• Paid editions on the same software, with Community staying free: Standard for one person and Pro for teams and organizations, with no offers or prices yet. Every paid service is planned as software you can run yourself at the edition that sells it, no access to your estate will require a Vericairn account, and you can move between Vericairn's hosting and your own either way; the roadmap lists all five no-lock-in rules.
• Separately installed extensions and the package registry, at milestone M4.
• Vericairn's catalog, at later milestones: more than 3,000 planned entries, including 1,290 domain packs, 992 foundries, 301 adapters and 575 providers. The creator domains above come first. Every entry is planned; a name in the catalog is scope, not availability. The catalog covers:
  • Creative and technical work: the web, games and Unity, books and book series, courses and course series, video and video series, worldbuilding, media, documentation, marketing, canon, adaptation, continuity, franchises, rights, localization, release readiness, analytics, crowdfunding, AI applications and extension ecosystems.
  • 27 industries: aerospace and defense; chemicals; construction; e-commerce and online retail; education institutions; environmental consulting; finance, accounting and audit; food and agriculture; governance, risk and compliance; information technology services and operations; insurance; land management; legal practice operations; life sciences quality and regulatory; manufacturing quality and operations; marine; marketing and advertising; medical; mining and minerals; nonprofits and grants; oil field; public sector; real estate and property management; refinery; telecommunications; transportation and logistics; and utilities and power.
  • In regulated fields, agents prepare and check the work, and licensed or authorized people make the decisions and perform the acts reserved to them.
• The roadmap gives the order.

Releases

The published releases are on the Releases page. Each carries the command line's archives for Linux, macOS and Windows, SHA256SUMS, a software bill of materials and the third-party notices; from 0.3.1 a release also carries Workbench's archives and its documentation set. The release index keeps every set from 0.2.0 on, with each release's notes and security sections, and names the candidates withdrawn before publication and why. The documents at docs/ are the maintained drafts for the next release; a released set is never edited.

Nothing here is a release until a release record in the Vericairn estate says so. The estate records every release and pins the one it runs on.

What is here

The following capabilities are in 0.8.2.

• Vericairn.Records: record formats 1, 2 and 3 (canonical JSON, ULIDs, content hashes, signed records, devices and admission, estate loading, validation, cleanliness checks, status, living documents), documented in docs/record-format-v1.md and, for what format 2 changes, docs/record-format-v2.md, with policies, duties and generated-document contracts in docs/record-format-v3.md. Device keys are held in the strongest custody the machine offers: CNG on Windows, the Secure Enclave on a Mac through the vericairn-enclave helper (src/Vericairn.Enclave, in Swift), the secret service on Linux, otherwise a file in per-user state (owner-only permissions on Unix; inherited directory ACLs on Windows).
• Vericairn.Runtime: the live store, objects, storage profiles, export and restore, recovery, upgrades, and the one implementation of the estate operations.
• Vericairn.Protocol, Vericairn.Daemon, Vericairn.Sdk: the versioned API contract, the daemon that owns an estate's live state and serves it over a local socket, pinned loopback TLS and, when the operator configures a private address, the local network to paired devices with mutual TLS and requests signed for that runtime, and the typed client with the device's side of pairing and its connections, documented in docs/api-v1.md with the threat model of pairing.
• The software journey: Vericairn.Packs.Software (repositories as resources, build and test checks as verification evidence, and the coding-agent launchers and independent Git workspaces the worker uses), Vericairn.Adapters.Git (repository observation, exact source reads and checked workspace/push operations) and Vericairn.Providers.GitHub (releases built by a GitHub Actions workflow and held as drafts, with intent recorded before effect and publication left to the operator, and the pull requests and merges of checked changes), documented in docs/software.md and docs/changes.md. The foundation keeps their contracts; a release goes through the provider its request names or its product record declares.

Developing on Windows, Linux or macOS

Development is supported on all three. Requires the .NET SDK pinned in global.json and git on the PATH. Files are LF in every working tree (.gitattributes), console output is UTF-8 with LF line endings on every platform. Continuous integration builds, tests, packs and checks local tool and SDK installation on all three operating systems for main, pull requests and manual runs. In CI and in the release workflow, a job retries up to five failed tests once each; every retried test is named in the run's summary, and a second failure fails the job. A separate workflow scans the commits of every pushed branch and pull request for secrets with a pinned, checksum-verified gitleaks. The release workflow builds the Secure Enclave helper on macOS. This repository's solution contains no iOS or Android client, so its build and tests make no mobile-platform qualification claim.

Build

dotnet build
dotnet test
dotnet run --project src/Vericairn.Cli -- records describe

Build output goes to artifacts/, which is ignored.

License

Apache License 2.0; see LICENSE and NOTICE.