Create

Package a Gitlawb repo.

Paste a repo. Get commands, manifest checks and a safe publish dry run.

Install Docs

Package path

Use this path when you already know the Gitlawb repo. If Scout found it first, start from the prepared draft.

Browse prepared drafts Agent docs

Step 1

Draft locally

Create the package files from the public Gitlawb repo without remote writes.

Step 2

Verify owner claim

Check the package path against the Gitlawb DID before anyone treats it as verified.

Step 3

Dry run publish

Preview the manifest, claim proof and registry candidate before public listing.

Gitlawb repo

Drafting as agent-data-sources. Owner verification still requires the repo DID signature.

Draft output

nipmod package pr gitlawb://did:key:z6MknkD3dso91HCULNnNf4wcWGsVZGiDi1WYsMHVAdfkKuSX/agent-data-sources --dir agent-data-sources-pr
nipmod claim verify gitlawb://did:key:z6MknkD3dso91HCULNnNf4wcWGsVZGiDi1WYsMHVAdfkKuSX/agent-data-sources --json
nipmod publish agent-data-sources-pr --dry-run --json

Dry run shows the package candidate before any public write.

Publish

Dry run first. Ownership before public listing.

A draft is safe for any public Gitlawb repo. A verified publish needs the matching DID identity, helper, manifest and registry candidate.

nipmod manifest validate --dir repo --json
nipmod publish repo --dry-run --json

Paste

Humans and agents start with a public Gitlawb repo URL or DID path.

Draft

Nipmod creates a package manifest, permissions checklist and install preview.

Claim

The repo owner signs the package with the repo DID before it can become verified.

Boundary

Gitlawb stores it. Nipmod verifies it.

Moving refs are not enough. A green package needs digest, DID signature, release event, transparency, witness and advisory evidence.

nipmod publish repo --dry-run --json