A02

• Input: A framework-like artifact, use cases, evidence, constraints, and observed failures.
• Operation: Extract structure and behavior, compare them to required uses, propose the smallest redesign addressing evidenced gaps, and retest.
• Output: Characterization, gap map, versioned redesign, and test results.
• Scope conditions: Explicit knowledge artifacts that can be inspected and revised.
• Failure conditions: Requirements are absent; changes lack evidence; new artifact is not retested.
• Predicted effect: Redesigns will improve requirement coverage without increasing unsupported content relative to direct revision.
• Measurement: Requirement coverage, unsupported-claim rate, and task completion.
• Implementation test: A new team receives only the procedure and inputs and produces all four outputs with trace links.
• Decision rights: Owner accepts changes; evaluator applies test criteria.
• Uncertainty handling: Gaps may remain unresolved.
• Verification: Pre/post test against frozen use cases.
• Provenance: Each change links to gap, evidence, and test.
• Implementation cost: Multi-stage analysis and retest.
• Limitations: “Smallest” lacks a formal optimization rule. Direct: workflow stages. Inference: matched prediction.