E.17:5.5 - Pins and local publication-profile fields (normative; never “axes”)

Intent. Make publication-time numeric, comparison, evidence-reference, and crossing claims explicit and auditable without minting another public kind or importing geometric metaphors. This is an optional formal branch. An ordinary publication form retains only the source pins needed to interpret claims actually used from it.

Reuse existing value definitions. A measured aspect is an admitted U.Characteristic with its membership predicate and Scale. A product of characteristic slots is an admitted U.CharacteristicSpace. A publication-profile field, abbreviated locally as a PC field, is only a field in the selected E.17 formal profile: it points to one of those admitted values or to another value or relation whose meaning is already defined. A PC field is not a U. kind, characteristic, evidence relation, comparator, bridge, or viewpoint by being present.

Initial local fields. Use only the fields that the selected publication form and receiving use consume:

PC.Number — a displayed numeric or comparable value of an exact U.Characteristic; name the characteristic reference and its unit, scale, reference plane, and edition when they affect interpretation.
PC.EvidenceBinding — a reference to an existing A.10 evidence path, evidence carrier relation, F.9 Bridge occurrence or description, or optional F.9 CL note; the field itself supplies no evidence, relation truth, or use permission.
PC.ComparatorSetRef — a reference to the comparator family used by a declared partial order.
PC.CharacteristicSpaceRef? — an optional reference to an exact admitted U.CharacteristicSpace when the claim is interpreted in that space.

These are local field names, not members of a catalogue of public kinds. A formal profile may declare another local field only by naming the admitted value or existing reference it carries, the predicate or relation that gives it meaning, the consuming publication use, and any required pins.

Norms (E17-PC).

E17-PC-1 (Exact grounding). A numeric or comparable field resolves the U.Characteristic, the membership or interpretation predicate or CG-Spec reference that gives the value meaning, and material pins {unit, scale, reference-plane, edition}.
E17-PC-2 (Lexical discipline). Forms and PC fields avoid “axis”, “dimension”, or geometric metaphors; use Characteristic, slot, and CharacteristicSpace where those admitted objects are actually meant.
E17-PC-3 (No hidden arithmetic). A form does not hide aggregation or normalization; it cites the calculation or normalization definition and edition.
E17-PC-4 (Crossing). For a semantic crossing, cite the F.9 Bridge and separate bounded-use claim. For a plane-dependent value, cite the selected ReferencePlane and applicable transfer or comparison rule. Add an F.9 CL note or B.3 penalty reference only when the receiving use actually consumes it; a field manufactures none of these relations or claims.
E17-PC-5 (Edition pinning). Fields that rely on maps, distances, spaces, set semantics, or transfer rules pin the exact applicable editions and trigger reissue when those editions change.
E17-PC-6 (Viewpoint conditionality). The separate bounded-use declaration says why each field is present. Resolve publicationViewpointRef only when the selected episteme is claimed as a U.View or the formal operation actually depends on that viewpoint. PromoteFace[s->t] may reindex or annotate a form; it adds and widens no claim.

Publication-form responsibilities when this profile is selected. PlainView may show PC.Number only when the exact characteristic and material pins resolve; otherwise use qualitative wording. TechCard may add PC.ComparatorSetRef or PC.CharacteristicSpaceRef? only for a declared ordering or characteristic use. AssuranceLane may carry PC.EvidenceBinding only as a pointer to the exact evidence or policy relation. InteropCard remains notation-neutral and points to the references needed by the external consumer.

Extending the profile. Give a new local field a plain and technical label, the value or reference it carries, the predicate or relation that gives it meaning and establishes membership or applicability, the identity-relevant edition, pinning rule, and one named consuming use. If the work instead needs a new public ValueKind, return that as a separate kind-settlement and product decision; E.17 does not admit it by declaring a field.

Adding or changing invariants.

Put a new invariant in the CG-Spec or other specification-use source that defines it; supply the test there.
Version any affected U.CharacteristicSpace, comparator, map, distance, or transfer rule; publish an explicit correspondence relation when semantics change and never mutate slots in place.
Update an A.21 gate check only when an actual gate consumes the invariant. Publication conformance can warn or block only according to the selected profile and bounded use; it does not create an operational gate.
State the edition-change and Lean-profile downgrade behavior that the concrete consuming use needs.