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:25:20 UTC

C.31:3 - Forces

ForceTension
Fast architecture repair vs measurement admissibilityPractitioners often need the next modularity move before a full measurement template exists.
Characteristic plurality vs scalar pressureDifferent modularity interpretations have different subjects, scales, evidence, declared measurement or comparison basis, subject-pattern needs, and risks; one score hides that plurality.
Useful proxy vs proxy substitutionA cheap share, count, or graph interpretation can guide local repair, but it may become a false quality, evidence, or decision claim.
Module-interface view vs broader structureModularity can involve functions, flows, control, work, evidence, data, placement, or scale, not only modules.
Local repair vs cross-case useA local diagnosis can stop at report-only use. Cross-case comparison needs the bearers, characteristic and comparison rule under C.16, with C.25 when a broader quality claim is made. G.5 governs a selected-set declaration and C.11 a local choice. E.24.PUB governs publication and audience availability; E.17 applies when a source-backed face and return are needed.
Complexity pressure vs complexity ontologyResidual pressure and growth signals are useful, but complexity is not one commensurable architecture characteristic.