Guides

Each guide is self-contained. All of them assume the quickstart is done.

Record Claude Code sessions

Claude Code carries identity in commit trailers — the collector reads them natively. Add to your project’s CLAUDE.md:

End git commit messages with:
Authored-By: claude-code/<model>
Session-Id: <session id>
Spec-Ref: <spec id>

Every agent commit then lands as change.authored with actor_type: agent, tool and model — and the review your human does before merge lands as change.reviewed. That pairing (agent wrote, human approved) is the evidence AI-assisted teams get asked for.

Record Cursor (and other agent tools)

Same mechanism, different writer. Configure your Cursor rules (or the tool’s commit template) to emit Authored-By: cursor-agent/<model> plus Session-Id. Any tool that can put a trailer in a commit message is supported without integration work — the format is the integration.

CI test evidence

Send a test.evidenced event per CI run so every change carries its test result. Minimal job step after your suite:

olobolo record test --change <sha> --result passed \
  --passed <n> --failed 0 --run-ref "$CI_RUN_URL"

Artifact hashes ride along, so the referenced test output can later be produced and re-hashed from your own CI archive.

Spec linking

Put Spec-Ref: <id> in the commit trailer; the collector hashes the spec document locally at link time and records spec.linked. Changes without a link surface as unlinked in the dashboard and count against your review posture — visible, not hidden.

Seal a release

A seal is a release.sealed event sent from your release pipeline on tag push — it binds the chain segment since the previous seal to the version, the unit that release evidence reports, attestations and anchors attach to. Send it as the last step of your release job via the ingest API with your source token; the dashboard’s Releases view picks it up immediately, and the seal itself triggers an RFC 3161 anchor of the new chain head.

Install the trust mark

The badge is free at every tier and renders live from chain state:

[![OLOBOLO](https://api.olobolo.com/v1/badge/<org>.svg)](https://olobolo.com/v/<org>)

Pick the layout and size that fits the surface with query parameters — the dashboard’s Trust mark — embed card generates the snippet for you (markdown and HTML, always with the link):

Parameter	Values	Default
`variant`	`full` (two lines), `pill` (one line)	`full`
`theme`	`dark`, `light`	`dark`
`size`	`regular`, `small`, `mini`	`regular`

Size	`full` (w × h)	`pill` (w × h)
`regular`	280 × 48	248 × 30
`small`	220 × 38	200 × 26
`mini`	192 × 30 (one line)	184 × 22

mini drops the “Verified ” underline; the state still shows as the dot (green only while verified) and in the image’s accessible label. The seal and the wording never change with size — only the room around them. Example: https://api.olobolo.com/v1/badge/<org>.svg?variant=pill&size=small&theme=light

Usage rules are part of the deal: the badge links to your public verification page, its wording is contractual and never changes to a claim of approval, and a revoked or failing state renders as such — that honesty is what makes the mark worth showing.

Export the chain

curl -o chain-export.jsonl https://api.olobolo.com/v1/export/<repo>

Export is free forever, at every tier, cancelled accounts included — the evidence is yours. Hand the export plus the verify guide to whoever asked the question.