top of page

THE MYAKH PLATFORM

How Authorization-Before-Execution Works

Every governed request moves through a deterministic sequence before the downstream AI system may act.

STEP 1

Resolve Identity

​​

​

MyAKH resolves trusted authentication, proofing, or external identity signals into a canonical subject DID and wallet context.

​

​​​​

​

STEP 4

Evaluate Likeness and Policy​

​

The system calculates similarity where applicable and evaluates operation, resource, consent, and governance rules.

STEP 2

Load Consent & Governance State

​

The Gatekeeper loads active consent, assurance metadata, wallet status, policy, resource permissions, and applicable license conditions.​​

​​

​

STEP 5

Allow, Deny, or Flag​

​

The Gatekeeper returns a structured decision and reason code. Only an ALLOW decision should permit the downstream platform to execute.

STEP 3

Validate Pipeline Compatibility​

​

​​The incoming likeness or content reference must be compatible with the stored embedding and pipeline version. Incompatible versions fail closed before similarity is calculated.

STEP 6

Generate Proof and Replay Record

​

The system produces a signed Decision Proof Object that can be retrieved, verified, and replayed for audit.​​

​

Example: Governed Avatar Synthesis

1. A verified rights holder is associated with a canonical identity and wallet.

​

2. Consent and digital-likeness permissions are recorded.

​

3. A platform submits a request to generate or use the avatar.

​

4. The request identifies the operation, resource, modality, and execution context.

​

5. MyAKH checks identity, consent, license conditions, version compatibility, likeness evidence, and policy.

​

6. The downstream synthesis system proceeds only if the Gatekeeper returns ALLOW.

​

7. A signed DPO provides evidence of the authorization decision.

Why This Matters

​Detection asks whether content appears suspicious after it exists.

 

MyAKH asks whether the requested use was authorized before the AI system acts.

​

​This changes governance from a post-processing review into an enforceable runtime control.

bottom of page