FPF.Reference:16.9.5 - 5. Build the repertoire and criteria without preselecting an architecture
Preface node
heading:fpf-reference-16-9-5-5-build-the-repertoire-and-criteria-without-preselecting-an-architecture:1911
What this page is
This is generated FPF reference text from the specification preface or supporting sections. It helps interpret FPF; it is not FPF Reference product documentation.
Methodology
Use it to understand how the specification wants to be read, then return to a route, pattern, or work packet for active work. Cite generated IDs only when the wording changes the task decision.
Content
C.39.RP returns an inspectable repertoire for the relation comparison:
The four Methods alone remain in local comparison locator LG-EC417-ReleaseMethods; the three accounts are adjacent repertoire entries with preserved statuses.
The values in the table are pinned for reliance from D-21 through D0. For an identified Method, rely on its current A.3.1 identity result, description edition, evidence window, and only each established relation needed by the use. For a candidate account, rely on its current account edition, named source contents or source window, preserved status and limits, and only already-established relations needed by the use; missing Method identity or a generic input/result relation remains an open limit, not a required field. If a required value is absent or has changed, stop the affected repertoire reliance and reopen the C.39.RP entries that depend on that value.
At D0 this application's reliance window ends; later recovery is outside this case.
For later non-AI recovery, obtain the applicable independent C.39.RP qualification/currentness, readiness, assignment, and permission/authority results. Create a new A.15.2 WorkPlan when coordination needs one. Ground any claimed later dated occurrence independently under A.15.1, whether planned or unplanned.
This application ends with withhold/next-slot. C-EC-Release-v2 stays outside the membership table as a proposed-whole architecture subject; missing family, Method-lineage, account-identity, and AI-transfer bases block only the claims that require them.
C.39.RQ states candidate-neutral contributions and locates every condition with its subject. The case separately names the Systems, performed decision Work and results, covering assignments, and independently obtaining permission or direct decision-authority relations:
The baseline B2 branch relies on one filled A.2.8.PER grant occurrence rather than inferring permission from a charter or register:
The occurrence identity is the tuple SA-GrantTraceAcceptReject-17, beneficiary assignment ref ASG-TraceReview-17, action-specification edition ACT-TraceAcceptReject-EC417-e1, policy edition TraceReviewCharter-17-e1, ClaimScope CS-EC417-AITraceSuggestions, and the D-21..D0 effective interval. A change in any member ends or splits the occurrence.
Only one provider suggestion is used in the filled case: AI-TraceSuggestion-EC417-01. At D-21 10:00..10:20, admitted System TraceReviewer-17 performs W-TraceAcceptReject-17-01 under ASG-TraceReview-17; the Work instantiates ACT-TraceAcceptReject-EC417-e1 within the grant scope and returns RES-TraceAcceptReject-17-01=accept. PEX-TraceAcceptReject-17-01 : PermissionExerciseRelation@Context connects that dated Work to the exact PERM-TraceAcceptReject-17 occurrence, with beneficiarySystemRoleAssignmentRef=ASG-TraceReview-17, exerciseScope=CS-EC417-AITraceSuggestions, and exerciseInterval=D-21 10:00..10:20. EV-PEX-TraceAcceptReject-17-01 is the ledger evidence about this exercise and remains distinct from the exercise relation. Every later used suggestion would require its own dated Work, result, currentness check, and Work-to-grant exercise relation.
Establish assignment, permission or authority, performed Work and decision result on their respective grounds. Capability, responsibility, access, currentness, readiness, and evidence remain separate as well. The AI provider holds none of the human assignments or relations. ASG-TraceReview-17 and PERM-TraceAcceptReject-17 end at D0; continuing safety or release assignments and authority extend neither the trace-review assignment nor the permission grant. For this worked application, after D0 no new AI suggestion is requested, accepted, or used. Every earlier trace-review occurrence and result remains in the evidence history.
Signed-first, provisional-first, supplier-preparation, and safety-preparation variants remain serious possibilities.
Last Updated: 2026-11-22 — upstream FPF commit 7a93d8f8 (github.com/ailev/FPF)