C.2.1:4.0 - First-use completeness questions
Begin with the three questions that identify the episteme. They are identity questions, not fields to fill.
| Always ask | Exact object recovered |
|---|---|
| What is being claimed? | the exact claim content carried by one U.ClaimGraph |
| What exact entity do those claims concern? | one identified U.Entity participating as the EntityOfConcern |
| Under which designation and interpretation rules are the claims read, and, where the claims use them, which measurement, comparison, or evaluation rules apply? | the effective U.ReferenceScheme |
If the task needs only the episteme’s identity, stop after the three answers. Otherwise state the concrete receiving use. Ask for an unresolved uncertainty or choice only when that use is a real inquiry or decision.
Open a row below only when its first column names the reader’s next sentence or action. Each positive answer adds an independently governed object or direct relation; none adds another slot or identity discriminator to the episteme.
| Open this row when the next sentence or action is… | Recover | Subject pattern |
|---|---|---|
| A claim or relation must cite the exact constitution occurrence, not merely say that the episteme exists. | one exact obtaining EpistemeConstitutionRelation occurrence, reidentified by the participant triple; designate it when an epistemic receiver needs a reference, or use the occurrence itself as a participant when another direct relation is the receiver | C.2.1:4.2.3 and A.6.REL |
| A reader must cite one exact claim inside one exact episteme edition, rather than the whole episteme. | one ClaimAddress: an exact episteme-edition reference plus an intrinsic claim identity declared by that edition’s exact ClaimGraph; if no such identity resolves uniquely, cite the whole episteme or identify the claim as a separate episteme | C.2.1:4.2.5 |
| An observer must inspect designated empirical claims against current observation, intervention, measurement, or test relations involving one exact holon. | one exact EpistemeEmpiricalGroundingRelation occurrence, its covered claim subgraph, claim-to-world mappings, and grounding holon; recover supporting evaluation or evidence use separately | C.2.1:4.3 and the direct observation, intervention, measurement, test, evaluation, or evidence pattern |
| A description must state the concern from which this episteme is read. | one exact U.Viewpoint episteme P and the named describing use that selects P; keep the episteme, its EntityOfConcern, the use, and P distinct | E.10.D2 and E.17.0 |
| A team will validate a Description as a specification before relying on it. | the exact Description episteme, checkable claims, and named harness or validation relation; preserve or update the named describing-use viewpoint only when that selection affects reliance | E.10.D2 and C.2.1:6 |
A classification assertion must say that this episteme conforms to a viewpoint and is a U.View. | one exact obtaining EpistemeViewpointConformanceRelation between this episteme and at least one exact U.Viewpoint episteme | E.17.0 |
| A reader must trace how this episteme was constructed from an earlier source episteme. | the exact source and receiving epistemes plus the governed viewing relation; view membership remains a separate conformance judgment | A.6.3 for construction and E.17.0 for membership |
| A claim must be restricted to one declared part of the situation under study. | one exact U.ClaimScope and its membership relation over U.ContextSlice | A.2.6 |
| A calculation or interpretation must use one selected organization of model use. | one exact BoundedModelUseStructure and the relation through which the receiving assertion or use selects it | A.1.1 and the direct receiving-use pattern |
| A reader proposes to compare, substitute, translate, publish, or otherwise use an obtaining cross-context Bridge. | one ordinary C.2.1 assertion episteme whose EntityOfConcern is that exact Bridge and whose ClaimGraph states the proposed use, direction, correspondence rule, loss tolerance, and polarity; recover reliance and any use that actually happened separately | C.2.1:4.2.3 for claim identity; F.9 for the Bridge; A.10 for ordinary evidence reliance; B.3 only when an actual named assurance claim is current; the direct receiver pattern for any actual use |
| A decision or inference must cite support links among the claims. | the exact JustificationGraph content that carries those dependencies | C.2.1:4.4; use A.10 only when ordinary evidence reliance is current, and B.3 only when an actual named assurance claim is current |
| A decision or evaluation will accept, reject, or withhold reliance because of evidence. | the exact evidence-use relation; evidence storage alone is insufficient | A.10 for ordinary evidence reliance; B.3 only for an actual named assurance claim |
| Reviewers must inspect or revise a classification judgment as an independent claim-bearing object. | one classification assertion episteme about the exact candidate, plus the exact governing criterion | C.2.1:4.2.3 with A.1 or C.3.2; E.24.UK only for public U-kind admission |
| A reader must assert that a later episteme revises, refines, or supersedes an earlier one. | one exact EpistemeEditionRelation occurrence | C.2.1:4.5 |
| An account must assert that particular Work occurred. | identify the actual performer and admit the dated Work independently; if the account also attributes it to an assignment, test that attribution separately | A.13 and A.15.1; F.6 only for the stated attribution |
| A publisher must make one selected episteme edition available to a declared audience for a bounded use. | the publication occurrence, publication form, and U.PresentationCarrier as distinct objects | E.17 and E.24.PUB |
| A user will calculate, infer, navigate, or inspect through a representation whose available operations matter. | the representation scheme, operations and correspondence needed for that use | the applicable representation pattern; A.6.3.RT for a same-EntityOfConcern transition; C.29 only for an unresolved mathematical-lens choice, transfer or reliance question |
| One receiving System must select, decline, or co-use candidate results of different kinds as representations for the same exact action or decision. | one C.37 use-bounded representation-selection account; keep each direct subject result, optional A.2.4 first-use classification, A.10 reliance path when material, and receiving result separately governed | C.37 |
Stop when no row describes the next sentence or action. A readable sentence naming the claims, EntityOfConcern, and effective reference scheme is then enough. Do not complete the table as a record. Use section 4.10 only when a later sentence or action actually needs the full relation and neighboring-object reference.