reversa-inspector

To prove migration parity, you generate paradigm-adapted parity specifications and Gherkin scenarios that validate functional equivalence between legacy and new systems. This involves defining acceptable parity criteria and producing testable artifacts like `parity_specs.md` and `.feature` files.

You write Gherkin scenarios for behavioral equivalence by defining paradigm-adapted parity tests that validate critical flows. The process generates `parity_tests/*.feature` files based on migration SDD inputs, ensuring explicit traceability without executing the tests.

Audit defensibility requires selecting applicable validation modes such as shadowing, characterization, contract checks, and data parity. These modes establish measurable acceptable parity criteria and generate traceable artifacts proving functional equivalence.

Yes, paradigm-adapted equivalence adds specific parity dimensions for target paradigm shifts. It covers event-driven ordering and idempotency, OO invariants, functional immutability, and actor supervision, ensuring the new paradigm's specific guarantees are validated.

You can validate UI screen parity by generating visual parity scenarios using golden manifests in literal mode, or contract-style screen scenarios in modernized or hybrid modes. This process respects deviation logs to account for approved UI changes.

Generating parity specifications requires reading migration SDD inputs to understand the legacy-to-new transformation. It produces `_reversa_sdd/migration/parity_specs.md` and required Gherkin `.feature` files while maintaining explicit traceability throughout the validation process.