Transparency
What RANKIGI Proves and What It Does Not
RANKIGI is a passive attestation layer. It produces cryptographic records of event metadata submitted to it. The honest scope of those records is described below.
Section 1
What RANKIGI proves
- The recorded sequence of events happened in this order.
- No event was modified after recording.
- Events were signed by this specific agent passport.
- The chain was sealed at this timestamp.
Section 2
What RANKIGI does not prove
- That the agent's reported actions reflect what actually occurred outside the observed surface.
- That the agent followed any specific regulation or policy.
- Legal admissibility in any jurisdiction.
- Regulatory compliance.
Section 3
How to use RANKIGI records
- As tamper-evident audit trail input for compliance review.
- As forensic evidence input for qualified legal review.
- As operational monitoring for agent behavior.
Section 4
Current Limitations and Roadmap Items
- Blockchain anchoring: RANKIGI uses Sigstore Rekor for public anchoring. Direct blockchain anchoring is on the roadmap.
- WebWitness perception anchoring: the perception anchor component (src/lib/webwitness/anchor.ts) is a mock implementation in this release. Production anchoring is on the roadmap.
- Infrastructure regions: additional compute regions are in development. Only us-east is currently live.
- KYA specification: the KYA open specification is authored by RANKIGI. External co-signers and industry adoption are in progress.
For specific legal or regulatory determinations, consult qualified counsel.