8000 feat(nav): Waze-grade live TomTom HUD + Palantir action/confidence by Blackleets · Pull Request #116 · Blackleets/aegis · GitHub
[go: up one dir, main page]

Skip to content

feat(nav): Waze-grade live TomTom HUD + Palantir action/confidence - #116

Open
Blackleets wants to merge 10 commits into
mainfrom
feat/nav-waze-palantir-hud
Open

Blackleets wants to merge 10 commits into
mainfrom
feat/nav-waze-palantir-hud

Conversation

@Blackleets
Copy link
Copy Markdown
Owner

Mobile nav polish toward Waze + Palantir. Wires unused useLiveRouteIncidents into RouteCockpitMobile, adds glanceable action + confidence on incident banners, prioritizes live on-route TomTom over context/quake while navigating. See docs/nav-waze-palantir-hud.md. Complements ontology Wave 1 (#115 / #114).

@vercel
vercel Bot commented Sep 6, 2026
Copy link
Copy Markdown

Deployment failed for project aegis with the following error:

Resource is limited - try again in 24 hours (more than 100, code: "api-deployments-free-per-day").

Learn More: https://vercel.com/nfyns-projects-b0cc0f41?upgradeToPro=build-rate-limit

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 493348b666

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment on lines +194 to +196
const destinationCoordinate = routeSnapshot
? { lat: routeSnapshot.destination.lat, lng: routeSnapshot.destination.lng }
: null;
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Stabilize the destination passed to the incident hook

destinationCoordinate is recreated on every render, while useLiveRouteIncidents includes destination in its effect dependencies and immediately updates its own state. During active navigation that update rerenders this component, changes the dependency identity, aborts the request, and starts another refresh, potentially creating an endless render/request loop before an incident response can complete. Pass a stable object, such as the existing destination object or a memoized coordinate.

AGENTS.md reference: AGENTS.md:L49-L52

Useful? React with 👍 / 👎.

action: nearbyEarthquakeAlert.magnitude >= 5
? 'Reduce y evita zonas inestables si puedes'
: 'Mantén precaución en la zona',
confidence: 'high' as const,
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Do not manufacture confidence for source alerts

When an earthquake is selected, this assigns high confidence without any confidence field in NearbyEarthquakeAlert; the context branch similarly hardcodes medium, and the TomTom presentation infers medium merely from locally classified critical severity. The HUD therefore presents an operator-facing confidence metric that was not supplied by the named source. Hide it when unavailable or derive it only from documented upstream confidence evidence.

AGENTS.md reference: AGENTS.md:L17-L18

Useful? React with 👍 / 👎.

Comment on lines +253 to +255
const liveIncidentDistanceMeters = liveRouteIncidents.incident?.distanceAheadMeters ?? null;
const proximityAlert = liveIncidentCockpit && liveIncidentDistanceMeters !== null
? {
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Expire stale traffic alerts before prioritizing them

After one successful incident response, repeated network/provider failures cause useLiveRouteIncidents to retain that incident with stale: true indefinitely, and this unconditional first branch continues placing it ahead of earthquake and context alerts without consulting or displaying checkedAt. A cleared traffic incident can consequently remain for the rest of a trip and suppress a newer critical alert; enforce a maximum age and expose the observation time before granting stale traffic top priority.

AGENTS.md reference: AGENTS.md:L50-L52

Useful? React with 👍 / 👎.

? { lat: routeSnapshot.destination.lat, lng: routeSnapshot.destination.lng }
: null;
const liveRouteIncidents = useLiveRouteIncidents({
enabled: navigationActive,
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Restrict driver incident guidance to driving routes

This enables TomTom road-incident monitoring for every active route, although RouteSnapshot.mode also supports walking and cycling and the existing RouteCockpitMobileSafe integration explicitly restricts the same hook to mode === 'driving'. Walking and cycling navigation can therefore show vehicle-specific actions such as changing lanes or holding the steering wheel; include the driving-mode check here as well.

Useful? React with 👍 / 👎.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant

0