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:10:20 UTC

C.2.6:4 - Solution

U.LanguageStateAnchoringMode is a nominal characteristic that states the primary anchoring regime of the U.Episteme named by the current position claim: bodily enactment, trace, model state, document, operator loop, or an explicit mixed regime. If source anchoring and current publication-face anchoring differ, both shall be distinguished rather than collapsed.

C.2.6:4.0a - Kind and characteristic boundary

U.LanguageStateAnchoringMode is a dependent durable characteristic value under the declared U.LanguageStateSpace / U.CharacteristicSpace boundary, not a root U-kind. Its identity is the anchoring-mode basis slot and nominal family for episteme publication positions. This characteristic does not decide evidence, source-currentness, publication-face, carrier, Work, gate, or reliance claims; those claims retain their own definitions and tests.

C.2.6:4.1 - Starter family

ModeReadingTypical evidence anchor
AM.EmbodiedFeltbodily or kinesthetic anchoring matters directlyembodiment note, felt trace, human witness
AM.TraceAnchoredtraces, logs, telemetry traces, or observations anchor the epistemetrace references, measured events, observations
AM.ModelLatentlatent or internal model state is the key anchormodel-state refs, probe results, latent summaries
AM.DocumentMediateddocument or description is the principal anchordocuments, cards, method-description text
AM.OperatorLoopthe episteme is directly tied to operator intervention or console controloperator witness, console event, policy hook
AM.Mixedmore than one anchoring mode matters substantivelyexplicit component list and why the mix matters

C.2.6:4.2 - Contribution boundary

U.LanguageStateAnchoringMode is an anchoring-mode characteristic for one U.Episteme position claim. It is not a representation factor bundle, closure state, truth status, evidence relation, source-currentness relation, Work claim, gate claim, or reliance permission by itself. Model-latent, operator-loop, embodied, trace, and document-mediated cases name where the episteme is anchored for the current claim. A publication-face, carrier, source-currentness, bridge-loss, Work, evidence, or gate claim needs its applicable definition or test; anchoring mode alone does not decide it.

If embodiment matters, it shall be declared here or immediately beside this characteristic rather than being hidden inside representation talk.

C.2.6:4.3 - Mixed-mode rule

AM.Mixed is admissible only when the component modes are named explicitly. “Mixed” shall not stand in for an undetermined anchoring mode.

C.2.6:4.4 - Bridge implications

An anchoring shift can matter when a receiving use needs a semantic relation between local senses from different semantic contexts. A shift from AM.EmbodiedFelt or AM.ModelLatent source anchoring to AM.DocumentMediated publication-face anchoring may provide evidence about an F.9 Bridge or bounded-use claim. Use F.9 to state and test the Bridge and the separate bounded-use claim, with its evidence and loss account. Use F.9.1 only for a separate optional stance note about that claim.