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:10:10 UTC

C.31:1 - Problem frame

Use this pattern when modularity or reusable-structure language is doing work in an architecture discussion and the practitioner needs to know which few characteristics matter, what repair follows, and whether any measurement or comparison is admissible.

First identify the few characteristics that matter to the architecture question, the observed difficulty and any needed repair. An adequate ordinary account can finish; ModularityVectorLite offers a compact way to retain it:

ModularityVectorLite:
  describedHolonRef:
  architectureQuestion:
  intendedArchitectureUse:
  claimScopeRef?: U.ClaimScope
  qualificationWindowRef?:
  architectureClaimRef?:
  selectedStructureRefs:
  structureKindRefs:
  liveCharacteristics:
  observedProblem:
  repairDirection:
  relatedClaimPatternLocatorsIfClaimed:
  nonAdmissibleOverread?:
  stopCondition:

For the first diagnostic move, select the characteristics needed to explain the observed problem and choose the next warranted repair. Keep this first inquiry small while preserving every distinction that changes that move. A bounded report-only proxy can be a sufficient result.

Claim-use boundary: before relying on a characteristic for comparison, causal explanation, assurance, selection or another further use, establish the grounds required by that claim. Making a qualified local account available to an audience preserves its limits; publication alone does not turn it into a measurement or a selection result. Add only the information on which the receiving use depends.

What goes wrong if C.31 is missed:

  • “modular” becomes a binary label;
  • a single modularity score hides incompatible characteristics;
  • interface publication is confused with substitutability;
  • internal cohesion is improved while evidence reuse gets worse;
  • bespoke residue moves from templates into work or assurance; and
  • complexity language becomes a commensurable score without a declared characteristic, scale, measurement basis, comparison basis, or admissible-use boundary.

What C.31 buys in practice: the practitioner can choose the modularity characteristic that matters, identify a warranted repair, and determine what further measurement, evidence, causal, scale, selection or accounting grounds the intended use requires.

For a question limited to one of the following, use the indicated pattern instead of C.31:

QuestionPattern
Source-label recoveryC.30.STRAT
Module-interface relation repairA.6.M
Reusable-structure accountingC.31.RSA
General measurement admissibilityC.16
Quality-family claimC.25
Architecture scale-preference claimC.31.ASAP
Mathematical-lens useC.29
Candidate architecture synthesisC.32
SelectionG.5 for selected-set result declaration; C.11 for local choice