E.17:5.4 - EntityOfConcern-side input and output vs publication (normative convention)

1. Input and Output are signature-side declarations. The Input and Output sections of a morphism describe declared input and output data or episteme types under the morphism signature; they do not depend on any publication face.
2. No duplication on faces. In the optional morphism profile, faces do not restate Input and Output lists; they carry only the source references, presence pins, and edition identifiers needed by the selected face and use.
3. Use Signature only for signatures. Use Signature only when the named object is a signature under an applicable signature pattern, such as U.Signature. On faces, use TechName or PlainName.
4. Comparison and ordering. A bounded source contrast under E.17.ID.CR retains its shared review frame and row-level comparison criteria. When a face publishes selection or an ordering, preserve the source-defined set or order semantics, make the comparator and any scalarization explicit, and cite ComparatorSetRef where that formal comparator family is used.
5. Bridge and plane references. A semantic crossing cites its F.9 Bridge and separate bounded-use claim. A plane-dependent value cites its characteristic, selected ReferencePlane, and applicable C.16 or A.19.CPM transfer or comparison rule. If B.3 is triggered and its assurance claim depends on an integration relation, retain that relation’s B.3 CL and Φ(CL) reference; infer no penalty from an F.9 Bridge or publication face.
6. Carrier references and relation positions. When the use depends on them, name the carrier reference, any A.10 evidence/provenance path or G.6 path citation, and the G.11 currentness result; keep U.Work occurrences distinct from epistemic claims via relation positions.
7. Publication is not execution. Publication morphisms carry no time or resource semantics; any build, render, or upload work is separate U.Work.