HivemindOS manual

GitLawb Code Proof

GitLawb Code Proof adds a signed record of who produced a piece of code. Use it when you want verifiable proof of agent code work. Your private context — the task, project, agent, machine, and decisions — stays in HivemindOS.

Code Proof is optional and off by default. Normal coding work does not need it.

Turn it on

Open More → Integrations and choose GitLawb Code Proof.
Read the network and identity explanation.
Install or repair the lightweight GitLawb tool when offered.
Create a local signing identity if you want signed proof.
Link Code Proof only to the projects that need it.

Creating an identity registers a public identifier with the network you choose. The private signing key stays on your machine.

Link a project

Create or pick a HivemindOS project, then link it to its GitLawb repository. Each project can use a different proof repository, and one computer can hold many projects.

When Queen Bee routes code work, it prefers a machine that already has the matching checkout. It may report that a checkout is behind or has local changes, but it never pulls, rebases, switches branches, or discards work to fix that.

What you see

Integrations: setup, identity, and connection status.
Work: a proof badge on tasks linked to a project.
Fleet: whether your main machine is ready for Code Proof.
Brain: optional hash-only receipts for reviewed memory writes.

A proof receipt holds a content hash, the previous receipt’s hash, your public identity, and cleaned-up agent or machine details. It never includes private memory, secrets, wallet keys, vault paths, or private machine addresses.

Do you need a full node?

Usually not. The lightweight tool is enough for identity and signed proof.

A full GitLawb node is a separate, heavier setup with its own database, storage, and ports. Start one only if a project needs local repository hosting or protocol participation. Do not expose a node or any private fleet service to the internet as a shortcut.

Turn it off

Disconnecting Code Proof does not affect normal tasks. Existing proof records stay where they were created.

Removing status data, removing the tool, deleting your signing identity, and deleting a full node are separate actions. Back up any identity or repository you want to keep before deleting it.