C.31:4 - Solution
C.31 defines and constrains modularity and reusable-structure characteristic assertions as C.16-compatible characteristic heads, composite descriptions, lens-backed characteristic interpretations, temporal or scale-sensitive characteristic interpretations, causal-use-sensitive characteristic interpretations, or report-only proxies. It starts from action guidance and adds fields for beyond-local-repair use only when a use being made requires them.
C.31:4.1 - Ordinary output: ModularityVectorLite
Start with the change someone has to make, such as replacing a module, qualifying an interface or servicing a variant. Identify the characteristics that could alter that action. For a substitution, specify what the replacement has to do with the receiving equipment under its operating conditions. Compare the proposed replacements against those conditions. A shared interface name can help find candidates. A check that covers the required fit and behavior can admit one directly. To claim that changing the interface would save work, compare the installation, migration and qualification work under the alternatives over the same planned uses. ModularityVectorLite can retain the account.
ModularityVectorLite:
describedHolonRef:
architectureQuestion:
intendedArchitectureUse:
claimScopeRef?: U.ClaimScope
qualificationWindowRef?:
architectureClaimRef?:
selectedStructureRefs:
structureKindRefs:
liveCharacteristics:
- characteristicRef:
characteristicScaleRef?:
evidenceRefs?:
comparisonBasisRef?:
currentCue:
repairDirection:
claimUseClass:
forbiddenOverread?:
observedProblem:
relatedClaimPatternLocatorsIfClaimed:
stopCondition:
The account is complete enough when it answers the architecture question or identifies the next warranted repair. State a blocked inference when a plausible intended reader could make it here and the distinction matters.
relatedClaimPatternLocatorsIfClaimed locates a governing pattern; it supplies neither the claim nor its grounds. Further use needs the subject, assertion and applicable rule. Rule identity is required only under section 4.3. Architecture scale-preference claims use C.31.ASAP.
C.31:4.1a - Filled ModularityVectorLite
ModularityVectorLite:
describedHolonRef: ProductPlatform@FieldPumpFamily
architectureQuestion: which structural repair would reduce field-replacement and certification burden?
intendedArchitectureUse: choose the next modularity repair for field service and procurement
claimScopeRef?: field-service and procurement architecture claims
qualificationWindowRef?: 2026Q2
architectureClaimRef?: ArchitectureClaim@PumpControllerPlatform
selectedStructureRefs: PumpControllerModuleInterfaceStructure, PumpControllerEvidencePackageStructure
structureKindRefs: ModuleInterfaceStructure, EvidencePackageStructure
liveCharacteristics:
- characteristicRef: InterfaceStandardizationShare
currentCue: three field variants need different wiring adapters behind ports with the same API name.
repairDirection: identify the electrical differences the adapters accommodate and which variants must remain in service before changing the shared interface.
claimUseClass: local repair cue
forbiddenOverread: the public API label is not substitutability or procurement suitability.
- characteristicRef: SubstitutabilityWidth
currentCue: both candidate boards fit the connector and passed a bench signal test. A is qualified for the required signal, rate and wiring throughout this enclosure's operating temperature range. B's rating excludes the required maximum.
repairDirection: admit A and exclude B from this pair for the specified enclosure. Establish the operating range for another enclosure before carrying the judgement there.
claimUseClass: eligibility of the two boards for this signal and wiring throughout the specified operating range
forbiddenOverread: the alternate-board count is not a selection result.
- characteristicRef: EvidenceReuseShare
currentCue: the electrical result covers A in this wiring and operating range. A different enclosure can expose the board to a higher temperature.
repairDirection: use the electrical result within its qualification. Compare the field enclosure against the qualified thermal conditions before commissioning any further test.
claimUseClass: local repair cue with possible evidence-package use
forbiddenOverread: reused evidence is not assurance sufficiency.
observedProblem: the team says the platform is modular because interfaces are public and evidence is reusable, but field replacement and certification still create variant-specific work.
relatedClaimPatternLocatorsIfClaimed: A.6.M for the module-interface relation; C.31.RSA if report-only share becomes reusable-structure accounting; A.10 or B.3 only if an evidence-use or assurance-use assertion is being made.
stopCondition: the service engineer can use A for the stated fit, signal and temperature requirements. Assess other procurement requirements or a proposed platform change when the decision calls for them.
The engineer can now name the eligible board among the two examined. To decide whether an interface change would reduce the cost of field service, compare the adapter and qualification work for the installed variants with the migration and service work after the change. An increased standardization share can coexist with higher service cost.
C.31:4.2 - Characteristic classes
Identify the classes that apply to the characteristic use. They distinguish requirements and can overlap: a measured temporal relationship used causally needs its measurement, time-window and causal grounds.
| Class | Use | Boundary |
|---|---|---|
DirectCharacteristic | A C.16-governed characteristic can be named with subject, scale, unit or unitless interpretation, declared measurement basis, comparability basis, and repair action. | It is not automatically a score or decision selector. |
CompositeCharacteristicDescription | The head is a bundle or description with sub-slots, such as function-module alignment or flow-boundary alignment. | Do not treat the bundle as one raw measure. |
LensBackedCharacteristic | The head depends on a model description or mathematical lens, such as a compression, RG, or coarsening lens. | Use C.29 when mathematical representation choice, transfer or reliance remains unresolved; use an adequate domain treatment directly. |
TemporalOrScaleCharacteristic | The head depends on time window, repeated instance, scale variable, aggregation scope, or source-return condition. | Apply C.31.ASAP for architecture scale preference, C.27 for temporal adequacy, and C.18.1 or C.19.1 when scale-law or general BLP preference claims are being made. |
CausalUseSensitiveCharacteristic | The interpretation is used to claim effect or intervention success. | Apply C.28 before relying on the claim causally. |
ReportOnlyProxy | The interpretation is only a local diagnostic or communication aid. | Preserve its stated scope and relevant limits; use the applicable subject rule before stronger reliance. |
In C.31, declared basis and comparability basis name C.16-compatible measurement or comparison fields. They are not generic reason words and are not substitutes for evidence, assurance, cause, source, decision, or architecture-description relations.
C.31:4.3 - Measurement-head mapping
When a proposed comparison or decision relies on a measurement head whose meaning or admissible operations remain unresolved, recover the following mapping. Reuse an adequate existing account; the form is optional.
MeasurementHeadMapping:
sourceHead:
knownMeasureFamilyOrPractice:
fpfCharacteristicKind:
scaleType:
unitPolicy:
declaredBasisNeeded:
requiredEvidence:
evidenceRelationRefs?:
evidenceProvenanceRelationRefs?:
sourceRelationRefs?:
evidenceClaimAbsentBecause?:
commonFalseUse?:
nonAdmissibleUse?:
repairAction:
relationFunctionClaimRef?: # only when this use depends on rule identity
authoritySourceRef?: # only when a non-pattern source carries relevant authority
Use an ordinary PatternID to locate the rule.
Under E.10 L-EPI-PUB, relationFunctionClaimRef identifies the defining or constraining ClaimGraph only when interpretation, comparison, migration, publication or reuse depends on that rule identity. It is not a demand to establish a separate relation-function individual.
When an external standard, policy or other non-pattern source carries the relevant authority, use authoritySourceRef for that source instead.
For example, an ordinary InterfaceStandardizationShare account states its subject, the counted interface population, conformance specification, ratio Scale, source/test basis and limitations. It needs no extra rule-identity claim merely to describe that share.
If a comparison combines two editions that count partial conformance differently, cite the defining predicates through relationFunctionClaimRef before treating their shares as comparable. The comparison still needs its measurement and evidence basis; citing the predicate supplies neither test results nor assurance.
This mapping prepares a C.16-compatible measurement or a report-only interpretation; it does not supply observations or a measurement procedure. Recover the evidence or source relations that the claim relies on. Use evidenceClaimAbsentBecause only when the receiving use needs an explanation of that absence; a local cue needs no invented evidence claim. Sharing a bounded account preserves its existing qualification.
C.31:4.4 - C.31 characteristic card
Use the full card when retaining or comparing the characteristic requires these distinctions. An existing adequate account can carry them:
ModularityCharacteristicCard:
characteristicRef:
subjectRef or relationSubjectTuple:
characteristicClass:
scaleRef:
unitInterpretation:
declaredBasisRef:
comparabilityBasisRef:
requiredEvidence:
evidenceRelationRefs?:
evidenceProvenanceRelationRefs?:
sourceRelationRefs?:
evidenceClaimAbsentBecause?:
proxyRisk:
auditQuestion:
nonAdmissibleUse?:
repairAction:
relatedClaimPatternLocators:
relationFunctionClaimRef?: # same rule-identity condition as MeasurementHeadMapping
authoritySourceRef?: # relevant non-pattern authority, when used
A measurement or comparison states the characteristic, bearer, scale, unit interpretation, measurement or comparison basis, and evidence on which it relies under C.16. Retain relevant limits and any warranted repair. When source material is used as evidence, identify that source relation. A checklist, dashboard label or inherited score supplies no missing basis. The optional card organizes this content; it does not make a qualitative diagnostic cue a measurement.
C.31:4.5 - Seed characteristic heads and repair actions
These heads are seeds, not an exhaustive taxonomy. Use only the heads that change the next action.
| Characteristic head | Intended characteristic interpretation | Typical scale or value form | Declared measurement or comparison basis | Defect signal | Repair direction | Escalation trigger |
|---|---|---|---|---|---|---|
InternalCohesionDensity | Density of typed relations inside a proposed module. | ratio or graph-derived value | typed dependency graph or DSM | proposed module has insufficient typed internal dependency basis | split the proposed module, move relations, or reclassify as component relation | comparison, clustering, or publication use |
ExternalCouplingDensity | Cross-boundary dependencies per module or interface. | ratio or distribution | typed dependency graph, interface graph, integration defects | hidden external dependencies dominate module boundary | expose dependency, revise interface spec, split context, or accept bounded exception | integration risk, assurance, or release claim |
InterfaceAlphabetSize | Count or entropy-like variety of interface types. | count or entropy-like value | interface registry | too many interface variants erase modular benefit | reduce variants, introduce interface grammar, split context, or document exception | platform grammar, candidate selection, or publication use |
InterfaceStandardizationShare | Share of interfaces conforming to declared specifications. | ratio or percentage | conformance tests and specifications | standardization is low where reuse needs it | define or narrow standards, add conformance tests, or stop at local exception | cross-case comparison, certification, or procurement decision claim |
InterfacePublicness | Openness, publication, and vendor-neutrality value. | ordinal or category | standards, API specs, licensing, access terms | open label lacks substitutability relation, substitution policy, conformance expectation, or interface specification | recover interface spec, substitution policy, and conformance expectation | open-architecture claim, procurement decision claim, or publication claim |
SubstitutabilityWidth | Number or diversity of compatible alternatives for a slot or interface. | count or diversity value | approved implementations, vendors, tests | only one viable implementation exists | repair interface spec, loosen unnecessary coupling, or mark single-source exception | competition, platform, or decision claim |
ModuleTypeReuseRate | Instances per module type or template. | ratio or count | product-line records, bills of material, template records | reuse is claimed only by repeated naming | define module type, allowed variation, and measurement basis | cross-case reuse or product-line publication |
TemplateCompressionGain | Description saving from template plus parameters compared with instance-by-instance descriptions. | ratio or bits under declared method | corpus or model-description method | compression erases safety, law-domain, or source distinctions | recover needed source distinctions or split the template; use C.29 for an unresolved representation choice, transfer or reliance question | lens-characteristic or effect claim, publication, or decision use |
FunctionModuleAlignmentCharacteristic | Functional elements and module relations align without unmanaged many-to-many exceptions. | vector, ordinal, or bundle description | functional view and module relation records | allocation hides many-to-many exceptions | split function from module claim, revise allocation, or add correspondence | candidate decomposition or quality-composition claim |
FlowModuleBoundaryAlignmentCharacteristic | Flow topology crosses declared interfaces rather than hidden channels. | vector, ordinal, or bundle description | transformation-flow structure refs and interface refs | flows bypass declared module boundaries | expose crossing, revise interface, or apply C.30.TFS-REL for the bounded architecture use of the selected transformation-flow structure | publication or assurance claim about that architecture use |
ControlStructureSeparationCharacteristic | Control responsibilities, rates, and boundaries are explicit enough for the architecture move. | ordinal or vector | LCA or control description and temporal adequacy basis | control relation is hidden inside module label | apply C.30.LCA, C.27, A.3.3, or B.3 when a control, temporal, dynamics, or assurance claim kind is being made | stability, assurance, or gate use |
HiddenCouplingDiscoveryRate | Hidden dependencies discovered after integration or change. | rate | defect and change records | dependencies appear late | expose side channel, revise interface spec, add sentinel, or reopen boundary | integration risk, repeated release, or assurance claim |
CrossBoundaryChangeReach | How many modules, views, or work items a local change touches. | distribution | change-impact records | local change travels farther than claimed | split relation, add interface grammar, revise allocation, or source return | release, decision, or comparison claim |
WorkRepeatabilityShare | Delivery, operation, or test work under repeatable method descriptions. | ratio | work records and method descriptions | work repeats as bespoke effort | describe the repeatable Method in a MethodDescription under A.3.2 or accept exception | work planning, evidence reuse, or scale use |
EvidenceReuseShare | Previously obtained evidence used again for a specified claim on another instance or in another use of the same instance. | ratio | evidence records and qualification conditions | a result is credited outside its qualified use, or a covered result is needlessly obtained again | reuse the earlier result when it covers the claim. When an instance needs its own observation, reuse the procedure and obtain that observation. | certification, safety-case, or assurance claim |
RegulatoryBespokeResidue | One-off regulatory or acceptance content not covered by reusable structures. | ratio or ordinal | safety, approval, or regulatory records | each instance needs new regulatory argument | isolate residue, add reusable evidence package, or keep bounded exception | safety case, approval, or publication claim |
LearningTransferCoefficient | Improvement transfer from one instance or run to subsequent instances. | slope or elasticity | repeated work data and learning curve records | improvement claim hides time or causal assumptions | apply C.27 for temporal adequacy and C.28 for causal use | causal, benchmark, or scale-preference use |
BespokeResidueShare | Share of structure not covered by reusable templates or rules. | report-only share unless C.16 measurement basis is declared | RSA description and exception register | residue is hidden under reuse score | use C.31.RSA and source-return condition | accounting, comparison, or decision claim |
RGFlowStability | Stability of characteristic vector across declared coarse-graining scopes. | vector or ordinal | declared multi-scope architecture graphs | coarse-graining hides lower-scope hazards | use C.29 for unresolved representation choice, transfer or reliance, and C.31.ASAP for an architecture scale-preference claim | RG, scale, or lens transfer use |
ExceptionCurveSlope | Change in one-off exceptions over a scale variable. | slope | exception records against scale variable | exceptions grow with scale | apply C.31.ASAP or accept bounded exception | scale preference, publication, or decision claim |
C.31:4.6 - Claim-scoped residual heads
C.31 uses residual heads only as qualitative repair cues. These heads do not create one complexity characteristic.
| Head | Meaning | Related claim pattern locator and assertion requirement | Risk | Repair direction |
|---|---|---|---|---|
| ComplexityGrowthPressure | Pressure to add, split, mediate, or stabilize a declared aggregation scope, interface grammar, control relation, evidence scope, work-method scope, abstraction scope, or source-return condition. | C.30.ILC, C.31.ASAP when an architecture scale-preference claim is being made, G.5, C.11 | treating more apparatus as progress | name the pressure and the repair direction; use set-return or decision patterns when the corresponding claim is being made |
FrustrationResidual | Persistent cross-scope residual after attempted local repair or a stated reason for its insufficiency. | C.30.ILC, C.29-local cross-scope lens claim | turning a lens-backed interpretation into proof | keep as residual cue or apply C.29 or C.30.ILC |
ConflictResidualSlope | Residual grows or shrinks over declared scale variable, scale window, or coarse-graining scale. | C.31.ASAP, C.29, C.27, C.18.1, C.19.1 | treating two points as universal law | declare window, lens-use boundary, and measurement basis or stop at report-only |
DeclaredScopeAdditionCost | Added work, evidence, change-policy, latency, observability, accountability, or interface cost from a new declared aggregation or control scope. | C.16, C.31, C.30.LCA | ignoring the cost of added structure | identify cost bearer and apply the measurement pattern if used for comparison |
BespokeResidueGrowth | One-off exceptions grow with deployment spread, regulation, or project repetition. | C.31.RSA, C.31.ASAP when an architecture scale-preference claim is being made | assuming all bespoke work is bad | split useful exception from repairable residue |
InterfaceAlphabetGrowth | Interface variants grow faster than reuse, substitutability, or integration payoff. | A.6.M, C.31 | premature standardization | add platform grammar, split context, or accept bounded variation |
SourceReturnCost | Frequency or cost of returning from a compressed, indexed, coarse, extracted, or accounting view to source-side structure records. | C.29, source-return discipline, A.10 | over-compression | add source-return condition or reduce compression |
ControlNestingDepthRisk | Nested control relations create latency, accountability, observability, stability, or assurance cost. | C.30.LCA, C.27, B.3, A.3.3 | LCA-as-proof | apply control, temporal, assurance, or dynamics subject patterns when the corresponding claim is being made |
C.31:4.7 - Proxy-risk discipline
When a decision relies on a proxy, identify how it could diverge from the intended value and how that divergence would be detected. The card can retain these as proxyRisk and auditQuestion. An observed divergence blocks the unsupported value inference; the measured proxy can remain a valid report within its scope.
| Head | Proxy risk | Audit question |
|---|---|---|
ExternalCouplingDensity | Teams hide dependencies instead of reducing them. | Did integration failures or source-return events fall? |
InterfaceStandardizationShare | Premature standardization blocks useful variation. | Did exception slope or workarounds rise? |
InterfacePublicness | Open label without substitutability. | Are alternative implementations viable under declared conditions? |
TemplateCompressionGain | Compression erases safety, law-domain, or source distinctions. | Did source-return events or bounded exceptions rise? |
EvidenceReuseShare | Reused evidence becomes stale or mis-scoped. | Does evidence remain valid in the new context? |
RGFlowStability | Coarse-graining hides lower-scope hazards. | Are source-return conditions triggered? |
C.31:4.8 - Rejected shortcut
The expression ModularityScore = average(all measures) is not admissible as a C.31 result. A local score is admissible only when the scoring method, codomain, polarity, characteristic basis, comparability basis, and use boundary are disclosed through the governing scoring or comparator pattern. Without that, keep the result as report-only or return to ModularityVectorLite.
C.31:4.9 - Lowering and currentness conditions
Lower or reopen a ModularityVectorLite, ModularityCharacteristicCard, or report-only proxy when any of these conditions changes the characteristic use:
- proxy audit worsens, such as more integration failures, workarounds, source-return events, stale evidence reuse, or bounded exceptions;
- measurement basis, comparability basis, scoring method, codomain, polarity, unit policy, or declared characteristic basis changes;
- evidence relation, evidence-provenance relation, source relation, evidence-claim-absent reason, or source-return condition changes;
- described holon, architecture question or intended use, ClaimScope or qualification window, architecture claim, structure kind, characteristic head, or repair direction changes;
- a report-only proxy is used to support a stronger comparison, assurance, causal, selection or scale-preference claim; publishing its qualified local meaning does not create that stronger use;
C.31.RSA,C.31.ASAP,C.16,C.25,C.29,C.30.STRAT,A.6.M,C.30,C.30.ASV,A.10,B.3,A.20,A.21,G.5, orC.11changes the boundary for the neighboring claim being made.
Admissible repair results are:
- keep the result report-only;
- split or rename the characteristic head;
- update basis or evidence fields;
- revise the repair direction;
- change
relatedClaimPatternLocatorsIfClaimed; - lower a score to a local proxy; or
- stop the unsupported use and establish the required subject claim under its applicable rule.