Repository navigation
docs: minute-resolution location history + asset.moved semantics (TRA-1118, hold for v1.5.0) - #216
Merged
Conversation
Location history is now recorded at one-minute granularity (platform PR trakrf/platform#576): webhooks.md documents the new movement-event resolution, the operator-save override exception, and the debounce property; data-model.md states the history endpoint's granularity; the API changelog records the behavioral change for integrators. Refs: TRA-1118
Deploying docs with
|
| Latest commit: |
a737f8d
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://75867d02.docs-4n7.pages.dev |
| Branch Preview URL: | https://docs-tra-1118-minute-resolut.docs-4n7.pages.dev |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This documents behavior that ships in app v1.5.0 (trakrf/platform#576, merged to platform main 2026-08-17). Prod is still v1.4.1 with the old per-read semantics, and this site describes prod. Draft until the release lands.
Merge responsibility for this PR sits with TRA-1142 (Release v1.5.0), which owns taking it out of draft, merging it after the prod deploy is verified, and confirming publication. TRA-1118 does not need to stay open waiting for it.
What changed
TRA-1118 made asset location history minute-granularity (one row per asset per minute; operator saves override the minute and emit movement events with the captured origin). Three docs claims became stale:
docs/api/webhooks.md— "That is the whole rule" no longer was. New section Movement detection has one-minute resolution: ≤1 location change per asset per minute from passive readers, mid-minute moves deliver with the next minute's read (≤60s), overlapping read zones can't flap (built-in debounce), operator saves win the minute and emit immediately with the overriddenfrom_location. Also:occurred_atwording loosened for save-driven events (minute resolution), the signature-tolerance note updated, "full scan stream" pointer corrected, and "Events went quiet" gains the just-moved case.docs/api/data-model.md— history endpoint now states its one-minute resolution and that it is location history, not a per-read scan log.docs/api/changelog.md— new anchored entry (#minute-resolution-history) recording the semantics change for integrators; no shape changes.Not included, deliberately: the v1.5.0 release-notes entry — that's release-time work covering the whole release, not just this change.
Build passes (
pnpm build, which validates internal links/anchors).Refs TRA-1118
🤖 Generated with Claude Code