Where the data comes from
PulseAI answers should be grounded in real vehicle, drive, charge, billing, and product-state data available to the signed-in user.
PulseAI is the premium explanation layer for real EVStreak data, with honest fallbacks when there is not enough context.
Illustrative — answers carry their derivation source. When context is thin, PulseAI says so.
PulseAI answers should be grounded in real vehicle, drive, charge, billing, and product-state data available to the signed-in user.
When PulseAI lacks enough data, it should explain what is missing instead of writing confident generic coaching.
PulseAI is an explanation layer over owner data, not a reason to expose raw telemetry or private records in public surfaces.
PulseAI turns real owner context into summaries and answers: why a week changed, what charging patterns say, and what progress looks like.
The public story should say preview when data or model-backed behavior is not yet captured from the live app.
If the answer needs data that does not exist, PulseAI should say what is missing and offer the next owner action.
A premium connected-car home for status, charge posture, route context, and the next meaningful EVStreak action.
Open featureCompleted drives become ownership memory: streak progress, efficiency context, and a better reason to come back.
Open featureCharging sessions become a quiet ledger for energy, cost-ready context, and ownership rhythm once real sessions exist.
Open featureA privacy-first product stance for official authorization, derived owner views, and clear non-affiliation language.
Open feature