A.6.B:8.4.5.2 - Atomize + Classify
L-PRJ-01 (Definition).
approved(project, approvalKind) is defined as a relation kind; approval kinds include: “sponsor-signoff”, “stage-gate-pass”, “budget-authorized”, “staffing-assigned”, etc.
(Truth-conditional: disambiguates kind and polarity.)
A-PRJ-01 (Gate predicate: stage entry).
For starting execution work, ExecutionAdmissible(project) holds iff required approvals are present and required prerequisites are satisfied (e.g., risk review completed, budget line exists, key roles staffed).
(This is the real “may start work” entry predicate; it references L-PRJ-01 for what counts as approvals. If “approved” is meant as permission rather than gate evidence, use the permission-word branch in §8.4.1. An approval registry entry or evidence carrier alone remains source/display evidence and is not a grant.)
D-PRJ-01 (Duty).
Admitted project-coordination system ProjectCoordinator-A is the actual duty bearer of separately obtaining ProjectEntryCommitment-PRJ-01 : U.Commitment; it SHALL not initiate execution unless A-PRJ-01 holds, SHALL keep the approval registry current, and SHALL retain or expose the evidence carriers referenced in E-PRJ-02.
(References A-PRJ-01 and E-PRJ-02 by ID.)
E-PRJ-01 (Gate decision result).
At Γ_time=snapshot(t), ProjectEntryGateResult-P-t : GateDecisionResult has gateRef=ProjectEntryGate-P, decisionSubjectRef=ProjectEntryClaim-P-t, boundedActionRef=StartExecution-P, and profileApplicationRef=ProjectEntryProfileApplication-P-t. That application of ProjectEntryProfile-v3 uses the complete required set {ApprovalCheck-P-t, RiskReviewCheck-P-t, BudgetCheck-P-t, StaffingCheck-P-t} : GateCheckApplicationResult[]; each exact application reports its checked subject and criterion, has sourceOutcome=satisfied, and maps to pass. The result records decisionValue=pass, action consequence “start StartExecution-P within the admitted project-entry window”, the project-entry scope and window, and recheck on any changed approval, risk-review, budget, staffing, profile, scope, or window.
(This actual E-* result applies the inputs named by A-PRJ-01; it is neither the A-* predicate nor performed execution Work.)
E-PRJ-02 (Evidence for reliance).
For reliance on E-PRJ-01, the exact observed carrier set is {DecisionRecord-R7, MeetingMinutes-M3, BudgetLine-B4, StaffingAssignments-S2, GateChecklistSnapshot-G9}. An A.10 evidence-provenance path links those carriers to the four exact GateCheckApplicationResult values and ProjectEntryGateResult-P-t. GateChecklistSnapshot-G9 displays the result; its presence alone establishes neither a check result nor the gate decision.
(References A-PRJ-01 and E-PRJ-01; avoids RFC deontics.)