69.7 Verification and Domain Error Analysis

Verification and Domain Error Analysis examines the mistakes most commonly made when verifying candidate values and controlling the domain of an equation, from accepting a candidate without testing it to overlooking a specific solving branch entirely. Each error is isolated, explained by the specific misunderstanding that produces it, and paired with its correction.

Candidate Automatically Accepted

The Error

A candidate value produced by the solving process is sometimes accepted as a final solution automatically, without being substituted back into the original relation to confirm it.

Why This Happens

This error occurs from treating the mechanical completion of the solving steps as equivalent to genuine confirmation, overlooking that certain algebraic manipulations can produce candidates that do not actually satisfy the original relation.

Transformed Relation Used as the Only Check

The Error

A candidate is sometimes verified by substituting it back into an intermediate, transformed version of the equation rather than into the original, unmodified relation.

Why This Happens

This error occurs from using whichever equation happens to be most recently on hand for the check, rather than deliberately returning to the original statement, missing the exact kind of discrepancy this verification step exists to catch.

Domain Restriction Recorded Too Late

The Error

A restriction on the domain, such as a denominator that cannot equal zero, is sometimes identified only after solving is complete, rather than before it begins.

Why This Happens

This error occurs from treating domain control as an afterthought rather than a preliminary step, risking that the restriction is forgotten entirely by the time candidates are ready to be checked against it.

Denominator-Zero Candidate Retained

The Error

A candidate value that makes an original denominator equal to zero is sometimes retained in the final solution set, overlooking that this makes the original expression undefined.

Why This Happens

This error occurs from checking only whether the candidate satisfies the simplified or transformed equation, without separately confirming it against the specific denominator restriction identified during domain control.

Even-Root Restriction Ignored

The Error

A candidate value that makes an expression beneath an even root negative is sometimes retained, overlooking that no real number can serve as that root.

Why This Happens

This error occurs from the same general oversight as the denominator case: checking the transformed equation alone without separately confirming the candidate against the even-root restriction identified during domain control.

Extraneous Candidate Kept

The Error

A candidate known to have arisen from a risky transformation, such as squaring both sides, is sometimes kept in the final solution set without being independently tested against the original relation.

Why This Happens

This error occurs from failing to apply the heightened scrutiny that transformation risk control specifically calls for, treating a candidate produced by a risky step the same as one produced by a fully reversible step.

Contextually Invalid Value Accepted

The Error

A candidate that is mathematically valid and passes every algebraic check is sometimes accepted as the final answer without checking it against the practical constraints of the real-world situation.

Why This Happens

This error occurs from treating algebraic verification as the final step of the process, skipping the separate contextual admissibility check that would catch a mathematically correct but practically nonsensical result.

Candidate Branch Left Unchecked

The Error

One of several branches produced during solving, such as one sign of a square-root method or one factor of a factored equation, is sometimes overlooked entirely, leaving its resulting candidate unreviewed.

Why This Happens

This error occurs from losing track of how many distinct branches the solving process actually produced, reviewing only some of them rather than confirming that every branch has contributed its candidate to the full review.

Verification and Domain Correction

General Correction Approach

Each error above is corrected by returning to the specific step it skips or misapplies: always substituting into the original, unmodified relation, identifying domain restrictions before solving begins, checking every candidate individually against denominator and even-root restrictions, applying heightened scrutiny to candidates from risky transformations, checking contextual admissibility separately from algebraic correctness, and confirming that every solving branch has been reviewed.

Why Isolated Correction Is Effective

Because verification and domain control follow a specific, deliberate sequence of identification, testing, and review steps, every error traces back to exactly one of those steps being skipped or misapplied, allowing for a targeted correction rather than repeating the entire verification process from the beginning.