Category language
category
AtlaSent’s canonical category statement. The product determines whether a
specific consequential computational action is organizationally authorized
under current conditions before the governed effect occurs.
mechanism
A per-request Authorization determination made at the execution boundary,
before a consequential computational action is allowed to produce its native
effect.
concept
A computational action capable of producing a material organizational effect
such that the organization may require explicit authority, policy conditions,
evidence, or enforcement before execution.
concept
The standing, scoped organizational right to cause a class of change.
Authority may be delegated, constrained, revoked, or expire. It is distinct
from technical capability, Approval, per-request Authorization, Decision,
Permit, and Evidence.
Identity and action
identity
The entity presenting a request at the system boundary, before runtime
identity resolution.
identity
The resolved runtime identity evaluated by Policy. Caller and Actor are
related but are not synonyms.
identity
The workload, service, process, device, or runtime actually attempting the
native effect. It is not automatically the requester or approver.
primitive
The consequential operation being attempted.
identifier
The categorical identity of an Action, represented by the canonical dotted
slug. On the public request surface this maps to
action.type / action_type.identifier
This specific occurrence of an Action. It is distinct from Action Type.
configuration
The organization-specific runtime governance/configuration object for an
Action Type. Action Class and Action Type are related but are not the same
concept.
concept
An Action subject to AtlaSent governance or enforcement. A Protected Action
is not a synonym for Action Class.
metadata
Binary enforcement-classification metadata. It is not Action Type identity
and is not an Action Class.
primitive
The governed object whose state may be affected. Public request surfaces
commonly use Target; normalized internal representations may use
Resource.
primitive
Current request or state inputs that are not themselves Authority or Policy,
such as environment, resource state, transaction facts, timing, or other
evaluated conditions.
Authority and decision
primitive
Standing organizational right to cause a class of change.
primitive
The per-request determination of whether this exact Action may proceed now.
evidence
Verified approver input satisfying a required condition. Approval is an input
to Authorization; it is not itself standing Authority, the final
Authorization determination, or proof that Execution occurred.
primitive
A scoped transfer of Authority subject to applicable constraints such as
role, time, resource, Action Type/Class, threshold, or Policy.
evidence
A verified governance fact consumed by Evaluation. A caller-supplied claim
does not become a trusted Assertion merely because it was supplied.
operation
The deterministic operation that evaluates the request against current
Authority, Policy, required Assertions/approvals, Resource, Context, and other
applicable conditions.
primitive
The runtime outcome of Evaluation:
allow, deny, hold, or escalate.
A Decision is not Approval. An allow Decision does not prove that Execution
occurred.decision
The request satisfies the evaluated Authorization conditions. A Permit may be
issued for the bounded execution context.
decision
The request is not authorized under the applicable evaluated conditions. No
Permit authorizes execution on that Decision.
decision
The request is not yet authorized because a required condition, state, or
evidence item remains outstanding.
decision
Additional authority, review, or evidence is required before the request can
become authorized.
Policy and enforcement
primitive
Versioned rules defining conditions under which Authority may permit an
Action. Policy is not itself Authority.
primitive
A published runtime snapshot of Policy rules used for Evaluation.
concept
The conceptual portable artifact embodying a positive Authorization. The
current runtime/wire implementation uses Permit as the concrete species.
primitive
The current runtime/wire artifact implementing a positive Authorization for a
bounded execution context. A Permit is verified immediately before execution.
It is not standing Authority and is not the durable Evidence record.
primitive
The enforcement point with practical ability to withhold or constrain the
native effect until required authorization conditions are satisfied. A Gate
is not a Policy engine.
operation
The point-in-time check that a Permit is authentic, current, appropriately
bound, unexpired, unrevoked, and unreplayed for the execution attempt. The
current public operation is
POST /v1-verify-permit.posture
An enforcement posture in which a governed action does not proceed through
the protected path when required authorization or verification cannot be
obtained. Apply this claim only to paths actually configured and tested for
fail-closed enforcement.
Execution and evidence
operation
The native system’s attempt to perform the Action. Execution is a separate
state from Authorization.
primitive
The actual state change or side effect produced by the native execution
system. A Decision or Permit issuance alone does not prove the Native Effect
occurred.
primitive
The durable record connecting determination, Permit lifecycle, Verification,
Execution, and execution conformance/outcome.
primitive
Cryptographically verifiable Evidence suitable for independent verification.
Proof is not a synonym for a Decision, Approval, Permit, or generic log line.
primitive
The tamper-evident, hash-linked evidence history used to preserve integrity
and ordering. Prefer tamper-evident over immutable unless a stronger
storage claim is independently supported.
Product packaging
product
Customer/product packaging around one or more Protected Actions. A Safeguard
can include Action Class configuration, Policy, gate requirements, authority
mapping, connectors/assertions, rollout/readiness material, and evidence. It
is not another authorization engine or a second action taxonomy.
product
A versioned mapping/reference package for a Safeguard, including Protected
Actions, gates, assertions/connectors, authority/onboarding, and
readiness/evidence material.