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	add source-return condition, split template, or apply C.29	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`	Evidence package items reused across instances or contexts.	ratio	evidence graph and validity context	evidence is recreated or mis-scoped	move repeated evidence into reusable evidence or assurance package	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	apply C.29 for lens use and C.31.ASAP when an architecture scale-preference claim is being made	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