Open Autonomous Intelligence Initiative

Subclass/Profile of: OAII Base Model — Device v0.1
Depends on: OAII Base Model — Common Types v0.1; Open SGI MVM Subclass — HomeWorldProfile v0.1

This document defines the MVM specialization of the OAII Device object for the Open SGI Aging-in-Place Event Recognition MVP.

---

1. Purpose

EdgeHomeDeviceProfile constrains a Device to serve as the local execution and trust boundary for a Home World. It is designed to:

• run edge-primary without continuous connectivity;
• host Sensors and local processing;
• enforce privacy and retention constraints;
• support explainable and auditable behavior via Logs.

---

2. Scope

A conforming EdgeHomeDeviceProfile instance:

• participates in exactly one HomeWorldProfile (MVM constraint);
• hosts the MVM sensor set and required mechanisms;
• supports safe degradation under resource constraints.

Out of scope for this profile:

• multi-home hub operation
• centralized data aggregation across homes
• cloud-orchestrated dependency

---

3. Required Attributes

An EdgeHomeDeviceProfile instance MUST implement all Device v0.1 required attributes, with the following constraints.

3.1 Identity and World Binding

• device_id : DeviceId — required
• world_refs : WorldId[1..N] — constraint: MUST include exactly 1 WorldId, referencing a HomeWorldProfile instance.

3.2 Device Classification

• device_type : string — required

Constraint: device_type SHOULD be one of:

• edge_hub
• wearable_node
• sensor_node
• virtual_node

3.3 Capabilities

• capabilities : ParameterSet — required

Minimum capability fields (normative for MVM interoperability):

• compute_class: {LOW, MID, HIGH}
• storage_class: {LOW, MID, HIGH}
• power_class: {MAINS, BATTERY}
• connectivity_modes: set (e.g., wifi, ethernet, cellular)
• acceleration: {NONE, CPU_ONLY, NPU, GPU}

3.4 Privacy and Access

• privacy_class : PrivacyClass — required
• access_class : AccessClass — required

Constraint: privacy_class MUST NOT be PUBLIC.

---

4. Required Hosted Objects (MVM)

A conforming EdgeHomeDeviceProfile instance MUST enumerate hosted objects as follows.

4.1 Sensors

• sensors : SensorId[≥2]

Constraint: MUST include at least:

• one MotionSensorProfile instance
• one ContactSensorProfile instance
• one DeviceHealthSensorProfile instance (may be virtual)

4.2 Mechanisms

The Device MUST declare hosted mechanisms (by MechanismId) for:

• signal summarization (≥1)
• event recognition (≥1)
• policy evaluation (≥1)
• logging (≥1)

Representation (normative):

• signal_processors : MechanismId[≥1]
• event_recognizers : MechanismId[≥1]
• (Optional additional fields MAY be used in implementation; this profile constrains minimum function, not field names.)

---

5. Offline and Degradation Requirements (Normative)

5.1 Offline Operation

EdgeHomeDeviceProfile instances MUST support:

• operation during network outage
• continued local Event recognition
• continued policy enforcement
• deferred outbound notifications (subject to Policy)

5.2 Safe Degradation

Devices MUST degrade safely under:

• resource exhaustion
• partial sensor failure
• storage pressure

Minimum safe behaviors:

• reduce sampling / switch to episodic capture where applicable
• increase reliance on summaries over raw retention
• suppress non-critical notifications
• emit DeviceHealth-related Events/Logs

---

6. Retention and Data Minimization Requirements

The Device MUST support bounded retention.

6.1 Signal Handling Defaults

• Raw Signals SHOULD be ephemeral.
• Summaries SHOULD be retained when needed for Knowledge formation.
• Export of raw Signals MUST require explicit Policy authorization.

6.2 Knowledge/Log Storage

• Logs MUST be stored locally.
• Knowledge MUST be storable locally.
• Rotation/aging MUST be supported.

---

7. Required Methods (Profile Requirements)

EdgeHomeDeviceProfile SHOULD support all Device v0.1 abstract methods.

Additional MVM requirements:

7.1 report_capabilities

• MUST provide the MVM minimum capability fields in Section 3.3.

7.2 enforce_privacy_policy

• MUST be able to apply redaction/retention effects to locally stored data.

---

8. Security and Trust Boundary Requirements (Normative)

• The Device MUST enforce access controls for configuration changes.
• The Device MUST support separation between:
  • resident-facing interfaces,
  • caregiver notification interfaces,
  • maintenance interfaces.
• The Device MUST surface its operating state and degraded modes.

---

9. Interoperability Requirements

• Devices MUST expose capability summaries in a machine-readable form.
• Devices MUST support stable Sensor identifiers across reboots.
• Devices SHOULD support export of Event summaries and Logs in open formats, subject to Policy.

---

10. MVM Non-Goals (Enforced)

EdgeHomeDeviceProfile explicitly disallows:

• continuous raw audio/video archival
• cloud-required inference
• hidden data export channels
• cross-home aggregation

---

11. Notes for Implementers (Non-Normative)

• A wearable node may conform if it satisfies offline operation and policy enforcement for its local scope.
• “DeviceHealthSensorProfile” may be implemented as a virtual sensor that emits Signals based on internal diagnostics.

---

Status: Draft v0.1 (Open SGI MVP Subclass Definition)