# ContextGuide.ai architecture brief

Version: concept architecture, August 2026

## Purpose

ContextGuide.ai is an adaptive assistance layer for compatible AI glasses. The glasses capture the scene and deliver audio. A paired Android phone performs the intensive perception, context reasoning and service orchestration.

This split keeps the wearable lightweight, lowers hardware cost and gives the product access to the user’s permitted Android services.

## Four layers

1. **Experience layer** — voice-first guidance for outdoor walking, public transport, indoor wayfinding, care and travel.
2. **ContextGuide intelligence** — situation detection, risk prioritisation, personalisation and selection of the right scenario module.
3. **AI and spatial services** — Gemini, Gemini Live, Google Maps Platform, Places API and ARCore.
4. **Connected services** — approved transport APIs, Wear OS signals, calendars, contacts and partner building data.

## Simplified data flow

1. The glasses provide a camera frame, microphone input and basic device state.
2. The phone combines this input with location, motion and permissions for the active module.
3. The context engine identifies the user’s likely goal and ranks observations by usefulness and risk.
4. A scenario module requests only the external services it needs.
5. The response is converted into one short voice instruction and returned to the glasses.

## Safety boundaries

- ContextGuide supplements rather than replaces mobility aids, trained assistance or medical care.
- Safety-critical guidance must expose confidence and fail safely when data is incomplete.
- Emergency escalation requires explicit user configuration and region-specific validation.
- Health signals are treated as assistive information, not a medical diagnosis.

## Privacy principles

- Permission boundaries are defined by module.
- Data collection is minimised and retention is opt-in where practical.
- Sensitive processing stays on the phone when the device and model allow it.
- External services receive the smallest useful data payload.
- Users can review, pause and remove connected services.

## Current status

This document describes the intended product architecture. Supported devices, interfaces and performance targets will be published with the pilot release.