A.6.C:4.1 — Four questions for contract-like boundary wording

Preface node heading:a-6-c-4-1-four-questions-for-contract-like-boundary-wording:16095

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

When unpacking contract-like wording or deciding what the terms and acts together establish, ask the questions that bear on that use. A question may yield zero, one, or several atomic claims. Add corresponding rows only when stable reuse, decision, audit, dispute, or cross-face projection needs the Claim Register; the question itself is not a bundle part or direct-object kind.

  1. What was promised?

    • The promised value or effect (the promise content) in the intended scope.
    • In FPF terms (A.2.3), U.PromiseContent is promise content, distinct from an execution event or an obtaining individual commitment.
    • Prose head rule (normative). When referring to U.PromiseContent in normative prose, authors SHALL use the head phrase promise content (or service offering clause or service promise clause) and SHALL NOT rely on the bare head noun service. If the surrounding text also talks about endpoints, systems, and operations, apply A.6.P:4.11a only when the current relied-on use hides which concrete subject or relation is meant; examples include a service access point, service delivery system, or service-delivery Work occurrence. Mere proximity to those words creates no additional claim or recovery duty.
    • Recommendation: when commitments, gates, evidence, or MVPK faces need stable citation of the promise content, give it a stable local ID (e.g., SVC-*) to prevent paraphrase drift.
    • Claim-classification discipline: keep meanings and definitions of the promised behavior in L. A generic prescription about that behavior is a separate D claim about its normative source and applicable rule content. If an actual System or separately governed party has that duty, state a separate D claim about the U.Commitment, plus any A-* and E-* references needed by that claim.
  2. What was said, published, or instituted?

    • Speech-act Work: when the passage asserts a particular communicative act, apply A.2.9 to establish its U.SpeechAct <: U.Work occurrence. An ordinary source attribution or publication reference can suffice when no such occurrence claim is needed.

    • Description/publication: identify the utterance episteme and any publication occurrence, form, rendering or carrier whose identity changes the current claim or use.

    • A speech act may institute or update a commitment or strong grant only when the context policy recognizes that act type and the subject pattern's obtaining conditions are met.

    • Published utterance descriptions can carry L/A/D/E-classified claims. Identify any actual speech act and institutional effect separately under their subject rules.

    • World-side obtaining rule (normative). The predicates defined in A.2.8 and the cited context policy decide whether a commitment obtains; the predicate defined in A.2.8.PER together with that policy decides whether a strong grant obtains.

      For a commitment, use the actual instituting basis required by its constitutive rule: the current A.2.9 path uses an actual U.SpeechAct; another basis requires a subject pattern that admits it and gives its occurrence rule. A strong grant requires the actual instituting speech act under A.2.8.PER.

      Preserve the participants, scope/window, current policy, and any revocation or supersession conditions. A Claim Register row, utterance description, publication, carrier, or identifier creates or proves neither relation by itself.

      For a commitment, a cited fact is constitutive only when the identified rule makes that fact current and the pattern for that subject supplies its test. Publication or approval may establish a publication/status relation only through that relation's predicate and obtaining facts.

    • Representation and reliance rule (normative). The model MAY assert or rely on a commitment or grant only through a separate atomic claim that identifies the U.Commitment or GrantedPermissionRelation@Context occurrence and cites its predicate, SubjectPatternLocator, participants, scope/window, and the currentness or evidence required by that use.

      For a commitment, cite the rule-required actual instituting basis and policy; for a strong grant, cite the actual instituting speech act and policy.

      Never infer the relation from Publish/Approve wording, a document, carrier, or completed-looking record alone.

  3. What governance or permission-looking claim exists?

    • A generic prescription states what one policy or other normative episteme requires; it does not create an individual duty bearer or commitment occurrence.

      A claim that one actual System or separately governed party has that duty instead cites one separately obtaining A.2.8 U.Commitment. Here the normative episteme may be a contract, SLA, protocol, or policy, and the generic claim also states where its rule applies.

    • When the model asserts or relies on an individual obligation, recommendation-as-duty, or prohibition, write a separate atomic D claim whose direct object is that separately obtaining U.Commitment.

    • For permission-looking wording, select one A.6 A6-AW-* row. Only A6-AW-NORM-GRANT enters D. Within A6-AW-GATE, an admission predicate for a named action or application enters A and an actual A.21 GateDecisionResult enters E; split them into separate atomic claims when both are present. Exercise, weak evaluation, conflict, and observed-source claims enter E when their closing facts are present. Classification under A.2.8.PER alone selects no quadrant.

    • Individual-commitment checklist (use only for the individual branch):

      • identify one U.Commitment occurrence and the separate D-claim or CommitmentAssertion about it;
      • select exactly one actual bearer branch: an admitted U.System or separately governed party;
      • name non-empty duty referents, any actual counterparties, normalized modality, scope, and validity window;
      • cite the current constitutive policy, its individualizing rule, and the actual instituting basis required by that rule;
      • cite a system-role assignment only when that rule uses the assignment as an applicability ground—the assignment is neither bearer nor duty; and
      • add evidence-claim or carrier references only when the receiving reliance or adjudication needs them.
    • Permission-branch pointer: cite the selected A6-AW-* row, its A.2.8.PER object when applicable, and that atomic claim's quadrant. Preserve the object's own schema, participants, and references; do not reuse the commitment checklist.

    • A commitment is not “the spec text”: an utterance description carries the statement, while U.Commitment is the separately obtaining relation described by that statement (A.7 and A.2.8).

  4. What happened, what followed, and what supports reliance?

    • Work: For one dated W : U.Work, recover each actual performer through A.13 and let A.15.1 independently admit the occurrence from that performer, enacted Method, extent, and containing System.

      Add an A.2.1 assignment reference and F.6 only when this account or a receiving use expressly consumes precise assignment-bound attribution through the same obtaining A.13 assignment; F.6 identifies neither the assignment nor the performer.

      Missing or failed F.6 alone leaves independently admitted Work intact. If the same finding questions a premise consumed by A.13 or A.15.1 admission, recheck that premise and its dependent claims.

    • Result or consequence: only when the sentence asks for one, select the matching A.15.1:4.6 row—an A.6.1 application/result binding or independently obtaining WorkResultRelation, A.15.PROD production branch, A.3.4 change, evaluation result, subject-specific delivery/transfer relation, or acceptance relation. An absent row stays absent.

    • Evidence: for a current evidence-use claim, name the supporting episteme, target claim and conditions required by its direct rule; use A.2.4 for first-use classification. Make the grounds required by any receiving reliance recoverable. Use A.10 when source recovery, provenance, currentness or bounded reliance must remain replayable; identify carriers and observation conditions when they affect the claim or its use.

