| Method Engineering Discipline boundary | A C.20-recognized Discipline when that result exists; otherwise a named bounded practice, collective, or population under C.36 with the Discipline claim unresolved. | A field name, school label, package, organization, or edition does not establish a Discipline. |
| admitted-Method branch | One independently A.3.1-admitted Method Engineering Method or variant plus a particular dated Work occurrence for which the A.15.1 enactsMethod predicate obtains. | Presence, teaching, a candidate account, or a source label establishes neither Method admission nor enactment. |
| candidate or observed-practice branch | A status-preserved candidate lineage or source-described observed practice, its candidate account or source claim, honestly named card, template, description episteme, or other claim-bearing material, and independently supported Work facts. A claim-bearing item is a U.MethodDescription only when one A.3.1-admitted Method is its EntityOfConcern and A.3.2 classifies the episteme. | This branch makes no Method or enactment claim until A.3.1 and A.15.1 independently succeed; use alone establishes no content defect. A needed correction to a candidate Method account can use ME.8 without changing its candidate status. |
| bounded population | Identified transmitting, receiving, recognizing, selecting, remembering, retaining, generating, or losing participants for the named predicate, place, and period. | “The organization”, “the community”, or “users” is insufficient without participant meanings and a boundary. |
| cultural predicate and disposition | The transmitted, selected, recognized, remembered, retained, generated, or lost value; participant meanings; applicability; positive test; discriminating negative or failed case; and the lightest truthful A.6.RCD result. | A convenient relation label does not create a direct relation kind or obtaining occurrence. |
| claim, evidence, and occurrence | The world-side direct relation or bounded relation-bearing claim; a separate claim episteme; evidence and reliance; and observations at named intervals. Use A.6.REL occurrence identity only when later work must distinguish occurrences. | A claim episteme, identifier, evidence item, or later report neither creates nor reidentifies a world-side occurrence. |
| participating subjects | Identified cards, descriptions with their recorded kind and status, publication occurrences, repositories or other Systems, teaching/tutoring/event Work, decision-rule epistemes, fields, forums, assignments, permissions, authority, and other direct relations actually relied on. | A bundle word does not establish selected structure; A.22 applies only to one selected organization whose constituents and obtaining relations change the decision, and C.30 only to a current architecture question. |
| bounded authorization | One named assignment, permission, or authority predicate with Agent, action or changed subject, scope, and positive basis that permits the intervention. | Ownership, project position, assignment, permission, authority, and expertise are not interchangeable. |
| development hypotheses and inquiry | Credible explanations whose different consequences could change the continuation or warranted claim; a new observation only when its attainable contribution warrants its whole burden. | Unresolved explanation does not erase a bounded supported account. Neither a second hypothesis nor a proposed study is a universal completion field; a causal or tested-change claim keeps its own evidence conditions. |
| practitioner or constructed-Method consequence | A separately observed change in practitioner Work, understanding, burden, result, or a constructed Method. | It is not the cultural claim and does not prove that claim caused the consequence. |