One canonical Subject.
Many independent systems.
The Subject stays. The Controller changes. GulliANT separates a persistent on-chain Subject from its replaceable wallet Controller. Applications can associate their own records with the Subject; systems using wallet addresses as permanent references would need to integrate the Subject instead. Each system retains its own data, policies and decisions. Illustrative scenarios, not claims of deployments or partnerships.
Institutional Finance & Banking
Digital-asset services need continuity beyond wallet addresses. Banks can associate their own customer records and permissions with a canonical Subject. Planned, authorized Controller replacement preserves that reference. Customer identification, account management and regulatory decisions remain within the institution's systems.
Real Estate & RWA
Long-term asset relationships need a stable reference. RWA platforms can associate participant permissions, attestations and relationships with a canonical Subject. Controller replacement preserves that reference. Legal ownership, asset transfers and property records remain governed by the relevant platforms and legal systems.
Crypto Infrastructure & Custody
Rotate the Controller. Keep the Subject. Planned key rotation, such as an HSM migration or a custodian change, can replace the Controller without changing the canonical Subject. This requires the current Controller. It is not recovery from a lost key. Integrated services can continue referencing the same Subject. The Subject Protocol itself does not hold assets or replace institutional security policies.
Web3 Applications
A user's history is not a wallet address. Games, DAOs and Web3 applications can associate participation, reputation and progress with a canonical Subject. Controller replacement preserves that reference, while applications retain ownership of their records, permissions and rules.
AI Agents & Autonomous Systems
An agent's reference should outlive its signing key. Applications can associate an agent's records and permissions with a persistent Subject. Authorized Controller changes preserve that reference as operational keys evolve. Agent capabilities, delegation and access restrictions remain under the integrating application's control.
KYC / KYB & Compliance
Providers verify. The Subject stays. Identity providers maintain verified identities and supporting evidence in their own systems. GulliANT's provider-agnostic Compliance Adapter records normalized provider-attested compliance facts without storing personal identities or KYC documents. The Subject stays unchanged when its Controller changes, so a provider's own association with it doesn't have to be rebuilt.
Smart Cities & Digital Infrastructure
Public services need lasting references. City platforms can associate permissions, service relationships and records with a canonical Subject rather than a wallet address. Controller replacement preserves that reference. Each public service retains its own data, access rules and responsibilities.