E.18:5.3 - S3 - Publication discipline (faces)
E.18 imports E.17 wholesale and associates MVPK faces with PublicationScope (USM).
MVPK remains the source for:
- the set of face designators (
PlainView,TechCard,InteropCard,AssuranceLane), - pin discipline and Publication Characteristics (PC),
- “no new claims; in the optional morphism profile, no re‑listing of inputs and outputs and no Γ‑semantics on publication morphisms”.
E.18 does not re-specify these rules; it only adds structure-scope obligations for faces published over transformation-flow paths:
- Crossings on faces. When a face publishes a GateCrossing, it cites the
CrossingRef,ChangedBindingAccountRefs[],GateId, and any currentGateDecisionResult, optionalDecisionLog, policy-application, or permission-claim refs. An F.9 Bridge block appears only for a separately established cross-semantic use; its optional card andCLdo not replace those refs. - Edition refs on faces. A face that cites
CG-Spec,ComparatorSet,UNM.TransportRegistryPhi, or another versioned value cites that exact value and edition. Edition citation alone requires no Bridge Card, UTS row, or semantic Bridge. - ComparatorSet and set returns (structure-scope). Any
ComparatorSetandSetSemanticsRefused along a transformation-flow path carries edition identifiers; affected faces are re-emitted on edition change; faces with comparison return sets and declared partial orders (no hidden scalarization), reusing MVPK’s declared-order discipline. - Gamma_time on compare and launch faces. Every current compare or launch publication face on an E.18 path pins
Gamma_time; implicit latest is not admissible. A.21 cites the exact current profile application and qualification window. CHR avoids acceptance thresholds (NoThresholdsInCHR); gate and threshold claims are carried by A.21 and Part G, while actual performed facts are established through independently obtaining relations involving exact Work occurrences under A.15.1. A sourceunknown,notRun, or error remains explicit before the current profile rule maps it to a gate decision.
Reminder. MVPK supplies the “signature” naming rule, the optional morphism profile’s input-output rule, arithmetic-visibility rules, and material numeric-pin requirements (E.17 §5.4-5.5). E.18 does not weaken those rules;
CC-E18-09states the additional constraints on faces published along transformation-flow paths.
Lean publish-mode (AssuranceLane-Lite). Lean changes publication faces only, not policy or checks. A current face cites the profileApplicationRef, identified GateCheckApplicationResult refs, and GateDecisionResultRef; it cites a DecisionLogRef only when an audit, history, replay, or reuse record is current. The underlying check-application results remain unchanged.
Decision stability and idempotency (gate-local). A gate decision is recomputed when an input named by A.21 changes. Only a current reuse, cacheability, or stability claim needs an equivalence witness covering the inputs whose equality that claim relies on; an optional DecisionLog may cite it. Use G.6 for evidence-provenance path visibility and G.11 for refresh implications. E.18 does not prescribe storage formats, key shapes, or hashing schemes.
Retargeting and semantic-Bridge boundary.
An EntityOfConcernRef change is not established by a UTS row, mapping label, card, CL, or GateCrossing; a kind change alone only reopens the C.2.1 identity test. First recover the exact A.6.4 arrow r from its endpoints, arrow rule or designator, and formal equivalence. Separately recover q, whose ClaimGraph states the invariant, visible loss, named receiving use, conditions, and affirmative or negative polarity. Compare the exact current facts with q and keep the current-case judgement separate: satisfies, fails, or cannot decide; for cannot decide, name the exact missing fact and reopen condition. Any application occurrence and Work remain separate. If the use also needs a semantic relation between two exact local senses, apply F.9 separately and keep its own bounded-use claim, optional CL, evidence, and reliance separate.