Jump to text
On this page
Copy and source
Published source confirmed at last check

Source changed 2026-11-22 12:18:55 UTC · snapshot created 2026-11-22 12:19:56 UTC · last check 2026-11-22 12:35:20 UTC

Library.Reference:6.2.2 - Unified term sheet for scales, layers and model abstraction

At first reading, ask what the question itself asks the recipient to compare. An author may give a whole System as material for a question about one part, or use one part to ask about a repeatable relation. In “at all levels”, recover the kind of holon and the part–whole relation, the functional ordering of layers, or the comparison of models for one inquiry. Where several are involved, identify how they are connected in the requested conclusion. “All” can range over the branches relevant to that question. C.39.QR:4.1.1, Recover what “all” covers

To choose a word for a project document, start with what you want the recipient to compare. How long is the system? Which systems make up its enclosing whole? Which functions take part in control? Which Methods make their performance possible? Which situations admit the claim? What does a more concrete model determine for the same decision? The answers can vary independently. A branch office can occupy two buildings while remaining one unit of the service. Two investigations can each cover fifteen offices and cover different offices. State the physical quantity, composition relation or covered population that answers your question.

Use the three settled model-comparison rows directly. Model refinement and model abstraction are converses for the same inquiry and interpretation. In a chain established by that comparison, L0 to L4 reads towards more abstract models and L4 to L0 towards more concrete models. A strict difference requires a feasible more concrete model whose completions preserve the earlier commitments and exclude an answer the more abstract model admits. These are the existing UTS.ModelRefinement.2026-11-16, UTS.ModelAbstraction.2026-11-16 and UTS.ModelAbstractionLevel.2026-11-16 with their original cells and NameCards. F.17:12.6 · F.18:4.5 · B.5.MR:4.2

To choose the composition scales and model abstraction for a task, start with the difference the recipient must be able to act on or explain. Follow the relevant part–whole relation for each kind. Test what becomes impossible to decide if the model merges two allowed situations, and which choices can remain open. A bound or common argument may cover the whole range. C.39.SA:4, Choose Composition Scales and Model Abstraction for the Task

For a range of composition, name the kind of whole and the relation through which its parts belong. Two ends can identify a range on a given chain. In a branching structure, say which branches or members the question includes when the ends leave that open. The question may call for a property at each scale, a relation across scales or a result of several contributions together. For each kind, follow the range its part in the answer requires. Across kinds, establish the relation that connects them. A Work can enact a Method, a report can describe that Work and two reports can draw on one observation. A change in how many composition scales a model represents can leave unchanged the distinctions it makes for a given question. If the relation is already clear, ordinary terms such as part, level and layer remain usable.

F.18 naming decisions. Each key below identifies a separate NameCard NC.RangeTerms.<key>. It concerns the kind defined by the cited owner in this edition. The selected designation is the Tech expression. The explanation gives the Plain reading for discussion. It also specifies the local sense of that expression under the FPF Core scheme. The last column records why a plausible competing term changes the inference.

