Open Autonomous Intelligence Initiative

Subclass/Profile of: OAII Base Model — World v0.1.1
Depends on: OAII Base Model — Common Types v0.1

This document defines the MVP specialization of the OAII World object for the Open SGI Aging‑in‑Place Event Recognition MVP.

---

1. Purpose

HomeWorldProfile constrains and configures a World to represent a single private residence in which edge‑primary event recognition operates. It establishes the minimum context required to interpret Signals as Events while maintaining privacy, dignity, and auditability.

---

2. Scope

A conforming HomeWorldProfile instance:

• represents one physical home (apartment/house);
• is optimized for one primary resident (MVP);
• supports local interpretation without cloud dependency;
• prevents cross-home meaning leakage.

Out of scope for this profile:

• multi-resident identity modeling
• cross-home aggregation
• clinical interpretation

---

3. Required Attributes (Profile Constraints)

A HomeWorldProfile instance MUST implement all World v0.1.1 required attributes, with the following constraints.

3.1 Identity and Versioning

• world_id : WorldId — required
• version_state : string — required

3.2 Temporal Frame

• temporal_frame : ParameterSet — required

Constraint: temporal_frame MUST include a stable local time base and a mapping strategy for wall-clock time changes (e.g., DST adjustments).

3.3 Contextual Axes (MVP Minimum)

• contextual_axes : ContextualAxis[≥5] — required

A HomeWorldProfile instance MUST include at least one axis for each of the following AxisTypes:

1. TEMPORAL
2. SPATIAL
3. ACTIVITY
4. DEVICE_STATE
5. POLICY_CONTEXT

Constraints:

• Axis definitions MUST be explicit and World-scoped.
• Axis value_domains MUST be bounded and interpretable.
• Additional AxisTypes MAY be included, but SOCIAL axes (if present) MUST default to SENSITIVE or RESTRICTED privacy_class.

3.4 Continuity Mechanism Bundle

A HomeWorldProfile instance MUST declare:

• continuity_mechanism_id : MechanismId
• continuity_mechanism_params : ParameterSet

Constraint: The continuity mechanism MUST preserve interpretability of previously recorded Events across routine evolution (e.g., baseline shift) without silently invalidating history.

---

4. Required ValueDomain Conventions (Profile Guidance)

HomeWorldProfile SHOULD adopt the following conventional domains for MVP interoperability.

4.1 SPATIAL Domain

• domain_type: DISCRETE_SET or ORDERED_SET
• values: named zones/rooms + entry/exit boundary tokens

4.2 TEMPORAL Domain

• domain_type: CONTINUOUS_RANGE (time) and/or ORDERED_SET (time windows)
• values: time-of-day windows (morning/afternoon/evening/night), durations

4.3 POLICY_CONTEXT Domain

• domain_type: DISCRETE_SET
• values: normal, quiet_hours, escalation_mode, maintenance_mode

---

5. Required Methods (Profile Requirements)

HomeWorldProfile SHOULD support the World v0.1.1 abstract methods.

5.1 apply_continuity_mechanism

Requirement: MUST be callable or representable such that the system can report continuity status (SUCCESS/PARTIAL/FAIL) during changes.

5.2 evolve_world

Constraints:

• MUST update version_state on success.
• MUST NOT silently invalidate Events.
• MUST, when needed, emit a “requires_reinterpretation” marker (implementation-specific) to inform downstream Knowledge/Agent updates.

---

6. Privacy and Boundary Requirements (Normative)

A HomeWorldProfile instance:

• MUST treat the home as a privacy boundary.
• MUST default to local processing and local retention.
• MUST NOT require raw Signal export to function.
• MUST support Policy constraints governing export, retention, and notification.

---

7. Interoperability Requirements

To support substitution and evolution:

• The World MUST provide stable identifiers for zones/axes used by Events.
• Event types MUST be World-scoped (by design) and SHOULD be namespaced when exported.
• The World SHOULD expose a minimal “World metadata summary” suitable for caregiver-facing explanations (without revealing raw Signals).

---

8. MVP Non-Goals (Enforced)

HomeWorldProfile explicitly disallows:

• multi-home/global context inference
• behavioral profiling across homes
• continuous surveillance archives
• clinical interpretation

---

9. Notes for Implementers (Non-Normative)

• A HomeWorldProfile instance can be initialized with an empty spatial map and learn zones over time, but zone identifiers must remain stable once established.
• A “maintenance_mode” policy context is strongly recommended to suppress non-critical notifications during device servicing.

---

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