Tokenized at ingest
When a record arrives, identifiers are replaced by tokens on the way in, ahead of persistence. Two things do the work: a deterministic layer that recognizes known identifier formats, and a named-entity recognition (NER) pass that catches identifiers in free text. Because tokenization happens at ingest, the raw value never reaches the decision chain. What lands on the chain is a token, and the chain is still fully verifiable over tokens.Governing storage without holding the value
The raw value still has to live somewhere: a compliant store like a UIDAI Aadhaar Data Vault. Sakshi’s job is to prove it went there, not to hold it. Given a reference key, Sakshi verifies the value landed in the vault by checking the key’s metadata, which the vault exposes without granting decode rights. It never sees or detokenizes the value.POST /api/v1/vishwas/verify-disposition returns a vault-verified
disposition when the check passes. A value backed only by a signed receipt is
recorded as attested, and a value sitting outside the vault, or offshore, is
flagged as a residency breach. An assertion would have hidden that; verification
surfaces it.
Document and KYC governance
Govern what was extracted, by which agent, and where it was stored.
Fairness screening
Declared-first screens that run without ever de-anonymizing anyone.