This index provides a consolidated view of the OAII Base Model v0.1 object set, their roles, and their relationships. The Base Model defines an open, object‑oriented, edge‑primary architecture for autonomous intelligence systems, with aging‑in‑place event recognition used as a reference domain.
The Base Model is normative at the object level and non‑normative at the implementation level.
1. Design Principles
The OAII Base Model is guided by the following principles:
- Object‑Oriented by Construction — responsibilities, interfaces, and limits are explicit
- Edge‑Primary — local autonomy, privacy, and resilience are first‑class requirements
- Event‑Centric — meaning is derived from bounded occurrences, not continuous surveillance
- World‑Scoped — interpretation, policy, and meaning are context‑bounded
- Policy‑Governed — governance is explicit, inspectable, and enforceable
- Open and Interoperable — objects and interfaces are designed for substitution and evolution
2. Object Set Overview
The OAII Base Model v0.1 consists of the following core object classes:
| Object | Role Summary |
|---|---|
| World | Contextual container defining scope, meaning, and validity |
| Device | Edge execution and trust boundary |
| Sensor | Observation source |
| Signal | Non‑semantic observable evidence |
| Event | Interpreted, bounded occurrence |
| Knowledge | Retained, structured context |
| Policy | Explicit governance and constraints |
| Agent | Decision‑making actor constrained by Policy |
| Interface | Human/system interaction surface |
| Log | Accountability and audit trail |
3. Dependency Graph (Conceptual)
World
├── Device
│ └── Sensor
│ └── Signal
│ → Event
│ → Knowledge
│ → Policy
│ → Agent
│ → Interface
│
└── Log (cross‑cutting)
Notes:
- World scopes all meaning and applicability
- Log spans all objects but is policy‑governed
- Objects interact through explicit references, not implicit state
4. Object Roles in the Aging‑in‑Place MVP
The following table summarizes how each object contributes to the Siggy / aging‑in‑place event recognition reference MVP.
| Object | MVP Role |
|---|---|
| World | Defines the home context and its axes (time, space, activity) |
| Device | Hosts edge computation and sensors |
| Sensor | Observes motion, location, sound, device state |
| Signal | Carries raw or summarized observations |
| Event | Detects meaningful changes (absence, entry, anomaly) |
| Knowledge | Stores routines, baselines, summaries |
| Policy | Controls notifications, privacy, escalation |
| Agent | Selects responses and assistance actions |
| Interface | Delivers prompts, alerts, confirmations |
| Log | Records decisions and lifecycle events |
5. Normative vs Non‑Normative Scope
Normative:
- Object definitions
- Required attributes and states
- Abstract methods and mechanism bundles
- Privacy and policy enforcement points
Non‑Normative:
- Specific algorithms or models
- UI frameworks or hardware platforms
- Storage technologies
- Vendor implementations
6. Interoperability and Substitution
The Base Model is designed so that:
- Sensors may be replaced without changing Event semantics
- Agents may vary in sophistication without bypassing Policy
- Interfaces may differ while enforcing the same constraints
- Knowledge may evolve without invalidating prior Events
This enables long‑lived systems that evolve without lock‑in.
7. Relationship to OAII and Open SGI
- OAII maintains this Base Model as an open, standards‑oriented specification
- Open SGI develops non‑normative reference implementations
- Siggy is an example reference MVP demonstrating the model in practice
No implementation is authoritative over the model.
8. Status and Next Steps
Status: OAII Base Model v0.1 — Complete Core Object Set
Planned next steps may include:
- Formalization of shared type schemas
- Conformance and profile definitions
- Reference mappings to existing standards
- Additional advocacy and explainer posts
This index serves as the entry point for reviewers, collaborators, and implementers exploring the OAII Base Model.

Leave a comment