C.3.A:Annex C - ESG and Method–Work guards
Preface node
heading:c-3-a-annex-c-esg-and-method-work-guards:59281
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
ESG obligations (normative)
When a state transition publishes or relies on a claim quantified over kinds, the ESG guard SHALL:
- pin the claim, exact quantified claim kind, receiving kind, and both needed
KindSignatureeditions; - establish the correct subkind restriction direction or, for a required correspondence between distinct kinds, the exact source-claim to target-receiving KindBridge relation and separate assertion;
- check Claim scope against the exact slice with all its declared selectors, including any
Gamma_timerequired by A.2.6; - when one or more actual candidates are part of the transition, evaluate the four-input judgment for each candidate under the receiving kind and preserve all three values;
- when a RoleMask is used, recover its declaration edition and, when the transition is candidate-bearing, evaluate the exact masked judgment;
- apply justified bridge consequences to R only;
- check the policy-required expression properties and required freshness on their owners; and
- return a separate state-transition disposition.
ESG MUST NOT widen G to hide incompatibility, treat a label as a candidate judgment, or convert unknown to false.
Method–Work obligations (normative)
Open this Method–Work guard when capability, method and WorkPlan are part of the prospective or actual Work use. A transformation identified under A.3/A.3.4 may already be a sufficient result: natural, spontaneous or formal change, for example, can be described without claiming Work.
Apply A.13 when the claim concerns scale-free agency. If the receiving use also claims that particular Work occurred, establish that occurrence under A.15.1. Identify who acts and what changes. For A.12:4.2 Reflexive Split, establish two distinct participants and the part relation of each to their common containing holon. Where the work instead concerns joint dynamics without separable acting and affected participants, use the applicable dynamics, interaction or causality account.
Method–Work use has two different boundaries.
Prospective entry. Before execution, a guard may decide that a holder capability, method, intended U.WorkPlan, JobSlice, and candidate inputs are sufficient to start. That decision SHALL NOT claim that Work already occurred. The holder's actual ability, ability statements or currentness assessments, fit predicates, WorkPlan, JobSlice, and entry record remain distinct.
Actual result or acceptance. When the check concerns performed Work, the guard SHALL identify exact W : U.Work as an independently grounded, world-side, dated 4D Work occurrence under A.15.1. Keep W distinct from the U.Work kind, JobSlice, capability and plan. A log, result record or assurance record about W remains a separate object; when it is a claim-bearing episteme, its content designates W.
A conforming Method–Work check SHALL:
- pin every expected input/output local kind and signature edition;
- for cross-context candidates, compare kind identity and recover target declarations and any required bridges;
- require the capability's governed Work scope to cover exact JobSlice with explicit time;
- for every actual input candidate and, after execution, every actual output candidate relied on, check admissibility and evaluate the four-input judgment under its pinned expected declaration only when admissible, preserving all three values;
- use exact RoleMask declarations and masked judgments when procedural tailoring is used;
- apply any justified bridge consequence to R, then check capability measures, qualification/currentness, and fit as separately governed predicates before deciding entry or acceptance;
- before execution, return only an entry disposition and keep W absent;
- after execution, ground result or acceptance in the independently identified W;
- keep W, inputs, outputs, JobSlice, capability, plan, logs, and assertions distinct; and
- refuse fail-closed on
falseorunknownwithout rewriting either value.
Ready-to-use skeletons
ESG_TypedGate(Claim, claimKind, claimSignatureEdition, receiveKind, receiveSignatureEdition, TargetSlice, candidates?). When the transition is candidate-bearing, apply Guard_CandidateUse to each with both declaration editions; otherwise apply Guard_TypedClaim for declaration-only use. Reuse shared checks and bridge consequences under E-01, then return the separate transition disposition.
MethodWork_EntryGate(Capability, WorkPlanRef, JobSlice, inputCandidates, inputDeclarations). Apply §C.2's prospective checks in E-01 order and check required freshness. Return “entry allowed/refused”. Do not create or identify W.
MethodWork_ResultGate(W, JobSlice, actualInputs, actualOutputs, declarations, ResultRecordRef?). First recover the independently grounded dated W under A.15.1. Apply §C.2's declaration, Scope, admissibility, and input/output judgment checks in E-01 order, then complete any acceptance predicates. Keep any ResultRecordRef as a reference to a separate episteme whose content designates W.
Worked examples [I]
ESG braking policy. The claim pins VehicleSignature@v4 and the dry/wet TargetSlice. The consumer is restricted to PassengerCar, and SubkindOfObtains(PassengerCar, Vehicle; plantVehicleScheme) holds under the paired exact declaration editions.
For VIN-17, evaluate J(VIN-17, PassengerCar, passengerCarEdition, TargetSlice)=true; C.3.1 monotonicity then supplies the Vehicle-side classification needed by the universal claim. If the unavailable brake-configuration data leave this classification unsettled, the judgement is unknown and the transition guard separately refuses the use.
Risk-score Work entry and occurrence. ComputeRiskScore capability is considered for request req-884 in JobSlice api-v2.3/eu-west/t-204. The entry guard evaluates the request under the pinned AuthenticatedRequest signature. If true, it may admit execution; no Work occurrence yet follows.
After execution, actual W = RiskScoreRun-2026-07-22T10:03Z-884 : U.Work is independently grounded as the dated world-side occurrence. RiskScoreRunLog-884 is a separate episteme designating W. The output score value is a separate candidate evaluated under its declared output kind and signature edition.
Cross-context plant use. The source claim and source kind cross via separate Scope and KindBridge channels. Plant-B recovers its own target declaration and evaluates TransportUnit candidate TU-9. Bridge assertions affect R; they do not classify TU-9 or create the later Work occurrence.
Anti-patterns and remedies
Last Updated: 2026-11-22 — upstream FPF commit 7a93d8f8 (github.com/ailev/FPF)