Jump to text
On this page
Copy and source
Published source confirmed at last check

Source changed 2026-11-18 21:11:39 UTC · snapshot created 2026-11-18 21:12:35 UTC · last check 2026-11-18 22:20:20 UTC

A.6:4.4 - Recover the separate claims in contract wording

When “the API contract” leaves a consequential ambiguity, use A.6.C to ask only the live questions: what was promised, what was said or instituted, what governance position obtains, and what happened. Use A.15.1:4.6 to separate any dated Work from the result, production, delivery/transfer, evidence, or acceptance claims made. Clear wording, including a semantic guarantee or recoverable ordinary metonymy, needs no unpacking record.

  • Promise content (promise content; U.PromiseContent, A.2.3): what is promised to be made available to eligible consumers — a promise, not execution (U.Work).
  • Utterance and publication: identify what is stated and published in the boundary descriptions or faces. Identify any actual speech-act Work under A.2.9 when that occurrence or its instituting effect is claimed; publication alone does not establish such an act.
  • Commitment (individual deontic relation; U.Commitment, A.2.8): whether one actual admitted System or other party is obligated, recommended-as-duty, or prohibited from doing something under an exact constitutive rule and required instituting basis. A system-role kind or assignment may help satisfy that rule’s applicability conditions; neither is the duty bearer or the commitment relation. A commitment does not establish responsibility, which needs its own direct domain predicate or a missing-governor result.
  • Permission-looking claim: do not make Permission a bundle part or quadrant. Select one A6-AW-* row for each atomic claim and cite its direct object.
  • Performed Work (A.15.1): identify the dated occurrence, performer, Method, time and containing System using the conditions in 4.1. Precise assignment-bound attribution is the separate F.6 claim when needed; its absence or failure does not revoke the Work.
  • Result or consequence (A.15.1:4.6 dispatch): only when current, name the exact A.6.1 application/result binding or subject-specific WorkResultRelation, A.15.PROD production branch, A.3.4 change, evaluation result, delivery/transfer relation, or acceptance relation.
  • Evidence (A.10): only when a receiving use relies on one of those claims, name the claim-bound evidence path and carrier.

In A.6 terms:

  • The signature supplies the boundary’s declared vocabulary, laws and applicability; it is not itself a promiser or obligor (A.7).
  • Deontic claims use A.2.8 for generic prescriptions or separately obtaining individual duties and commitments, and A6-AW-NORM-GRANT for the current norm/grant branch. Other permission-looking claims keep the placement and object named by their selected row.
  • Classify each atomic operational “guarantee” claim as L (truth-conditional law), A (entry predicate), D (generic prescription, individual commitment, or current grant), or E (actual exercise, evaluated result, work effect, or measured property with evidence).

Optional-object example. SVC-DEPLOY-1 states promise content. Admitted system ReleaseManager-4 performs SA-4711 : U.SpeechAct under ReleaseManager-4@ReleaseShift; the exact policy may institute COM-4711 : U.Commitment or PER-4711 : GrantedPermissionRelation@Context. Later admitted system Operator-7 performs DeployRun-4711 : U.Work under its covering assignment.

If the application returns ReleaseArtifact-4711, cite the exact A.6.1 result binding or an already governed WorkResultRelation; if that artifact is delivered, cite a separately obtaining transfer relation defined by its subject pattern; if acceptance is claimed, cite the criterion, evaluation result, and acceptance relation; identify dated evaluation Work only when the claim depends on that occurrence.

An A.10 path may support whichever one of those claims is relied on. Omit every absent object: the Work can occur without a result, delivery, acceptance, or evidence-use claim.

Use A.6.C — Contract Unpacking for Boundaries for the expanded account and the same A.15.1:4.6 dispatch.