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

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 08:01:07 UTC · snapshot created 2026-10-03 08:04:31 UTC · last check 2026-10-03 08:15:20 UTC

E.17.ID.CR:5 - Archetypal grounding

Worked-slice note. Use the system case, episteme case, and worked boundary examples as a heterogeneous example bank, not as one recommended progression. They show different bounded outcomes for the same governing pattern: some cases stay small and stop, some stay mixed with a neighboring pattern, and some reopen or apply another governing pattern when outside observations, environmental change, or downstream constraints change what the comparative review unit can honestly carry. Complete the seven-row card for the current comparison unit; if the boundary trigger fires, stop here or apply the governing pattern for the crossed claim.

E.17.ID.CR:5.1 - Tell

ComparativeReviewUnit names the bounded middle band where a team prepares one explicit bounded comparison over source epistemes or source publications with already declared references, while any stronger crossed claim remains outside until the governing pattern for that claim is named. The comparison unit is the bounded comparative review unit. That review unit stays modest enough that a reviewer can still see the shared review frame, the same EntityOfConcernRef when the compared sources describe the same entity, the declared comparison criterion, the blocked downstream claim or effect, and the boundary trigger that would end interpretation.

E.17.ID.CR:5.2 - Show (System)

Source slice. Two pinned operating notes describe the same service episode from different operational responsibilities. One note has its source reference in the maintenance log, the other in the continuity dashboard for the same declared episode and the same EntityOfConcernRef.

Comparative review unit. Under the declared comparison criterion, the maintenance note foregrounds operator-induced variance, while the continuity note foregrounds buffer-sensitive drift; each view exposes a blind spot in the other without granting direct substitution.

Why this stays here.

  • source relation and source references are explicit;
  • the same EntityOfConcernRef remains preserved;
  • one bounded comparative lift is added;
  • no substitution licence is added;
  • no rival action-selection question is yet being asked.

E.17.ID.CR:5.3 - Show (Episteme)

Source slice. Two pinned analytic renderings over the same evidence set are already available for review. One rendering is a SourceLinkedExplanationReconstruction on a TechCard face; the other is a compact comparison sheet that preserves the same evidence set and the same described operational episode.

Comparative review unit. For maintenance reviewers, the reconstruction foregrounds operator load more than the comparison sheet, while the comparison sheet foregrounds recovery sequencing more than the reconstruction; this difference is useful for review, but it is not yet a design recommendation or an action-selection claim.

Why this stays here.

  • the base-case governing patterns remain identifiable;
  • the comparative lift is explicit and bounded to one reviewer task;
  • explanation-face governance and same-entity transform discipline remain with their neighboring patterns;
  • authority-bearing use and prompt-bearing action-selection pressure remain governed by their neighboring patterns.

E.17.ID.CR:5.4 - Worked boundary examples

E.17.ID.CR:5.4.1 - Lower-boundary stance-note case

Stance-note unit. F.9 already records an obtaining Bridge and a bounded-use claim for reading the local maintenance-pressure term alongside the partner continuity term. This separate note says that, for that use, the relation is best read as asymmetry-explicating rather than substitution-friendly.

Why it stays under F.9.1:

  • the Bridge and bounded-use claim already exist;
  • the note only makes the claim easier to read; and
  • no bounded comparative lift beyond that stance note is added.
E.17.ID.CR:5.4.2 - Mixed primary-pattern composition with A.6.3.RT

Base-case rendering. A same-entity comparison sheet retabulates one pinned incident note into columns for trigger, pressure, and recovery.

Comparative review unit. In the retabulated view, the recovery column makes the operator-induced asymmetry easier to inspect than the trigger column, but the table is not treated as establishing a new causal hierarchy.

Why this remains mixed rather than collapsing:

  • A.6.3.RT still governs the base representation shift;
  • bounded comparison is secondary and only adds a bounded comparative lift;
  • most restrictive forbidden-use constraint wins, so no new ontology or gate claim is licensed.
