For contributors and maintainers

Evidence that follows the work

Varve keeps development feedback fast while making integration and release decisions traceable. Every stage has a clear owner, an exact source identity, and an honest status.

The path

Commit locally. Certify remotely. Publish deliberately.

Shape the change

Keep commits focused and preserve unrelated work in the checkout.

Check the impact

The planner selects the narrowest useful local and remote lanes.

Freeze the source

CI, candidate checks, and Pages deployments carry the exact commit they ran.

A practical start

Run the smallest useful check first

From the repository root, inspect the plan before starting a broader gate. The full suite is reserved for changes whose risk or release stage actually requires it.

pnpm verify:plan
pnpm verify:affected
pnpm verify:push

For a read-only view of synchronization and prior attempts, usepnpm workflow:status, pnpm workflow:doctor, andpnpm workflow:history -- --json.

What the checks prove

A green local hook is not a published release

Local checkpoint

Git supplies the refs being pushed. Local lanes run against clean snapshots of those committed trees, while expensive browser, native, visual, and release work remains visible as CI responsibility.

Integration certification

The stable CI check reconciles selected jobs and deliberate skips against one exact commit. Missing, cancelled, timed-out, or unexpectedly skipped work is incomplete.

Release candidate

Triage can collect bounded failures without certifying anything. Only final mode can produce passed candidate evidence for the exact source and policy hash.