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

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 08:25:59 UTC · snapshot created 2026-10-03 08:26:43 UTC · last check 2026-10-03 09:55:09 UTC

A.6.RSIR:2 - Problem

Without this pattern:

  1. Lexical cues create shadow kinds. Interface, role, slot, endpoint, and function words become local root kinds because they sound technical.
  2. Participant, declaration, and representation uses become system roles. A direct relation-participant meaning, declaration-local SlotKind, argument, field, endpoint, or representation position is renamed as a system-role kind. Evidence-use, transformation, and interface claims then lose their direct relations and patterns.
  3. System-role kinds become declaration or representation labels. A real context-local system-role kind is demoted into a declaration-local SlotKind or source-schema field, so its KindSignature, exact assignment occurrence and window, SystemRoleAssignmentStateRelation, and Work consequences can no longer be recovered.
  4. Signatures absorb implementations. A law-governed U.Signature is used as if it were a mechanism, method, work-start gate decision, interface conformance proof, or publication.
  5. Participant, declaration, application, and representation boundaries are skipped. A field or parameter is edited without deciding whether it denotes a direct relation-participant meaning or actual participant, a declaration-local SlotSpec, an A.6.1 argument or result declaration, one exact operation application and actual binding, or a position in a selected representation.
  6. Evidence and status uses keep old role grammar. An episteme, standard, report, publication, or badge is said to have a role instead of being used in an evidence-use, source-use, status-use, publication-use, assurance-use, or gate relation.
  7. Neighboring patterns are copied locally. A pattern repeats negative catalogues such as “not proof, not permission, not gate” instead of recovering the current object and applying the pattern that defines or constrains the claim.