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

Source changed 2026-11-18 21:11:39 UTC · snapshot created 2026-11-18 21:12:35 UTC · last check 2026-11-18 22:00:10 UTC

A.6.H - Wholeness Language Unpacking — RPR-WHOLE

Type: Relational-precision specialization Status: Stable Normativity: Normative unless marked informative

At a glance. Use A.6.H when words such as whole, part, integrity, complete, turnkey, or end-to-end hide the object or relation on which a decision depends.

Use this when. Enter after A.6.P:4.11 has recovered the candidate objects and the sentence needed by the receiving use, and that sentence asks about a whole, part, structure, integrity, coverage, or completion. A.6.H helps the practitioner expose the candidate whole or other bearer, its boundary when relevant, the independently identified parts or constituents, and the direct claim together with the rule that defines, constrains, or tests it.

Not this pattern when. Do not enter merely because a source contains a trigger word. Use A.17 or the applicable subject rule for a Characteristic or constraint, C.16 for a measurement, and C.16.P while characteristic or scale wording remains unresolved. Evidence-use and assurance questions follow §6. Use C.2.1 for episteme identity or edition, E.17/E.24.PUB for publication, and the applicable A.3/A.15 rule for Method, WorkPlan, or Work. Keep using A.6.P when the candidate objects or the receiving sentence are still unknown.

What goes wrong if missed. A situation record, diagram, bundle, adjective, phase label, or coverage slogan becomes the supposed whole or relation. Parts, members, portions, phases, method factors, Work parts, evidence, and measured characteristics are then silently treated as one generic “part of” claim.

What this buys. A short identity-first repair from overloaded prose to one or more direct claims with participants and, when needed, PatternID locators for their definitions or tests—or to an explicit blocker when a needed predicate is absent.

What changes in practice. The practitioner writes the few direct sentences the next decision consumes: which entity, which relation and participants, and which rule defines or tests the claim. Add a blocked-inference guard only when its rejected reading has an independent local ground, is plausible for the intended reader, and changes truth, understanding or use; use the smallest clear correction under F.19.

A.6.H:1 - Problem frame

Natural language compresses several different engineering questions into the same small vocabulary:

  • What individual is being treated as one whole?
  • Where is its boundary, and what lies outside it?
  • Which independently identified objects are parts, constituents, members, portions, or proper temporal restrictions?
  • Which relations among those objects obtain?
  • Does a named use need a construction trace or a selected structure?
  • Is the same whole being recognized again, or must it be reidentified?
  • Is “complete” about performed Work, capability, specification, evidence, or another coverage claim?
  • Is “integrity” a measured characteristic, an assurance claim, or a claim that an assembled entity remains one whole?

Those questions have different participants, predicates, and subject patterns. A.6.H keeps the source wording readable while making the load-bearing claims exact.

A word is load-bearing here when a requirement, invariant, interface statement, architecture choice, model relation, decision, test oracle, assurance use, or downstream action depends on its interpretation. E.10 is the pattern for shared wording-use discovery. A.6.H begins only after the current wholeness-family claim has been selected by value.

A.6.H:2 - Problem

Without identifying the objects, the following failures recur:

  1. Candidate-whole ambiguity. “The whole system” is asserted before one candidate entity, boundary, or identity rule is recoverable.
  2. Reference-level drift. One noun phrase alternates among a referent, a claim-bearing episteme, a publication form or carrier, intended Work, performed Work, and evidence.
  3. Parthood overload. Physical components, conceptual constituents, collection members, measured portions, and temporal restrictions are written as one generic inclusion.
  4. Order-as-structure. A method factor, step description, plan item, or performed occurrence is treated as a component because a diagram places it inside a box.
  5. History-as-parthood. A v2, revision, edition, shift, retry, or monitoring window is routed through PhaseOf before episteme identity or Work-temporal law is applied.
  6. Construction-by-list. A list of objects, repeated trace, or selected diagram is treated as proof that one whole or direct relation obtains.
  7. Coverage-as-wholeness. “Complete”, “turnkey”, or “end-to-end” is treated as a whole-level property without a scope, covered items, direct coverage or completion predicate, or current Work state.
  8. Integrity collapse. A measured characteristic, security or data-integrity term, evidence report, assurance claim, and structural-whole claim are all forced through mereology.
  9. Change-by-vocabulary. Generic verbs such as recompose, rephase, or recomplete replace the changed object and direct changed relation.

