C.29:4.4.1 - Output set and declared-use boundary
Use the single output/reliance rule in :4.4. The form states the mathematical account; a used empirical, causal, semantic-bridge, assurance or decision result additionally needs its subject-pattern basis in :4.4.6.
LensMappingMode, LensUseBoundaryValue, and declared lens use are separate fields.
| Lens-use aspect | Question it answers | Where it is recorded |
|---|---|---|
| Mapping construction | How does the mathematical object represent, abstract, embed, quotient, simulate, learn, or transfer the phenomenon? | LensMappingMode, PreservedStructure, LostStructure, and any ScaleWindow? or CoarseGrainingRule?. |
| Lens-use boundary value | What limited lens-use value is declared for this use? | LensUseBoundaryValue, validation overlay when validation use is being claimed, and neighboring evidence or assurance patterns when their claims are being made. |
| Declared lens use | What can the working reader now do, and when must the use stop or return? | declaredLensUse, NextLensUseAction, StopCondition, optional blockedLensOverread?, and named governing FPF patterns. |
LensMappingMode names construction, not permission. Typical local values include representation, abstraction, quotient, coarse-graining, embedding, homomorphism, isomorphism, functor-like transfer, simulation, and learned or fitted representation. A broad family name such as graph, field, category, geometry, quantum-like, variational, or Bayesian is only a prompt until the concrete construction and preserved structure and lost structure are named.
LensUseBoundaryValue declares only a limited lens-use boundary:
LensUseBoundaryValue value | Declared use | Stop or neighboring-pattern condition |
|---|---|---|
| analogy-only prompt | orientation, hypothesis generation, recognition cue | decision, assurance, causal claim, or publication as established model |
| diagnosticOnly | finding a candidate obstruction, bottleneck, mismatch, missing state variable, or rival-lens split | prediction, decision, causal use, bridge substitution, assurance, or ontology without the neighboring-pattern result named by value |
| formal derivation inside accepted theory | local explanation or theorem-backed transfer when assumptions hold | empirical claim without observation or evidence |
| simulation | candidate model and scenario exploration | real-world causal or predictive reliance without validation |
| empirical fit | local prediction inside validation regime | out-of-regime generalization and causal use |
| accepted domain theory | local domain model use | cross-context ontology import |
| SoTA-echo candidate | structured exploration and lens-use testing | accepted FPF law, assurance, release, or foundation claim |
| mechanized proof | formal property under assumptions | real-world adequacy unless assumptions and evidence hold and any needed semantic Bridge is established |
State the declared lens use in declaredLensUse and its stopping or return boundary in StopCondition. Elegance, familiarity, source prestige, and mapping type supply no substitute for that declaration. Include blockedLensOverread? only when it passes F.19’s plausible-reader test.