Glossary

Use these terms across the guides, Console, SDKs, and API reference. API identifiers appear in code style; product concepts use the names shown here.

Use these definitions when reading an authorization trace, configuring a policy, or discussing an integration. Billing terms link to their full contractual usage definitions below.

Term	Meaning
Action hash	Canonical digest binding the intended environment, action, subject and actor, resource, context, audience, and nonce
Active Brainprint	Commercial usage unit based on a subject's qualifying assurance within its contractual billing window; see the precise billing definition
Actor	The entity performing the request; the supported canonical actor type is human
Anchor	Customer-declared basis for associating a subject with an account; the customer verifies that association
Assurance Profile	Typed claims with status, coverage, freshness, evidence references, reason codes, limitations, and versions
Assured Action	Commercial usage unit for qualifying authorization activity, subject to exclusions and deduplication
Audience	The relying-party application or service for which an action and proof are intended
Authorization	A recorded decision for a particular bound action request
Brainprint	Private, tenant-scoped learned behavioral reference contributing continuity evidence
Challenge	Action-bound passkey confirmation or a clearly labeled sandbox simulation that reevaluates the original request
Client token	Short-lived browser credential scoped to a subject, environment, and registered origin
Consumption	Online one-time state transition that prevents the same proof from being accepted again through the consuming API
Context	Small, schema-validated request material needed to bind the consequential operation
Coverage	Quantity and modality coverage of accepted evidence; not identity confidence
Decision	Exactly one of allow, challenge, hold, or deny
Enrollment	Collection and completion process that establishes the subject's initial model under server readiness checks
Environment	Sandbox or live resource and credential boundary within a tenant
Evaluation	Time-bounded shadow study with recorded success criteria and outcomes
Evidence	Derived interaction features and integrity metadata submitted by the SDK
Freshness	Age of evidence relevant to a claim or decision
Idempotency key	Stable logical request identifier reused only for retries of the same request material
Insufficient evidence	Assurance status or reason translated by policy into challenge, hold, or denial
JWKS	Published JSON Web Key Set used to verify proof signatures
Nonce	Request-specific value bound into the action hash and protected against improper reuse
Outcome	Customer report of what actually happened after an authorization
Policy	Immutable, versioned requirements and constraints applied to a protected action
Proof of Agency	Short-lived signed artifact bound to the allowed action and relying-party audience
Protected action	Registered consequential operation with a stable key, resource type, context schema, risk class, and policy
Relying party	Customer service that verifies the proof and enforces the business operation
Research consent	Separate recorded permission for supported research use, distinct from ordinary service operation
Session	Enrollment or observation interval for a subject
Shadow mode	Policy evaluation that records hypothetical decisions without enforceable proof issuance
Subject	Tenant- and environment-scoped pseudonymous person record owning a Brainprint
Tenant	Customer administrative and data isolation boundary

Billing terms are defined in Usage and billing. Security boundaries are described in Architecture and Threat model.