The practical failure is non-decidability: another reader cannot tell which object is at issue, what relation is claimed, what evidence would bear on it, or which stronger use is blocked.

A.6.H:3 - Forces

ForceTension
Conversational economy vs. recoverabilityOrdinary prose needs compact words, while a load-bearing use needs identifiable objects and relations.
Whole recognition vs. relation truthRecognizing one candidate whole does not establish its parts, structure, integrity, or completion.
Stable identity vs. changeA useful history needs continuity, while changed epistemes, Work occurrences, and replaced carriers must not be collapsed.
Structural description vs. performed realityMethod descriptions, plans, diagrams, and evidence can guide work without becoming the performed occurrence or its parts.
Minimal apparatus vs. downstream assuranceMost cases need one readable direct claim; some need a construction trace, selected structure, measurement chain, or assurance relation.
Cross-domain wording vs. subject-specific rulesModule, pipeline, team, integrity, and complete travel across domains, but their governed objects do not merge.

A.6.H:4 - Solution

A.6.H:4.1 - Entry and result contract

Enter with:

  • one sentence or decision that depends on wholeness-family wording;
  • the candidate objects recovered under A.6.P:4.11;
  • the receiving use that would change if the wording were read differently; and
  • any already known definition, constraint, or test and its PatternID locator when that reference must travel.

Return one of:

  1. one or more readable direct claims, each naming the predicate or claim family, ordered participants, material qualification, and the PatternID locator when its defining or testing content must be cited;
  2. one next action for a still-current measurement, evidence-use, episteme, publication, Method, plan, Work, production, or completion question: apply the named rule when its entry holds, or stop when no such question remains; or
  3. an A.6.RCD missing-governor[...] result naming the participants, proposed predicate, affected use, and absent definition, applicability, or occurrence-identity rule. Name a future pattern or declaration need only when one is identifiable.

When evidence cannot yet select among several readings, keep the candidate objects, discriminating questions, and affected receiving use explicit in ordinary prose. Under an already known rule, missing case facts leave the claim unknown; contrary facts can support a negative result. Neither is a missing-governor result. An ordinary shared note may hold the alternatives, keeping each separately recoverable. Its contents may supply claims or grounds, but its presence alone establishes no whole, relation occurrence, identity, coverage, assurance result, or new kind.

A.6.H:4.2 - Recover objects and relations

