E.20:5 - Archetypal Grounding
Optional citation, no suite or mechanism change. A suite description adds only an optional citation of an already-introduced U.Mechanism episteme by its MechanismDefinitionRef. Its admitted membership, denotation, closure, obligations, pins, protocol semantics, and relied-on neighboring relations remain unchanged. Name the suite-governing locus and stop. This citation opens neither a new mechanism declaration target nor a MIP-run manifest. A membership addition instead uses the suite-change branch.
| Working rule | Add a mechanism to an existing suite variant | Introduce a new mechanism family + suite | |
|---|---|---|---|
| Scene | Mechanisms evolve: new stages appear, methods mature, and planning records need to remain citeable. | A team wants an additional “stage” in a characterization pipeline, but does not want to mutate the kernel suite. | A new domain needs a mechanism family or species not yet present in any existing mechanism-profile cluster (for characterization: A.19.*), plus a suite that composes several distinct mechanisms with a P2W hook. |
| Definition-locus assignment | Each changed item has one governing definition. Make the change there. | 1) Add the introduced U.Mechanism episteme under the mechanism-subject pattern. 2) Add a suite variant under the suite-subject pattern. 3) Pin the variant in one WorkPlan. 4) Wire the variant through a GPatternExtension. | 1) Add the new operation-family declaration and archetypal grounding under the subject pattern. 2) Add A.6.7.<FamilyKey> describing the suite. 3) State suite-specific planned values inside one WorkPlan. 4) Add SoTA packs and wiring modules. |
| Resolvable target first | No suite treats a dangling designator or reservation stub as an introduced mechanism. | Create the reservation stub or introduced mechanism target first; add only an introduced mechanism to admitted suite membership. | Create each mechanism target first; then publish suite membership by designator. |
| Suite discipline | Suites are descriptive: membership, obligations, pins, protocols; not mechanisms and not gates. | The variant’s suite_protocols names the new stage; publish/telemetry remains outside the suite. | The new suite defines shared obligations and allowed pipelines without embedding mechanism semantics. |
| P2W planning-to-work boundary | One exact WorkPlan is the planning record; §4.7 governs its declaration-local rows, while enactment witnesses actual runs. | The WorkPlan pins the chosen suite variant and any method or specification references; use declaration-local rows only for existing members under A.15.3. No row carries launch values or decision logs. | Declaration-local rows for existing members under A.15.3 state planned fillers and pins that downstream flows cite through the exact WorkPlan edition. |
| SoTA updates | Methods change faster than kernel meaning; wiring is where choices are governed. | A GPatternExtension selects a scoring method by edition‑pinned ref; no kernel mutation required. | The family ships method packs and wiring modules; the identity-bearing content of each introduced U.Mechanism remains at its mechanism-subject pattern. |