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 02:22:15 UTC · snapshot created 2026-10-03 03:38:22 UTC · last check 2026-10-03 04:15:10 UTC

A.19.CN:8.4.2 - Assurance CN‑frame — evidence freshness and related local meanings

Entity graph view:

NormalizationMethodInstance ── used for ──> characteristic re-expression
F.9 Bridge ── relates ──> exact source and target F.17 cells
ComparisonClaim ── cites ──> normalization instance and/or Bridge-use claim
RelianceClaim ── cites ──> evidence status and assurance limits

The normalization instance identifies the declared re-expression and its validity window. The Bridge identifies only an obtaining relation between two exact local senses. A comparison that relies on either one says so in its own use claim; its evidence and assurance limits remain explicit.

Relational stub:

TableKey columns (essential)
NORMALIZATION_METHODNORMALIZATION_METHOD_ID; KIND; DESCRIPTION_REF
NORMALIZATION_INSTANCENORMALIZATION_INSTANCE_ID; NORMALIZATION_METHOD_ID; SRC_CHAR_ID; TGT_CHAR_ID; FORMULA_SPEC_OR_LUT_REF; VALIDITY_WINDOW; EVIDENCE_REF
BRIDGEBRIDGE_ID; SOURCE_CELL_REF; TARGET_CELL_REF; DIRECTION; CORRESPONDENCE_RULE; APPLICABLE_USE; TOLERATED_LOSS
COMPARISON_USEUSE_CLAIM_ID; RESULT_REF; NORMALIZATION_INSTANCE_ID?; BRIDGE_ID?; EVIDENCE_USE_REF; ASSURANCE_REF?
ASSURANCE_EVENTAE_ID; USE_CLAIM_ID; EFFECT; DETAILS; WINDOW

The tables make an audit path possible without assigning meaning to the table itself. A low-assurance relation, stale normalization instance, or refreshed evidence can be recorded as a distinct event and can reopen only the comparisons that rely on it.