This publication introduces Snapshot-Bound Admissibility Sequel, a non-operational specification artifact defining a snapshot-bound pre-execution admissibility class over an external carrier protocol layer. The specification defines a boundary-first admissibility regime in which execution may proceed only when admissibility has been externally grounded before action. For this class, lawful admissibility requires a strictly defined canonical basis time T₀, a valid snapshot relevant to T₀, a ruleset in force at T₀, deterministic derivation of the admissibility outcome from snapshot and ruleset, and a binary canonical outcome of ALLOW or DENY. If a valid snapshot basis at T₀ does not exist, execution is inadmissible. This artifact is non-operational. It does not publish an implementation, service interface, deployment method, credential path, payment path, or operational control mechanism. It is not a governance framework, not a post-failure truth layer, not a probabilistic scoring system, and not a discretionary review surface. The specification preserves the external-anchor law: without an external admission anchor, execution is structurally impossible in the canonical path, and refusal precedes execution. The central time law is: Admissibility belongs to T₀, not to the later machinery that transports, records, or applies it. Relation to existing boundary work: CRAB fixes the cloud-reference admission principle: system-significant cloud execution is inadmissible without an external admission anchor. SAB fixes the admission-entry boundary: an execution intent must first be admitted into the admissibility regime before a valid boundary request can exist. This sequel class defines the time-bound basis logic by which admissibility is grounded. License and use notice: This artifact is released under CC BY-NC-ND 4.0. It may be read, cited, linked, and referenced with attribution. No commercial use, modified versions, derivative specifications, operational implementations, service claims, or implied endorsement are granted by this publication. Any operational, commercial, implementation, licensing, or evaluation use requires separate written permission from the author.
Independent Researcher (Tue,) studied this question.