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

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 18:45:20 UTC

A.2:5.3 - A Standard Used in Design Work

An engineering team uses RFC 9110 while designing an HTTP service. Keep these claims separate:

  1. DesignTeam-2 independently counts under ProtocolDesignerSystemRole in the current slice when its signature criterion is satisfied.
  2. For this hypothetical assignment-bound case, suppose the practice has declared ProtocolDesignSystemRoleAssignment under U.SystemRoleAssignment according to A.2.1, and DesignAssignment-1 is one obtaining occurrence with holder DesignTeam-2 and assigned kind ProtocolDesignerSystemRole.
  3. The RFC publication is the source episteme in the direct source-use or external-rule relation selected by the design claim.
  4. In this hypothetical case, recover DesignTeam-2 as the exact actual performer through A.13 with that same obtaining DesignAssignment-1, then let A.15.1 independently admit the dated design Work. Suppose this Work was performed under DesignAssignment-1; F.6 afterward establishes that relation to this same assignment. F.6 identifies neither assignment nor performer, and failed attribution would leave the Work intact. The Work may separately produce a MethodDescription or SystemDescription only through the applicable production claim.