Use the following sequence only as far as the current sentence requires:

  1. Recover the working question. State what a reader must decide, do, accept, measure, rely on, start, continue, or stop. The cue word selects no branch.
  2. Name the subject and reference level. Distinguish the referent entity, claim-bearing episteme, publication occurrence, publication form, presentation carrier, Method, MethodDescription, WorkPlan, performed Work, and evidence carrier. Keep only the subjects current in this case.
  3. Recover a candidate whole only for a whole claim. Identify the candidate individual, its direct identity pattern, relevant boundary or delimitation, environment, and at least one interaction, dependency, or constraint across that boundary when the use needs it.
  4. Identify the alleged parts independently. A label, location, list, graph node, file section, timestamp, or common name does not by itself establish the claimed parthood. Recover each component, constituent, entity said to belong to a collection, portion, temporal restriction, Method factor, Work part, or other object using the rule that defines or tests that claim.
  5. State each needed direct relation claim separately. Name its participants and test the predicate under the asserted polarity, modality or conditions. Identify an occurrence only when the receiving use needs that identity. Recognition of the whole or the mere presence of a trace, view or record does not establish the relation; relevant content can supply facts to test under its rule.
  6. Add construction or selected structure only when the receiving use consumes it. C.13 may report already recovered parts, relations, constraints, and a construction rule. A.22 may identify one selected structure when its selection basis and identity discriminators are current. Their presence alone establishes no direct part or relation; apply the relevant rule to the claims and grounds they supply.
  7. Recognize or reidentify the whole only when that question is current. Use A.1 for holon recognition and B.2 for a remaining whole-reidentification question after direct existing-whole explanations have been tested. A changed adjective or part list alone decides neither.
  8. Separate coverage, completion, and performed Work. Name what is covered, under which scope and criterion, by which relation, and whether the claim concerns a MethodDescription, capability, plan, Work occurrence, production result, evidence set, or another subject. Apply the rule for that subject. For a deliberately asserted dated Work, recover A.13’s performer basis and independently admit the occurrence under A.15.1; use F.6 afterward only for attribution through the same assignment. A.15.PROD governs its production claim when applicable. Ordinary practitioner action needs no invented Work identity.
  9. Stop after unpacking. State each recovered whole, relation, characteristic, Work, evidence use, or verdict directly. Apply another named rule only when one question remains and its entry holds; otherwise stop with the completed claims or blocker.

A.6.H:4.3 - Classify integrity by the claim it carries

The word integrity never chooses mereology by itself.

Current sentenceObjects to identifyGoverning exitBlocked overread
“Structural integrity is measured at X.”bearer, integrity Characteristic, Scale or coordinate, Unit when needed, measurement method, result, and time stance; evidence pointer when the receiving use requires itC.16 and the applicable measurement pattern; C.16.P while the characteristic or scale wording remains unresolvedDo not invent a candidate whole, boundary, parts, or PhaseOf merely because the Characteristic is named integrity.
“This report supports the integrity claim.”target claim, supporting content and its claim-bearing episteme, evidence-use relation, and the relying use, limitations, currentness, or carrier reference required by this questionthe rule for the supported claim; A.2.4 for evidence-use classification, A.10 when a replayable source-to-use account is needed; B.3 for an assurance claimA report title, provenance link, or measured value alone establishes no assurance result.
“The assembled pump remains an integral whole.”pump, direct identity rule, boundary, independently identified parts, direct assembly or parthood relations, any current selected structure, and the whole-recognition or reidentification questionA.14, C.13, A.22, A.1, or B.2 as selected by the claimThe adjective integral or presence of a BoM or assembly record does not establish the whole or relations; relevant recorded facts may support the claim under its rule.
“Data integrity” or another defined term of artbearer, defined Characteristic or constraint, threat/assumption or qualification basis, and receiving usethe characteristic, constraint, security, measurement, or evaluation patternDo not reinterpret the term as structural wholeness unless the sentence separately makes that claim.

If the source leaves these readings open, preserve the alternatives and block the named use until evidence discriminates them.

A.6.H:4.4 - Select the direct relation, not a generic part edge

