# Read inverse variation in Book Isle: a constant product is more than opposite trends

Language: en
Canonical: [Read inverse variation in Book Isle: a constant product is more than opposite trends](<https://allluckly.cn/en/guides/nasbook-inverse-variation-product-negative-correlation/>)
中文：[中文 HTML](<https://allluckly.cn/guides/nasbook-inverse-variation-product-negative-correlation/>)
English: [English HTML](<https://allluckly.cn/en/guides/nasbook-inverse-variation-product-negative-correlation/>)
Published: 2026-11-13T00:00:00+08:00
Modified: 2026-11-13T09:43:51+08:00
Author: Bison

Compare product-twelve and sum-twelve data, checking models, domains and negative controls rather than calling every decreasing relation inverse variation.

English translation of the [Chinese original](<https://allluckly.cn/guides/nasbook-inverse-variation-product-negative-correlation/>), translated on 2026-11-13. Original publication dates, attribution, code and version notes are retained.

An increasing horizontal value and decreasing vertical value do not establish inverse variation. Read an original example with a stated model in Book Isle and separately calculate ratios, products and sums. Use external notes if needed; no curve fitting in the app is assumed, and agreement at a few points cannot replace a rule over the specified domain.

## Copy variables and permitted values

Record book, location and problem statement. Treat x and y as abstract positive numbers initially, with stated model `y=12/x`, so zero is excluded for x. Keep the control `y=12-x` separately; it is not an equivalent form. Do not invent counts or speeds that add integer or physical restrictions. For points without a stated rule, mark a candidate model instead of attributing your guess to the author.

## Generate two columns at matching inputs

Use x values one, two, three, four and six. The product model gives y values twelve, six, four, three and two; the sum model gives eleven, ten, nine, eight and six. Pair every output with its own input instead of copying two descending lists. Both fall across these positive inputs, with different patterns. Reordering inputs requires moving their matching outputs, not combining separately sorted columns.

## Actually calculate every product

Products in the first column are twelve throughout. In the second they are eleven, twenty, twenty-seven, thirty-two and thirty-six, despite opposite trends. Retain at least two actual multiplications instead of an unsupported repeated answer. Twelve is the stated constant here. For a problem with units, also record the product’s unit rather than silently multiply unrelated quantities into an unexplained number.

## Check a doubling relationship independently

In the product model, doubling x from two to four halves y from six to three; doubling three to six halves four to two. In the sum model, ten becomes eight when two becomes four, not half. This is a model-based check, not proof from any fortunate pair. Keep both input pairs and specify doubling versus reciprocal scaling. A decrease of three in one pair does not establish a fixed subtraction step.

A noninteger input of one and a half gives eight; doubling it to three gives four. Both products remain twelve, so this abstract positive domain is not integer-only. A problem about object counts needs its actual integer restrictions; do not introduce one and a half people merely to reuse this check.

## Distinguish a constant ratio in direct variation

For `y=3*x`, inputs one, two and four yield three, six and twelve, with output-to-input ratio three. Direct variation checks a constant ratio; this inverse model checks a constant product. In the inverse column, ratios include twelve, three and four thirds, not one constant. Constants and multiplication or division do not make the models equivalent. An inverse function is also not simply another name for inverse variation.

The control’s sums are twelve for all five pairs. It has its own invariant rather than being ruleless because it is not inverse variation. Compare fixed sum with fixed product instead of calling one valid model right and the other wrong. A discrepancy arises only if the author explicitly labels the sum data as inverse variation.

## Recheck the domain before admitting negatives

If a separate version permits negative real inputs except zero, x of minus two gives y of minus six and product twelve, not minus twelve. Do not fill a connecting point at zero between the two branches; it is undefined. When the original task permits only positives, this is a separate mathematical control. An apparent approach to an axis does not imply reaching zero, nor promise that a real system follows the ideal model without bounds near zero.

## Check declining lines and mismatched pairs

If notes merely say negative correlation, recover the pairs and calculate products: a trend does not supply an exact inverse rule. For a mismatching product, check pairing, copying and units before considering an approximate model. Do not replace observations by twelve divided by x and claim the source originally supplied them. For unclear graph scales, keep intervals or unknowns and consult a clear table, rather than treating zoomed pixel distances as exact data.

## Leave and return to distinguish three relationships

Leave and return, hiding conclusions and reconstructing the product-twelve, sum-twelve and ratio-three controls from their rules. Keep variables, domain, five pairs, product and doubling checks, and unknowns. Explain why the second column is not inverse variation. Success separates supplied assumptions, manual checks and trends. Recheck the model for another book or unit rather than storing these particular numbers as universal answers.

## Related guides and sources

[Read function composition with Book Isle: pass the inner output to the outer function](<https://allluckly.cn/en/guides/nasbook-function-composition-inner-outer-order/>); [Read statistical claims in Book Isle: restore denominators, time windows and source tables](<https://allluckly.cn/en/guides/nasbook-statistical-claim-denominator/>).

Checked on November 13, 2026: [Apple public information](<https://itunes.apple.com/lookup?id=6766198898&country=cn&entity=software&timestamp=20261113>) lists Book Isle 1.1.4, requiring iOS / iPadOS 15.6 or later. See the [official App Store](<https://apps.apple.com/cn/app/id6766198898>) for published capabilities; verify specific controls in the installed version.

Method reference: [OpenStax: direct and inverse variation models](<https://openstax.org/books/precalculus-2e/pages/3-9-modeling-using-variation>). Samples, passages and controls are original exercises. Sources establish definitions and checking methods rather than new automatic analysis in the app. Manual records may be kept externally, and unknown fields should remain explicit. This article does not claim step-by-step testing on a physical device, private server or every output environment.