E.18:6 - Archetypal Grounding (Tell–Show–Show; concise)

Tell (one first-principles P2W specialization). A first-principles-to-work path is one path through a selected transformation-flow structure, not P2W as a whole: U.Signature(profile=FormalSubstrate) declaration, principle frame, mechanism, normalization, selection, planning, pre-run work-entry claim, later exact Work occurrence when one exists, and current evaluation or currentness relations occupy exact identified positions. E.18.1 separately carries the accepted problem-side claim through whichever of those relations becomes current.

Show-A (Supply chain). The loci run from procurement through inbound quality control and normalization to supplier selection; selection and planning inform each other; planning leads to execution and then refresh. Execution includes receipt Work admitted under U.Work and keeps its receipt records separate; refresh uses quality telemetry and re-emits the affected faces. When an incoming lot moves from the supplier-receipt position to the internal-QC position and its locality binding changes, record the crossing with CrossingRef, the A.2.6 locality fact, the rule that permits the change, and the A.21 gate. If the two labels also use different local senses, identify their F.17 cells and test the F.9 Bridge, the C.2.1 bounded-use claim, and current reliance separately. A penalty appears only when a current policy is cited through PolicyIdRef, the policy applies, its rule supports the penalty, and any separately needed authority relation and participants are established. Comparators remain pinned to the named CG-Spec value and edition.

Show-B (Neural-net functional). Loci: U.Signature(profile=FormalSubstrate) declaration (typed tensor-operation declaration) -> mechanism (combinator algebra) -> UNM (dataset normalization; TransportRegistry^Phi) -> selection (architecture and hyperparameter set; Pareto set over accuracy@ratio and FLOPs@ratio) <-> planning (compute budget horizon) -> Work (exact training-run occurrences admitted under U.Work; any Delta is stated in a separate record) -> refresh (parity inserts; slice-scoped). Faces pin DescriptorMapRef.edition and DistanceDefRef.edition when QD telemetry values are shown; illumination remains report-only telemetry by default.

Show-C (Developed product, then application - network case). Development, later application, and further use keep separately identified TFS values when they have their own identified objects, Work occurrences, local position bindings, DesignRunTag boundaries, and change boundaries. A tool may be made, then used to make a chair, then the chair may be used while a person writes a text. Apply E.18.NET to select those TFS members and cite each exact production, use, participation, or other cross-member relation with its defining predicate and occurrence rule. Do not join them with U.Transfer; if a required relation has no predicate or occurrence rule, return missing-governor.

Show-D (FPF pattern development and use - network case). Pattern development, application to an EntityOfConcern, and use-found evaluation keep separately identified TFS values when each has its own identified object, Work, positions, and local state. Apply E.18.NET and cite the exact use, evaluation, evidence-return, or repair-trigger relation that connects their positions, together with the pattern or declaration that defines its predicate and occurrence identity; if no such rule is available, return missing-governor. E.18 defines each member’s internal structure and smallest reopened PathSlice. A reader-facing role label remains ordinary wording until E.10.ROLE recovers its meaning; neither that label nor a feedback arrow makes the members one TFS or supplies the cross-member relation.

Cross-pattern boundary slice (QD archive). A QD selector returns an archive. Under E.18, the selector occurrence and returned archive may occupy positions on one PathSlice; the archive is returned by the exact selector relation, not by the slice, and remains a set or archive rather than a hidden scalar. Under A.20, an archive insertion or update step may have exact constraint-validity results and a complete required-set summary; no acceptance is inferred. Under A.21, a comparability gate or LaunchGate publishes a decision only when its gate relation consumes the declared independent check results. Under E.20, a newly introduced selector-mechanism definition remains the meaning locus. These are four identified loci, not one prescribed work order.

Post-2015 SoTA echoes (illustrative): TAMP and MPC, MAP-Elites and QD (incl. CMA-ME), refinement-typed stacks, profunctor optics. Worked examples and Tell-Show-Show vignettes for P2W, comparator and archive, network cases over separately identified development and application TFS members, and one-TFS refresh specializations stay outside this selected-structure core unless a current pattern explicitly selects them.