A.19.SOURCE-SET-SPACE-SUBSTRATE - Source-Set and Search/Outcome-Space Substrate
Preface node
heading:a-19-source-set-space-substrate-source-set-and-search-outcome-space-substrate:37100
What this page is
This is generated FPF reference text from the specification preface or supporting sections. It helps interpret FPF; it is not FPF Reference product documentation.
Methodology
Use it to understand how the specification wants to be read, then return to a route, pattern, or work packet for active work. Cite generated IDs only when the wording changes the task decision.
Content
Type: Architectural (A) Status: Stable Normativity: Normative
Plain-name. Source-set / search-outcome-space substrate.
Working contribution. Identify the set being searched or compared, the space used to describe its members, and the space in which their outcomes are judged. State the relation that connects source members to outcome values and the limits of that relation. Search and outcome may use the same A.19 space; the two uses still need to remain distinguishable.
A.19.SOURCE-SET-SPACE-SUBSTRATE:0 - Use this when
Use this pattern when a search, comparison or synthesis depends on all of the following:
- one declared source set or composition of source sets still matters and must stay recoverable;
- one search-side space reference and one outcome-side space reference must both be explicit;
- the line must say whether those refs resolve to one declared
CharacteristicSpaceor to two distinct declaredCharacteristicSpacevalues; - the reader must know what the source-to-outcome relation connects, in which direction, and through which declared carrier, declared map ref, or qualifier ref;
- distortion, uncertainty, or error must be specified.
This is the right pattern for QD, OEE, archive/front, or adjacent synthesis lines when the problem is no longer only "what space exists?" and not yet "what shortlist or shipped result do we publish?".
Not this pattern when:
- you only need to declare or compare
CharacteristicSpaceitself, with no source-set or source-to-outcome requirement; useA.19; - you are publishing selector or shipping metadata such as
SelectorOutcomeKind,SetResultFamily,HandoffKind, or public shortlist identity; useG.5orG.10; - you are building one interpretive view over an already-declared substrate; use
A.19.DECLARED-SUBSTRATE-INTERPRETIVE-VIEWor a local specialization such asG.2; - you need live-pool or frontier-retention policy; use
C.19. UseA.15.7to choose a situation-responsive next action andC.24to plan tool or service calls after the action is fixed.
A.19.SOURCE-SET-SPACE-SUBSTRATE:0.1 - What goes wrong if missed
If this pattern is missed, authors usually collapse several different things into one vague "space" or one vague "projection":
- the declared source set disappears behind bare words such as
front,archive,palette, orportfolio; SearchSpaceRefandOutcomeSpaceRefnever become explicit, orSpaceRefRelationKindnever becomes explicit, so one line hides whether search and outcome use one declared space twice or two different declared spaces;DescriptorMapReforDistanceDefRefgets mistaken for the space itself rather than one representation or metric qualifier;- publication metadata in
G.5orG.10starts standing in for substrate semantics; - and distortion, uncertainty, or error is either hidden or treated as if every non-trivial case were only one bridge-loss story.
The result looks tidy, but the reader cannot tell what is being searched, what is being evaluated, what is only being published, and where uncertainty enters.
A.19.SOURCE-SET-SPACE-SUBSTRATE:0.2 - What this buys
This pattern buys one conservative but expressive substrate declaration:
- the source set stays visible;
- the search-side and outcome-side references over
A.19spaces stay distinct; - the relation between those refs becomes inspectable instead of being hidden in one overloaded noun or verb;
- heavier qualifier refs remain available without being forced into every case;
- and interpretive-view or publication neighbors can reuse the substrate without changing what it means.
The practical payoff: readers can tell what the line is acting on, what relation between the two space refs it assumes, what kind of qualification they must keep in view, and which neighboring pattern governs the next use or action if that requirement grows.
A.19.SOURCE-SET-SPACE-SUBSTRATE:0.a - TERM/LEX token-status guard (local-first)
Keep this token-status split explicit:
CharacteristicSpaceis the reusedA.19kind. This pattern does not mint a second space kind.SearchSpaceRefandOutcomeSpaceRefare role-named local fields whose slot content is typed by the existingCharacteristicSpaceRef/SpaceRefidiom. They are not new heads, not slot aliases inside the space, and notU.Roleclaims. These field names distinguish the search-side and outcome-side uses of the referenced A.19 space.SpaceRefRelationKindis a local relation-kind field over those two refs. In this pattern,sameDeclaredSpaceAsanddistinctDeclaredSpaceFromare controlled token values for that field, not free prose.SourceToOutcomeRelationandDistortionPostureare local declaration fields. Their field names do not by themselves create one new generic ontology; the declaration requirement is satisfied only when their payload is explicit enough to audit.SourceSetFamily,SourceSetComposition, andDerivedViewKindare local fields in thisSourceSetSpaceSubstratedeclaration. Their use as fields does not establish a new object kind.BasePaletteRef,OutcomeMapRef,SpaceMetricRef,TransitionRelationRef,BridgeDistortionNote,DescriptorMapRef, andDistanceDefRefare neighboring refs or interpretive qualifiers reused here. This pattern may cite them, but it does not redefine them.carrierinsideSourceToOutcomeRelationidentifies the relation definition, map, model or operation that supplies the connection. Its definition can be stated or cited where the reader can recover it. A containing paragraph expresses that definition; the physical or digital entity bearing that text is identified separately under E.24.PUB.
A.19.SOURCE-SET-SPACE-SUBSTRATE:0.b - First-minute operator cue and confusion guide
When the receiving use depends on the source set, search space and outcome space together, recover the following facts from the existing account. Add only what is missing; an adequate paragraph or model declaration needs no duplicate form.
First recover:
- Name the source set, or the contributing source sets and their composition.
- Point
SearchSpaceRefandOutcomeSpaceRefto declaredCharacteristicSpace. - Choose
sameDeclaredSpaceAsordistinctDeclaredSpaceFrom. - State the source-to-outcome relation in direction, mode, and carrier.
- State the applicable limitations. A primary posture token may organize them; supply it when a selected interface requires one, without hiding other material qualifications.
If one of these facts cannot yet be recovered, preserve the established source and space facts, name the missing basis, and withhold the complete substrate claim and only the use that depends on that basis. Use the applicable subject pattern when it can supply the missing result.
A descriptor map or distance definition supplies one part of this account; it does not identify the source set and both spaces by itself.
A.19.SOURCE-SET-SPACE-SUBSTRATE:1 - Problem frame
A search, comparison or synthesis may depend on several source sets and spaces. Make the following information recoverable:
- one declared source set, such as a front, archive or palette, or a composition of identified source sets;
- one search-side reference to an
A.19CharacteristicSpace; - one outcome-side reference to an
A.19CharacteristicSpace; - one
SpaceRefRelationKindover those two references, stating whether they resolve to the same declared space or to two different declared spaces; - one relation from the source-side line into the outcome-side line;
- and one declared posture about whether that relation is transparent, approximate, learned, lossy, uncertain, or otherwise qualified.
Without a declaration of these components, readers may use a neighbouring declaration for a question it does not answer. A.19 gets stretched from space typing into source-set governance. C.18 descriptor maps start masquerading as the whole search space. G.5 and G.10 publication fields start reading like ontology. Interpretive views or atlas views drift into default meaning instead of staying optional derived help.
A.19.SOURCE-SET-SPACE-SUBSTRATE:2 - Problem
How should one declare a source-set and search/outcome-space line so that:
- the declared source set remains explicit and recoverable;
SearchSpaceRefandOutcomeSpaceRefstay refs to declaredA.19CharacteristicSpace, not new free-floating space kinds;- the text states whether those refs point to one declared space or to two distinct declared spaces;
- 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;
- distortion, uncertainty, and error are stated rather than hidden in prose;
SourceSetCompositionandDerivedViewKindremain conditional fields rather than fabricated mandatory baggage;- qualifier refs such as
OutcomeMapRef,SpaceMetricRef,TransitionRelationRef, andBridgeDistortionNoteremain available but substrate-side only; - and neighboring declarations such as
A.19,C.18,G.5,G.10, andA.19.DECLARED-SUBSTRATE-INTERPRETIVE-VIEWcan dock to the substrate without redefining it?
A.19.SOURCE-SET-SPACE-SUBSTRATE:3 - Forces
A.19.SOURCE-SET-SPACE-SUBSTRATE:4 - Solution
Declare the source set, both space uses and the source-to-outcome relation with its limitations. Add conditional fields or companion declarations when the intended use requires them.
A.19.SOURCE-SET-SPACE-SUBSTRATE:4.1 - Substrate declaration and related work
Use this pattern to declare:
- the source set, or composition of source sets, used by the search or comparison;
- the recoverable source-set identity when the family name alone would be ambiguous;
- the search-side reference to one declared
A.19CharacteristicSpace; - the outcome-side reference to one declared
A.19CharacteristicSpace; - the
SpaceRefRelationKindover those two ref positions; - the source-to-outcome relation;
- and the distortion, uncertainty, or error posture for that relation.
Do not use this pattern to declare:
A.19space typing itself;- selector outcome publication, shortlist identity, or shipping closure;
- live pool policy or enactment planning;
- or optional interpretive-view families that interpret or reorganize an already-declared substrate.
A.19.SOURCE-SET-SPACE-SUBSTRATE:4.2 - Minimal declaration
The notation below names the required content and conditional fields:
Interpret the fields as follows:
SourceSetFamily?names the declared family of the immediate source set and is required for a single-source account. For a composition without a distinguished source,SourceSetCompositionsupplies the source basis by identifying each contributing source, its family and member contribution rule. If the receiving use singles out a primary source, identify that source and retain its family inSourceSetFamily.SourceSetRef?names the declared source set or set result when its identity would otherwise be ambiguous, including when a neighboring governing pattern supplies that identity. For a composition, recover each contributing set throughSourceSetComposition; add a separateSourceSetRefwhen the receiving use also depends on the identity of a combined set result. A reference may be omitted only when its intended set is otherwise unambiguous.SearchSpaceRefpoints to one declaredA.19CharacteristicSpacein the search-side position.OutcomeSpaceRefpoints to one declaredA.19CharacteristicSpacein the outcome-side position.SpaceRefRelationKindstates how those two refs relate. In ordinary use, the token is eithersameDeclaredSpaceAsordistinctDeclaredSpaceFrom.SourceToOutcomeRelationidentifies the source members or values, target outcome values, direction and relation mode, with the defining map, model, operation or rule incarrier. The mode distinguishes a description, projection, prediction, scoring relation or other declared connection; naming it does not establish that its output is accurate or suitable for a receiving use.DistortionPosturestates the conditions and limits needed by the receiving use. A primary token may organize this account or satisfy a selected interface requirement. It does not make the qualifications mutually exclusive: a learned map may also be uncertain and model-dependent. The local tokens includetransparent-for-current-use,lossy-bridge,metric/model-dependent,transition-dependent,uncertainty-bearing,learned/adaptive, andunstable-under-refresh.SourceSetComposition,DerivedViewKind, and related...Kindvalues remain declaration fields or controlled field values unless some governing pattern promotes them; they are not automatically independent heads merely because their names end withKind.
The two reference fields designate A.19 spaces. SpaceRefRelationKind reports whether their resolved values are the same or distinct under A.19 meaning. Two identifiers or declaration documents may describe the same space; different spellings alone establish no distinction. Recover a changed basis, Scale meaning or other space-defining content before asserting distinctness. This local token field is not itself an A.6.5 reusable relation-kind declaration.
A.19.SOURCE-SET-SPACE-SUBSTRATE:4.3 - Substrate declaration laws (SS-0..SS-7)
SS-0 - Required declaration content. Treat a line as declared substrate only if one recoverable source-set basis, two recoverable space refs, one explicit ref-to-ref relation kind, one explicit source-to-outcome relation, and one explicit posture are present together.
SS-1 - Ref typing is preserved.
SearchSpaceRef and OutcomeSpaceRef must resolve to declared A.19 CharacteristicSpace. They do not become parallel space kinds, slot aliases, or role claims.
SS-2 - Source-set recoverability is mandatory.
The reader must be able to recover the source set and its declared family. For a composition, recover every contributing set, its family and its member contribution rule; identify a primary source only when the receiving use distinguishes one. Use SourceSetRef, SourceSetComposition or an accessible source that uniquely supplies the needed identities. A family name alone does not resolve several same-family sources.
SS-3 - Relation requirement must be explicit.
SourceToOutcomeRelation is conforming when its participants, direction, mode and defining map, model, operation or rule are recoverable. Add an interpretive qualifier only when it changes that relation's use.
SS-4 - Posture honesty is mandatory.
DistortionPosture must say whether the line is transparent for current use or qualified by loss, metric/model dependence, transition dependence, uncertainty, learning/adaptation, or instability under refresh. State all material qualifications, even when one primary token is used for indexing. A token alone supplies no error bound, validation result or permission to rely on the outcome.
SS-5 - Conditional and qualifier fields stay subordinate.
SourceSetComposition, DerivedViewKind, BasePaletteRef, OutcomeMapRef, SpaceMetricRef, TransitionRelationRef, and BridgeDistortionNote may clarify the substrate, but they do not replace the required declaration content and do not become mandatory everywhere.
SS-6 - Publication and policy stay outside. Publication metadata, shortlist identity, live-pool policy, and enactment policy remain neighboring decisions. A substrate line may feed them, but it does not decide them.
SS-7 - Admission is fail-closed.
If the source basis cannot be recovered, either space ref is unresolved, SpaceRefRelationKind cannot be chosen, relation direction, mode or carrier remains vague, or a qualification needed by the receiving use is unresolved, then the complete substrate claim is not established. Preserve the recovered source and space facts, state the missing basis and withhold only the use that depends on it. Use the applicable subject pattern when it can supply the missing result.
A.19.SOURCE-SET-SPACE-SUBSTRATE:4.4 - Profiles
Use one of these ordinary profiles:
- Shared-space profile.
SearchSpaceRefandOutcomeSpaceRefboth resolve to the same declaredCharacteristicSpace, andSpaceRefRelationKind = sameDeclaredSpaceAs. - Cross-space profile.
SearchSpaceRefandOutcomeSpaceRefresolve to two distinct declaredCharacteristicSpacevalues, andSpaceRefRelationKind = distinctDeclaredSpaceFrom. - Derived-source supplement.
If the visible source set is derived, make the derivation recoverable. Use
DerivedViewKindandBasePaletteRefwhen the receiving use needs that derivation or would otherwise lose the base palette, as §4.7 specifies.
A.19.SOURCE-SET-SPACE-SUBSTRATE:4.5 - Operational declaration sequence (fail-closed)
When declaring one substrate-bearing line, proceed in this order:
- Entry test. Confirm that the line needs source-set plus search/outcome-space plus relation/posture discipline. If it only needs
CharacteristicSpacetyping, useA.19. If it only needs publication or policy, apply the governing pattern that carries that publication or policy question. - Recover the source basis. For one immediate source set, state its family and recover its identity. For a composition, use
SourceSetCompositionto identify every contributing set, its family and how its members contribute; designate a primary source only when the receiving use singles one out. AddSourceSetRefor cite a source when needed to make an identity unique. - Recover the space refs. Point
SearchSpaceRefandOutcomeSpaceRefto already-declaredCharacteristicSpace. - Choose the ref-to-ref relation kind. Declare
sameDeclaredSpaceAswhen both references resolve to the same A.19 space by value, anddistinctDeclaredSpaceFromwhen their defining contents establish distinct values. If that identity question is unresolved, retain the uncertainty rather than inferring difference from two declarations. - State the source-to-outcome relation. Give direction, mode, and carrier. If one named
OutcomeMapRefor another declared interpretive qualifier carries the relation, cite that qualifier. Otherwise state the relation definition or supplying operation in prose. - State the qualifications. Identify the loss, model or metric dependence, transition dependence, uncertainty, adaptation or refresh limit that affects the use. A transparency claim needs a basis. Retain every material condition; use a primary token when useful for indexing or required by a selected interface.
- Add only needed fields. Add composition, derived-view, base-palette, metric, transition, or bridge qualifiers only when the case depends on them.
- Run the boundary check. If the line starts deciding publication metadata, shortlist identity, live candidate policy, enactment policy, or interpretive-view organization, stop and apply the pattern that governs that question.
Incomplete-account result. An unresolved requirement in steps 1-5 leaves the complete substrate claim unestablished. Apply SS-7: preserve what is known and withhold only uses that require the missing basis. A declared uncertainty is a qualification to preserve, not by itself a failure to identify the substrate.
A.19.SOURCE-SET-SPACE-SUBSTRATE:4.6 - Canonical rewrite forms
The §4.2 schema can express either profile: both space references may resolve to the same A.19 value or to distinct values. Use a block, prose or an existing model account that makes the source, spaces, relation and limitations recoverable. A new block is not required when that content is already sufficient.
A.19.SOURCE-SET-SPACE-SUBSTRATE:4.7 - Conditional fields stay conditional
Use SourceSetComposition when the account consumes several declared source sets. Identify each contributing set and its family, and state how its members enter the source basis, such as a union or specified subsets when that is the construction.
For a single immediate source, SourceSetFamily remains required. For a composition, retain a primary source and its family only when the receiving use distinguishes one. Otherwise the recoverable composition supplies the source basis without inventing a primary family. Neither branch silently changes any contributing set's identity or family.
For example, a comparison may consume the union of declared Front-F and Archive-A without privileging either. SourceSetComposition identifies both sets, their families and the union. No primary SourceSetFamily is required; both space refs and the source-to-outcome rule apply to that declared source basis.
Use DerivedViewKind only when one derived view is active and the reader must be able to recover that derivation.
Use BasePaletteRef only when a derived tradition or palette view would otherwise hide the recoverable base palette.
A.19.SOURCE-SET-SPACE-SUBSTRATE:4.8 - Qualifier refs stay substrate-side
OutcomeMapRef, SpaceMetricRef, TransitionRelationRef, and BridgeDistortionNote are admitted as substrate-side qualifier refs.
Use them when:
- one
OutcomeMapRefor named declared map ref disciplines the source-to-outcome relation; - one metric disciplines spread, neighborhood, or comparison claims;
- one
TransitionRelationRefdisciplines dynamic coupling or transfer; - or one bridge-loss note is the reason the relation is qualified.
These qualifiers help explain the relation. They do not replace the recoverable source basis, the search-side and outcome-side spaces, or the declared relation and its applicable limitations. The source basis may be one set or the composition described in §4.7.
The substrate cites the qualifier definition on which it relies. A later view may introduce its own representational qualification; distinguish that view claim from a change to the source-to-outcome relation. If the underlying relation changes, revise its declaration and recheck dependent uses.
A.19.SOURCE-SET-SPACE-SUBSTRATE:4.9 - Descriptor maps and distance definitions dock here, but do not replace the space refs
When a neighboring line already uses DescriptorMapRef or DistanceDefRef, dock it:
DescriptorMapRefmay realize or qualify the search-side or outcome-side representation requirement, as the current line requires;DistanceDefRefmay realize or qualify the metric requirement over that representation on either side, as the current line requires;- but neither one replaces
SearchSpaceReforOutcomeSpaceRef; - and
CharacteristicSpaceremains a different kind fromDescriptorMap.
Use this rule when a reader could mistake a descriptor map or distance definition for the declared space.
A.19.SOURCE-SET-SPACE-SUBSTRATE:4.10 - Publication and shipping remain downstream consumers
G.5 and G.10 may carry metadata such as SelectorOutcomeKind, SetResultFamily, SourceSetFamily, SourceSetComposition, DerivedViewKind, and BasePaletteRef when one selected or shipped result is being published.
That does not mean G.5 or G.10 defines the substrate.
Read the boundary this way:
- this pattern defines the substrate that later publication must preserve;
G.5publishes selector-facing outcome metadata;G.10ships publication metadata and pins;- neither one redefines the search-side reference, the outcome-side reference, or the source-to-outcome relation.
A.19.SOURCE-SET-SPACE-SUBSTRATE:4.11 - Ordinary and heavier use
Stop with the source set, both resolved spaces, their same/distinct relation, the source-to-outcome connection and its applicable limits. Add composition, derivation, map, metric, transition or Bridge detail only when it changes the receiving use. A later view or publication can reuse this account without copying it into another declaration.
A.19.SOURCE-SET-SPACE-SUBSTRATE:4.13 - Using the substrate with neighboring patterns
Once the substrate is declared, select the neighboring pattern for the remaining question:
- Use
A.19.DECLARED-SUBSTRATE-INTERPRETIVE-VIEWwhen the next requirement is interpretive help over the same substrate. The interpretive view may foreground the line, but it does not become the ontology. - Use
G.2when that interpretation becomes palette-first, tradition-facing atlas work. Keep the base palette and the cited substrate recoverable while doing it. - Use
A.6.Pwhen one passage collapses source set, space ref, interpretive view, atlas view, or map/ref wording into one umbrella word. Repair the wording back to the substrate declaration before adding more theory. - Use
F.18when the problem is label choice or naming-side comparison around this declaration. Naming notes may explain why one head is better named; they do not settle the substrate relation. - Use
A.0when the task is cold-reader glossing of these tokens. Glosses explain the terms; the source, spaces, relation and limitations required by §4.2 must still be recoverable from the account.
If a neighboring use needs a changed source-to-outcome relation or qualification, revise the declaration and reconsider the conclusions that depend on the change. Reuse unaffected content.
A.19.SOURCE-SET-SPACE-SUBSTRATE:5 - Archetypal Grounding
A.19.SOURCE-SET-SPACE-SUBSTRATE:5.1 - System
One QD line keeps saying that one archive is both the search-side role and the evaluation basis. Downstream readers need to see that the same declared CharacteristicSpace can still occupy two different role positions without turning the archive or the descriptor map into the space itself.
In this constructed case, Archive-12 is the selected candidate set. The declared descriptor map assigns behavior Coordinates to its members; the separately declared neighborhood metric is used to assess coverage in that same behavior space.
The archive supplies the candidate members; both space references resolve to the same declared CharacteristicSpace. The descriptor map assigns Coordinates, and the distance and metric define the stated coverage comparison. Selection or archive maintenance can reuse these relations while keeping the archive distinct from the space.
A.19.SOURCE-SET-SPACE-SUBSTRATE:5.2 - Episteme
One synthesis line presents one derived tradition front and then starts speaking as if the visible front were the default meaning of the whole palette.
The visible front stays a derived view over the recoverable palette. AdoptionEstimate@ed=1 supplies the stated conditional source-to-outcome mapping. A later interpretive or atlas view may reorganize the presentation while preserving that mapping and its model limitations.
A.19.SOURCE-SET-SPACE-SUBSTRATE:5.3 - Boundary anti-case
One note says only that "the shortlist front is the published result for the current selector result" and names no source-to-outcome relation, no search-side space, no outcome-side space, and no posture.
This is not a substrate declaration. It is publication metadata over one already-selected set.
Apply G.5 or G.10 to that note.
A.19.SOURCE-SET-SPACE-SUBSTRATE:5.4 - Use-situation spread
Use the pattern this way across different working situations:
A.19.SOURCE-SET-SPACE-SUBSTRATE:6 - Bias-Annotation
- Gov bias. The pattern prefers explicit declaration over convenient shorthand.
- Arch bias. The pattern keeps substrate, interpretive view, and publication consumers separated even when one merged story would read more smoothly.
- Prag bias. The pattern prefers a short substrate declaration that can be reused across search, synthesis, and publication-adjacent lines.
- Qualification bias. Learned or adaptive relations need their applicable uncertainty and model limits. A metric or transition model is added only when the claim uses it.
A.19.SOURCE-SET-SPACE-SUBSTRATE:7 - Conformance Checklist
Apply these declaration checks to the claims and qualifiers used:
A.19.SOURCE-SET-SPACE-SUBSTRATE:8 - Common Anti-Patterns and How to Avoid Them
A.19.SOURCE-SET-SPACE-SUBSTRATE:9 - Consequences
Benefits
- Readers can see what the line is acting on, what spaces it distinguishes, what relation is declared between the two space refs, and what outcome load it claims.
- The source and space declaration can be reused for representation, selector-result declaration and publication.
- Heavier qualifiers such as declared map refs, metrics, transitions, and bridge-loss notes remain usable without being forced into every initial declaration.
Trade-offs
- The line must expose one relation and one posture instead of hiding them in umbrella prose.
- Some cases that used to look "simple" will expose uncertainty or loss that now needs to be declared.
- Neighboring interpretive-view or publication patterns may need to be read as companions rather than assumed from local shorthand.
A.19.SOURCE-SET-SPACE-SUBSTRATE:10 - Rationale
Beyond the space structure defined by A.19, this declaration identifies:
- which declared source set is active;
- which declared space is named in the search-side position;
- which declared space is named in the outcome-side position;
- what
SpaceRefRelationKindsays about those two refs; - how source members are connected to outcome values;
- and the transparency, distortion, uncertainty or error claimed for that connection.
That is why this pattern stops before interpretive views and before publication metadata. If it tried to say less, the load would collapse back into vague space or projection talk. If it tried to say more, it would start absorbing views, fronts, archives, shortlists, or shipping semantics that belong elsewhere.
A.19.SOURCE-SET-SPACE-SUBSTRATE:11 - SoTA-Echoing
A.19.SOURCE-SET-SPACE-SUBSTRATE:12 - Relations
- Builds on:
A.19,A.17,A.18. - Coordinates with:
C.18,C.19,A.15.7,C.24,G.5,G.10,A.19.DECLARED-SUBSTRATE-INTERPRETIVE-VIEW,A.6.P,A.0. - Used by:
A.19.DECLARED-SUBSTRATE-INTERPRETIVE-VIEWand interpretive or atlas methods when a receiving use needs a derived view over the declared substrate. - Does not replace: selector outcome publication, shipping metadata, live pool policy, or enactment planning.
A.19.SOURCE-SET-SPACE-SUBSTRATE:End
Last Updated: 2026-11-22 — upstream FPF commit 7a93d8f8 (github.com/ailev/FPF)