Intended claimRequired test and subject patternTypical non-inference
Physical or structural componentIdentify both entities, the direct ComponentOf predicate, boundary relevance, and obtaining facts under A.14/the structural pattern.Diagram containment or removal from a list does not establish component parthood.
Conceptual or content constituentIdentify the episteme or publication-unit whole and the constituent under A.14. Keep the described referent separate.A section in a file is not therefore a component of the described system.
Measured portionName the whole, portion, extensive measure μ, compatible unit, additivity/non-overlap rule, and boundary under A.14.A percentage, share, or smaller numeral does not make a structural component.
Collection belongingName the collection, its identity rule, the entity said to belong, and the collection’s own rule for when belonging begins and ends.Belonging alone is not transitive parthood and does not make an acting collective system; neither does it prohibit a separately grounded part relation.
Proper temporal restriction of an enduring individualApply the subject’s direct identity rule, then use PhaseOf(x,y) only when x is the same y restricted to a proper interval. Ordinary restrictions may nest or overlap. Coverage and non-overlap apply only to a separately selected exhaustive partition under A.14.A timestamp, state label, or changed property alone does not create a phase object.
Distinct episteme historyCompare C.2.1 claim content, EntityOfConcern, and effective ReferenceScheme. When a discriminator changes, identify another episteme; assert EpistemeEditionRelation only when its independent historical-continuation predicate obtains.v2, a filename, shared title or publication order does not by itself establish identity or continuity. Revision or source-use facts matter only through the relevant identity or continuation rule.
Performed Work interval, episode, part, retry, resumption, or later occurrenceAfter the Work basis in §4.2, use A.15.1 TemporalPartOf_work, EpisodeOf_work, OperationalPartOf_work, another admitted Work-part relation, or a separately identified Work occurrence according to its predicate.A shift, phase, step, log row, or MethodDescription section never routes Work through generic PhaseOf.
Method factor, order, branch, or joinIdentify Methods and method-composition claims under A.3.1/B.1.5; use B.1.4 only for a bounded aggregation of already recovered order relations.A box, sequence position, description constituent, plan item, or Work part is not a Method part by appearance.

A.6.H:4.5 - Unpack complete, turnkey, and end-to-end

Ask what the claim of completeness allows the next reader to do.

Candidate readingWhat must be namedDirect return
Complete whole or assemblycandidate whole, identity, boundary, required parts, direct relations, construction rule when current, and completion predicateA.1, A.14, C.13, A.22, or the construction/completion pattern
Specification coverageclaim-bearing episteme, described EntityOfConcern, effective ReferenceScheme, required content or criterion set, coverage predicate, scope, and gapsC.2.1 and the coverage/evaluation pattern; A.3.2 only when the episteme is classified or used as a MethodDescription under its membership rule
Capability coverageholder, capabilities, required actions or conditions, scope, and direct coverage criterionA.2.2 and the capability/coverage pattern
Work coverage or completionWork occurrence(s) admitted under §4.2, temporal extent, performed parts or episodes when needed, completion or production predicate, acceptance boundary, and evidenceA.15.1, A.15.PROD, or the applicable completion/acceptance pattern
Evidence coverageclaim set, evidence-bearing objects, evidence-use relations, scope, limitations, and receiving usethe applicable coverage rule; A.2.4 for evidence-use classification, A.10 when a replayable source-to-use account is needed; B.3 for an assurance claim
End-to-end method or workflowMethods, method parts and joins, exposed interactions, failure and stop conditions; performed runs remain separateA.3.1 and B.1.5, with §4.2 for an asserted Work

A sentence may require several rows. Write several direct claims; an ordinary note may hold them when each remains separately recoverable.

A.6.H:4.6 - Use wording as a cue, not as ontology

The following recurring expressions are useful review cues:

  • whole, entire, integrated, coherent, holistic — ask whether there is a candidate whole, a measurement or assurance claim, or only rhetoric;
  • part, piece, component, module, element, subsystem, includes, contains, comprises — recover the object and direct relation rather than accepting the noun;
  • phase, version, revision, edition, lifecycle — apply the direct identity pattern before any history label;
  • complete, turnkey, end-to-end, fully specified — recover the coverage or completion claim;
  • pipeline, workflow, process, step, stage — distinguish Method, MethodDescription, WorkPlan, performed Work, order relation, and publication representation;
  • collection, group, team, set — distinguish who or what belongs under the collection’s own rule, an acting system, system-role assignments, and a selected collection structure;
  • context, environment, discipline as a whole — name the bounded context, episteme family, community, organization, or other subject before making a boundary or nesting claim.

When a cue occurs inside a defined term of art, retain the definition and its PatternID locator when needed. Open A.6.H only if the sentence also makes an unresolved whole, part, structure, coverage, or completion claim.

