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

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 05:29:54 UTC · snapshot created 2026-10-03 05:30:57 UTC · last check 2026-10-03 07:00:10 UTC

C.11:4.5.1 - Always explicit versus conditionally activated objects

The following objects should be explicit in every usable C.11 decision record:

  • DecisionSubject and DecisionSubjectGranularity;
  • OptionSet;
  • one evaluative basis through PreferenceOrder or EvaluativeMeasure;
  • BeliefState;
  • OutcomeModel;
  • ChoiceRule;
  • ChoiceResult.

The following objects activate when the case needs them:

  • InterventionModel for causal repair;
  • CounterfactualModel plus SubjunctiveDependenceRelation for success-first or predictor-coupled repair;
  • ProbeActionSet, ProbeBudget, CostToProbe, ValueOfInformation, and ValueOfComputation when one more probe or one more computation pass is still live.

What matters is not that every decision record mechanically mentions every token. What matters is that the current comparison does not smuggle one active question without naming the object that carries it.

Immediate lexical commitments:

  • the default chooser term is DecisionSubject, not Agent;
  • DecisionSubjectGranularity names the chooser-bearing level when the question is about whether the chooser is one person, team, organization, or another collectivity-bearing system rather than one generic scalar or coordinate;
  • relation-heavy wording remains answerable to A.6.P together with A.6.5.

Local plain glosses for the load-bearing inventory:

  • DecisionSubject: who or what is actually carrying this choice now, whether that is one person, one team, one committee, one organization, or another collectivity-bearing system;
  • DecisionSubjectGranularity: the level at which the choice is being attributed, such as person-level, team-level, or organization-level rather than one vague “agent” label;
  • OptionSet: the concrete options already on the table now;
  • PreferenceOrder: the current better-than / worse-than ordering over those options for this decision subject;
  • EvaluativeMeasure: the explicit utility-style or desirability-style scoring measure used when the case needs magnitudes, thresholds, or trade-offs rather than only one ordering;
  • BeliefState: the current uncertainty-bearing state about the world, the case, and the likely consequences of the options;
  • OutcomeModel: the model that maps options plus the current uncertainty picture to the consequences that matter for this choice;
  • InterventionModel: the part of the model that says how the world changes because one option is actually taken;
  • CounterfactualModel: the model used to compare relevant non-actual alternatives or alternate decision procedures;
  • SubjunctiveDependenceRelation: the dependence between this choice and one predictor, one linked chooser, or one structurally similar decision procedure when intervention talk alone is not enough;
  • ChoiceRule: the current choice doctrine or operator that says what conditions make choose now, reject current set, probe again, or reroute lawful in this case;
  • ChoiceResult: the emitted result record saying which of those lawful choice results actually follows now under the current ChoiceRule;
  • ProbeActionSet: the further checks, measurements, simulations, or questions that can still be run before commitment;
  • ProbeBudget: the remaining time, money, attention, or tolerated delay available for those pre-choice probes;
  • CostToProbe: the real cost of another measurement, question, simulation, trial, or delay before commitment;
  • ValueOfInformation: the expected gain from learning more before choosing;
  • ValueOfComputation: the expected gain from spending more reasoning or compute before choosing.

What follows from DecisionSubject being wider than Agent:

  • the chooser in C.11 need not be one person-like agent;
  • a team, committee, organization, or coupled human-tool system may be the DecisionSubject when that is the real level at which the choice is being made;
  • the pattern therefore does not force agency characterization to do the job of naming who or what is currently choosing.

This floor is enough to keep choice doctrine inspectable and stable. It does not yet assume one full branch-specific quantum-like package or one cross-scale geometry-heavy package.