E.17.ID.CR:5.4.3 - Mixed primary-pattern composition with E.17.EFP

Base-case rendering. A TechCard-face explanation rendering is already classified as SourceLinkedExplanationReconstruction and publishes a bounded connective policy.

Comparative review unit. For maintenance reviewers, this rendering foregrounds the difference between operator load and throughput pressure more than the original prose, but it is not treated as a design-level recommendation.

Why this stays mixed rather than collapsing:

  • E.17.EFP still governs explanation class and face bounded use;
  • bounded comparison only adds bounded comparative use for one reviewer task;
  • E.17.EFP still governs explanation-face use; any authority-bearing use must name its governing pattern.
E.17.ID.CR:5.4.4 - Guided review aid with bounded interaction mode

Source slice. A reviewer UI presents two already pinned source notes side by side for the same described operational episode.

Guided comparative review unit. Question: which note foregrounds variance introduced by operator timing rather than environmental drift? Bounded comparative use: bounded comparative triage only. Misuse risk: do not treat this aid as action selection or release guidance.

Why it stays here:

  • the interaction mode is explicit but still bounded;
  • the review unit answers one contrastive question rather than creating prompt pursuit or action-selection pursuit;
  • bounded use and overread risk are visible instead of being smuggled into interface tone.
E.17.ID.CR:5.4.5 - Product and design-review comparison case

Source slice. Two already available design-review notes describe the same integration boundary for the same planned release. One note foregrounds coupling and rollback pressure; the other foregrounds delivery simplicity and lower immediate implementation cost.

Comparative review unit. For architecture review, the first note foregrounds coupling risk more than the second, while the second foregrounds delivery simplicity and lower immediate implementation cost more than the first; that asymmetry is useful for discussion, but it is not yet a recommendation to choose either option.

Working-boundary use. This is the ordinary stay-here case: the shared review frame, bounded comparative lift, and outside-work boundary are already explicit, so the bounded comparative review move itself stays primary.

Why it stays here:

  • the same planned release remains the EntityOfConcernRef;
  • one bounded comparative lift is made explicit for a declared review task;
  • the unit helps design discussion without quietly becoming action selection or approval.
E.17.ID.CR:5.4.6 - Compliance and release-review comparison case

Source slice. An internal control checklist and a vendor compliance bulletin are already available for the same release candidate and the same declared control scope.

Comparative review unit. For release review, the vendor bulletin foregrounds protocol conformance more than rollback evidence, while the internal checklist foregrounds rollback evidence more than protocol conformance; this comparison helps frame the review, but it is not yet a release gate or equivalence claim.

Working-boundary use. This is the same stay-here case under release or compliance pressure: the comparison unit is already stable enough, so the primary question is the bounded contrast rather than local repair or PublicationUnit stabilization.

Why it stays here:

  • the comparison criterion is explicit and bounded to one review task;
  • the source references remain visible and the same release candidate stays in view;
  • the review unit helps an engineer-manager see a review asymmetry without laundering gate authority.
E.17.ID.CR:5.4.6.a - Research-review comparison case

Source slice. Two already available research syntheses discuss the same measured phenomenon and the same declared evidence slice. One synthesis foregrounds variance decomposition limits more; the other foregrounds protocol repeatability more.

Comparative review unit. For method review, the first synthesis foregrounds variance decomposition limits more than the second, while the second foregrounds protocol repeatability more than the first; this asymmetry helps frame the discussion, but it is not yet a method choice or a claim that one synthesis is globally better.

Why it stays here:

  • the same measured phenomenon remains the EntityOfConcernRef;
  • the comparative lift is bounded to one review task;
  • the unit helps research discussion without quietly becoming action selection or ontological reframing.
E.17.ID.CR:5.4.6.b - Program and cultural-review comparison case

Source slice. Two already available programme briefs discuss the same continuing initiative and the same declared participation scope. One foregrounds continuity of community engagement more; the other foregrounds short-term event visibility more.

