2026-02-13-ONE-PERSON-MANY-SCOPES

One Person, Many Scopes

You are not your organization. You’re a thread that runs through all of them.


Dr. Sarah Chen is a breast oncologist at one hospital, a principal investigator at another, a clinical advisor at a startup, and a reviewer for two journals. Five roles. Five organizations. One person.

In most software systems, Sarah has five accounts, five passwords, five credential files, and five separate records of her work. If the startup wants to verify her clinical authority, they call the hospital. If the journal wants to confirm her research credentials, they check PubMed. Nobody connects the dots. Nobody has a unified view of Sarah.

CANONIC does.

Identity as Scope

In CANONIC, a person is a scope — just like an organization is a scope. One identity. Multiple affiliations. Each affiliation is a governed relationship with its own inheritance chain.

Sarah’s VITAE — her governed identity document — is versioned, committed, and hashed. It carries her credentials, her publication history, her clinical authority, and her work across every organization she touches. When she validates an AI recommendation in one hospital and then advises the startup, her authority carries over. Not because someone made a phone call. Because the governance framework links her VITAE to every scope she participates in.

One person. Many scopes. Full traceability.

Why This Matters Now

Enterprise AI deployments involve people who span organizations. A compliance officer who consults for three health systems. A developer who contributes to open-source projects and commercial products. A physician who moves between two hospital systems.

If your governance framework can’t handle multi-org identity, you’re either duplicating credentialing work across every organization — expensive, fragile, certain to drift — or you’re ignoring the cross-org dimension entirely, which means your “governed” system has a gap the size of a person.

CANONIC governs both entities: the person AND the organization. Both are scopes. Both carry governance. Both are on the LEDGER. When the auditor asks “who validated this recommendation?” — the answer traces through a VITAE to every relevant credential, regardless of which organization the work was performed in.

Figures

Context Type Data
post flow-chain nodes: Hospital → Institute → Startup → VITAE

CANONIC — One identity. Many scopes. Full governance.