Distribution

The badge

An SVG, not a hosted image. It renders in a README with no runtime, and it cannot phone home — which for a supply-chain security product is not a detail. A badge that beaconed on every page view would be indefensible.

Preview

State

Live, with collateral posted against the version claim.

Bond, whole units1500

Already scaled out of the bond asset's decimals, which is what the badge expects.

High-risk capabilities0

Above zero, a bonded badge turns amber rather than green. Bonded is not the same as harmless.

Paste into a README

[![Lockstep pin for kuru-quote](lockstep-kuru-quote.svg)](https://lockstep.dofolabs.space/pins?pin=0xdd42841469d224a4d4cfacfd49e6cff1f79a5944a056e18606653f06b2acf3ed)

The badge links to the pin it describes, so a reader can check the claim rather than take the colour on trust. A badge nobody can verify is decoration.

lockstep-kuru-quote.svg is a file you commit, which is why the image path is relative. lockstep publish writes it for you and prints this line; the GitHub Action puts both in the run summary.

Why amber exists

A green badge on a skill that can call approve(address,uint256) would be misleading. The bond is posted and the version claim is honest, but the skill can still grant an allowance over a whole balance. So a bonded pin with high-risk capabilities is amber: the publisher is accountable, and the power is real.

from this registrykuru-quote would render green