07 · Rule verification

Check every rule in the converted code

The new screen can open and its tests can pass while an old business rule is missing. Verification needs the inventory created before conversion, not only the cases remembered afterward.

Compare against the original catalog

WXCode checks the converted code rule by rule. A rule receives an outcome: implemented, adapted, missing, or not applicable. Where a rule lives in the new code, the report can point to its file and line. This makes the review specific enough to investigate.

Approved illustration of rule-by-rule verification
Approved illustration of rule-by-rule verification; this is not a capture of a live report.

Separate implementation from review

The verifier is separate from the agent that wrote the code. That separation helps it look for behavior the implementation might have overlooked. An adapted rule needs a stated reason; a missing rule needs a decision before the delivery is closed.

  • Implemented: confirm the new code preserves the intended behavior.
  • Adapted: confirm the deliberate change with its owner.
  • Missing or not applicable: record the decision and its rationale.
Source rule catalog used as the verification baseline
The source-linked catalog shown in the English carousel uses a Portuguese sample project.

Keep evidence for the next slice

The verdict links a business question to a code location and a human decision. It is more useful than a general statement that the conversion passed, and it gives the next team a way to understand what changed.

← All chapters