C.20:5 - Archetypal Grounding
C.20:5.0 - System/Episteme contrast
The examples distinguish the field candidate from a system, episteme and the relations used to describe its construction. Each cell retains its own subject pattern; the table is not an assembly rule.
| Reader function | System-side safety scene | Episteme-side discipline scene | C.20 boundary |
|---|---|---|---|
| Exact object | One production line with hazardous operations is an exact U.System under A.1; its work and state remain separate. | One exact canon or discipline-description U.Episteme states accident-model and tolerable-risk claims about its declared EntityOfConcern under its effective ReferenceScheme. The SafetyEngineering-SE field candidate remains another entity. | Neither the system nor one episteme is the discipline; identify the field candidate and test its construction independently. |
| Concept contribution | Acceptance clauses and evaluation templates bound to exact rigs and windows are epistemes used by the plant system and its Work, not concepts owned by the system. | Canon content can include causality models, design rules, proofs, benchmarks, formal knowledge bases, proof carriers, and concept schemas under their direct episteme, form, or representation patterns. | Ask which exact claim-bearing contribution is constitutive and which whole-forming claim states how it connects to the assembly; conceptual relevance alone creates no part. |
| Symbolic representation | Local SOP and checklist notation can express plant procedures for one bounded use. | CLIF, RDF/TriG, proof scripts, diagrams, and other notation packages can express or represent canon content. | E.17/E.24.PUB and C.29 govern form, carrier, publication, and representation; symbolic appearance identifies none of System, Episteme, or Discipline. |
| Assembly contrast | A line-specific standard, plant procedures, and a certifying unit are exact epistemes, Methods, systems, system-role kinds or assignments, or Work inputs around a possible Safety-Plant-A field candidate. | Canon papers, formal models, a journal or committee, and system-safety or resilience-engineering tradition claims are likewise separately governed around SafetyEngineering-SE. | A list or formula alone establishes neither candidate’s construction. For either scene, recover exact parts, obtaining disciplinePartOf occurrences, whole-forming couplings, assembly, reidentification, whole characteristic, and larger-assembly compatibility. |
| Evidence-lane contrast | Plant tests can supply validation evidence (LA). A design proof can supply verification evidence (VA). Check that the quantities used by the tests and proof correspond when the argument connects them, and check any tool qualification on which the argument relies. | A proof over kinds can establish a formal consequence. Replications or a meta-analysis can support an empirical claim. If a checker produced a relied-on result, establish its qualification for that check. | A.10 keeps the exact source, currentness, and reliance needed by the use. When an actual named assurance claim is current, B.3 adds only the characteristics and result fields that its argument consumes. Evidence changes no System, Episteme, or Discipline identity and creates no part relation. |
C.20:5.1 - Safety engineering as a positive construction
Suppose SafetyEngineering-SE is one exact field candidate. C.2.1 independently identifies HazardCausalityCanon-v5 as a claim-bearing episteme. A.3.1 independently identifies HazardAnalysisMethod-v4 and IncidentLearningMethod-v2 as reusable Methods. None is a C.20 part yet.
The field assembly makes these exact contributions current:
HazardCausalityCanon-v5supplies the hazard, causal, and acceptable-argument meanings used by the two Methods;HazardAnalysisMethod-v4supplies the reusable analysis practice by which those meanings constrain identification and treatment of hazards;IncidentLearningMethod-v2supplies the reusable practice by which separately governed incident and evaluation results can challenge or refine the canon claims.
The three exact relation occurrences are disciplinePartOf(HazardCausalityCanon-v5, SafetyEngineering-SE)@I-SE-core-1, disciplinePartOf(HazardAnalysisMethod-v4, SafetyEngineering-SE)@I-SE-core-1, and disciplinePartOf(IncidentLearningMethod-v2, SafetyEngineering-SE)@I-SE-core-1. They share the maximal current continuous obtaining interval I-SE-core-1 = [2024-04-01T09:00Z, open): its left boundary is the dated field-assembly activation at which all three contributions first became jointly required.
At the continuation check 2026-07-31T23:59Z, each contribution remains required, the canon meanings remain connected to method preconditions and result meanings as stated by the exact whole-forming claims, the same candidate and reidentification rule continue, and no cessation boundary has occurred; therefore the right boundary remains open. If any contribution ceases and later resumes, that part’s interval ends at cessation and a new disciplinePartOf occurrence begins at resumption. The field assembly requires those contributions, and the reidentification rule admits them as current parts.
The local A.17 Characteristic PracticeKnowledgeCouplingReplayability has the exact subject SafetyEngineering-SE and the ordinal A.18 Scale broken < partial < replayable: its criterion asks whether the named canon-to-Method constraints and result-to-canon revision routes remain executable across the declared safety-work classes. No constituent can have that whole value alone.
If a current use needs a measured value, C.16 requires the exact measurement subject, method, model, Scale, dated measurement Work, uncertainty, and result episteme; the label alone supplies no reading.
The reidentification rule permits a compatible canon revision or replacement Method only when the field boundary, causal and argument meanings, practice-knowledge feedback, and whole characteristic remain within declared continuity conditions. Removing the feedback route, changing the governing safety concern and field boundary, or replacing the assembly by unrelated document and method lists falls outside the rule.
Safety Journal, a standards committee, a university curriculum, a laboratory, a bridge to resilience-engineering terminology, a comparison CG-Spec, and a published discipline card remain separately governed. This example establishes no C.20 part predicate for them, so their parthood remains unresolved. A positive or negative part claim needs the corresponding C.20 grounds.
For A.1’s larger-assembly test, the separately identified rule episteme EngineeringFieldAssemblyRule-v3 describes a governed larger-field construction whose applicability requires one constituent field to expose stable hazard-constraint meanings, analysis-result meanings, and identity-preserving interfaces to design and verification practices. SafetyEngineering-SE has those interfaces and its reidentification rule preserves them, so it is compatible with that possible assembly while remaining the same candidate. The rule episteme does not create the compatibility facts, and this result asserts no actual disciplinePartOf(SafetyEngineering-SE, Engineering-E) occurrence.
A C.13 Gamma_m.sum trace may report the candidate, three parts, three part-relation occurrences, whole-forming claims, assembly, reidentification rule, and whole characteristic. Writing or publishing that trace does not construct SafetyEngineering-SE.
C.20:5.2 - A department, corpus, and method registry are not yet a discipline
Safety Department A performs research and teaching Work. Its repository contains standards and papers, and its registry lists analysis Methods. Those facts identify the organization, its research and teaching Work, the standards and papers, and registry membership under their subject patterns. Any publication occurrence additionally needs its own audience-availability basis under E.24.PUB.
They leave the field constituents, disciplinePartOf occurrences, practice-knowledge assembly, whole characteristic and reidentification rule unresolved. The discipline classification is therefore unknown on these facts. The recovered collection and work organization may suffice for the current question; do not treat filled card positions as grounds for a positive classification.
C.20:5.3 - Cross-field reuse does not create a transdiscipline
A safety-engineering team proposes to reuse one resilience-engineering term. F.17 resolves the two exact SchemeSenseCell values, and their semantic-context projections differ. The stated directed BridgePredicateProfile applies to those endpoint readings at its stated as-of basis; the current endpoint meanings satisfy its relation-kind-specific semantic condition and Boolean truth condition; and all required dependencies are present. F.9 therefore identifies an obtaining directed Bridge. A separate bounded-use proposition states the direction, mapping rule, tolerated loss, and polarity for this hazard-review use. Review Work may rely on that proposition through A.10, and a comparison may apply A.19.CPM.
The directed correspondence relates the two meanings of the term. To rely on that correspondence in the hazard review, the bounded-use proposition must support this use in the stated direction, and the A.10 reliance check must permit it. If the teams combine their methods to produce this review, the joint result can establish interdisciplinary work. A resilience principle has transdisciplinary reach when the same relation admits warranted interpretations in different disciplines under stated conditions. To show that the safety team used it here, identify which distinction, inference or choice in its hazard review depended on the principle. Evidence from the second discipline may already establish the wider reach. To establish a new discipline, identify the candidate whole and examine all six construction components in section 4.1.
C.20:5.4 - Canon revision, same field, and another field
HazardCausalityCanon-v6 changes claim content and is another C.2.1 episteme. Historical continuation from v5 is tested separately. The same SafetyEngineering-SE can continue if its C.20 rule permits that replacement and the required contribution meanings, whole-forming couplings, boundary, and whole characteristic persist. The old part occurrence ends and the new one begins; a description or evidence window does not decide those intervals.
If the replacement rejects the field’s former causal object, changes the practice-knowledge feedback rule, and changes the field boundary beyond permitted continuity, the same-discipline claim fails. The project then tests another candidate and uses B.2 only if a receiving use needs a whole-reidentification conclusion. A new canon edition, renamed department, or republished card alone decides neither branch.