C.20:4.3 - State whole-forming claims before choosing notation
Part relations alone do not make one discipline. State the field assembly in ordinary domain language:
- which exact claim-bearing contributions supply the field’s knowledge commitments, distinctions, explanatory resources, or admissible questions;
- which exact methods or other independently governed parts supply reusable ways of investigating, designing, intervening, evaluating, or learning;
- which claims state how knowledge contributions constrain, explain, or qualify practice contributions;
- which claims state why separately governed results of actual practice are relevant to evaluation, revision, or replacement of knowledge contributions;
- how incompatible or rival contributions coexist without being silently equated;
- which boundary, stop conditions, exposed interfaces, and substitution conditions keep the assembly one field-level whole.
Each whole-forming statement stays at the lightest truthful disposition supplied by its direct relation pattern or A.6.RCD: an existing direct predicate, a local compound claim, or a reusable predicate-definition episteme. A readable arrow such as uses, supports, tests, belongs to, standardizes, or aligns does not admit a relation kind and does not make a part relation obtain.
The assembly rule names the exact current part relations, contribution meanings, whole-forming claims, permitted alternatives, incompatibilities, boundary conditions, failure conditions, and substitution conditions. A C.13 Gamma_m.sum construction trace may report those facts when a named use needs an inspectable account. The trace is a C.2.1 episteme and creates none of the parts, relations, assembly, identity, or characteristic.
The historical signature was Γ_disc : ⟨EpistemeCanon, StandardsSet, OrgCarriers, {Bridges}, Policy⟩ → U.Discipline. Read it only as a map into the direct construction account. Its useful intent was to assemble a reviewable field-level whole account, preserve provenance, support separately governed publication of that account, and enable admissible comparison; none of those receiving functions creates the whole.
Every former argument remains available but loses automatic constructor and identity force: EpistemeCanon routes to exact canon epistemes and their claims; StandardsSet to exact standard epistemes, Methods, and practice claims; OrgCarriers to independently identified systems, system-role kinds and assignments, and Work; {Bridges} to exact F.9 occurrences and bounded-use propositions; and Policy to exact comparison, evidence, assurance, and acceptance declarations under their subject patterns. Section 4.6 gives the complete intake prompts for those families. Historical Gamma_disc expressions are therefore only incomplete shorthand for a C.13 construction account. A five-field argument list, Discipline Card, or filled schema does not complete the account and does not have constructor force.