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

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 10:15:17 UTC

C.25:4 - Solution - Q-Bundle normal form

C.25 defines a lightweight normal form for the claim content of engineering quality families. A publisher facing a quality term first decides whether one claim episteme should state:

  • one admissible CHR characteristic, or
  • one structured quality bundle whose measurable slots, scope slots, mechanisms, statuses, and evidence remain explicit.

C.25:4.1 - Endpoint split

Use the single-characteristic branch when one exact U.Characteristic, one declared Scale, and the ordinary CHR laws carry the quality claim. The claim-bearing result is still one C.2.1 episteme about its exact bearer; C.25 adds no bundle record.

Use the Q-Bundle branch when several differently typed contributors are part of one quality claim. The result is one C.2.1 episteme whose ClaimGraph contains the record-shaped Q-Bundle content below.

C.25:4.2 - Q-Bundle shape and identity boundary

The full escalation form is:

Q-Bundle := <Name, QualityBearer, ClaimScope?, WorkScope?, Measures[CHR], QualificationWindow?, Mechanisms?, Status?, Evidence?>

Q-Bundle names a C.25-local record-shaped part of one exact U.ClaimGraph. It is not a new Kernel kind, an independently identified world object, or a second identity beside the enclosing episteme. That episteme supplies the exact claim content, one independently identified QualityBearer as its EntityOfConcern, and the effective U.ReferenceScheme under which the quality claim is read.

The ? is operative: omit any optional slot unless changing it could change the current claim or receiving action. A bundle may therefore contain only Name, QualityBearer, Measures, and one load-bearing scope or window. The full tuple is an escalation aid, not a form every author must fill.

Changing any bundle content that changes the quality claim changes the ClaimGraph and therefore identifies another episteme under C.2.1. A changed layout, form, publication occurrence, or carrier can leave that episteme unchanged. A gate, publication, proxy, comparison, or roll-up cites the exact episteme or one exact C.2.1 ClaimAddress, meaning the exact edition plus an intrinsic claim identity declared by that edition’s ClaimGraph. Later ClaimAddress uses in C.25 mean that same value; a field list or raw record reference is not enough.

C.25:4.3 - Field meanings

  • Name. The engineering quality family label inside the claim content, such as Availability, Resilience, or Security; it is not an identity key.
  • QualityBearer. The one independently identified EntityOfConcern of the enclosing claim episteme. It may be an exact U.System, U.PromiseContent, U.Episteme, or another exact entity under its direct identity pattern. When selected organization is the subject, use one A.22 U.Structure with exact constituents, selected obtaining relations, applied constraints, and one selection-use frame. A list of local system-role kinds and assignment occurrences does not by itself identify a bearer.
  • ClaimScope / WorkScope. USM sets over U.ContextSlice describing where the claim holds or where the capability’s deliverability claim may be evaluated. These are set-valued scope objects, not characteristics.
  • Measures[CHR]. One or more admissible CHR characteristics, each bound to one declared scale.
  • QualificationWindow. The temporal policy under which the quality claim is judged.
  • Mechanisms / Status. References to realizations of operation families declared in U.Mechanism epistemes, control presences, certification states, or other named gating prerequisites. They are not measurements.
  • Evidence. Anchors that justify the measures, mechanisms, or scope claims.

C.25:4.4 - Guard reading

A quality guard is conjunctive only over the truth conditions that the current claim actually declares. For example:

declared scope covers TargetSlice AND declared measures satisfy their own laws AND each other declared prerequisite holds

An absent optional slot contributes no condition. Each measure keeps its own Scale and comparison law; a trade-off, alternative, weighted combination, or partial order must be stated under the pattern that defines it rather than being smuggled into AND. If this typed decomposition cannot express what makes the claim true, do not force the family into C.25.