A.6.H:4.7 - Describe change through the object that changed

When a wholeness-looking story changes, name the object and direct relation:

  • for a different boundary or interaction claim, state the changed object and apply the applicable boundary or delimitation rule;
  • for an added, removed, or differently related item, test the parthood, collection’s own belongs-to, portion, or selected-structure claim;
  • for changed episteme content, EntityOfConcern, or effective ReferenceScheme, compare C.2.1 identity and test edition continuity separately;
  • for a different publication form, occurrence, or carrier, state that publication or carrier claim and apply its rule;
  • for a changed Method, MethodDescription, WorkPlan, Work history, production result, or completion claim, state that object and apply its rule;
  • for a changed coverage scope, criterion, evidence set, or assurance use, repair that direct claim rather than inventing a generic completeness status.

Do not substitute a generic change lexicon for those objects and predicates. A readable verb is welcome when the direct claim remains recoverable.

A.6.H:5 - Archetypal Grounding

A.6.H:5.1 - Assembled pump

Source sentence: “After seal replacement, the assembled pump remains an integral whole.”

  1. The subject is PumpUnit-37, not the maintenance record, drawing, or seal-replacement Work.
  2. The pump’s direct identity rule decides whether the same individual continued.
  3. The current use names the pump boundary, impeller, casing, replacement seal, and the assembly or parthood relations on which operation depends.
  4. If the decision consumes one selected organization of those relations, A.22 governs that structure; if it consumes a construction account, C.13 reports already recovered facts.
  5. A.1 recognizes the candidate whole; B.2 opens only if the replacement leaves a whole-reidentification question.
  6. For a calibration, seal-replacement or inspection Work claim, use the basis in §4.2. State any claimed change separately under the rule for the changed object.

A.6.H:5.2 - Laboratory pipeline

Source sentence: “The whole chromatography pipeline is turnkey, and the chemist owns the whole thing.”

The repair separates the following claims and unresolved questions; turnkey and owns still need the receiving decision and discriminating facts:

  • the reusable procedure is one Method or composite Method under A.3.1/B.1.5, with joins and exposed interactions;
  • identify its procedure document as a separate episteme under C.2.1. It is a U.MethodDescription under A.3.2 only if its EntityOfConcern is an admitted Method and it makes a substantive claim about that Method as a way of doing;
  • “turnkey” becomes the specification, capability, Work, or evidence coverage claim needed by the receiving use;
  • treat owns as a local wording cue. First state the decision that depends on it and the proposed sentence. Candidate readings include, for example, property or title, possession or custody, operational control, decision authority, stewardship or responsibility, assignment, commitment, and permission; they have different participants and predicates. Apply the direct rule when one exists, or return A.6.RCD missing-governor[...] naming the participants, proposed predicate, affected use, and absent definition; and
  • identify any asserted dated laboratory run as Work using §4.2.

Thus “the laboratory owns the instrument,” “the chemist has custody during the run,” “the chemist may authorize disposal,” and “the chemist is responsible for calibration” are four different claims. None follows from belonging to the team, classification, assignment, commitment, or permission merely by form.

No one claim is a component relation merely because the source uses pipeline or whole.

A.6.H:5.3 - Paper, proof, and revision

Source sentence: “Section 3 is part of the proof, and v2 is part of v1.”

  • Recover whether Section 3 is a constituent of the paper episteme, a publication-unit constituent, or a described proof step. Keep those subjects separate.
  • Recover argument order under its subject pattern rather than as physical containment.
  • Compare the C.2.1 triples for the two labelled epistemes. Changed claim content identifies two epistemes. Assert EpistemeEditionRelation(E_v1,E_v2) only when its historical-continuation predicate obtains.
  • If the subject rule and A.14 admit a proper temporal restriction of one unchanged episteme, PhaseOf(E@τ,E) may state that restriction. Needing or using the episteme only during an interval states a use or applicability condition; it does not by itself identify a temporal part. Neither claim connects v1 to v2.
  • Keep any drafting, review, or publication Work separate from publication occurrences and from the two epistemes that participate in EpistemeEditionRelation.

