TAMITOS Move development: one outing, consistent totals

TAMITOS Move's current development work separates a visible outing from the accepted measurements that contribute to its totals. The aim is to keep an overlapping phone and watch recording from appearing as two outings while retaining an explicitly accepted, uncovered contribution. This is an implementation update, not confirmation that every distributed app version already behaves this way.

The distinction matters when someone finishes an activity, opens their history and then checks a weekly summary. Those screens answer related questions, but they should not invent different facts. A route describes a recording. A summary adds eligible contributions. A reward follows its own rules. Making those meanings visible is more useful than forcing every number to look identical.

Why two recordings are not automatically two outings

A phone and a watch can observe the same walk. Adding both complete distances would exaggerate the activity. Discarding the watch entirely can also lose a genuinely accepted part outside the phone recording. The useful question is which measurements describe the same interval and which contributions have actually been accepted.

In the inspected implementation, an overlapping imported session does not automatically become another visible outing. A contribution is retained only under explicit conditions, including an accepted projection and a partial-coverage indication. Raw overlapping measurements are not treated as permission to guess extra kilometres. The original GPS route and splits remain associated with the phone recording.

That last point protects interpretation. A combined weekly total is not a newly measured continuous GPS route. Drawing a longer line or recalculating an individual best from unrelated fragments would make a stronger claim than the available evidence supports.

A small model example

Imagine a phone recording showing 4,000 metres. A second source reports a longer original workout, but the accepted uncovered contribution is only 50 metres. In this model, the useful summary is one outing with 4,050 accepted metres across the relevant aggregate. It is not two complete workouts and it is not a new 5,000-metre phone route.

The inspected test definitions use this kind of distinction. They retain the original route distance for an individual record while allowing accepted contributions into period totals. These are definitions of expected behaviour, not a claim that we ran those tests during this editorial review or measured a real walk of those lengths.

The same reasoning applies to time. An accepted additional interval may belong in an aggregate without changing the recording's original splits. A reader should be able to understand what the number represents before deciding that two screens disagree.

Refreshing should not create another contribution

History can arrive across multiple pages or be refreshed after connectivity returns. Repeated presentation of the same source should not accumulate the same contribution again. The current merge implementation identifies contributions rather than treating every received row as new activity.

Test definitions cover repeated pages, overlapping legacy rows and rejected or zero projections. They also preserve an unknown accepted distance as unknown instead of replacing it with a larger raw number. That is a useful product principle: missing information should remain visible as a limitation rather than silently becoming a flattering estimate.

This work does not establish the accuracy of a phone's physical GPS measurements. Deduplicating records and measuring a route accurately are separate engineering questions, requiring different evidence.

Calendar boundaries need their own check

An outing can cross midnight, the start of a week or New Year. The accepted source's own timing matters when allocating its contribution to a period. Moving every part into the parent outing's calendar bucket can make one screen look tidy while shifting activity into the wrong week.

A useful review therefore compares the same period, timezone and activity scope. It checks an ordinary outing, an overlapping import and a boundary case. It also checks what happens when history is incomplete: a partial set of downloaded rows should not be presented as a complete year.

These are proposed review steps for understanding the development change. They are not a promise about a particular user's records or an instruction to edit historical activity.

What is implemented, and what remains to verify?

The source reviewed on 2 November 2026 contains the merge logic and targeted test definitions. Distribution, exact-build validation and physical-device acceptance remain separate release questions. A commit alone does not prove that the Google Play or TestFlight version on a particular device contains the change.

No new provider availability, historical reward recalculation or guaranteed points are announced here. Movement totals, reward eligibility and donations also remain different concepts. A clearer activity summary does not convert points into funded euros or create a donation.

For the public product context, visit TAMITOS Move. To understand how source evidence differs from a release, read prototype versus production readiness and follow QORPO Live. Our studio blog records other development explanations.

Questions readers may have

Should I choose the larger number from my phone or watch?

No universal rule follows from this update. The development approach uses accepted contributions and their meaning, rather than automatically choosing the larger original recording.

Does one visible outing mean every total must match its route?

No. A route and a period aggregate can have different legitimate scopes. The interface should explain that difference rather than imply a newly measured route.

Is this an announcement of a released app update?

No. This article describes inspected development work. Check the actual distributed version and its release notes for availability.

Sources

• TAMITOS Move development source and test definitions, reviewed 2 November 2026. Pinned implementation evidence is retained in our editorial ledger.
• Official TAMITOS Move product page.
• QORPO studio development feed, a discovery aid rather than proof of distribution.