E.11:5.9 - An API or contract sentence mixes several kinds of claim

A reader says, “The API or contract-language description says X.” First distinguish recognizing the encountered description from unpacking what its sentence claims. A description can mix an admissibility gate, duty, evidence claim, action invitation and access note; its familiar label does not settle any of them.

If the unresolved question is “what description is this?”, open A.6.RSIG. When recognition is sufficient and the sentence mixes boundary claims, open the Solution of A.6.B or A.6.C to recover atomic L/A/D/E-classified claims under A.6. Use A.6.P if relation wording hides participants or predicate, C.16.Q if quality wording hides its characteristic and scale, and A.6.A if an action invitation is the actual subject.

An already accepted engineering account may instead need reader-facing publication under E.17; E.17.0 answers view recognition, and E.24.PUB answers publication occurrence, form or carrier. Stop when the direct boundary-claim body is opened or the Claim Register or atomic claim set is ready for the next governing use. Return to description recognition if its defining episteme is still unclear. One API sentence supplies neither a complete Contract Bundle nor proof of downstream effect, performed action, quality or evidence.