beamfall/corvint

A Beamfall project.
Context your agents can cite. Changes your reviewers can check.
Corvint is a local-first context compiler for coding agents. Before an edit it hands the agent
Git-pinned evidence with the reason each item is there. After the edit it binds every diff hunk
to cited evidence, an explicit unknown, or a verifiable mechanical exception, in a portable
sidecar that CI checks without an LLM.
Install ·
Workflow ·
Status ·
Documentation
**One native Go binary.** No account, hosted service, database, embeddings, or permanent daemon.
go.mod declares no module requirements. Read commands do not mutate repository or trace state;
the two bounded exceptions are a local .corvint/self-observations.jsonl ledger and, only while
the operator marker .corvint/unplanned-reads.enabled exists, .corvint/unplanned-reads.jsonl —
neither is a direct input to ranking, evidence, or authority. Learning from these ledgers requires
an explicit operator step and a frozen held-out gate (AGENTS.md invariant 4). Version
1.0.0-rc.2 is the published prerelease and the second release candidate for Corvint 1.0;
what 1.0 promises and what is still being qualified.
Why Corvint
Finding relevant text is only part of a coding task. An agent also needs to know which document
governs the change, which tests constrain it, and what evidence is missing. A reviewer needs to
follow those decisions back to their sources.
Corvint makes that evidence inspectable through context receipts and a map beside the diff.
- **Every result explains itself.** Each item in a packet carries the Git blob it came from, the
path and line, the authority that admitted it, a confidence level, and a plain-language
inclusion reason. A reviewer can follow any citation to immutable content.
- **Your repository is the authority.** Agent instructions, accepted decisions, and specs you
already keep outrank syntax matches, history correlations, and learned traces. Corvint uses
the documents you have; it introduces no new spec language.
- **It says what it does not know.** Coverage, omissions, uncertainty, and freshness are fields
in the receipt, and a hunk without cited evidence is an explicit unknown. Task-level retrieval
abstention is experimental and unqualified; see Status.
- **Reviewers get a disposition for every hunk.** A Change Evidence Map (CEM) links each textual
hunk of a diff to cited evidence, an explicit unknown, or a mechanical exception. The verifier
checks patch, hunk, blob, and span identity locally, with no LLM, no index, and no shared
service. The protocol is Apache-2.0, so anyone can implement or verify it.
- **Local and explicit.** The core reads Git and prints JSON. Default evidence flows make no
network call. query, context, impact, affected, and non-executing prove modes report
mutates: false, subject to the private-ledger exceptions above. record explicitly retains
task outcomes; learning stays local, bounded, secret-screened, and evaluation-gated.
Sixty seconds on this repository
You need Git and Go 1.27.2 or later; the full development gate pins exactly go1.27.2.
Run this from the root of a Corvint checkout on macOS or Linux:
That asks what a change to the CLI entry point could affect. The receipt names the requested
path, the tests that constrain it, the reason each result was admitted, and what the result limit
left out. No installation or account is needed. Abridged output captured from public commit
f51f3c9e6fbfc5a6b219692e8bf46e4e43297a36 with its source-built CLI (fields, results, and
evidence records omitted; shown values unchanged). Your checkout determines the hashes and counts:
Install the binary to use Corvint in any supported Git repository:
Versioned assets are on the releases page. The
Core rc.2 release contains only
corvint, with four macOS/Linux archives, SHA256SUMS and verification-report.json. A matching
native archive needs Git but no Go compiler; verify both the downloaded archive and its internal
checksums before running it. Read the exact platform's qualification, including native versus
emulated runs. Tasks has its own developer release; source companions are not automatically
included in a Core archive. Source builds of main report 1.0.0-rc.3, an unreleased candidate
label, and carry fixes made after the rc.2 tag (decision 0486). Like rc.1, rc.2 is unsigned, and 1.0 will be too: SHA256SUMS only, publisher
identity NOT_VERIFIED (decision 0433). The installation guide covers checks, first use,
optional tools, upgrades and removal.