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

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 15:41:27 UTC · snapshot created 2026-10-03 15:43:46 UTC · last check 2026-10-03 15:55:10 UTC

A.21:4.3 - Profile application

A GateProfile describes a policy. It does not show that the policy applies. Every gate decision points to the current application of one profile rule. That application identifies:

  • the profile rule and edition;
  • the gate, decision subject, and bounded action to which it applies;
  • its scope and qualification window;
  • the complete required and optional check set;
  • the mapping rule for each applicable source outcome;
  • the consequence attached to each aggregate decision; and
  • any separately required authority or responsibility relation.

A.21 has no implicit default profile. A branch name, PathSlice, sentinel, publication mode, product label, or earlier decision does not select or authorize a profile. A new slice may bound changed data or trigger reevaluation; it cannot weaken inherited safety, regulatory, evidence, or other obligations. Any weakening needs another current rule application that permits it and any authority relation required for that change.