E.18.2:4.1 - First-use record

Use this compact record for ordinary cases:

TransformationFlowMathematicalDescription@Context:
  # exactly one described ontic subject branch is present:
  DescribedTransformationFlowStructureRef?:
  DescribedTransformationFlowStructureNetworkRef?:
  DescribedSliceOrLocusRef?:
  CandidateMathObject:
  ExpressionKind:
  MappingMode:
  PreservedStructure:
  LostStructure:
  DeclaredUse:
  BoundaryStop:
  C29LensUseRef?:
  PublicationFaceRef?:

Exactly one of DescribedTransformationFlowStructureRef? and DescribedTransformationFlowStructureNetworkRef? is present. The first points to one E.18 TFS; the second points to one already selected E.18.NET network. DescribedSliceOrLocusRef? may cite an existing path, slice, FlowPositionRef, ExposedFlowPositionRef, member path, E.18.NET NetworkCrossFlowRelationRowRef, or other independently identified part without copying the fields that define that object. CandidateMathObject and ExpressionKind name the graph, algebra, category, tuple, morphism, quotient, fold, refinement, factorization, wiring, matrix, network expression, or related mathematical object. PreservedStructure, LostStructure, DeclaredUse, and BoundaryStop follow the C.29 discipline when the expression is claim-bearing. PublicationFaceRef? points to a separate E.17 publication face. The compact record has no generic neighboring-object reference. When a neighboring claim is materially needed, cite its exact C.2.1 claim-bearing episteme in the subject-specific account; identify an ontic subject or relation occurrence only through a separately named, correctly typed reference supplied by the pattern for that claim.