A.6.H:5.4 - Integrity measurement and assurance

Source sentence: “The structural integrity score is 0.82, so the system is assured.”

Recover the bearer, integrity Characteristic, Scale, measurement method, result episteme, evidence, and time stance under C.16; use C.16.P if the characteristic or scale construction remains unclear. For “the system is assured”, name the target claim and assurance use before applying B.3; then recover the evidence-use relation, scope, limitations, and relying context. The score alone does not establish that assurance result.

A.6.H:6 - Recognition and assurance stay separate

Recognition questions decide which objects and direct relations are current:

  • Is there one candidate whole under A.1?
  • Which independently identified parts, constituents, members, portions, or temporal restrictions participate?
  • Which direct relations obtain?
  • Does a selected structure or construction account matter to this use?
  • Does the same whole persist, or is reidentification current?

Evidence-use questions ask how the evidence bears on the claim for the stated use. Apply the rule for the target claim, with A.2.4 for evidence-use classification. Use A.10 when provenance, currentness, or reliance requires a replayable source-to-use account, including carrier identity when material:

  • Which claim is being examined?
  • Which evidence bears on it through which relation?
  • What scope, limitation, time stance, and relying use apply?
  • What judgement about recognition, relation truth, measurement, completion, or another claim does the evidence warrant?

Apply B.3 only when a named assurance claim and assurance use are current. Evidence can make an assertion inspectable without becoming constitutive of the whole or relation.

A.6.H:6.1 - Bias-Annotation

  • Governance bias. The pattern favors reviewable direct claims over rhetorically satisfying wholeness language. Ordinary prose and explicit unresolved alternatives mitigate this when a decision is not yet due.
  • Architecture bias. Use the applicable patterns and small typed vocabularies instead of one reusable wholeness schema. The minimum-current-object rule mitigates unnecessary apparatus.
  • Ontological/epistemic bias. It insists on separating referent, episteme, publication, Method, plan, Work, and evidence. This cost is paid only when the distinction changes the receiving use.
  • Pragmatic bias. It favors early disambiguation to avoid downstream refactoring. A local direct sentence is sufficient; reusable declarations or structures are added only for a named later use.
  • Didactic bias. It uses recurring cue words and worked cases to teach the route; F.19 governs the connected language-and-precision reading, with E.10 cues and direct wording rules where needed.

A.6.H:7 - Conformance Checklist

IDRequirement
CC-A6H-1The entry names the working decision, candidate objects, receiving use, and load-bearing sentence.
CC-A6H-2The subject level is explicit when referent, episteme, publication, carrier, Method, plan, Work, or evidence would select different relations.
CC-A6H-3A whole claim identifies the candidate individual, direct identity pattern, boundary or delimitation when relevant, and independently recovered parts or constituents.
CC-A6H-4Every direct relation claim identifies its participants and satisfies the rule for its polarity or stated modality. An affirmative occurrence claim requires adequately grounded obtaining facts; a negative claim requires its own non-obtaining criterion or adequate closure basis. Missing facts establish neither result. Representation content may supply facts; co-listing or form alone does not establish the relation.
CC-A6H-5PortionOf names an extensive measure μ, compatible unit, and additivity/non-overlap basis.
CC-A6H-6PhaseOf is used only for a proper temporal restriction admitted by A.14 and the unchanged individual’s direct identity rule. A use window alone establishes no temporal part; changed epistemes use C.2.1 and Work uses A.15.1.
CC-A6H-7Method factors, description constituents, plan items, and performed Work parts remain separate and use their subject patterns.
CC-A6H-8integrity is classified as a characteristic/measurement, evidence/assurance, structural-whole claim, or another defined term before another rule is applied.
CC-A6H-9complete, turnkey, and end-to-end name the covered objects, scope, criterion, predicate, gaps, and applicable defining or testing rule.
CC-A6H-10C.13 construction and A.22 selected structure are added only for a named use. Their presence alone establishes no direct part or relation occurrence; their content is examined under the applicable rule.
CC-A6H-11A.1 recognition and B.2 reidentification are opened only when those questions arise; an adjective, list, or changed label decides neither.
CC-A6H-12The result is one or more subject-qualified assertions, an explicit unknown result, a needed next action or a missing-governor result. An ordinary note may hold them; its presence alone establishes no whole, relation occurrence, or new kind. A PatternID locates needed defining or testing content, or an identifiable future definition need. Any added blocked-inference guard satisfies the F.19 conditions stated at entry.