KeySelected designation and ownerLocal sense for this useCompeting reading and reason for the choice
SizeScaleScale, A.18, C.16.P:4The CSLC kind of an organized set of possible values for a specified Characteristic, with its permitted comparisons and operations. Say measurement scale in discussion.A common scale can be used to report many different physical sizes.
SizeValueCoordinate, A.18, C.16.MRThe CSLC kind of a single value in the domain of a declared Scale. To report physical size, name the system, characteristic such as overall length, measurement conditions and unit where applicable. Give the supported coordinate, or report the supported interval, set or bound when the information warrants only that. A known upper bound on length can settle a clearance decision. For two otherwise comparable lengths of 2 m and 3 m, the scale stays the same while the coordinates differ.A coordinate alone identifies neither the system measured nor the body of evidence that supports the measurement result.
SystemComponentOf, A.14, B.1.2:4The A.14 structural-component relation kind. For system composition, identify both systems and establish the integration of the component into its encompassing system. A chain of those relations supports talk of system-composition levels.Two systems can differ greatly in length without standing in this relation.
MethodMethodPartOfRelation, B.1.5, B.1.5.CM:4The relation kind whose ordered participants are the independently identified part Method and whole Method. The whole’s stable construction requires its contribution or admits it as an alternative for a required contribution. Follow the relations to describe Method-composition levels.A supplier can provide an input from outside that Method. An admitted alternative retains membership even on a day when another was selected.
WorkOperationalPartOf_work, A.15.1:4.1a, B.1.5.EW:4The operational-part relation kind between two independently identified Work occurrences. The performed content of the first is constitutive of the second at the stated operational grain. Use Work-composition levels along this relation.For a proper temporal sub-occurrence A.15.1 specifies the distinct TemporalPartOf_work relation. Mere temporal overlap supplies neither relation.
EpistemeConstituentOf, A.14, B.1.3:4The semantic-constituent relation kind. Establish the integration of the selected content into the encompassing episteme. To rely on its conclusion, B.1.3 also asks how the grounds combine. Follow such constituents when referring to levels of epistemic composition.Reports can share an observation without being parts of one another. A page in a binder gives a publication location.
DisciplineDisciplinePartOfRelation, C.20:4.2The relation kind between an independently identified part entity and a candidate discipline. The knowledge or practice has to be integrated into the discipline’s organization for its field problem under C.20. Use discipline composition for the resulting organization.A cited discipline can supply a useful result while remaining outside this composition. A further level requires a further admitted composition.
Layerfunctional layer, C.30.STRAT:4.2, C.30.LCA, C.32.LCAThe local kind of functional grouping identified by the organizing contribution, the membership criterion and its member functions in the named architecture. In a control account control layer may be sufficient once the exchanges are understood.Different Methods can implement that grouping. A claim that one of them is composite needs the admitted Method participants and their construction.
ClaimU.ClaimScope, A.2.6:6.3The set of context slices in which an identified claim applies. In speech, state where the claim is applicable.The number of observed cases cannot identify this set or prove the claim throughout it.
AbilityU.WorkScope, A.2.6:6.4The set of work-condition slices designated by a qualified claim about a holder’s ability.Scope membership can license evaluation of the ability claim. A performed job and its outcome need their own grounds.
PublicationU.PublicationScope, A.2.6:6.5The slices where a publication view or form is admissible for use, within its applicable underlying claim or work scope.Timely access to the publication and its actual use by a recipient are separate questions under E.24.PUB.

F.17 citation rows. This thread is RangesOfCompositionAndModelAbstraction, edition 2026-11-20. Each row below concerns the exact kind in bold in its NameCard. For System, Method, Work, Episteme and Discipline, it is the indicated relation kind. For SizeScale and SizeValue, it is the indicated CSLC kind. For Layer, it is the local kind of functional grouping defined in C.30.STRAT:4.2. Claim, Ability and Publication name the three existing scope kinds in A.2.6. Each such kind token has kind U.Kind. A place in a chain of relations, an actual instance, a measurement result and an entire discipline remain available for discussion in their own right.

The ReferenceScheme is the FPF Core interpretation stated in the exact sense for each key K. SenseCell.RangeTerms.K.2026-11-20 pairs the selected expression with that sense. Each cited owner edition that supplies a needed premise has a separate basis relation to this cell. For instance, A.14 identifies semantic constituency and B.1.3 establishes how common grounds affect the composed inference. The section collects the existing CSLC, USM and composition designations in one sheet. The ordinary phrases for levels in §6.2 are retained for following chains. The qualified functional layer sense retains C.30.STRAT’s functional grouping when a source also uses layer for the implementing Method. These are new citation rows for the established meanings. No cross-discipline Bridge follows from shared spelling.

Stable row IDNameCard and sense-cell keyAdmitted citation use
UTS.RangeTerms.SizeScaleSizeScaleState the scale for comparing a named characteristic under compatible conditions.
UTS.RangeTerms.SizeValueSizeValueReport the coordinate of a specified size characteristic on that scale for the identified system under its measurement conditions.
UTS.RangeTerms.SystemSystemIdentify the system composition and range under discussion.
UTS.RangeTerms.MethodMethodIdentify the admitted constituent Methods and the range needed for the encompassing Method.
UTS.RangeTerms.WorkWorkTrace actual constituent performances to the encompassing occurrence.
UTS.RangeTerms.EpistemeEpistemeIdentify the composition of interpreted content and its shared grounds.
UTS.RangeTerms.DisciplineDisciplineExplain which knowledge and practice a discipline actually integrates.
UTS.RangeTerms.LayerLayerName a functional grouping and explain how it contributes or exchanges results.
UTS.RangeTerms.ClaimClaimAsk whether a target context slice belongs to the stated claim scope. The domain of “each” identifies the members quantified over within the claim. Its applicability is a separate question.
UTS.RangeTerms.AbilityAbilityAsk whether the target work conditions are within the qualified ability claim’s scope.
UTS.RangeTerms.PublicationPublicationAsk whether the intended use is within the publication’s admissible scope.

Each row uses its NameCard’s reason for selecting the name and the competing reading it excludes. Reopen the affected row when its governing criterion, exact sense, selected expression or receiving use changes, or when its wording repeatedly licenses the competing reading. A term row lets the reader cite a meaning. The corresponding Method still determines whether the relation holds in the work at hand.