E.18:5.12 - S12 - Exact viewpoint references to E.18 constructs

Use this when. Use S12 only when a current claim maps one exact viewpoint episteme to exact E.18 constructs. Ordinary work with a selected transformation-flow structure, valuation, path slice, or crossing does not open S12, and one mapping may stop after one row.

Imported interface. E.17.0 defines viewpoint membership and episteme–viewpoint conformance. E.17.1 defines local catalogue declarations and U.ViewpointRef members. E.17.2 provides the project-local TEVB authoring template; it ships no catalogue, reference, or viewpoint episteme value. S12 uses those results and does not copy their catalogue or conformance procedure. E.24.PUB defines publication, and C.29 defines any separately current representation or correspondence.

First useful move. Resolve one viewpointRef : U.ViewpointRef under the effective reference scheme to the named viewpoint episteme. Then name only the E.18 loci, transfer occurrences, gates, crossings, paths, or valuations used by the mapping claim. The reference is not a relation, the viewpoint episteme is not a template position, and the mapping makes neither the E.18 constructs nor their conformance relation obtain.

Stop there unless the current claim separately needs candidate-view conformance, whole-family coverage, retargeting, cross-context meaning, publication, representation, or actual Work. Follow the defining pattern for that claim rather than reproducing it here. A token such as VP.Functional may remain P’s ordinary reader-facing designator after resolution; it is not a viewpoint id, reference, family member, or conformance result.

Project-local TEVB position	Exact reference resolution	E.18-specific mapping contribution
function-oriented	exact `r_functional : U.ViewpointRef` resolves exact `P_functional` under the effective scheme	Name the exact transformation-flow structure, valuation, transformation or capability-facing loci, gates, crossings, paths, and current comparator or publication pins that the mapping actually consumes. Any actual Work and exact performer are independently established through A.13 and A.15.1. Add F.6 only when the mapping also consumes precise assignment-bound attribution; missing or failed F.6 leaves the Work intact.
procedure-oriented	exact `r_procedural : U.ViewpointRef` resolves exact `P_procedural` under the effective scheme	Name the exact `U.WorkPlan`, dated Work, state, transfer, gate, path, or valuation references used by the mapping. A gate may decide attempted entry; it creates no Work occurrence.
allocation-responsibility	exact `r_allocation : U.ViewpointRef` resolves exact `P_allocation` under the effective scheme	Name only the exact E.18 interface, locus, transfer, gate, crossing, or valuation references consumed by the mapping. Local system-role kinds, C.3.2 classification judgments, A.2.1 assignments, supervision, and responsibility or authority relations remain separate claims under their defining patterns.
module interface	`r_module : U.ViewpointRef` resolves `P_module` under the effective scheme	Name the Signature and Mechanism loci, transfer occurrences, gates, crossings, paths, or valuations used by the module-interface mapping. A different described subject needs A.6.4 retargeting; a changed `CtxState` binding uses the E.18 crossing rule.

The four rows use one grammar: an exact reference resolves exact P, and a separately current mapping claim names the E.18 constructs it uses. A project may use one row without materializing the other three. Four rows are required only by a separately identified whole-family coverage claim under E.17.1/E.17.2.

Conditional map row. Persist UTS.ViewpointMap only when the mapping claim is made or consumed:

UTS.ViewpointMapRow:
  EffectiveReferenceSchemeRef:
  ViewpointRef: exact U.ViewpointRef
  ResolvedViewpointEpistemeRef: exact P
  PrimaryE18ConstructRefs[]:
  MappingClaimEpistemeRef?: when the mapping claim is persisted separately
  CandidateEpistemeRef?: only with an obtaining E/P conformance relation
  EpistemeViewpointConformanceRelationRef?: only with CandidateEpistemeRef
  CrossingRefs[]?: only crossings consumed by the mapping
  GateRefs[]?: only gates consumed by the mapping
  PublicationUseRef?: only an independently current E.24.PUB use
  RepresentationRelationRef?: only an independently current C.29 relation

The optional branches carry references to independently established results. They do not repeat the classification, assignment, responsibility, Work, publication, representation, Bridge, or retargeting tests. If a semantic-context comparison is current, use the exact F.17/F.9 path and bounded-use claim; catalogue provenance or equal labels supply none of them.

S12-scoped checks, only when UTS.ViewpointMap is current.

ViewpointRef resolves exact P under the stated effective scheme. The row never calls the reference a relation or P a position.
Every PrimaryE18ConstructRef, crossing, and gate resolves the exact E.18 value or occurrence consumed by the mapping; the row creates none of them.
Candidate-view, whole-family, publication, representation, cross-context, retargeting, and Work branches appear only when that separate claim is current and cite its defining pattern’s result.
One-viewpoint use needs one row. Familiar labels or four unbound template names establish no whole-family coverage.

Purpose. Provide a neutral E.18 mapping from one resolved project-local engineering viewpoint reference to exact E.18 constructs without turning the reference into a relation, P into a template position, or a familiar label into viewpoint, view, family, publication, or conformance evidence.