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

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 05:40:05 UTC

C.2.4:18 - Review Matrix and Endpoint Boundary Tests

C.2.4:18.1 - Review matrix

A reviewer should ask:

  • are the named anchors genuinely present rather than presupposed;
  • does the level rest on recoverable meaning rather than tone, formatting, arrows, or columns;
  • is the direct semantic branch explicit, or is a relation route being inferred from presentation alone;
  • are the participants, actions, fields, meanings, conditions, bounds, or ordinary wording required by that branch still hidden;
  • has an intended activity or plan been mislabeled as Tech Work before an occurrence is admitted;
  • if AE justifies a route change, does the publication meet the named receiving pattern’s entry conditions?

C.2.4:18.2 - Endpoint-boundary test

High AE does not by itself authorize endpoint claims, gate claims, or quality ascriptions. If such consequences appear, show which downstream governing pattern takes over.

C.2.4:18.3 - Migration note for false precision

Rigid templates, capitalized labels, or tidy sentence rhythm can simulate articulation. Migration should therefore test whether the claimed branch-appropriate structure, including any required anchors or slots, is really recoverable; if not, the articulation level should drop.