Proposed Action
The specific action being requested, initiated, recommended, or prepared for execution.
A deterministic gate mechanism for evaluating consequence-bearing action before execution is permitted.
Status: Published Framework
The Pre-Execution Admissibility Gate (PEAG™) is a VTI governance framework for applying execution admissibility at the boundary between proposed action and authorized execution.
PEAG establishes a deterministic decision gate through which a proposed consequence-bearing action must pass before execution is allowed.
Rather than relying only on post-event monitoring, audit logging, or reconstruction, PEAG evaluates whether the proposed action is admissible before execution is permitted to proceed.
A system should not execute merely because it can. It should execute only when the action is admissible.
PEAG PrinciplePEAG is not the whole theory of consequence governance.
Consequence Science explains why governance exists. Deterministic Trust Architecture describes how computational systems can govern consequence. Execution Admissibility defines the boundary where proposed action is evaluated.
PEAG is the gate mechanism applied at that boundary.
Execution Admissibility asks whether action may proceed.
PEAG provides a deterministic gate for answering that question before execution occurs.
If admissibility conditions are not satisfied, the action should not cross the execution boundary.
Modern computational systems provide extensive mechanisms for monitoring, auditing, logging, reconstruction, and post-event review.
These mechanisms describe what occurred after execution. They do not inherently determine whether a consequence-bearing action should have been permitted to form.
As systems become increasingly autonomous, distributed, and capable of producing legal, financial, operational, regulatory, and safety consequences, governance must address admissibility before execution.
PEAG defines a structured pre-execution control gate that evaluates admissibility conditions before a consequence-bearing action is allowed.
Implementations may evaluate identity, authority, policy, evidence, trust state, contextual conditions, risk thresholds, continuity controls, and other admissibility factors prior to granting execution authorization.
Execution proceeds only when admissibility requirements are satisfied under the governing control model.
The specific action being requested, initiated, recommended, or prepared for execution.
Whether the actor or system currently has authority to initiate or approve the proposed action.
Whether governing rules, constraints, permissions, and prohibitions allow the action under current conditions.
Whether available evidence is sufficient, current, verifiable, and aligned with the proposed action.
Whether the operational governance condition supports execution eligibility at the time of evaluation.
Whether the action is admissible, inadmissible, pending, insufficient, conflicted, or escalated.
Capability is not permission. Permission is not admissibility.
Admissibility DistinctionExecution Admissibility is the governance concept that a proposed action must satisfy defined conditions before execution is allowed.
PEAG is the gate framework that applies that concept at the execution boundary.
In this relationship, Execution Admissibility defines the decision requirement, while PEAG provides the pre-execution gate mechanism.
The Deterministic Execution Admissibility State (DEAS™) defines a structured representation of admissibility conditions.
PEAG governs the execution decision boundary through which those conditions are evaluated before authorization.
DEAS represents admissibility state. PEAG governs the gate through which that state is evaluated for execution.
Deterministic Trust Architecture provides the broader computational architecture for evaluating identity, authority, policy, evidence, trust state, and admissibility before execution.
PEAG is a specific pre-execution control mechanism within that broader architecture.
Trust-State Systems represent the operational governance condition of an actor, system, workflow, credential, or proposed action at the time execution is evaluated.
PEAG may use trust-state evaluation as part of its admissibility determination before allowing execution to proceed.
PEAG is applicable to computational environments where execution authorization carries material consequence.
The VTI Foundation develops standards, governance models, and conformity programs related to execution admissibility and consequence-governance infrastructure.
Future standards or conformity programs may incorporate PEAG-related controls, evaluation criteria, and certification requirements.
PEAG is non-normative unless expressly incorporated into a published VTI standard, annex, conformity program, or certification requirement.
Consequence Science explains why execution must be governed.
PEAG provides a gate mechanism for preventing consequence-bearing action from proceeding unless admissibility conditions are satisfied.
We do not engineer consequence. We engineer the governance of consequence.
Guiding Statement