<aside> 👁️

Document purpose: Give ISAC useful situational awareness without turning awareness into surveillance.

Document status: Architecture/design specification. Current implementation status is controlled by the roadmap and stage evidence.

</aside>

Awareness Levels

• Level 0 - Private: only information explicitly supplied by the user.
• Level 1 - System: CPU, RAM, GPU, battery, applications, processes and resource pressure.
• Level 2 - Workspace: projects, IDE, Git, terminal, creator tools, games and local work context.
• Level 3 - Connected Environment: calendar, email, smart home, notifications, cameras, microphones and sensors. Explicit opt-in.

Event-Driven Design

Prefer OS events, application events, filesystem watchers, API events and resource thresholds over constant polling.

Physical Sensors

Webcam and microphone access must be off by default, clearly permissioned, visibly indicated while active and independently revocable. Raw recordings should not automatically become memory.

<aside> ⚠️

Camera/microphone access can expose sensitive information about people and surroundings. Setup should warn users to enable it only where they have the necessary consent and understand the privacy implications.

</aside>

Smart Home

Separate capabilities by risk:

• Low risk: read temperature/status
• Routine control: lights and ordinary automations
• High risk: locks, alarms and potentially dangerous equipment; explicit governance and confirmation by default

Sustainability Awareness

Allow GCF cost models to consider battery, thermals, energy use, cloud compute and unnecessary background work. ISAC may defer low-priority work when on battery or avoid loading a larger model when the expected benefit does not justify the cost.

Memory Boundary

Seeing an event does not mean remembering it. GCF decides whether an observation is transient context, useful evidence or memory-worthy.