A.6.H:8 - Common Anti-Patterns and How to Avoid Them

Anti-patternFailureRepair
Holistic-as-evasion“We took a holistic view” replaces the decision, subject, boundary, or relation.Name the receiving use and claim, or remove the load-bearing assertion.
Universal part-ofComponents, constituents, members, portions, phases, Method factors, and Work parts share one edge.Recover each object and direct predicate under its subject pattern.
Record-as-wholeA wholenessSituation, bundle, BoM, graph, or trace is treated as the whole or relation.Recover the candidate entity, independently grounded facts, and assertion with its predicate; apply the subject pattern’s definition or test.
Structure-as-sequenceMethod order or plan order becomes containment.Recover Methods and order/join claims under B.1.5/B.1.4; keep Work separate.
Version-as-phaseDifferent epistemes are called phases of one document lineage.Apply the C.2.1 identity triple, then test EpistemeEditionRelation independently.
Work-phase shortcutShift, monitoring window, episode, retry, or resumption uses generic PhaseOf.Apply A.15.1’s temporal-part, episode, operational-part, retry, resumption, or occurrence rule.
Integrity-as-wholenessA measurement, security property, report, or assurance claim is forced through parts and boundary.Use the four-way integrity classification in 4.3.
Completeness-by-rhetoric“Turnkey” or “end-to-end” supplies no covered set, scope, criterion, or subject pattern.State the specification, capability, Work, evidence, construction, or completion claim.
Description/referent driftThe same noun alternates among a system, model episteme, document, carrier, plan, and Work.Name each current subject and its direct relation.
Generic change narrationA new change verb replaces the changed object and predicate.State the boundary, relation, episteme, publication, Method, Work, or coverage change.

A.6.H:9 - Consequences

BenefitsCosts and mitigations
Decidable disagreementsThe practitioner must name the subject and receiving use before arguing about the word.
Local repairOne sentence may become several direct claims; stop after the claims the receiving use needs.
Separate rule sourcesMereology, episteme identity, Work, measurement, evidence, publication, and assurance retain their distinct rules.
Honest uncertaintyAn unresolved case blocks only the named use; the candidate readings and discriminating questions remain explicit.
Reusable evidence-use claimsRecognition facts and evidence-use claims can be checked independently; B.3 assurance applies only for a named assurance claim and use.
Less ontology by wordingFamiliar trigger words no longer mint kinds, relations, structures, or lifecycle objects.

The practical test: if “whole” matters, name the thing, the relation, and what the reader may do with the claim.

A.6.H:10 - Rationale

Wholeness language is useful because it compresses boundary, identity, relation, construction, coverage, and assurance into ordinary speech. The same compression becomes dangerous only when downstream work relies on one particular reading.

The minimal repair starts with the working decision, recovers only the objects that decision consumes, and applies another rule only for a still-current question. This preserves conversational economy while preventing a representation, record, label, or adjective from replacing an in-world object or relation.

The sequence also preserves two positive uses. PhaseOf can state a proper restriction of one unchanged enduring individual, including an unchanged episteme, when A.14 and the subject’s direct rule admit it; fixed episteme identity alone does not establish the restriction. Ordinary whole recognition remains useful when a candidate entity, boundary, parts, relations, and direct identity rule are current.