Comparative review unit. For programme review, the first brief foregrounds participation continuity more than the second, while the second foregrounds short-term visibility more than the first; this comparison helps frame the discussion, but it is not yet a funding, curation, or programme-direction decision.

Why it stays here:

  • the same initiative remains the EntityOfConcernRef;
  • the comparison criterion is explicit for one declared review task;
  • the unit helps programme discussion without laundering decision authority.
E.17.ID.CR:5.4.6.c - Exogenous-change stop-and-reopen case

Source slice. An internal release-review comparison sheet already compares one control checklist and one vendor bulletin for the same declared release candidate and the same control scope. Mid-review, an external incident bulletin arrives and changes the rollback assumptions governing use of that same candidate.

Initial comparative review unit. Before the new bulletin, the vendor bulletin foregrounds protocol conformance more than rollback evidence, while the internal checklist foregrounds rollback evidence more than protocol conformance; this comparison frames the review, but it is not yet a release gate or equivalence claim.

Working-boundary follow-through. This case begins on the same stay-here case as E.17.ID.CR:5.4.6, but outside observation then changes the declared comparison criterion, so the unit stops and reopens instead of being carried forward by inertia.

Why this stops and reopens.

  • the new outside observation changes the declared comparison criterion;
  • the previous bounded comparison can remain traceable, but it cannot continue by inertia as if the same governing review conditions still held;
  • the bounded next use is either to restate a fresh comparative review unit over the new declared criterion or to apply a neighboring governing pattern if downstream gate or authority question has now become primary.
E.17.ID.CR:5.4.6.d - Lighter comparison note with source-return discipline

Source episteme and source publication set. A release team already has the full internal rollback worksheet, vendor bulletin, and incident-note bundle for one release candidate. A short comparison note is then prepared for the daily review stand-up.

Comparative review unit. For today's review, the vendor bulletin foregrounds protocol conformance more than rollback evidence, while the internal rollback worksheet foregrounds rollback evidence more than protocol conformance; this short note is only a review aid over the same release candidate, and the full source episteme or source publication set remains primary for any bridge, release, coarsening, or work or reliance claim.

Why it still stays here:

  • the comparison unit is still one bounded comparative review unit, not a replacement for the source episteme or source publication set;
  • the note remains source-pinned through the already available source episteme or source publication set, and bridge, gate, or work or reliance use remains with the governing pattern for that claim;
  • any attempt to treat the short note as enough for equivalence, release approval, execution claim or effect, or a reduced-use source substitute requires source-bearing return, A.6.3.CSC Controlled Semantic Coarsening, or another neighboring pattern.
E.17.ID.CR:5.4.6.e - Functional versus constructive-description comparison

Source slice. A functional-description publication and a constructive publication or product-description publication describe the same pumping skid. The functional description foregrounds flow relation and method-selection relation; the constructive description foregrounds module composition and installed equipment.

Comparative review unit. For design review, the functional description foregrounds what the skid is supposed to do in the declared flow relation, while the constructive description foregrounds what parts are present. This contrast helps the engineer keep function and construction separate, but it is not a module-equivalence claim, a performed-work record, or a gate decision.

Why it stays here:

  • both source publications keep source references and remain inspectable;
  • the same pumping skid remains the EntityOfConcernRef;
  • the bounded comparative lift is the function-versus-construction contrast for one review task;
  • module equivalence, work occurrence, evidence, and gate claims remain blocked downstream uses.
E.17.ID.CR:5.4.6.f - Method-option comparison without method choice

Source slice. Two method descriptions are already pinned for the same fabrication task. One foregrounds lower setup cost; the other foregrounds tighter result-measurement discipline.

Comparative review unit. For method review, the description of method M-1 foregrounds lower setup cost more, while the description of method M-2 foregrounds tighter result-measurement discipline more. This comparison helps prepare method discussion; method choice, a work plan, and evidence that either method has been performed remain outside it.

