Admissibility Vector

Admissibility is determined at the point of execution through the convergence of multiple conditions.

The Admissibility Vector defines the dimensions evaluated at runtime to determine whether an action may bind institutional consequence.

Definition

The Admissibility Vector is the set of conditions that must be satisfied simultaneously at the execution commit boundary for an action to be permitted.

Admissibility is not a single rule or policy.

It is a multi-dimensional evaluation.

Vector Components

Admissibility is evaluated across five dimensions.

Authority (who can act)

Derived from declared sovereignty.

Defines whether the actor — human, system, or agent — is permitted to perform the action.

State (is transition valid)

Determines whether the current system state allows the proposed transition.

An action may be valid in general but invalid in the current state.

Constraints (rules and limits)

Policy rules, regulatory requirements, contractual obligations, and operational limits.

Constraints define what must not be violated.

Context (execution conditions)

The situational conditions under which execution occurs.

Includes timing, dependencies, environment, and risk posture.

Evidence (what supports the action)

Required supporting information that validates the action.

Ensures that execution is not based on assumption or incomplete information.

Admissibility Evaluation

At the execution commit boundary, SCIA evaluates all dimensions of the vector.

An action is admissible only when:

• authority is valid
• state is eligible
• constraints are satisfied
• context is appropriate
• evidence is complete

Architectural Principle

Admissibility is determined through convergence, not sequential checks.

Failure in any dimension results in a non-admissible outcome.

Typed Outcomes

SCIA produces a typed admissibility outcome:

• ADMISSIBLE
• ADMISSIBLE_WITH_CONDITIONS
• ESCALATE
• NOT_ADMISSIBLE
• INSUFFICIENT_INFORMATION

Relationship to SCIA

The Admissibility Vector is evaluated within the SCIA control plane.

SCIA enforces the outcome at the execution commit boundary.

Relationship to Authority Lineage

Authority Lineage defines how authority is constructed.

The Admissibility Vector evaluates whether that authority is valid at execution.

Invariant

No action binds institutional consequence unless all dimensions of the admissibility vector are satisfied at the point of execution.

Closing statement

Admissibility is not determined by intent.

It is determined by the convergence of authority, state, constraints, context, and evidence at execution.

Admissibility Vector — Runtime Evaluation at Commit

Admissibility = Authority + State + Constraints + Context + Evidence

Explore the Architecture

• Category Overview
• Overview of Execution Admissibility Architecture.
• Execution-Bound Enterprise
• Operating model for governed execution.
• SCIA Reference Architecture
• Control architecture enforcing admissibility at runtime.
• Authority Lineage
• Structural chain for resolved authority at commit.
• Pre-Execution Pressure Test
• Diagnostic that surfaces execution risk before consequence binds.

© Arqua Pty Ltd. All rights reserved.