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

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 17:24:51 UTC · snapshot created 2026-10-03 17:30:20 UTC · last check 2026-10-03 19:05:20 UTC

A.6.A:4.9 - Lexical guardrails

In Tech prose and normative prose:

  • bare affords, invites, calls for, actionable, ready for, ripe for, natural next step, the model wants, or the interface tells MUST NOT appear without immediate repair;
  • actionable insight MUST be made precise as the actual claim, candidate action, question or missing basis; use C.16.Q when the claim is evaluative;
  • affordance MUST NOT be treated as a monadic property of a site participant without enactor, site, and coupling frame;
  • an invitation MUST NOT be presented as if it were already a duty, gate, or work occurrence;
  • a latent policy cue MUST NOT be presented as if it were already an explanation;
  • articulationHint MUST NOT be treated as F, as acceptance status, or as a replacement for A.16 grounding references;
  • generic Surface facet tokens MUST NOT be introduced inside A.6.A; publication face, publication form, interop publication form, carrier, or rendering participation must be declared under A.7 and publication-face and publication-form discipline, not by widening the site classification;
  • hidden enactor language inside adjectives such as graspable, deployable, actionable, ready SHALL be unpacked;
  • quoted metalinguistic uses are allowed, but SHALL be marked as token-under-discussion.