Jump to text
On this page
Copy and source
Published source confirmed at last check

Source changed 2026-11-18 21:11:39 UTC · snapshot created 2026-11-18 21:12:35 UTC · last check 2026-11-18 22:10:10 UTC

C.20:0 - Use This When

Use this pattern when a team needs to decide whether a field is one durable practice-and-knowledge whole rather than a label or collection. Typical moments include:

  • comparing rival traditions without letting a shared label, Bridge or comparison table merge them;
  • reusing a practice across semantic localities while preserving local meanings, direction, tolerated loss and field boundaries;
  • testing whether a Method, theory, standard or subdiscipline is a constituent rather than merely used, cited, registered or taught in the field;
  • determining continuity while a canon, standard or accepted practice changes, and identifying another whole when the reidentification rule fails;
  • using an applied, multidisciplinary or transdisciplinary classification under its stated criterion.

Primary EntityOfConcern. One exact U.Entity candidate being tested for recognition as U.Discipline. The candidate is recoverable before the classification result.

First useful move. Name the exact candidate and two independently identified candidate parts: at least one making a knowledge-bearing contribution and at least one making a reusable-practice contribution. Then state why each direct part relation obtains and one whole-forming fact that couples the two contributions. Do this before letting the discipline name support a comparison, selector or dispatcher, health or maturity claim, transport, or edition decision. If those facts are unavailable, retain the supported account of separately governed objects or their collection and leave the discipline claim unresolved.

What goes wrong if missed. A field name starts doing the work of a canon, method repertoire, institution, bridge, comparison policy, and maturity score at once. The reader may then treat a card or graph as establishing parts, or treat changes to a journal, standard, method list, or dashboard as establishing a new discipline. Cross-locality reuse can also look valid after local meanings, evidence lanes, or comparison rules have drifted.

What this buys. A practitioner can say what the discipline is made of, how the parts form one practice-and-knowledge whole, what remains the same through change, and which surrounding objects are merely used by discipline work. That makes comparison, transport, stewardship, and edition work inspectable without reducing the field to a document list or domain label.

Not this pattern when.

  • Use domain or catalogue work for a subject-area label.
  • Use the effective ReferenceScheme, ClaimScope, and F.17 local-sense row for one local meaning.
  • Use F.9 only when a semantic relation is claimed between two exact F.17 SchemeSenseCell values from different semantic contexts and its predicate obtains.
  • Use C.2.1 and its publication or source-use patterns for one theory, standard, canon item, or their exact episteme edition.
  • Use C.3, C.2.1, and direct historical or provenance relations for a school, variant, lineage, or classification.
  • Use A.3.1 and B.1.5 for a Method or composite Method.
  • Use A.15.1 for dated Work.
  • Use A.22 for a selected relation organization.
  • Use A.19.CPM for an actual comparison.
  • Use C.21 for field-health characteristics.
  • Use E.24.PUB for publication.

Use C.20 when determining, explaining, or relying on whether one exact field-level candidate has the required construction and continuity. The result may be true, false or unknown. Missing constructive facts leave the discipline claim unknown; they do not establish that the candidate is only a collection. Continue with the separately supported objects or collection when those suffice.