Skip to main content
An evidence pack is a regulator’s instrument encoded as data: each clause is mapped to the evidence that satisfies it, and each mapping is scored against the live records in your deployment. The result is a readiness score and a signed bundle you can hand to an auditor. Adoption moves the score, assertions do not. This guide picks a clause map, reads its readiness, and exports a signed pack. An ingest key is enough to read every endpoint here.
1

Pick a clause map

List the instruments this deployment maps. The name field is the map_name the pack endpoints take.
2

Check the readiness score

Readiness scores every clause across every mapped instrument. A clause is READY only when each evidence type it cites passes a live check against this deployment’s data. Gaps come back with the specific failing evidence and the fix that unblocks them.
Work the gaps in leverage order. One fix, like assigning an owner to an orphan agent, often unblocks several clauses at once.
3

Generate the pack

Generate the pack for a map. It is built live every time: chain verification runs, telemetry computes, and counts query the current records. It is never a cached document. window_days bounds the evidence window (default 30).
4

Export a signed bundle

The export endpoint returns a freshly generated pack, Ed25519-signed with this deployment’s key over the exact bytes. Anyone holding the public key can verify it offline, with no live connection to Sakshi.
The signature covers the exact serialized bytes of the pack. Re-serialize or edit a field and verification fails, which is the point.

​
Next steps

Evidence packs

How instruments are encoded as clause maps and scored on live evidence.

Fairness screening

The Vishwas declared-first screens that feed several clauses.

Bound autonomy

The kill switch and envelope evidence that many clauses depend on.

API reference

The full Vidhi endpoint surface.