Decide what the commission has settled. Start with the decision someone needs to make. A buyer may be deciding whether to close an order. A supplier may need to know whether a correction is still due. Work from the request, the terms that took effect and the available records. If a counteroffer changed the deliverable, establish whether and when the parties adopted it. An unanswered request can be all that happened.

For each condition on the next action, find what establishes it. For an owed action or result, identify who undertook to do or supply what for whom. Ask whether the same acceptable result could be produced another way and whether anyone is owed that particular performance in its own right. A supplier may commission an expert opinion to prepare its response. The customer may require the opinion as a condition of acceptance, or may have ordered the consultation itself. Look for the term or accepted change establishing each connection. A completed check may enable a later decision by the customer. It settles acceptance itself only if the agreement gives it that effect. Trace any promises between supplier and expert on their own terms. The supplier's need for the opinion can coexist with either customer arrangement. When the composition of the performed Work matters, B.1.5.EW:4.2 distinguishes a constituent action from work that supplies a result used by another. Follow each undertaking only as far as the receiving decision requires.

Establish what counts as delivery and what counts as acceptance. Producing an item, declaring it ready, delivering it, a user learning of it, and a party accepting it can happen at different times. One notice can declare completion in one undertaking and supply the entire deliverable in another. An earlier decision can settle today's inquiry when it covers the result, recipient and conditions now at issue. If the order calls for a fresh decision, establish that it took place. If the order makes receipt at an agreed repository sufficient for acceptance, a receipt identifying the required item and deposit can settle both delivery and acceptance. An order can make acceptance effective on deposit while allowing later objections. Acceptance then holds from deposit and the right to object continues for the stated period. If acceptance instead takes effect at the end of the period unless someone objects, establish that the period elapsed and that no qualifying objection was made. An earlier decision can settle acceptance if the terms also authorise that route.

Determine how the applicable rule combines the contributions. An authorised representative can accept for several recipients. A board's rule may require a quorum and a specified number of votes in favour. A clerk can record the decision the board reached. An order can instead require distinct assents, compatible parts, or a separate delivery to each recipient. Establish the scope of the mandate, the relevant acts and the connection between them that the rule requires. The records may cover different parts or editions when the rule recognises the correspondence. For a conclusion about a class of orders, show why the rule and the combination apply throughout that class, and which facts each order must supply.

Apply the terms to the facts that can be established. If every history consistent with the terms and evidence gives the same answer, and at least one such history is possible, give that answer. If records conflict, check which record governs or whether independent grounds settle the decision. When the conflict remains unresolved and the other grounds do not suffice, leave that conclusion open. If different histories would give different answers, or the conflict prevents a conclusion, identify the fact needed, where to obtain it and when the recipient needs it. A recorded refusal or a missed binding deadline can rule out one route to acceptance. A negative conclusion for the whole order requires grounds covering every route the agreement allows for the date in question. A missing receipt can leave delivery open. An adverse assessment can itself complete an order for an assessment. Determine separately whether correction, payment or further service is due under the corresponding undertaking.

For example, an archive orders a finding aid for two reading rooms. Its acceptance rule requires each room to approve the entries retained for it and both sets to use the same index. The east room accepts its entries in draft 6. The west room accepts its entries in draft 7. Either approval can establish a local decision. Both can establish acceptance of the combined aid if the retained entries are the approved ones and the two sets use the same index, as the order requires. An edit to the index that breaks this condition defeats that combination. If the order instead delegates acceptance of the entire aid to the head archivist, that officer's qualifying decision suffices. The same two room approvals then answer a different question.


Last Updated: 2026-11-22 — upstream FPF commit 7a93d8f8 (github.com/ailev/FPF)