360INR: Follow the units from tasks to points to items

360INR arithmetic exercise: convert completed tasks into points and points into guide items, keeping units, whole items and leftover points separate.

Eight completed tasks, forty-eight points and four guide cards can describe the same example at three stages. They cannot be added into a total of sixty. A 360INR reader looking at an activity explanation should keep the unit attached to each number. The keyword does not define the unit. A clearly stated conversion rule does, and following that rule step by step reveals both the available quantity and any remainder that has not yet become a whole item.

## Set the conversion rule first

Our invented learning activity awards six points for each accepted task, and one guide card requires ten points. Only whole guide cards can be requested. There are no extra point sources in this exercise. These conditions supply a two-link chain: accepted tasks become points; points become cards. Write the rates as six points per task and ten points per card. A bare six or ten is much easier to apply in the wrong direction.

Begin with eight accepted tasks. Multiply eight tasks by six points per task to obtain forty-eight points. The task unit cancels in the calculation and the answer is in points. This stage does not yet tell you the number of cards. Dividing eight by ten would combine a task count with a points-per-card rate, which are not matching units. The resulting number might look mathematical but would not represent the quantity the rule asks you to calculate.

Now divide forty-eight points by ten points per card. That yields four whole cards with eight points left over under the whole-item condition. It does not yield five cards by rounding to the nearest whole number. Nor can the eight leftover points be described as eight extra cards. A remainder retains the unit of what was left: here it is points. Whether those points can be carried forward in a real activity would require its own stated rule.

We find a reverse check useful because it tests the story as well as the multiplication. Four cards use forty points. Adding the eight remaining points gives the original forty-eight. Then forty-eight divided by six returns eight accepted tasks. The chain balances in both directions. This is not a forecast of a reward; it is a way of checking that a written example has not lost units or silently spent the same points twice.

## Attempted is not accepted

For the 360INR exercise, suppose ten tasks were attempted but only eight met the stated acceptance condition. The calculation still starts with eight, not ten. The rate is six points per accepted task. If someone reports sixty points by multiplying all attempts by six, their arithmetic is internally correct for the wrong input. Clarifying the input definition is therefore part of the calculation, rather than a separate administrative detail that can be ignored until after the total is announced.

Add one more accepted task and recompute. Nine tasks produce fifty-four points. Five whole cards would use fifty points, leaving four. The change from eight tasks to nine adds six points, but the available whole-card count rises from four to five because the previous eight-point remainder was already close to the ten-point threshold. This is why an item count can rise unevenly even when every accepted task adds the same number of points.

Next ask the inverse question: how many accepted tasks are needed to reach at least three cards, starting with zero points? Three cards require thirty points. At six points per task, five accepted tasks provide exactly thirty. For four cards, forty points are required, so six tasks give only thirty-six and seven give forty-two. The whole-task condition means seven, with two points left after four cards. Rounding down would leave the target short.

## Read the remainder honestly

The example has two different whole-number boundaries. Cards must be whole when converting an existing point total, so forty-eight supports four cards. Tasks must be whole when asking how to reach a target, so forty points require seven tasks at the defined rate. The first question asks what a fixed total can supply; the second asks what minimum input reaches a fixed target. Recognising the question prevents a single rounding habit from producing opposite kinds of error.

The 360INR chain is now complete: eight accepted tasks lead to forty-eight points, which support four whole cards and eight remaining points under our rules. Each answer has its own unit. If the rate, acceptance condition or item requirement changes, recompute from the changed link rather than adjusting the final count by guesswork. A sound explanation lets another reader reproduce every step and see exactly where a number stops being tasks and starts being points or items.