Verified identity tells AtlaSent who or what is acting. It does not tell AtlaSent what the organization authorizes that Actor to do.
Verified Actor Identity
How AtlaSent establishes the Actor from an authoritative identity source without treating identity as authority.
Execution-time authorization
The fresh per-request authorization determination made at the execution boundary.
Organizational authority
The standing, scoped organizational right to cause or approve a class of change.
Consequential computational actions
The actions whose effects may require explicit authority, policy, evidence, or enforcement.
Identity, authority, authorization, approval, and access
Why these concepts — plus Permit, Execution, Effect, and Proof — must not be collapsed.
The controlled lifecycle
allow is not a Permit; a Permit is not Verification; Verification is not Execution; Execution is not Effect; Evidence is not automatically Verified Proof.
Product/runtime nouns
Action class
The organization-specific runtime governance/configuration object for an Action Type.
Policy
Versioned rules defining conditions under which Authority may permit an Action.
Permit
The bounded runtime artifact carrying a positive Authorization to an execution boundary.
Runtime flow
How Evaluation, Permit verification, execution, observed effect, and evidence connect end to end.
Proof verification
How Evidence becomes independently verifiable Proof for the properties actually checked.
Approval
Verified approver input that may satisfy a required condition; not itself final Authorization.
Distinctions that must remain intact
- Identity ≠ Authority
- Authority ≠ Authorization
- Authority ≠ Approval
- Approval ≠ Decision
- Decision ≠ Permit
- Permit ≠ Verification
- Verification ≠ Execution
- Execution ≠ Effect
- Evidence ≠ Verified Proof
allow≠ Execution- Action Type ≠ Action Class
- Action Class ≠ Protected Class
- Gate ≠ Policy
- Proof ≠ generic log
Where to go next
- Understand identity: Verified Actor Identity.
- Understand the category: Execution-time authorization → Organizational authority.
- Understand the governed object: Consequential computational actions.
- Understand the distinctions: Identity vs. authority vs. authorization vs. approval vs. access.
- Build: Quickstart — your first protected action.
- Trace the runtime: Runtime flow → Permit → Proof verification.