Prikk

Version control, patch by patch

Patches build projects.

Small, deliberate changes — sealed into history anyone can verify.

Early implementation. Good for review, experimentation, and contribution. Not yet a place to keep history you cannot lose.

Get started View on GitHub

$ prikk --help

Get started

Try Prikk

curl -fsSL https://github.com/prikk-vcs/prikk/releases/latest/download/install.sh | sh
cargo install prikk

Linux, macOS, and Windows. The install guide covers pinning a version, verifying checksums, and building from source.

A calmer way to work

Commit. Seal. Verify.

commit — queue a signed patch seal — fix it into a block verify — anyone, offline

Committing does not publish. A patch is queued and signed first, and only sealing makes it history.

Patches accumulate and are sealed into blocks, connected in a verifiable chain.

A quiet chain: patches arrive, and the project grows.

The idea

Small changes. Clear history.

01

Patch

Describe a change as a first-class piece of project history.

02

Evidence

Keep the path from change to result explicit and inspectable.

03

Growth

Integrate useful changes without making the project harder to reason about.

Patch by patch

Bring changes together. Keep the story yours.

  1. Start

    A small platform holding a few scattered blocks, one glowing green among plain ones. A small platform holding a few scattered blocks, one glowing green among plain ones.

    A new project begins.

  2. Patches

    Four cards, each a focused change, flowing along glowing lines toward an arrow. Four cards, each a focused change, flowing along glowing lines toward an arrow.

    Small, focused patches flow in.

  3. Integrate

    The blocks assembled into one connected cube, glowing along its internal seams. The blocks assembled into one connected cube, glowing along its internal seams.

    Prikk integrates and validates with confidence.

  4. Grow

    The cube alive with leaves growing from it, surrounded by sparkling light. The cube alive with leaves growing from it, surrounded by sparkling light.

    The project grows, alive and spreading.

What you get

Validation, not vibes.

  • Validation & Evidence

    Trust built in.

  • Confident Merge

    Proven-confluent, or refused with a reason.

  • Read-only Merge Evidence

    See a change before you take it.

Try it

What it looks like

$ prikk commit --from-worktree -m "genesis"
recorded worktree patch in active WAL
baseline ref: heads/main
patch id: c29910f552275f805d9b8efd513a4c47995249393ccc...
WAL sequence: 1
operations: 1
referenced blobs: 1
text edits: 0
  create-file hello.txt
note: multi-operation text diff minimization, patch algebra, rename detection, and audit plugins remain later increments
note: the message is validated but not stored -- it will not appear in `prikk log`; persisting it is a later increment

Real output, not a mockup.

Prikk

Build with patches, not uncertainty.

Get started GitHub