Aadya connects privacy-preserving proofs, wallet-bound authority, organizational delegation, and governed risk decisions. Each surface below distinguishes the reference implementation from the production, partner, and governance work it does not yet replace.
Start with a narrow decision, bind it to the right holder or organization, and leave an inspectable receipt. The cards describe the product intent; their status labels describe what is demonstrable today.
A private-presentation reference path demonstrates an over-threshold proof and a verifier-scoped result. A wallet-backed route can request an age claim with holder binding. They solve related problems, but they do not make the same privacy promise.
Reference and wallet-demo paths
The private proof is reference-grade; wallet compatibility does not by itself establish issuer trust, cross-site unlinkability, or a production holder-device deployment.
Bind a decision to a device-held key, user authentication, and the transaction it authorizes. The reference flows make holder binding and step-up visible rather than treating a successful login as sufficient authority.
Reference verification and sample payment flows
The payment surface verifies signed sample authorization data; this site does not move money. Regulated payment roles, bank connectivity, and a production SCA programme require separate participants and governance.
Prove an organizational role with a minimally disclosed credential, then issue a narrower, signed authority to an agent. Spend caps and denials can be decided at action time and retained as auditable records.
Test-ecosystem and reference delegation
The organizational proof uses demonstration credentials and a test trust context. It is not a production vLEI lifecycle, an accredited issuer, or an endorsement by GLEIF, EBSI, or a standards body.
The JointRisk control room separates fraud and early-credit-loss assessments while sharing an accountable feature layer. It records a signed, transaction-bound approve, step-up, or decline decision before the simulated action.
Synthetic-data control-room demo
It is not a calibrated bank model, a live GFTN deployment, or a claim about payment-fraud reduction. No bank, customer, or GXS production data is used in the reference scenario.
The demos are deliberately narrow: they let you observe a decision and its limits before discussing integration or deployment.