A.6.H:11 - SoTA-Echoing

Source traditionSource contributionLocal adoptionRejected shortcut
ISO/IEC/IEEE 42010:2022, architecture-description practiceDistinguish the entity of interest from its description and make concerns, viewpoints, environment, and boundary explicit.Recover the candidate referent and boundary before treating a description or publication as evidence about it.A view, diagram, or architecture document is the system whole or establishes its parts.
ISO/IEC 21838-2:2021, upper-ontology disciplineBFO distinguishes continuant parthood from occurrent parthood; its temporal parthood has occurrent domain and range.FPF’s A.14 makes a local choice: proper temporal restriction of one unchanged enduring individual, including an unchanged episteme, under its direct identity and relation tests. This differs from BFO temporal parthood and supplies no episteme-edition or Work shorthand.One universal part edge or lifecycle object covers components, versions, and Work.
ArchiMate 3.2, enterprise-architecture relation practiceDifferent structural and behavioral relations answer different questions.Use the source vocabulary as a comparison aid while retaining FPF subject patterns and occurrence rules.A modelling-language edge label establishes the in-world FPF relation.
Team Topologies, sociotechnical boundary practiceTeam boundaries, interaction modes, and cognitive load affect organization and flow.Treat team and ownership wording as cues. Recover the claim made using the distinctions in §5.2, and use A.6.RCD only when no current pattern defines the needed predicate.A team boundary or a list of who belongs to the team establishes no ownership, responsibility, assignment, or Work by itself.
ISO/IEC/IEEE 29148:2018, requirements qualityRequirements should identify the item, condition, and verifiable claim without referent/document ambiguity.Recover subjects, scopes and predicates on load-bearing surfaces. Add a guard only under the F.19 conditions stated at entry.A specification sentence becomes true or complete because the document is complete-looking.
NIST SP 800-53 Rev. 5, security and privacy controlsIntegrity claims depend on the information at issue, constraints, threats, controls, assessment, and evidence.Recover the data/security integrity characteristic, measurement, evaluation, or assurance question and apply its rule before any structural-whole reading.Every occurrence of integrity means wholeness or mereological coherence.

Whenever fraction, percentage, or share is used as a part claim, recover the extensive measure μ and additivity basis before PortionOf; otherwise keep the value with the pattern that defines its measurement, allocation, collection belonging, or other claim.

A.6.H:12 - Relations

  • Specialises: A.6.P after its 4.11 whole/part/integrity/coverage branch has recovered candidate objects and the receiving sentence.
  • Uses for direct mereology: A.14; construction accounts to C.13; selected structures to A.22; holon recognition to A.1; and remaining whole reidentification to B.2.
  • Uses for episteme and publication questions: C.2.1, A.3.2, E.17, E.24.PUB, and C.29 as selected by the subject.
  • Uses for Method, plan, and Work questions: A.3.1, B.1.5, A.15.2, the A.13/A.15.1/conditional F.6 basis in §4.2, A.15.PROD, and B.1.4 only for bounded aggregation of already recovered temporal or order relations.
  • Uses for integrity, evidence, and assurance questions: A.17 or the applicable subject rule for a Characteristic or constraint; C.16 for measurement, with C.16.P for unresolved characteristic or scale wording; A.2.4 for evidence-use classification, A.10 for a needed replayable source-to-use account, and B.3 for an assurance claim.
  • Uses for absent relation governance: A.6.RCD after the participants, required predicate, and blocked receiving use have been identified.
  • Does not establish from wording or record form alone: a whole, lifecycle or other new kind, automatic edition series, universal part relation, coverage status, assurance verdict, or direct relation occurrence.

A.6.H:End

Referenced in the corpus

3 literal mentions in other sections. Read their context to establish the relation.