C.31.RSA:4.5 - Structure-relocation actions

RSA is useful because it points to relocation and repair actions:

Situation	Repair direction
Repeated delivery work contains structure that is not explicit in the work or method description being used.	Move repeated structure into `MethodDescription`, work structure, or reusable work relation.
Repeated interface exceptions are handled one by one.	Add or revise interface grammar, variability slots, or substitution policy; use A.6.M when this is a module-interface claim.
An undocumented dependency crosses module or view boundaries.	Expose the dependency, revise boundary, add correspondence, or add source-return condition.
Evidence is recreated for each instance.	Move repeatable evidence into an evidence package, assurance argument record, or validity-context note.
Regulatory or safety-case residue remains one-off.	Split reusable argument structure from context-specific exception; apply B.3 to the assurance claim, including a claim about safety-case support, and G.6 when a citable provenance path is needed.
Compression hides needed distinctions.	Reduce compression, add source-return condition, or apply C.29 for lens-governed compression or reduction claims.
Bespoke residue protects necessary local variation.	Keep it as a bounded exception with admissible use and non-admissible use.

A high reusable-structure share is not always good. The architecture question is where structure lives—for example, in reusable templates, interfaces, flows, control relations, work methods, evidence packages, or unique exception networks and hidden coupling—and what action follows.

After a relocation or reuse move, ask what got worse:

Reuse move may improve	Check what may worsen
Template reuse	Loss of needed variation, hidden local exception, or stale source-return condition.
Interface grammar	Interface relation cost, conformance work, change cost, migration cost, or substitution constraint.
Work-method reuse	Context mismatch, extra handoff cost, slower local response, or hidden work exception.
Evidence-package reuse	Evidence decay, validity-window mismatch, missing context witness, or assurance overread.
Assurance-argument reuse	Weakest-link dependency, certification-window mismatch, or unexamined regulatory exception.
Compression or lens-backed accounting	Lost source distinction, observer-budget dependency, or C.29 stop-condition breach.
Bespoke-residue reduction	Reduced resilience, local-fit loss, or new hidden coupling.

A conforming RSA move states the reusable locus, the bespoke or residual locus, the accounting basis, the first repair direction, and the first cost, loss, or source-return condition that can make the move inadmissible.