reversa-paradigm-advisor

To prevent paradigm mismatches during legacy system migration, you must detect the source programming paradigm and map it to the target stack's natural paradigm, documenting concrete implications and requiring a human decision to bridge the gap.

You can classify legacy architecture paradigms by analyzing specification artifacts to detect procedural, classic OO, functional, event-driven, actor model, dataflow, or hybrid behaviors using documented evidence rather than direct source code reading.

When target natural paradigms differ from legacy systems, the mismatch translates into at least four concrete, citeable implications with severity ratings that future migration agents must honor, requiring an explicit human strategy decision to proceed.

Mapping a legacy procedural paradigm to a functional target stack requires proposing viable paradigm alternatives and articulating the concrete gap implications, which typically necessitates an explicit architectural strategy decision rather than a direct code translation.

The best way to document paradigm shift decisions is to record the user's choice and justification into a dedicated paradigm decision artifact, enumerating pending implications for subsequent migration agents like Curators, Strategists, Designers, and Inspectors.

Yes, you need existing migration briefing and specification artifacts within your SDD directory structure to infer the target natural paradigm and generate the required paradigm decision documentation accurately.