CC-B1.5-1 | The candidate whole and every claimed Method part are independently identified as exact U.Method values under A.3.1 before B.1.5 tests the composite-method qualification. |
CC-B1.5-2 | Step wording, description nodes, plan items, Work occurrences, file modules, graph edges, registries, source wording, mechanism material, formal substrates, mathematical lenses, and evidence or publication-use claims are not Method parts by position or label. Keep each with its direct governor unless it is independently identified as an exact U.Method and methodPartOf separately obtains. |
CC-B1.5-3 | Every methodPartOf(partMethod, wholeMethod) occurrence passes the required-contribution or admitted-alternative test. Its ordered-pair identity is exact; all bounded alternatives may obtain simultaneously, Work selection does not toggle them, and a changed admitted-part set reidentifies the whole Method or leaves the claim open. One part Method may have several whole Methods only through separately supported pairs and separately qualified whole constructions; no unique parent or closure property follows. |
CC-B1.5-4 | Every serial, parallel, guarded, iterative, fallback, adapter, substitution, or typed-join use states a concrete decidable claim and selects A.6.RCD’s lightest sufficient disposition. A relation kind and occurrence are required only after independent admission for a named occurrence-semantics use. |
CC-B1.5-5 | The already identified candidate Method states whole-level participant meanings, applicability, preconditions, intended effects or preserved conditions, invariants, bounds, accepted inputs and outputs, failure and stop conditions, interface decisions, and reidentification rule before its composite qualification is accepted. |
CC-B1.5-6 | Exposed, forwarded, and encapsulated interactions are distinguished because changing the reusable action or admissible boundary changes Method identity. A named caller system, planner system, auditor, substituting-method selection use, or assurance use determines whether the boundary account must be explicit or published; reliance does not create its identity effect. |
CC-B1.5-7 | Exact U.MethodDescription edition, independently identified boundary-account form and U.PresentationCarrier, bounded-use- and audience-declaration epistemes, separate publication Work, five-participant EpistemePublicationRelation occurrence, raw audience, and designation content remain distinct. PublicationFormExpressionRelation and PublicationFormBearingRelation state the supporting links; a system performs the Work, while the publication occurrence makes the edition available. |
CC-B1.5-8 | A load-bearing A.22 selection names the selecting system, selection Method, dated Work and bindings, any persisted result episteme, and the structure’s exact constituents, independently admitted obtaining relation occurrences, constraints, and use frame. A one-off hypothetical comparison asserts no selected U.Structure. |
CC-B1.5-9 | When the composite method needs a separate higher-level reidentification or emergence explanation, use B.2 in addition to the explicit B.1.5 method reidentification rule. |
CC-B1.5-10 | A temporal slice, episode, event-log segment, telemetry interval, engine stroke, detector component, or U.WorkPlan item is neither a Work part nor a Method part by appearance. Keep each with its subject pattern. A genuine Work part enacts a submethod only through a separate exact A.15.1 enactsMethod occurrence; whole Work may enact the whole Method without mirrored Work parts. |
CC-B1.5-11 | A receiving use that needs order aggregation names B.1.4’s exact ordered relation designations, OrderSpec, and join or independence conditions; the aggregation record or notation does not enter method identity or make relations obtain. |
CC-B1.5-12 | Typed joins name the upstream intended-result meaning and downstream precondition, plus an adapter or governed correspondence when those meanings differ, and a failure route; signatures do not establish the holder’s actual ability. |
CC-B1.5-13 | Dated Work, performing Systems, separately declared assignment species, actual assignment occurrences, obtaining F.6 attributions, resource use and costs, yields, dissipation, telemetry, results, and production, together with separate evidence-, publication-use-, evaluation-, delivery-, and acceptance claims, use their subject patterns and do not become Method identity fields. |
CC-B1.5-14 | Assurance hooks name cutsets, fragile joins, adapter points, CL-sensitive mappings, and the exact envelope or claim scope consumed by B.3; no performance or quality claim follows from composition alone. |
CC-B1.5-15 | A direct method-composition claim establishes no A.14 structural-component relation, work-part relation, or selected-structure identity unless the corresponding direct predicate separately obtains. |
CC-B1.5-16 | Method parts, Work parts, common referents, method order, and temporal adjacency establish neither transformation parthood nor a composite transformation; missing transformation-composition governance returns missing-governor[transformation-composition] for the proposed whole and independently identified changes, without an atomism inference. |
CC-B1.5-17 | A first–then or vertical account receives both checks: preserve every real continuation condition as order or unfolding, and test whether several Methods contribute during the same bounded Work situation without one total sequence. Source order creates no level; simultaneous use creates no Method part, composite Method, Work part, or level. |