reversa-curator

To decide which legacy business rules to migrate or discard, classify each rule as MIGRATE, DISCARD, or HUMAN DECISION based on your migration brief and chosen paradigm. This systematic rule-by-rule evaluation prevents migration failures and scope drift while generating target_business_rules.md and discard_log.md artifacts.

Handling ambiguous business rules during migration requires routing them to human decision and logging them in an ambiguity log with cross-references. This ensures missing-rule cases receive explicit review rather than being silently dropped or incorrectly migrated from legacy unit specs.

Generating traceability logs for discarded business rules requires rendering a structured discard_log.md with explicit justifications and provenance for each rule. This artifact documents why specific legacy rules were excluded from the target paradigm mapping during the agent workflow.

Running a rule inventory migration decision requires migration_brief.md, paradigm_decision.md, and domain or code-analysis artifacts to be present. These input files provide the migration scope and paradigm context needed to evaluate legacy unit specs and classify rules.

You need to run the migration curator after the initial migration step so it can read legacy specs and the brief, then generate decision artifacts. It confines outputs to the _reversa_sdd/migration/ directory and updates ambiguity_log.md with pending items requiring human review.