C.25 - Q-Bundle: Express a Quality Claim as One Characteristic or a Structured Bundle
Type: Definitional (D) Status: Stable Normativity: Normative unless marked informative
Plain-name. Quality-bundle normal form.
Builds on.
C.2.1for the enclosing quality-claim episteme;A.2.6for scope algebra;A.6.1for operation-declaration references when current;C.16/A.18for Characteristic and Scale legality.
Coordinates with.
C.17-C.19for quality-related measurement families;C.16.Pwhen characteristic/scale/score wording is not yet recoverable;A.15for method, work-plan, or work-occurrence gating;C.16.Qfor quality/evaluative-characterization wording before the endpoint is one explicit characteristic, Q-Bundle-shaped claim content, objective, or another governing pattern.
Use this pattern when an engineering-quality family such as availability, resilience, security or maintainability may be hiding several differently typed contributors and the reader needs one claim that keeps them distinct.
First useful move. Ask: what would make this quality claim false? If one measure on one declared Scale answers the question, state that one Characteristic and stop. Use Q-Bundle-shaped claim content only when several differently typed contributors—such as a measure and scope, or measures plus a load-bearing window or mechanism—jointly determine the answer.
First result. Write one readable quality claim about one exact bearer and include only the contributors on which its truth or the next receiving action depends. Ordinary prose can express that structure; no separate template is required. Omit an optional slot unless changing it could change the current claim or receiving action.
Nearest non-use. Stay with the direct Characteristic pattern when one measure and Scale carry the claim. Use the direct scope, measurement, evidence, assurance, gate, publication, viability-envelope, or temporal pattern when that neighboring question—not quality-family decomposition—is the current work.
C.25:1 - Problem frame
Engineering quality language repeatedly drifts into one of two invalid simplifications: either every -ility is treated as one scalar characteristic, or every engineering-quality statement is left as loose evaluative prose. A conforming engineering corpus therefore needs a uniform discipline that keeps admissible measurements, scope declarations, mechanisms, statuses, and evidence visibly separated without inventing a new kernel ontology.
C.25:2 - Problem
Without a normal form for engineering quality families:
- Composite families are scalarized illegally. Terms such as resilience, security, or maintainability are treated as if one number exhausted them.
- Scope is confused with measurement.
A claim’s
ClaimScope/WorkScopeis spoken of as if it were a magnitude rather than a USM set-valued applicability object. - Mechanism and status are mistaken for evidence or metrics. Presence of redundancy, certification, or audit controls is described as if it were itself a measurement value.
- Guards become unstable. Admission checks silently mix scope coverage, numerical thresholds, mechanism presence, and evidence freshness in one phrase.
- The governing pattern for the quality claim remains unclear.
After
C.16.Qrepairs a bare quality term, orC.16.Prepairs characteristic, scale, score, metric, or proxy wording inside that term, the admissible endpoint is unclear unless FPF distinguishes single-CHR cases from bundle-shaped quality families.
C.25:3 - Forces
| Force | Tension |
|---|---|
| Simplicity vs category distinctions | Authors want one convenient quality label; the framework must still keep CHR, USM, mechanism, status values, and status-use relations distinct. |
| Comparability vs local applicability | Measures should compare legally across contexts, while scope remains context-local and set-valued. |
| Thin ontology vs practical authoring | The pattern should regularize quality authoring without creating a new heavy kernel family for every -ility. |
| Endpoint clarity vs expressive breadth | Some quality terms are one characteristic; others are bundles. The endpoint rule must cover both without ambiguity. |
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 portion of one episteme’s claim content. It is not a new Kernel kind, an independently identified world object, or a second identity beside the enclosing episteme. That episteme supplies the claim content, one independently identified QualityBearer as its EntityOfConcern, and the effective reference scheme under which the quality claim is read.
The ? marks an optional slot: omit that 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, orSecurity; it is not an identity key. - QualityBearer. The one independently identified EntityOfConcern of the enclosing claim episteme. It may be a
U.System,U.PromiseContent,U.Episteme, or another entity under its direct identity pattern. When selected organization is the subject, use oneA.22U.Structurewith 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.ContextSlicedescribing 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.Mechanismepistemes, 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 declares. For example:
declared scope covers TargetSlice AND declared measures satisfy their own laws AND each other declared prerequisite holds
An optional field can be left out when the claim does not depend on it. When another party uses that claim to make a decision, recover the conditions of that decision and compare them with what the claim covers. A supplier may document response time while the receiving service also requires current information. Meeting the response-time target settles that part. The service can accept both conditions when it also has grounds for freshness. An established breach of either bound rules out acceptance under this joint requirement.
Each measure keeps its own scale and comparison law. Use the declared decision rule for alternatives, trade-offs, weighted combinations or partial orders. If the typed decomposition cannot express what makes the claim true, use the pattern that governs the comparison.
C.25:5 - Archetypal Grounding
A quality family is not automatically one metric. Use one Characteristic when one measure and Scale carry the claim; use a Q-Bundle only when several differently typed contributors are jointly load-bearing.
Minimal availability case.
Under ServiceQualityScheme-v4, the claim says: CheckoutAPI maintained at least 99.9% availability for customer-facing request handling over the rolling 30-day window. Its exact bearer is the independently identified CheckoutAPI System. In this example the receiving use separately checks coverage of customer-facing requests and the rolling-window qualification as well as the ratio.
Its Q-Bundle content has Name: Availability, ClaimScope: customer-facing request handling, Measures: AvailabilityRatio[%] >= 99.9, and QualificationWindow: rolling 30 days. WorkScope, Mechanisms, Status, and Evidence are omitted because this drafting use does not rely on them.
If evidence reliance, a failover prerequisite, or a gate later becomes current, add only the direct relation or slot that question needs. If the receiving question instead asks only for AvailabilityRatio under an already fixed scope and measurement window, the single-Characteristic branch is sufficient.
Escalation examples. A resilience or security claim often needs several measures, scenario or attack-class scope, mechanisms or control statuses, and a qualification window. Those contributors belong in the bundle only when they are part of that claim’s truth conditions; treating the family as one scalar score would erase which contributor failed.
C.25:6 - Bias-Annotation
The pattern biases authors toward explicit decomposition. It is better to publish a visibly structured quality bundle than to gain short-term convenience by collapsing scope, measures, and mechanisms into one overloaded quality label.
C.25:7 - Conformance Checklist
-
CC-C.25-1If an engineering quality claim is intended as one measurement characteristic, the publisher SHALL bind it to one namedU.Characteristicwith one declared scale. -
CC-C.25-2If the claim requires multiple measures, scope slots, mechanism slots, status slots, or qualification windows, the publisher SHALL use Q-Bundle-shaped ClaimGraph content rather than an undeclared scalar surrogate. -
CC-C.25-3ClaimScopeandWorkScopeSHALL remain USM set-valued scope objects; they MUST NOT be treated as ordinal or numeric quality levels. -
CC-C.25-4Mechanism or status slots MUST NOT be conflated withMeasures[CHR]. -
CC-C.25-5Any scalar comparison or thresholding inside a Q-Bundle SHALL apply only to declared CHR measures, not to scope slots. -
CC-C.25-6When cross-context comparison is current, the publisher SHALL align the exact bundle heads or slots, resolve the two exactF.17local senses, and, when their<ReferenceScheme, LocalSenseClaim>projections differ and the comparison needs semantic correspondence, test the directF.9Bridge predicate and state a separate bounded-use claim only if that Bridge obtains.The comparison and its reliance MUST NOT change any Q-Bundle slot; ordinary reliance uses
A.10, whileB.3opens only when a named assurance claim is current. -
CC-C.25-7A materialized Q-Bundle SHALL be recoverable as content of one exactC.2.1episteme with one independently identified QualityBearer as EntityOfConcern and one effective ReferenceScheme. A gate, publication, comparison, proxy, or roll-up MUST NOT cite a field list as though it were an independently identified bundle object.
C.25:8 - Common Anti-Patterns and How to Avoid Them
| Anti-pattern | What it looks like | How FPF prevents it |
|---|---|---|
One-number -ility | Resilience = 82 with no declaration of what is being measured and what scope/scenario is intended. | CC-C.25-2 requires a Q-Bundle when the family is composite. |
| Scope as metric | The claim treats wider applicability as a higher quality value rather than as a larger USM set. | CC-C.25-3 keeps scope set-valued and non-CHR. |
| Mechanism equals quality | Presence of a mechanism or certificate is reported as if it were the measurement itself. | CC-C.25-4 keeps mechanism/status slots distinct from measures. |
| Ambiguous guard | The reader cannot tell which coverage, thresholds, windows or mechanisms make the claim true. | Make those conditions and their kinds recoverable, in ordinary prose or explicit slots. |
C.25:9 - Consequences
| Benefit | Trade-off / Mitigation |
|---|---|
| Category distinctions. Scope, measurement, mechanism, and status no longer collapse into one term. | Slightly heavier authoring structure; mitigation: only composite cases need a bundle, and immaterial optional slots remain absent. |
| Portable comparison. CHR measures compare legally, while scope remains governed by USM set algebra. | Authors must declare scales and scope explicitly. |
| Shared guard structure. Method/work guards can read the same structure without hidden semantics. | Requires discipline in separating guard factors. |
Endpoint classification. C.16.Q can terminate in either one characteristic or one Q-Bundle with a clear endpoint pattern. | Requires a first-pass endpoint decision during authoring. |
C.25:10 - Rationale
Engineering quality language is useful because it groups recurring concerns under memorable family labels. The same grouping becomes dangerous when those labels are mistaken for one universal metric. C.25 preserves the family labels but forces the underlying structure to stay typed and visible.
C.25:11 - SoTA-Echoing
The comparison below selects lines by the quality-family problem they can solve.
| Current problem-solving line | What it solves well | Remaining limit or effort cost | C.25 disposition |
|---|---|---|---|
| ISO/IEC 25010:2023 product quality model | Provides a current reference model of nine product-quality characteristics and their subcharacteristics for specification, measurement, evaluation, and acceptance criteria. It prevents one undifferentiated word quality from doing all the work. | Its reference taxonomy does not identify one local claim episteme, its exact bearer, use-bounded scope, window, mechanism prerequisite, or evidence reliance. A domain may also need qualities outside its ICT-product boundary. | Adopt characteristic decomposition and explicit measures; do not import the taxonomy as a universal bundle schema or bearer identity. |
| Google SRE Workbook: Implementing SLOs and Alerting on SLOs | Couples an indicator and objective to an explicit time window, error budget, stakeholder decision, and actionable response; multiwindow and multi-burn-rate alerts expose the precision/recall and management trade-off. | It is a mature service-reliability line, not a general ontology of resilience, security, maintainability, or assurance. It assumes measurement and operational-policy work whose cost is justified only for the receiving use. | Adapt the explicit measure/window/action boundary and the rule that engineering effort should match the decision; do not make an SLO or error budget mandatory for every quality family. |
| NIST SP 800-160 Vol. 2 Rev. 1, Developing Cyber-Resilient Systems | Treats cyber resilience through distinct goals, objectives, techniques, approaches, and design principles for anticipating, withstanding, recovering from, and adapting to adverse conditions. It keeps resilience from becoming one score. | The line is security-specific and intentionally broad; applying its life-cycle and risk constructs can be expensive. It does not provide one lightweight local claim identity or universal aggregation law. | Adopt the separation of scenario, measures, mechanisms, and outcomes when they are load-bearing; reject a universal resilience scalar. |
| OMG SACM 2.3 | Separates structured claims, argument links, artifact references, counter-evidence, and interchange packages, making an assurance case inspectable across tools. | A complete assurance case and its interchange structure can be much heavier than an ordinary quality claim. SACM does not decide which quality contributors make the claim true or whether one bundle guard is admissible. | Keep quality claim content distinct from evidence and assurance. Open A.10 or B.3 only on their own trigger instead of embedding an assurance case in C.25. |
FPF-local synthesis. C.25 combines the contributions needed to express the local quality claim: one exact bearer; a single-Characteristic exit; otherwise a typed separation of load-bearing measures, scopes, windows, mechanisms, statuses, and evidence references; and a guard over only the conditions the claim states. The tuple and this conditional guard are FPF synthesis, not a claim that contemporary practice already shares one universal Q-Bundle.
Defeating and reopen conditions. Prefer a direct domain pattern when it already supplies a clearer composite-quality identity, aggregation law, and practitioner route. Reopen C.25 when:
- a useful quality claim cannot be stated through the available typed contributors without inventing filler;
- a non-conjunctive trade-off or dependency cannot be named under its direct pattern;
- the record costs more than the receiving decision warrants; or
- a proxy repeatedly becomes the decision object despite the source claims remaining load-bearing.
C.25:12 - Relations
E.21 specialises Q-Bundle-shaped claim content for FPF pattern-quality claims. C.25 remains the general endpoint pattern for engineering quality families; E.21 governs the claim when its exact EntityOfConcern is one FPF pattern version evaluated as action-guiding FPF text.
C.27 temporal-claim relation.
- C.27 may flag: a quality-family statement where agility, resilience, adaptability, recovery, or robustness depends on braking, redirection, stabilization, recovery rate, or rhythm under effort.
- This pattern keeps: quality-family bundle structure, scope, mechanism/status slots, evidence, qualification window, and failure mode.
- Non-admissible use: temporal adequacy alone does not establish quality adequacy; speed, recovery, or rhythm becomes quality content only when it contributes to a declared quality-family claim. Include scope, mechanism/status slots, evidence, and failure mode only when the claim or receiving action depends on them.
- Coordinate with C.27 only when a temporal claim is being used to change action; do not make every quality bundle carry dynamic slots.
Other relations.
- Builds on:
A.2.6for scope algebra,A.6.1for operation-declaration references when current, andC.16 / A.18for CHR legality. - Coordinates with:
C.2.2a,A.16.0,A.10for ordinary reliance on a bounded cross-context use;B.3only when a named assurance claim is current;A.15for gate use;C.16.Pfor unresolved characteristic, scale, score, metric, or proxy wording inside a quality-family statement;C.16.Qfor overloaded quality or evaluative-characterization wording;C.33,C.34, andC.35when captured structure, lost structure, preservation, or generated-result adequacy becomes part of a composite architecture quality family;C.17,C.18, andC.19for adjacent quality-family measures;F.9when bundle comparison needs semantic correspondence between local senses with different interpretation bases, orF.9.1when Bridge stance annotation is required.
- Constrains: engineering quality authoring whenever a quality term would otherwise drift between single-CHR and composite-bundle readings.
C.25:12.1 - Endpoint function in evaluative classification
Use C.25 directly when the engineering quality claim and its contributors are already recoverable. Use C.16.Q for unresolved evaluative wording and C.16.P for an unresolved Characteristic, Scale, score, metric or proxy; then return to the endpoint their result supports. qualityTermAscription(...) may remain a transitional repair record, but it is not the universal resting place when the admissible result is a claim about one Characteristic, one episteme with Q-Bundle-shaped claim content, or an explicit objective-oriented quality claim under its own endpoint pattern.
C.25:13 - Decision Test: Single Characteristic or Bundle?
The most common authoring failure is not in the bundle syntax itself; it is in choosing the wrong endpoint shape. The quickest useful test is to ask what would make the quality claim false.
C.25:13.1 - Use one U.Characteristic when
A quality claim should terminate in one admissible CHR characteristic only when all of the following hold together:
- one measurable aspect is doing the evaluative work,
- one declared scale is enough to compare relevant cases,
- the bearer and scope are already clear without introducing extra quality slots,
- mechanism or status presence is not itself part of the core quality head,
- and downstream gates can read the claim without needing a bundle decomposition.
Examples include a narrowly declared AvailabilityRatio[%], a specific latency percentile, or one response-time threshold under one fixed window.
C.25:13.2 - Use a Q-Bundle when
A quality claim belongs in C.25 when one family label is standing over several distinct typed concerns, for example:
- several measures are needed together,
- scenario or claim scope is load-bearing,
- mechanism presence or certification state constrains admissibility,
- qualification windows alter the reading materially,
- or one scalar head would hide which part of the family is failing.
The bundle is the explicit authoring form for claims whose truth conditions are already composite.
C.25:13.3 - Borderline cases
Some quality families contain both a bundle-shaped form and a narrow single-characteristic form. For example, a service team may use:
- one CHR characteristic for a narrow uptime commitment, and
- one Q-Bundle for the broader service-availability family that includes scope, windows, failover mechanisms, and evidence.
This is legitimate as long as the text states clearly which head is currently in play. The single-characteristic form does not replace the broader family; it selects one evaluative slice of it.
C.25:14 - Slot Interaction Law
C.25 names the slots and defines how they interact.
C.25:14.1 - Scope and measure remain orthogonal
ClaimScope answers where or under what contextual slice the quality claim holds; WorkScope answers where the capability’s deliverability claim may be evaluated. Measures[CHR] answer how a measurable aspect behaves. A broader scope is not a larger measurement value; a narrower scope is not a penalty value. Scope is governed by set inclusion and coverage, not by scalar order.
C.25:14.2 - Mechanism and status are gating slots
Mechanisms and statuses may be load-bearing for admissibility, but they do not become measurements merely because they matter. A redundancy mechanism may be required for claiming a resilience bundle, and a certification status may be required for external publication, yet neither slot is itself the Measures[CHR] head.
This matters because many quality arguments fail by turning mechanism presence into an implicit score.
C.25:14.3 - Declare windows that affect the claim
A quality claim that depends on rolling windows, observation periods, maintenance intervals, or disruption horizons must publish that temporal qualifier explicitly. If the truth of the quality claim changes when the window changes, then the window is part of the declared bundle record rather than optional commentary.
C.25:14.4 - Report-only summary proxies
A publisher may compute a report-only summary proxy, such as a compact quality summary value. Identify the source quality-claim episteme or exact ClaimAddress, and state which Q-Bundle slots the proxy summarizes and omits. The proxy is a separate Characteristic or claim under its direct pattern; it does not replace that source in a norm, gate, comparison, endpoint classification or cross-context use.
C.25:15 - Worked Quality Families
C.25:15.1 - Availability family
A narrow service commitment may use AvailabilityRatio[%] as one characteristic. A broader availability family usually still needs a bundle because the claim depends on:
- declared service and time scope,
- observation and qualification window,
- one or more mechanism slots such as failover or redundancy,
- and evidence tying the measurement to declared observation conditions.
The bundle form makes it possible to distinguish “the measurement fell short” from “the measurement is fine but the declared mechanism prerequisite was absent”.
C.25:15.2 - Resilience family
Resilience is almost never one scalar. It commonly binds together:
- disruption scenario scope,
- observed restoration measures, such as mean time to restore under a declared observation protocol, and the recovered data point,
- recovery mechanisms and preparedness states,
- and scenario-specific evidence about drills, restorations, or incident traces.
Keep the observations distinct from their objectives: RTO bounds permissible recovery duration, while RPO specifies the required data-recovery point. Neither is an observed recovery result. Compare the observations with the applicable objectives under the declared rule.
Trying to compress this into a single resilience value can hide the difference between fast recovery in one scenario and structural fragility in another.
C.25:15.3 - Security family
Security claims routinely combine:
- trust-zone or attack-class scope,
- measurable characteristics such as patch latency, control coverage, or response interval,
- control-set and certification slots,
- and evidence from audit, observation, or incident review.
C.25 therefore treats broad security-family claims as bundle-shaped unless the claim has already been narrowed to one admissible CHR characteristic.
C.25:15.4 - Maintainability and evolvability
For maintainability or evolvability, recover the particular claim and the contributors on which it depends. These may include:
- the system or change-class scope;
- measures such as change lead time, defect reintroduction rate, restoration interval or review load;
- enabling mechanisms such as modularity rules or a test harness; and
- the observation window or other support used.
Keep measures distinct from mechanism and scope claims. A narrow claim carried by one Characteristic can stop there; a broader claim retains every load-bearing contributor, not every example in this list.
C.25:16 - Authoring and Review Guidance
C.25:16.1 - For authors
Begin with what would make this claim false? Then:
- identify the exact bearer and the quality-family label used in the claim;
- if one measure on one declared Scale carries the claim, state that Characteristic and stop;
- otherwise add only the differently typed contributors that jointly carry the claim;
- omit scope, window, mechanisms, status, or evidence when changing that slot would change neither the claim nor the receiving action;
- identify the enclosing C.2.1 episteme through its claim content, bearer, and effective ReferenceScheme; and
- add a proxy, gate, publication, evidence relation, or assurance result only when its own receiving question is current.
The schema remains available for a demanding case; it is not the authoring order for every bundle.
C.25:16.2 - For assessors
A checking reader should ask:
- whether the chosen endpoint shape is admissible,
- whether any scope slot is described as a scalar,
- whether mechanism presence has been mistaken for a metric,
- whether the window is optional or load-bearing,
- and whether any summary proxy is being used to replace the underlying bundle.
C.25:16.3 - For gate designers and assurance leads
Resist a guard such as resilience must be high. Cite the exact quality-claim episteme or addressed claim and name only the slots the decision uses—for example one scope, one measure threshold, a load-bearing window, or a required mechanism. Do not require an absent slot merely because the source claim uses Q-Bundle-shaped content.
C.25:17 - Repair and Boundary Notes
C.25:17.1 - Repair from bare quality requirement prose
Keep a familiar label such as security requirement when its content already makes the intended claim clear. If the label hides what is required, recover the endpoint:
- choose the endpoint shape first,
- then bind the requirement or commitment to that explicit head.
C.16.Q may still be the entry repair for overloaded quality wording, and C.16.P may repair characteristic, scale, score, metric, or proxy wording inside the same statement; C.25 is the resting place only after the engineering quality family has been made explicit.
C.25:17.2 - Boundary to cross-context use and reliance
For cross-context comparison, use the bundle alignment and conditional correspondence operation in section 18.3. That comparison changes neither the endpoint’s Characteristic-or-bundle kind nor the bundle’s claim content.
C.25:17.3 - Boundary to publication convenience
A report, summary publication, or executive summary may express only one slice of the selected quality-claim episteme. Keep the selected episteme and any exact ClaimAddress distinct from its publication occurrence, form, and carrier under E.24.PUB. A coarser form does not collapse the source claim content, while changed Q-Bundle claim content identifies another episteme even when the file or layout stays the same.
C.25:17.4 - Serviceability and supportability
Serviceability, supportability, and adjacent family labels often look simple in prose but become composite as soon as operational use is declared. An admissible bundle for this family may need:
- support-scope slices,
- measured restoration or service intervals,
- mechanism slots for support mechanisms, access discipline, or replacement procedures,
- and evidence from service traces or support records.
The lesson is the same as elsewhere in C.25: once the truth of the family claim depends on several typed contributors, the bundle should stay explicit.
C.25:17.5 - Boundary to description-side and selector-side evaluation
C.25 is for engineering quality families whose bearer is a system-side, promise-side, or explicit quality-bearing artifact. It does not automatically cover:
- viewpoint-fit or grounded architecture adequacy claims, which may belong in viewpoint or evaluative-ascription patterns,
- or selector/objective heads where quality means use-value under a search or portfolio frame.
This boundary matters because the same word quality appears across those zones. C.16.Q repairs overloaded quality wording, C.16.P repairs characteristic, scale, score, metric, or proxy wording when that is the hidden object, and the resting endpoint depends on what is being evaluated.
C.25:18 - Bundle Decomposition and Comparison Law
C.25:18.1 - Local decomposition rule
A family label may remain stable while its internal slots differ materially across contexts. Conforming comparison therefore starts by aligning the bundle decomposition: scope slots with scope slots, measure slots with measure slots, mechanism/status slots with their own kinds, and evidence/window slots with their own kinds. Comparing one bundle’s measure directly to another bundle’s mechanism claim is a category error even if both sit under the same family label.
C.25:18.2 - Narrow slice versus whole family
A publication may expose one narrow Characteristic claim from a broader Q-Bundle-shaped claim episteme, but it must identify that addressed claim as only one contributor to the broader family. It must not cite the slice as though it exhausted or reidentified the source episteme.
C.25:18.3 - Cross-context family comparison
Cross-context comparison of quality families starts with explicit bundle alignment: compare scope with scope, measures with corresponding measures, mechanisms or statuses with their own kinds, and windows or evidence only when the receiving comparison uses them.
For each semantic correspondence the comparison needs, resolve the two exact F.17 senses and test the direct F.9 predicate only when their <ReferenceScheme, LocalSenseClaim> projections differ. Cite a Bridge only when it obtains, then state the proposed use separately with its direction, correspondence rule, tolerated loss, and polarity.
Keep observed loss in evidence, use A.10 for ordinary reliance, and open B.3 only on its own assurance trigger. None of this changes the Q-Bundle or supplies an automatic penalty.
C.25:19 - Gate, Proxy, and Reporting Discipline
C.25:19.1 - Report-only summary proxy
Apply the report-only proxy rule in section 14.4 to the exact source episteme or addressed claims.
C.25:19.2 - Gate binding rule
When a gate uses a quality family, take its acceptance conditions from the receiving decision. Cite the quality-claim episteme or its addressed claims and identify which conditions each supports, such as a measure in a specified window or a required mechanism. Reuse other evidence for any condition the supplied claim leaves open. The gate’s own rule determines what to do with a known failure or an unresolved condition.
C.25:19.3 - Roll-up caution
A roll-up is another claim-bearing episteme. It cites the exact source epistemes or ClaimAddresses being combined, states the admissible aggregation or summary rule, and remains distinct from them. If the roll-up begins to drive local engineering action directly, reopen the source claims and the exact Q-Bundle slots on which that action relies instead of treating the summary score as the bearer or bundle.
C.25:20 - Review Matrix and Repair Tests
A checking reader can test a Q-Bundle with five questions:
- Is the endpoint shape admissible? One characteristic where one characteristic is live, one bundle where several typed contributors are load-bearing.
- Are scope and mechanism slots kept distinct from measures?
- Is any summary number being used to replace the bundle?
- Would a gate still be auditable if the family label were removed?
- If comparison needs cross-context semantic correspondence, is the
F.9Bridge predicate tested separately from the family bundle?
Repair from bare family prose should therefore recover the endpoint shape first, then choose whether any narrow slice deserves a separate CHR publication.
C.25:20a - Viability-envelope, quantum-like, and temporal-claim relation note
Use C.25 for the quality-family decomposition needed by a quality claim, proxy metric, trade-off, gate, or report. A viability claim should not become quantum-like merely because it involves uncertainty, feedback, several qualities, or changing operating conditions; a temporal claim should not become a Q-Bundle merely because the working phrase mentions speed, cadence, rhythm, or recovery.
Practical reading:
- Decide whether one Characteristic answers the quality question; if it does, stop there.
- If several differently typed contributors are load-bearing, identify the bearer and include only those measures, scopes, windows, mechanisms, statuses, or evidence anchors.
- If one proxy or this bundle answers the receiving question, stay in
C.25. - Open
C.26.3when several conditions must hold together under a disturbance and the question is whether the viable region is retained, violated or unresolved, or how a proposed change could restore it. - Open
C.27only when a temporal claim is being used to change action—for example, when rate-change, effort, window, resistance, recovery, or cadence changes that action.
For an envelope question, use C.26.3:4.5 to recover the exact bearer and protected work or result, derive the relevant conditions from ways that work can fail, and obtain bounds from the receiving requirements and actual provision. Keep each bound’s subject explicit. Compare the available observations with those bounds under the disturbance. A supported diagnosis can finish the use: a known violation establishes failure of the conjunction even while another condition is unknown; a positive viability claim needs all required conditions supported.
For proposed regulation, identify the intervention and which constraint each predicted effect concerns. Retain the grounds, unknown effects, displaced work, trade-offs and adaptation costs needed to judge that proposal. Recover needed authority or execution conditions for the proposed action. Unknown acceptability limits remain a requirement question or an explicit scenario assumption; observed averages do not supply normative bounds. These conditions are part of the claim and its use, not a compulsory envelope form.
Useful outputs:
- one
C.2.1quality-claim episteme with Q-Bundle-shaped content when the issue is quality decomposition; - a
C.26.3supported envelope diagnosis or conditional regulation proposal, with the grounds required by that result; - a
C.27temporal-claim adequacy card when a claim used to change action says that an intervention changes a rate, recovery, or cadence; state its effort, window, and resistance where load-bearing;
C.25:20b - Architecture-decision Q-Bundle boundary
C.32.P2S, C.32.PAD, and C.32.ADA may cite exact C.25 quality-claim epistemes or ClaimAddresses as architecture-characteristic inputs, accepted-loss structure, guardrail rows, feedback concerns, or adequacy concerns. C.25 keeps their Q-Bundle claim content, bearer, scope, measures, mechanisms, qualification window, and evidence distinct from the problem-to-structure architecturing flow, project architecture decision relation, and ADR-like publication projection.