Why it stays here:

  • the reviewed source epistemes are pinned;
  • the comparison criterion is explicit;
  • no selected-method, work-plan, performed-work, evidence, or engineering-justification claim is added;
  • if the team chooses a method or prepares a work plan, record the selected method as project U.Method, record the work plan as U.WorkPlan under A.15.2, and use A.15.1 only when a dated U.Work occurrence is the governed occurrence claim.

Nearest neighboring-work examples. The next four cases are the nearest worked boundaries for prompt pressure, same-entity viewing, ontology shift, and gate or authority misuse. Use them when the near-top negative-boundary rows fit and you need one worked cue for keeping the comparison unit from carrying outside work.

E.17.ID.CR:5.4.7 - Upper-boundary prompt-bearing case

Prompt-bearing review unit. “This contrast raises the question whether both systems are being constrained by the same hidden gating variable, so we normally publish a U.AbductivePrompt around that shared control possibility.”

Why ComparativeReviewUnit no longer governs:

  • abductive-prompt or action-selection claim governs the next action;
  • the review unit is now prompt-bearing rather than only interpretive;
  • the selected governing pattern is B.5.2.0 or B.5.2 through explicit U.AbductivePrompt publication.
E.17.ID.CR:5.4.8 - Same-entity viewing boundary case

Viewing rendering. The source note is retabulated into a compact comparison sheet that preserves the same claims and entity but makes pressure, trigger, and recovery fields easier to inspect.

Why it does not enter interpretation:

  • the main question is representational reshaping rather than bounded comparison;
  • no bounded asymmetry or interpretive claim is added;
  • the more precise governing pattern is A.6.3.RT.
E.17.ID.CR:5.4.9 - Ontology-boundary anti-case

Ontology-pressuring review unit. The older maintenance note and the new field-observation note are best treated as two observational cuts over the same latent failure mode, so we normally recast both under a new operational kind and treat the source labels as legacy labels.

Why ComparativeReviewUnit no longer governs:

  • the case is now asking for a same-referent interpretation with continuity-witness demand or retargeted-EntityOfConcernRef interpretation;
  • continuity witnesses would now be needed;
  • bounded comparative interpretation is no longer enough, so the case applies OntologicalReframing.
E.17.ID.CR:5.4.10 - Authority and gate misuse anti-case

Authority-pressuring review unit. Because this comparison consistently foregrounds the safer operating condition, reviewers can use the review unit directly as a release gate and do not need the underlying source episteme or source publication during triage.

Why ComparativeReviewUnit no longer governs:

  • the review unit is being overread as gate-facing authority;
  • the bounded comparison has become a substitute for the source episteme or source publication;
  • the release-gate claim is governed by A.21 and the applicable release policy; use A.20 only for an internal-constraint check that meets its transformation-flow conditions.
E.17.ID.CR:5.4.11 - Invalid publication and repair example

Invalid review unit. These two views describe the same entity for current operations, so the team can use whichever wording is easier.

Why it is invalid here:

  • no source references are visible;
  • bridge-mediated comparison is being implied without an explicit obtaining Bridge and bounded-use claim;
  • blocked substitution and authority claims are being smuggled in through soft phrasing.

Minimal repair. Under Bridge B-12, bounded-use claim UC-12 has B-12 as its EntityOfConcern and says, with affirmative polarity, that the source-note-to-receiving-note direction is suitable for comparing only the operator-timing concern in this review task; the remaining source distinctions are tolerated loss, not substitution. A current A.10 result supports relying on UC-12 for that exact use. Both notes foreground the concern, but they are not substitution-equivalent and the source episteme or source publication set remains primary. The pattern for the proposed review decides authorization, and evidence of the review Work says whether it occurred. Card BC-12 may be cited when that optional package is useful.

What the repair does:

  • restores the source references and verifies bridgeOccurrenceRef, the bounded-use claim’s EntityOfConcern, its use/direction/rule/loss/polarity tuple, and current A.10 reliance for that exact positive use, while keeping any bridgeCardRef optional;
  • narrows the claim back to bounded comparison and leaves authorization and the occurrence of comparative-review Work to their own patterns and evidence;
  • reasserts the blocked downstream claim or effect.