Library / First Principles Framework (FPF) - Core Conceptual Specification
Jump to passage
In this reading

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 05:29:54 UTC · snapshot created 2026-10-03 05:30:57 UTC · last check 2026-10-03 06:35:10 UTC

A.6.6:12 - Relations

Specialises A.6.P Relational Precision Restoration. A.6.6 handles basedness wording by recovering the actual dependent, base, and direct relation, then stopping or opening only the additional object required by a named use.

Builds on A.6.REL and A.6.0. The direct pattern supplies relation obtaining and occurrence identity. A reusable RelationSignature is justified only for an already admitted relation kind and shared declaration content; the declaration form alone establishes no occurrence.

Builds on A.6.5 only when reusable declaration content is current. SlotKinds, ValueKinds, and reference modes type participant positions inside that RelationSignature; an ordinary one-case assertion needs no SlotSpec record.

Coordinates with A.2.4 and A.10. A.2.4 states the exact evidence-use relation. A.10 represents the independently established sources, Work, result epistemes, carriers, provenance, currentness, and later-use relations needed for bounded reliance. Neither pattern admits generic verifiedBy or validatedBy edges, and Work is not an evidence carrier.

Coordinates with A.14 and C.2.1. Constructive grounding and empirical grounding retain their exact direct predicates and participants. Their assertion epistemes and evidence remain separate from the world-side relations.

Coordinates with A.6.3 and A.6.4. A.6.3’s viewing construction keeps the source and receiving epistemes distinct with the same exact EntityOfConcern. A.6.4 retargets between different exact EntitiesOfConcern; its retargeting arrow r, bounded-use assertion q, current-case judgement, operation application, and Work remain distinct. Ordinary aboutness alone selects neither construction. A.6.6 adds no second arrow or universal relative-to object.

Coordinates with F.9 and ReferencePlane rules conditionally. F.9 applies only to an obtaining Bridge between two exact F.17 cells and keeps its bounded-use claim separate. A ReferencePlane crossing uses its applicable plane relation. If both are current, state both; if only one is current, introduce no object from the other branch.

Coordinates with A.2.6, A.7, and E.24.UK: A.2.6 governs scope and explicit Γ_time; implicit “latest/current” remains inadmissible. A.7 keeps EntityOfConcern, Description-episteme, specification use, and publication face, form, unit, carrier, and rendering distinct. E.24.UK supplies the kind-admission boundary applied in A.6.6:4.1.

Coordinates with C.3.3 and E.18. C.3.3 supplies U.KindBridge only for an independently established cross-local kind correspondence, with its exact kinds, direction, declared CL^k, and use/loss conditions; different participant kinds alone establish no KindBridge or silent re-typing. E.18 retains the meanings of its assurance operations on U.Transfer, including CalibrateTo, CiteEvidence, AttributeTo, and ConstrainTo; A.6.6’s declaration-change labels do not replace them.

Coordinates with E.8, F.0.1, F.15, and F.17: E.8 governs pattern-authoring order and SoTA discipline. F.0.1 recovers exact source-local meaning; F.17 supplies an optional durable sense address or basis relation. F.15 supplies the carrier/source-currentness, provenance, and refresh validation harness when that validation is current.

Feeds E.10, E.10.D1, and F.18 lexical governance. Umbrella words trigger recovery of the direct relation. Ordinary relation-specific prose remains valid; notation and durable public names are added only for a named use.