fpf.tools
Library / First Principles Framework (FPF) - Core Conceptual Specification
Jump to passage
In this reading
Source · lines 32965–32977

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 02:22:15 UTC · snapshot created 2026-10-03 03:38:22 UTC · last check 2026-10-03 04:15:10 UTC

A.19.SOURCE-SET-SPACE-SUBSTRATE:2 - Problem

How should one declare a source-set and search/outcome-space line so that:

  1. the declared source set remains explicit and recoverable;
  2. SearchSpaceRef and OutcomeSpaceRef stay guarded refs to declared A.19 CharacteristicSpace, not new free-floating space kinds;
  3. the text states whether those refs point to one declared space or to two distinct declared spaces;
  4. the source-to-outcome relation is explicit enough for the reader to know which source-to-outcome relation mode is being claimed: mapped, projected, translated, scored, or otherwise connected;
  5. distortion, uncertainty, and error are stated honestly rather than hidden in prose;
  6. SourceSetComposition and DerivedViewKind remain conditional fields rather than fabricated mandatory baggage;
  7. qualifier refs such as OutcomeMapRef, SpaceMetricRef, TransitionRelationRef, and BridgeDistortionNote remain available but substrate-side only;
  8. and neighboring declarations such as A.19, C.18, G.5, G.10, and A.19.DECLARED-SUBSTRATE-INTERPRETIVE-VIEW can dock to the substrate without redefining it?