A.15.5:4.3 - Commitment and Launch Boundary

Keep commitment facts separate from the readiness value. The criterion may consume exact current commitment claims and their qualification intervals, but ready, readyWithKnownGaps, notReady, or unknown does not mean committed, institute a commitment, discharge one, or authorize entry. State the practical next move—stop, prepare, probe, seek a separately governed commitment, submit to a gate, launch only under its separately satisfied entry conditions, or recheck—as the result’s bounded use and return condition, not as another ontic status family. The older labels readyForProbe, readyForCommitment, committed, blocked, and requiresGateDecision therefore resolve to a local readiness value plus an explicit next move, commitment claim, stop, or gate question; they are not additional ReadinessResultValue members.

Use A.2.8.PER when a pre-entry readiness criterion consumes permission material. Name each exact value and its own qualification: a current GrantedPermissionRelation@Context occurrence with its beneficiary, permitted-action specification, U.ClaimScope, and validityWindow; a distinct NonProhibitionFinding@Context with its frame and evaluationWindow; and any PermissionNormConflictFinding@Context with its overlapWindow, disposition, and, when settled, the subject pattern’s resolution result and effectiveWindow. Non-prohibition is not a grant, a grant does not resolve conflict, and an unresolved current conflict blocks or degrades the readiness use under the criterion. PermissionExerciseRelation@Context and NonViolationFinding@Context require already dated actual work: cite either only as evidence about a different exact Work occurrence, or in an explicitly marked post-launch recheck after the target Work is actual, with its own exerciseInterval or evaluationWindow. Neither retrospective result proves current grant, capability, future exercise or non-violation, readiness, gate passage, or target-work performance. The readiness result institutes no permission, exercises none, resolves no conflict, and turns no non-prohibition finding into a grant. Use A.21 only when a current profile application governs the declared check applications and their mappings to a distinct GateDecisionResult. Keep DecisionLogRef, scope, currentness result, and effective window recoverable for this readiness use. A readiness badge, green tile, full-kit label, or commitment board position is not gate passage; gate passage creates none of the permission objects.