How it works
From agent action to verifiable receipt.
RANKIGI witnesses submitted actions, seals them into hash chains, and gives reviewers a receipt they can verify without trusting the dashboard.
01
Agent acts
Your SDK or API call submits metadata for an agent action. The agent does not wait on RANKIGI to continue.
02
RANKIGI witnesses
The event is canonicalized, scoped to an agent and organization, and checked at the ingest boundary.
03
Receipt is hashed
SHA-256 binds the canonical payload and prior chain head into a new event hash.
04
Chain advances
The event is appended with previous_hash and chain_index so reordering or alteration is detectable.
05
Head is anchored
Chain heads can be anchored to external timestamp and transparency infrastructure.
06
Reviewer verifies
A browser verifier or verify.py recomputes the chain outside the dashboard.
Proof boundary
Observable is not provable.
ProvesThe submitted chain is internally consistent under the displayed cryptographic checks.
Does not proveThat every real-world agent action was submitted to RANKIGI.
Depends onYour integration submitting the right event metadata at the right boundary.