GitLawb Code Proof

GitLawb adds signed provenance to code work. HivemindOS keeps the private story—your task, project, agent, machine, decisions, and review—while GitLawb can prove the repository side of the result.

Code Proof is optional. You can use HivemindOS for normal coding work without installing GitLawb or running a code node.

Enable Code Proof

1. Open More → Integrations.
2. Choose GitLawb Code Proof.
3. Review the network and identity explanation.
4. Install or repair the lightweight GitLawb tool when offered.
5. Create a local signing identity if you want signed proof.
6. Link Code Proof only to the projects that need it.

The first-run setup also offers Code Proof as an optional choice. It starts off. Enabling it can create a local identity and register the public identifier with the selected network; the private signing key remains on your machine.

What Appears In HivemindOS

• Integrations shows setup, identity, and connection status.
• Work can show a proof badge on a task linked to a project.
• Fleet can show whether the primary machine is Code Proof ready.
• Brain can keep optional hash-only receipts for reviewed memory writes.

A proof receipt can include a content hash, previous receipt hash, public identity, and sanitized agent or machine context. It does not need the private memory body, provider secrets, wallet keys, exact private vault path, or private machine address.

Link A Project

Create or select the HivemindOS project, then link it to the intended GitLawb repository. One computer can hold many projects, and each project can use a different proof repository.

When Queen Bee routes code work, HivemindOS can use the private project registry to prefer a machine that already has the matching checkout. It may report that a checkout is behind or has local changes, but it should not pull, rebase, switch branches, or discard work merely to improve the status badge.

When You Need A Full Node

Most users do not. Lightweight proof readiness is enough for identity and signed metadata.

A full GitLawb node is a separate, heavier setup with its own database, storage, ports, and lifecycle. Start one only when a project specifically needs local repository hosting or protocol participation. HivemindOS keeps that setup lazy and explains the additional weight before installation.

Do not publish a node or private fleet service to the internet as a shortcut. Follow the network exposure and backup guidance shown by the integration.

Disable Or Remove It

Disconnecting Code Proof should not block ordinary HivemindOS tasks. Existing proof records remain part of the projects or networks where they were created.

Uninstall choices are intentionally separate: removing HivemindOS status data, removing a managed tool, deleting a local signing identity, and deleting a full node are not the same action. Back up any identity or repository material you intend to keep before approving a destructive removal.

The normal recovery path is to leave projects and Hive Superbrain intact, disconnect Code Proof, and reconnect or repair it later.