Vreko is building verification infrastructure for consequential claims about AI-assisted work. It uses evidence from the systems where the work happened while preserving source authority, attribution, uncertainty, freshness, correction/revocation, and bounded disclosure.

The first application is the Operator Passport for AI-heavy engineers and the people evaluating their work. The Passport is an operator-controlled projection of resolved evidence state. Ask the Passport is a query interface over an authorized projection. Hiring is the first proving ground for the verification primitive, not the whole company.

The current private Alpha asks whether a consequential recipient can legitimately rely on Vreko-resolved proposition state without reconstructing every underlying source, and whether competent native/commodity systems can independently construct an equivalently trusted portable state.

Enterprise work-admission assurance, independent audit/IVO workflows, and other consequential recipient decisions are expansion hypotheses, not current product claims or second Alpha markets.

Read this first, because it determines what you will and will not find here.

The Vreko core is proprietary. The daemon, the intelligence engine, the pattern store and the hosted service are not open source and are not published in this organization.

Selected interfaces are public so that the surfaces you would integrate against can be inspected, versioned and depended on:

vreko-cli and mcp-server are legacy developer-tooling distribution and documentation surfaces: they carry the package manifest, changelog, license and docs that ship with each release. The implementation is built from the private core, so you will not find it in those repositories. This is deliberate, and stated there too.

• ai-swarm, an audit-first, gate-controlled agent pipeline framework. Methodology and tooling, independent of the Vreko product.
• sopr-mcp, experimental. A brand-neutral reference implementation of the Service-Oriented Protocol Router pattern for tool-heavy MCP servers. No performance benchmark is published for it; the repository says so explicitly.

npm install -g @vreko/cli

Then vr --help.

Vreko consumes workspace.json, an independent Apache-2.0 open standard for committed repository intelligence, maintained at workspacejson.

Vreko does not own workspace.json. It is a separate project with its own organization, governance and release authority, and it is usable without Vreko.

Five packages from before the rename, config, contracts, events, sdk, infrastructure, are no longer public. They were superseded by the workspace.json standard or simply deprecated, they had no forks and no external contributors, and keeping a retired product name on the organization's public listing said something about Vreko that is no longer true.

They are retained privately rather than deleted, so their history is intact.

@snapback/contracts was superseded by @workspacejson/spec. The other four have no successor: they were internal packages that stopped being used.

• vreko.dev
• docs.vreko.dev
• Discord

The public repositories in this organization are Apache-2.0 except vscode (GPL-3.0) and sopr-mcp (MIT). The Vreko core is proprietary and is not covered by any of them.