A.6.C — Contract Unpacking for Boundaries
Type: Architectural (A) Status: Stable Normativity: Normative (unless marked informative) Placement: Part A → A.6 Signature Stack & Boundary Discipline Builds on: A.6 (stack + classification intent), A.6.B (L/A/D/E), A.6.P:4.11a (service/access subject-pattern recovery), A.7 (EntityOfConcern, Description episteme, and carrier separation), A.2.3 (
U.PromiseContent), A.2.8 (U.Commitment), A.2.8.PER (strong/weak permission, exercise, and conflict), A.2.9 (U.SpeechAct), A.15.1 (U.Work), A.10 and B.3 (evidence and assurance use), E.10 (L-SERVandLEX-BUNDLE), E.17 (MVPK “no new semantics” faces), F.12 (service acceptance and evidence discipline) Naming boundary: F.18 may provide durable names for recovered terms when naming is current; it does not define or constrain the promise-content, speech-act, commitment, permission, work, evidence, or boundary ontology. Vocabulary boundary: “Contract”, “SLA” and “guarantee” are Plain-level source cues. The four questions unpack their meaning without defining a newContractkind. Purpose (one line): Resolve consequential ambiguity in boundary contract language through the applicable four questions and atomic claims; use the A.6.B Claim Register only when the receiving use needs a record under §4.5.
Use this when. Use A.6.C when words such as contract, promise, guarantee, SLA, or interface agreement leave a consequential ambiguity about what was promised, instituted, governed, performed, produced, delivered, accepted, or evidenced.
First useful move. Rewrite the live passage so each assertion identifies its subject, predicate, operands, and governing source; apply only the questions that the passage makes live.
What changes in practice. Familiar contract language can remain in Plain prose while technical and normative claims become classifiable under A.6.B and adjudicable through their direct sources.
Ordinary non-use boundary. Clear local contract wording with no consequential ambiguity needs no unpacking record. A one-off repair may end in the repaired atomic prose; create or extend the Claim Register only when stable reuse, decision, audit, dispute, or cross-face projection needs it.
A.6.C:1 — Problem frame
Boundary descriptions frequently use “contract” as shorthand for “the thing that governs the interaction”. That shorthand collapses four practical questions and the separately governed objects needed to answer them:
- What was promised? — the promise content, if any,
- What was said, published, or instituted? — the speech-act Work, descriptions, publication occurrences/forms/carriers, and any separately governed institutional effect,
- What governance or permission-looking claim exists? — the one atomic norm, grant, gate, exercise, evaluation, conflict, or source claim selected by its job,
- What happened, what followed, and what supports reliance? — dated Work, each separate result or delivery claim, and each evidence claim.
When these questions are answered with one undifferentiated object or row, authors can conflate a semantic guarantee with an undertaking, attribute a dated act to its description instead of its performer, encode runtime gates as if they were internal laws, or treat observability as a property of text rather than of carriers and work. A.6 and A.6.B already provide an L/A/D/E claim-classification discipline for boundary claims, but “contract” language remains a recurring entry point for category mistakes.
Service-cluster note (modularity + lexicon). When contract wording appears alongside service, service provider, server, SLA, SLO, or service-level and a relied-on boundary use hides a concrete subject or relation, recover that hidden choice through A.6.P:4.11a while asking the four questions below. Mere co-occurrence does not trigger recovery, and clear, quoted, historical, illustrative, or harmless ordinary wording remains usable. U.PromiseContent is written as promise content, never as bare “service”.
A.6.C makes contract-language usable inside the A.6 stack by providing a canonical unpacking that can be applied to APIs, hardware interfaces, protocols, and socio-technical boundaries.
Non‑goals (to preserve modularity). A.6.C does not:
- define “legal contract” doctrine (offer, acceptance, consideration, jurisdictional enforceability, etc.);
- resolve conflicts across scales or contexts: keep the current grant or prohibition as its own D claim, classify the conflict finding as E through A.6
A6-AW-CONFLICT, and use the mediation predicate and assertion only when mediation is current; - redefine the core meanings of
U.PromiseContent,U.Work,U.SpeechAct,U.Commitment, or theA.2.8.PERresults—it only makes “contract talk” classifiable into those objects or claims. - redefine quadrant semantics (
L/A/D/E) or cross‑quadrant reference rules; those are defined normatively in A.6.B.
A.6.C:2 — Problem
How can an author write (or repair) contract-language so that:
- Act and commitment claims name compatible participants, without mistaking an interface description for the actual interface or its bearer,
- Governance claims are distinguishable from permission-looking gate, exercise, evaluation, conflict, and source claims by the job of each atomic statement rather than by A.2.8.PER membership,
- Operational “guarantees” become adjudicable by recovering the claim, the facts its predicate requires, and the grounds for any receiving reliance; the answer may be a supported result or an unresolved claim with its missing basis,
- Multi-view publication (MVPK faces) does not create a parallel contract object or another canonical claim set by paraphrase drift?
A.6.C:3 — Forces
| Force | Tension |
|---|---|
| Conversational convenience | People will keep saying “contract”; banning the term is unrealistic. |
| Ontological correctness | Familiar contract wording can hide whether a guarantee is semantic, a prescription, an undertaking, or an observed result. |
| Boundary diversity | Software APIs, hardware connectors, protocols, and SLAs share the “contract” word but differ in what is adjudicated and how. |
| Multi-view publication | Faces support audience fit when projection is needed; rephrasing can change the claim. |
| Adjudicability | When “guarantee” or authority wording leaves a consequential ambiguity, recover the semantic truth, generic prescription, individual commitment or current grant, entry predicate, or observed/evaluated claim needed by the receiving use. |
| Minimality | The unpacking should be lightweight enough to apply during routine authoring and review. |
A.6.C:4 — Solution
Use the four questions to recover the claims made, then classify them through A.6.B. The answers connect the promised content, any actual institution, the applicable conditions and the observed result only where the passage asserts those relations.
A.6.C:4.1 — Four questions for contract-like boundary wording
When “contract”, “guarantee”, “promise”, “SLA”, or “interface agreement” leaves a consequential ambiguity, ask only the live questions below. 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.
-
What was promised?
- The promised value or effect (the promise content) in the intended scope.
- In FPF terms (A.2.3),
U.PromiseContentis promise content, distinct from an execution event or an obtaining individual commitment. - Prose head rule (normative). When referring to
U.PromiseContentin 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 anyA-*andE-*references needed by that claim.
-
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.Workoccurrence. 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.CommitmentorGrantedPermissionRelation@Contextoccurrence 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/Approvewording, a document, carrier, or completed-looking record alone.
-
-
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. OnlyA6-AW-NORM-GRANTenters D. WithinA6-AW-GATE, an admission predicate for a named action or application enters A and an actual A.21GateDecisionResultenters 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.Commitmentoccurrence and the separate D-claim orCommitmentAssertionabout it; - select exactly one actual bearer branch: an admitted
U.Systemor 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.
- identify one
-
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.Commitmentis the separately obtaining relation described by that statement (A.7 and A.2.8).
-
-
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.6row—an A.6.1 application/result binding or independently obtainingWorkResultRelation, 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.
-
A.6.C:4.2 — Classification recipe into A.6.B (L/A/D/E)
After unpacking, classify each atomic statement using the Boundary Norm Square as defined normatively in A.6.B (quadrant semantics + form constraints + cross‑quadrant reference discipline). A.6.C does not redefine L/A/D/E; it applies them to contract-language as follows:
- Promise content and conditions → classify by the claim.
- Put meanings, invariants, and metric definitions for what is promised in L (
L-*in signature laws and definitions). - Recover what “eligible”, “covered” or “valid iff” means. A definition or declared scope remains L; an admission predicate for a named action or application is A; a finding that a particular case meets the conditions is E. A duty concerning those conditions is a separate D claim.
- Put meanings, invariants, and metric definitions for what is promised in L (
- Governance and permission-looking claims → claim-specific quadrant.
- Put a generic contract, SLA, protocol, or policy prescription in D as a claim about its normative source and applicable rule content. Put an individual-duty claim in D only when it cites a separately obtaining
U.Commitmentunder A.2.8; do not use a completed record as the relation. - For authority-looking wording, select one A.6
A6-AW-*row: norm/grant → D, admission predicate → A, and an actual A.21GateDecisionResult, exercise, evaluated finding/conflict, or source observation → E. Split a predicate and an actual gate result into separate atomic claims. Cite the A.2.8.PER object only where that row requires it; the selected subject pattern or kind of direct object does not choose the sentence’s quadrant. - If a generic prescription or individual duty requires satisfying or enforcing a gate, its
D-*claim MUST reference the relevantA-*claim by ID or canonical location (D→A). - If reliance on either D branch needs evidence, cite the relevant
E-*claim or evidence-use relation (D→E); for the individual branch, aCommitmentAssertionmay carry that reference.
- Put a generic contract, SLA, protocol, or policy prescription in D as a claim about its normative source and applicable rule content. Put an individual-duty claim in D only when it cites a separately obtaining
- Performed Work → E (did it happen?).
- Name the A.15.1 Work occurrence and its performer, Method, extent, and containing System. Add an assignment reference and F.6 only when the claim or a receiving use consumes precise assignment-bound attribution; do not add an output or delivery field.
- Result or consequence → E when current (what else happened?).
- Use the one applicable
A.15.1:4.6predicate and subject assertion for the returned value, production, change, evaluation result, delivery/transfer, or acceptance claim; cite the pattern that defines or constrains that claim.
- Use the one applicable
- Evidence → E when relied on (how can the claim be used?).
- State the target claim and the independently established evidence-use or other direct support relation, including its polarity and limits. Use A.2.4 for first-use classification and A.10 when a replayable source-to-use account is needed. Keep the grounds required by the receiving use; identify carriers and observation conditions when they affect that claim or use.
Keyword placement rule (canonical claim set).
Within the canonical L-, A-, D- or E-classified claim set, BCP-14 keywords are statement operators. Classify the claim through A.6.B: a generic prescription or an independently instituted duty, recommendation-as-duty or prohibition enters D. When MAY, OPTIONAL or authority-looking wording is ambiguous, use the A.6 A6-AW-* branch. If its object or meaning remains unresolved, retain it as bounded source wording with that uncertainty; marking it informative does not settle the claim.
A.6.C:4.3 — “Guarantee” disambiguation
When “guarantee” leaves a consequential ambiguity, use the applicable distinction below:
- Semantic guarantee → L (“by definition or invariant”).
- Admission guarantee → A (“this action or application is admissible iff …”).
- Governance guarantee → D (“provider commits or implementer must”).
- Operational claim → E (an actual occurrence, condition or result under its subject predicate). Name Work, evaluation or observation when the claim depends on it. Retain an unresolved claim when required grounds are missing; report a negative result only when the grounds establish it. Qualify evidence support for the receiving use under §4.1, question 4.
If none fits, recover the remaining meaning before classifying it. Mark an aspiration as such only when that is what the source expresses; otherwise keep the unresolved wording and the missing meaning visible.
A.6.C:4.4 — MVPK faces are not second contracts
The atomic claims for one boundary use have one canonical source; use the A.6.B Claim Register when §4.5 calls for it. Publication faces present those claims for a bounded reader and use under E.17:
- Faces may select, summarize, and render claims for audiences. A selected episteme’s
U.Viewmembership separately requires E.17.0 conformance to a viewpoint. - Faces must not add a new boundary claim; they project the existing classified claims.
- Any face-level decision-relevant or normative-looking statement SHOULD cite the underlying claim ID(s) or canonical location(s). A new boundary claim MUST be added to its canonical source before publication on a face. Informative commentary may explain source claims without adding boundary semantics.
Keyword rule (faces).
Each face sentence containing a BCP-14 keyword MUST cite its existing classified claim ID or canonical location and direct object. Duty/recommendation/prohibition and current-grant projections cite their D claim; a gate projection cites its A claim; exercise or evaluated-finding projections cite their E claim. Use the selected A.6 A6-AW-* row for permission-looking wording.
A face-level keyword creates no object or quadrant. If the boundary claim is not traceable, put it in its canonical source before publishing it on the face; informative commentary is limited to explanation that adds no boundary semantics. To avoid keyword-evasion, equivalent deontic phrasings (e.g., “is required to…”, “is prohibited from…”) SHOULD follow the same claim-reference discipline even when no BCP-14 keyword is present.
Projection may be paraphrased for audience fit, but it MUST NOT change the deontic or semantic claim; if exactness is critical or disputed, use verbatim.
A.6.C:4.5 — A.6.B Claim Register additions (recommended)
When stable reuse, decision, audit, dispute, or cross-face projection needs a record, use the A.6.B Claim Register (IDs, statements, quadrant, and canonical location). A one-off local repair ends with the repaired atomic prose. When the register is needed, add only the current A.6.C fields below without creating another record or ontology kind:
-
bundleId(optional local ID grouping atomic claims discussed together) -
questionRef(optional pointerQ1,Q2,Q3, orQ4to the four questions above; it selects no kind, subject predicate, or quadrant) -
directObjectDesignation: useU.RelationRefconstrained to the relation family for a relation occurrence, the applicableU.EpistemeReffor a whole episteme, or the admitted reference kind for another independently identified entity.When one claim inside an episteme is the direct object, use
C.2.1 ClaimAddress: episteme-edition reference plus intrinsic claim identity declared by that edition’s ClaimGraph.The entity-reference branches designate independently identified objects; the claim branch designates content inside the named edition. Neither carries the designated content.
-
directObjectPatternLocator(the pattern-description locator for the ClaimGraph that defines or constrains that direct object; it asserts no ownership relation) -
faceRefs(optional mapping fromPlainView,TechCard,InteropCard, orAssuranceLaneto where this same claim is rendered)
Each row uses the A.6.B fields for one statement, claim ID, quadrant, and canonical location. Do not create a second boundary-language record or a Permission, Utterance, WorkEvidence, or result-or-evidence umbrella kind.
A.6.C:5 — Archetypal Grounding (Tell–Show–Show)
A.6.C:5.1 — Tell
When boundary contract-language leaves a consequential ambiguity, recover the claim and referent, then answer only the live questions below. Keep ordinary metonymy when its capable participant and relation are locally recoverable; a literal act or individual commitment needs that participant and the governing conditions.
- What was promised? State the promise-content claim if one exists.
- What was said, published, or instituted? Identify only the asserted speech act, description/publication objects and institutional effects, under the conditions in §4.1.
- What governance or permission-looking claim exists? State either a generic D prescription with its normative source and applicability, an individual D claim about an obtaining commitment with its actual bearer and institution basis, or the selected
A6-AW-*claim in its own quadrant. State responsibility separately under its admitted domain predicate or return its missing governor. - What happened, what followed, and what supports reliance? State dated Work, each current result/change/delivery/acceptance claim, and each current evidence-use or reliance claim separately; omit absent claims.
When those answers need stable reuse, decision, audit, dispute, or cross-face projection, write them in the one A.6.B Claim Register: one atomic statement, direct object, subject assertion, non-semantic pattern locator, and quadrant per row. Otherwise stop with the repaired atomic prose. Faces cite reused claim IDs or canonical locations; they do not create another bundle record.
A.6.C:5.2 — Show (System archetypes)
(A) Software API boundary
Draft wording:
“The Payments API guarantees idempotency. Clients must provide Idempotency-Key. We log all requests. Availability is 99.9%.”
Source clauses and additional illustrative premises:
Preserve “We log all requests”; the draft supplies no particular logging Work or observation basis. “Availability is 99.9%” does not say whether 99.9% is a target, a promised bound, or an observed value; that meaning remains unresolved.
For the extended case below, assume the PaymentsAPI description/publication, definitions of idempotency and key uniqueness, a gate policy with an additional key-validity condition, and a generic provider-side idempotency prescription. These are additional case premises, not atoms recovered from the draft. The source’s client requirement remains to provide Idempotency-Key.
-
Description/publication: signature or mechanism publication for
PaymentsAPI(MVPK faces: TechCard, InteropCard). -
L: define idempotency and the uniqueness semantics of
Idempotency-Key. (“Idempotent” is a semantic property, not a duty.) -
A: admissibility predicate: request is admissible iff
Idempotency-Keyis present and valid. (Gate belongs to mechanism.) -
D: the API policy generically requires covered clients to provide
Idempotency-Key. In this extended case it also states a provider-side idempotency prescription. No individual commitment follows from those clauses alone. If the case claims thatClientIntegrator-AorProviderSystem-Abears one of those duties, cite that bearer’s separately instituted A.2.8 commitment. (Responsibility, if claimed, needs its own direct relation.) -
E — additional hypothetical evaluation: suppose admitted system
PaymentsAvailabilityEvaluator-AperformedAvailabilityEvaluation-Payments-T1 : U.Workover the Payments API request population and windowTusing the availability metric stipulated for this evaluation.A.6.1 application
PaymentsAvailabilityApplication-T1has result bindingavailabilityResult -> AvailabilityResult-Payments-T1; that C.2.1 result episteme statesobservedAvailability=99.9%forT.When the SLA decision relies on this result, an A.10 path links it to the request-log and measurement carriers used. This hypothetical observation does not select the meaning of the draft’s unlabeled 99.9%.
(B) Hardware interface boundary
Draft wording: “The connector guarantees safe operation. Devices must not exceed 20V. Negotiation must succeed before power is applied.”
Source requirements and additional illustrative premises:
The draft leaves open whether “Devices must not exceed 20V” is a device-behavior constraint or an obligation on a capable bearer, and it does not identify the safe-operation predicate. Preserve the 20V upper bound and the requirement that negotiation succeed before power is applied. The additional gate and test below do not resolve the bearer or safety choices.
-
Description/publication — additional case premise: assume a published interface spec supplying the pinout, electrical ranges, handshake procedure, and the test declaration used below.
-
L: electrical invariants and allowable ranges are definitions and invariants (truth-conditional).
-
A — additional gate premise: suppose the interface specification makes power delivery admissible only after the handshake state reaches an agreed mode.
-
Requirement awaiting classification: retain “Devices must not exceed 20V”; recover its constraint or duty-bearer reading before assigning it to L or D. The negotiation-before-power requirement remains distinct from the additional gate predicate.
-
E — additional hypothetical test: suppose admitted system
HardwareTestSystem-AperformedConnectorSafetyEvaluation-T1 : U.WorkoverConnector-C1under the declared method, load, and temperature window.A.6.1 application
ConnectorSafetyApplication-T1has result bindingsafetyResult -> ConnectorSafetyResult-T1; that C.2.1 result episteme statesmaximumObservedVoltage=19.8V,handshakeState=agreed-before-power, andConnectorSafetyCriterion-v3=satisfiedfor those conditions.When relied on, an A.10 path links this result to
TestReport-C1-T1,VoltageTrace-C1-T1, andNegotiationLog-C1-T1carriers.In this hypothetical test, 19.8V is below the retained 20V upper bound. The separately given criterion result does not by itself settle the draft’s unspecified safe-operation claim.
(B-PER) Compact permission replay (only when the permission branch is live)
Situation: “ReleaseAuthoritySystem, acting as release grantor under assignment ReleaseGrantor-A, approved DeploymentAgent-A, acting under assignment Operator-A, to deploy Release-4711 after preflight.”
Unpack + classify:
-
Promise content (optional):
SVC-RELEASE-4711states which release artifact eligible consumers are promised. -
Speech-act Work:
ReleaseGrantorAssignmentis a declaredU.SystemRoleAssignmentspecies. OccurrenceReleaseGrantor-Ahas admitted SystemReleaseAuthoritySystemas holder and the local release-grantor kind as assigned-kind value. That System performs datedApproveoccurrenceSA-4711under the assignment.The assignment supplies only the holder and assigned-kind facts used by the policy. Any authority required by
ReleaseGrantPolicymust obtain independently.Under the applicable policy,
SA-4711institutes—not merely publishes—grant occurrencePER-4711only if the A.2.8.PER obtaining conditions hold. -
D — current grant (
A6-AW-NORM-GRANT):ReleaseOperatorAssignmentis another declared species. OccurrenceOperator-Ahas admitted SystemDeploymentAgent-Aas holder and covers this window. The grant’s beneficiary participant cites that occurrence, and its permitted-action participant isU.EpistemeRef(Deploy-Release-4711).This Claim Register row uses
U.RelationRef(PER-4711), constrained toGrantedPermissionRelation@Context, as itsdirectObjectDesignation.SA-4711, the two assignments, policy, context, scope, and window remain grounds or qualifiers.The model may use this D claim only while the A.2.8.PER conditions make
PER-4711obtain and the row cites the named occurrence, act, and policy. -
E — weak evaluation alternative (
A6-AW-WEAK): if the basis establishes only current absence of prohibition in a sufficiently complete frame, recordNonProhibitionFinding@Context; do not promote it to a strong grant or place it in D. -
A — independent entry predicate (
A6-AW-GATE): “deployment is admissible iffPER-4711currently obtains and preflight is green” is anA-*predicate. It may consume the grant as one condition but is neither the grant nor proof of gate passage. If an actual gate decision is also asserted, record its A.21GateDecisionResult, bounded action, applicable profile application, complete required check-application result set, decision value, and consequence as a separate E claim. -
E — actual Work and exercise (
A6-AW-EXERCISE): A.13 first recovers admitted SystemDeploymentAgent-Aas the performer through obtaining assignment occurrenceOperator-Aof declared speciesReleaseOperatorAssignment; A.15.1 independently admits datedU.WorkoccurrenceDeployRun-4711. Because this permission-exercise branch expressly consumes precise assignment-bound attribution, F.6 then relates that already admitted Work through the same assignment and checks holder equality and coverage.The Work must instantiate the action specification inside the grant’s scope and window. Only then may
PermissionExerciseRelation@ContextbindWorkRef(DeployRun-4711)toU.RelationRef(PER-4711), constrained toGrantedPermissionRelation@Context. The assignment contributes the beneficiary and attribution facts consumed here.Missing or failed F.6 alone leaves independently admitted Work intact but blocks this attribution-dependent exercise branch. If the same finding questions a premise consumed by A.13 or A.15.1 admission, recheck that premise and its dependent claims. Planned work, the approval wording, and preflight alone are not exercise.
-
E — optional result or delivery: if
DeployRun-4711returnsReleaseArtifact-4711, cite the A.6.1 result binding or an already governed subject-specificWorkResultRelation; if that artifact is transferred, cite the independently obtaining delivery/transfer relation defined by its subject pattern. -
E — evidence (optional): an A.10 path may link the grant, Work, exercise, result, or delivery claim to its current carriers for one bounded reliance use.
A.6.C:5.3 — Show (Episteme archetypes)
(C) Multiparty protocol boundary (behavioural and session-type motif)
Draft wording: “The protocol guarantees progress. Participants must follow the sequence.”
Source clauses and additional illustrative premises:
The progress guarantee needs its semantic or operational meaning. For the illustrative case below, assume the published protocol description and the trace-admissibility criteria; the named trace evaluation is an additional hypothetical case.
-
Description/publication: protocol description (could be a type spec or protocol spec plus explanatory views).
-
L — when the guarantee is semantic: the progress property is a law over the protocol model (truth-conditional, within the theory).
-
A — additional entry-condition premise: suppose a session-entry mechanism uses the declared trace criteria to determine whether an interaction may enter the session. Its entry predicate is A; the trace-validity definition remains L and an actual conformance verdict is E.
-
D: the protocol description generically requires covered participants to follow the stated sequence. It asserts no individual commitment occurrence.
-
E — additional hypothetical trace evaluation, not inferred from the progress guarantee: suppose admitted system
ProtocolConformanceEvaluator-AperformedProtocolConformanceRun-T1 : U.Workover bounded interactionTrace-42.A.6.1 application
ProtocolConformanceApplication-T1has result bindingconformanceResult -> ProtocolConformanceResult-T1; that C.2.1 result episteme statesconformanceVerdict=passandobservedTerminalState=completedunderProtocolConformanceCriterion-v5.For a disputed interaction, an A.10 path links this result to
MessageTrace-42,ConformanceRunRecord-T1, andProtocolAuditRecord-42carriers.
(D) Socio-technical “SLA + audit trail” boundary
Draft wording: “Provider shall respond within 4 hours for Severity‑1 incidents. Only Severity‑1 is covered. Evidence is provided by ticket logs.”
Unpack + classify:
-
Promise content (service promise clause, when present): a responsiveness promise for a defined incident class and window is separate from the SLA’s generic prescription.
-
Description/publication: SLA publication (and its views for different audiences).
-
Scope from the source: the promise covers only Severity-1 incidents. This coverage restriction becomes an A claim only when a separately defined admission rule uses it as an entry or continuation condition for a named action or application.
-
D: the SLA clause generically requires the covered Provider to respond within 4 hours for Severity-1 incidents; only Severity-1 is covered. Claim that actual provider
ProviderSystem-Abears the four-hour duty only after the SLA’s individualizing rule and required actual basis establish one A.2.8 commitment; otherwise keep the clause generic. -
Evidence source clause: the draft names ticket logs as evidence; it supplies no measured response interval.
-
E — additional hypothetical response evaluation: suppose admitted system
SLAEvaluator-AperformedResponseEvaluation-Ticket-17 : U.Workover Severity-1 ticketTicket-17under the declared clock and measurement method.A.6.1 application
ResponseMeasurementApplication-Ticket-17has result bindingresponseIntervalResult -> ResponseIntervalResult-Ticket-17; that C.2.1 result episteme statesobservedResponseInterval=3h42mandwithinFourHourTarget=true.When the SLA decision relies on this result, an A.10 path links it to ticket, response-timestamp, clock-source, and severity-classification carriers. The four-hour requirement is from the source;
3h42mis the additional hypothetical observation.
A.6.C:6 — Bias-Annotation
- Gov bias: prefers explicit accountability and adjudication hooks; increases clarity but adds authoring overhead.
- Arch bias: optimises evolvability by preventing hidden coupling across stack layers.
- Ontological and Epistemic bias: enforces EntityOfConcern, Description episteme, and carrier separation; requires compatible participants for literal agency claims without rejecting recoverable interface metonymy.
- Prag bias: accepts that “contract” is common vocabulary; offers a disciplined rewrite rather than prohibition.
- Did bias: aims to be teachable via repeated unpacking examples across boundary types.
A.6.C:7 — Conformance Checklist
A boundary description conforms to A.6.C iff it satisfies all items below:
-
CC‑A.6.C‑1 (Four questions, atomic answers). When contract-like wording leaves a consequential ambiguity, the text SHALL answer only the applicable four-question branches with atomic claims. Each asserted object and its subject predicate SHALL remain separately recoverable. Classify each claim through A.6.B and identify the defining pattern when its rules govern that claim.
-
CC‑A.6.C‑2 (No agency to epistemes). When a dated act or individual commitment is claimed, the text MUST identify its capable actual participant and MUST NOT substitute an API/interface label, description, publication carrier, kind, or assignment for that participant’s basis. Ordinary metonymy may remain when its participant and relation are locally recoverable.
A generic prescription SHALL name its normative source and applicable content without inventing an individual bearer.
An individual duty or commitment SHALL name its actual bearer and separately obtaining
U.Commitment; an assignment may appear only as an instituting rule’s applicability ground. -
CC‑A.6.C‑3 (Classify contract-language statements via A.6.B). When contract-language leaves a consequential ambiguity, its unpacked statements SHALL be atomic L/A/D/E claims. In that unpacking, permission-looking wording SHALL select one A.6
A6-AW-*row; A.2.8.PER membership alone MUST NOT set the quadrant. -
CC‑A.6.C‑4 (Promise content ≠ Work discipline). A statement about one dated Work SHALL name the A.15.1 occurrence. A result, production, change, delivery/transfer, evidence or acceptance statement SHALL use its own direct object and shall not be inferred merely from Work. Promise-content language remains about
U.PromiseContent. When service or access-like wording occurs in a relied-on boundary claim, recommendation, decision, gate, assurance, publication, or reuse and hides the concrete subject, participant, predicate, kind, permission, Work occurrence, or next subject question, the text SHALL recover that hidden choice through E.10 L-SERV and A.6.P:4.11a, then state the assertion under the recovered predicate with its pattern locator. Quoted, historical, illustrative, and harmless ordinary wording remains outside this recovery rule; an actualU.PromiseContentreferent still uses the head phrase promise content, not bare service. -
CC‑A.6.C‑5 (Evidence hook for operational guarantees). When a “guarantee” expresses an operational claim, the text SHALL state the E claim’s predicate, object, relevant scope or window, and what establishes it or remains missing. Name Work, evaluation or observation when the claim depends on it. If required grounds are missing, retain the claim as unresolved; report a negative result only when the grounds establish it.
For evidence use, the text SHALL keep the grounds required by receiving reliance recoverable under §4.1, question 4; use A.10 when a replayable account is needed and identify carriers or observation conditions when they affect the claim or use.
-
CC‑A.6.C‑6 (No second contracts via faces). MVPK faces MUST NOT add new boundary claims; they publish only the existing canonical L/A/D/E claims under E.17. Informative commentary may explain those claims without adding boundary semantics. An asserted
U.Viewseparately requires E.17.0 conformance. -
CC‑A.6.C‑7 (RFC‑keyword discipline inside faces). Each MVPK face sentence containing a BCP-14 keyword MUST cite its classified claim ID or canonical location, direct object, and selected
A6-AW-*row when permission-looking. Only norm/grant claims cite D; gate claims cite A; exercise and evaluated findings cite E. -
CC‑A.6.C‑8 (Obtaining is not representation). A
PublishorApproveutterance, a document, carrier, or record does not by itself institute or prove aU.CommitmentorGrantedPermissionRelation@Context. The obtaining predicate and cited context policy decide whether the relation obtains.A Claim Register row may assert or support reliance on it only when the row names the occurrence, predicate,
SubjectPatternLocator, participants, scope/window, and current evidence required by that use.For a commitment, the row cites its rule-required actual instituting basis and policy; for a strong grant, it cites the actual instituting speech act and policy. The row alone does not create the relation.
When the grant occurrence is the row’s direct object,
directObjectDesignationSHALL be aU.RelationRefconstrained toGrantedPermissionRelation@Context; an entity reference,ClaimAddress, display label, or arbitrary identifier cannot fill that branch.
A.6.C:8 — Common Anti-Patterns and How to Avoid Them
| Anti-pattern | Why it fails | Repair |
|---|---|---|
| Literal commitment assigned to a description | An interface label does not select a description or an actual bearer; a carrier bears a publication form and is not thereby a description episteme. | Recover the claim and referent. Keep a semantic guarantee or clear policy metonymy. For a literal commitment, name the capable bearer, current policy and separately obtaining U.Commitment; keep any assignment as rule ground. Distinguish description, represented interface/access object, form and carrier only when the claim needs them. |
| Guarantee-without-substrate | The word hides whether the claim is semantic, deontic, an entry condition, or an operational claim such as an actual gate result or an observed or evaluated result | Classify semantic law as L, a generic prescription or claim about an individual commitment or current grant as D, an admission predicate as A, and an actual occurrence, condition or result as E; examples include an A.21 GateDecisionResult and other observed or evaluated results. Use A6-AW-* for permission-looking wording. |
| SLA smuggled into laws | Mixes governance with semantics; breaks substitution reasoning | State the target as a generic D prescription or an individual commitment, reference its L-defined metric and A conditions, and cite the E evaluated result plus A.10 support when current |
| Gate written as obligation | Confuses admissibility predicates with deontic claims | Write the predicate as A; write a generic prescription or separately instituted individual duty as a D→A reference. |
| Work-result-evidence bundle | “The delivered work and its log prove acceptance” makes one phrase carry occurrence, result, transfer, evidence, and verdict | Name the A.15.1 Work first; use the applicable A.15.1:4.6 route for each current result, delivery/transfer, or acceptance claim. Use A.2.4 for first evidence-use classification or the direct rule for a further support claim. Use A.10 when provenance, currentness or bounded reliance must remain replayable, retaining the grounds required by that use. Omit absent claims. |
| Face-level paraphrase drift | A face silently changes a claim’s object or quadrant | Use meaning-preserving face prose and cite the canonical claim ID or location, direct object, and selected A6-AW-* row when applicable. Add a new boundary claim to its canonical source before publishing it on a face. Use verbatim text when exactness is critical or disputed. |
| Cross-scale contract collapse | Commitments, grants, and conflict findings at different scales are treated as one D claim | Keep commitments and current grants as separate D claims; classify the permission conflict finding as E through A6-AW-CONFLICT; use mediation only under its subject pattern |
| Mandatory four-question record | Every clear use of contract wording creates rows for all four questions | Apply A.6.C only to a consequential ambiguity, answer only the live questions, and let a one-off repair end in the repaired atomic prose |
A.6.C:9 — Consequences
Benefits
- Category mistakes become systematically repairable.
- Generic prescriptions remain usable without invented occurrences, while individual commitments remain distinguishable and adjudicable through their actual bearer, rule, instituting basis, scope, validity, and any evidence needed for reliance.
- Boundaries remain evolvable: laws, gates, governance, and evidence can evolve with controlled coupling.
Trade-offs and mitigations
- Additional authoring effort; mitigated by applying the unpacking only when contract-like wording leaves a consequential ambiguity, and by persisting a Claim Register entry only when stable reuse, decision, audit, dispute, or cross-face projection needs it.
- Some stakeholders prefer “one sentence contract”; mitigated by MVPK faces that present curated projections while keeping the underlying claim set coherent.
A.6.C:10 — Rationale
FPF already distinguishes signatures, mechanisms, dated Work, separately identified results or consequences, and evidence use. When contract-language collapses them, the author asks what happened, what separate result or delivery is claimed, and what evidence supports the reliance use.
F.18 may supply durable names for recovered terms, but it does not provide the ontology. A.6.C keeps promise content, speech act, commitment or grant, dated Work, application/result binding, production, change, delivery/transfer, evidence, and acceptance distinct and independently optional. This keeps contract language classifiable under A.6.B without turning A.15.1 into a semantic source of result or delivery.
A.6.C:11 — Source contributions
The following sources contribute distinct disciplines to boundary interpretation.
- BCP 14 (RFC 2119 and RFC 8174) supplies the interpretation of capitalized requirement keywords. A.6.B separately classifies the claim; the visible keyword alone does not establish its object or whether an individual relation obtains.
- Behavioural and session types describe typed interactions, including safety and progress properties. These support the distinction between model properties, admission conditions, implementer obligations and actual trace results.
- Algebraic effects, handlers and effect systems distinguish declared operations from their handling. This is a useful analogy for declaration versus actual application; a result, production, delivery, evidence use or acceptance requires its own relation.
- ISO/IEC/IEEE 42010:2022 viewpoint discipline supplies conventions for descriptions under viewpoints. E.17.0 tests a selected episteme’s
U.Viewconformance, while A.6.3 governs any separately claimed construction. A.6.C keeps the boundary claims traceable across ordinary E.17 publication faces.
A.6.C:12 — Relations
-
Uses and is used by
- Uses A.6.B for L/A/D/E claim classification, atomicity, and cross-quadrant reference discipline.
- Used by A.6 cluster conformance (“contract unpacking”) as the detailed, reusable form of that discipline.
- Complements A.6.S (signature engineering): contract unpacking is a common constructor step when turning prose boundaries into publishable signatures.
- Coordinates with A.6.P families: when “contract or guarantee” wording in a boundary use still leaves a consequential ambiguity after RPR, apply A.6.C to that ambiguity. (A.6.C is not a specialization of A.6.P; A.6.P is relation‑precision, A.6.C is boundary‑contract disambiguation.)
-
Coordinates with
- A.7 (EntityOfConcern, Description episteme, and carrier) for correct placement of evidence claims.
- A.15.1 for the dated Work occurrence and its §4.6 dispatch to application/result, production, change, evaluation, evidence, delivery/transfer, and acceptance patterns.
- F.12 (service acceptance) for structuring how promise-level commitments connect to evidence and acceptance windows.
- E.17 MVPK “no new semantics” rule to prevent publication faces from becoming new contracts.
- A.2.8.PER for the permission-side direct objects; A.6
A6-AW-*and A.6.B classify each atomic claim without treating pattern selection as its quadrant.