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.
Latest release · NuGet · Install · Limitations · Support · Roadmap · Source
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 the records, in your git repository by default, of every work order, brief, run, result, review, decision and release behind it.
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. Vericairn's own development runs this way.
Begin
The Community edition is Apache-2.0. With the .NET 10 SDK and git on Linux, macOS or Windows:
dotnet tool install --global dotnet-vc
The repository's first steps create your first estate in a minute, and the operator's guide continues to a work order, an agent's run, its review and acceptance, and a release.
Limits that affect your start
- Vericairn is pre-1.0: commands and record formats still change between releases.
- The archives are unsigned developer builds, without code signing or notarization. Verify each download against its checksum.
- The command line is qualified on Linux x64, macOS on Apple silicon and Windows x64. Workbench, the desktop, is not qualified on any platform.
- The worker runs only exact, qualified coding-agent versions, and its spending caps are soft.
- Remote, the phone client, is not built, and no catalog entry below ships yet.
- Help is self-service, with no promised response time.
The limitations and platforms guide gives every current limit.
Official destinations
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.
Planned
Vericairn's catalog plans more than 3,000 entries: 1,290 domain packs that describe a field's work, 992 foundries that start or reshape a project, 301 adapters for the formats and tools you use, and 575 providers for the services you deliver through. None of them ships yet. The first creator domains come first: websites and web applications, then books, book series and world building, courses and video, and crowdfunding.
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. A name in the catalog is planned scope, not availability; the roadmap gives the order.
Vericairn.org will become the home of the community: learning, participation, extension discovery and the package registry. Until then the community is on GitHub.