EIOS is an open framework for AI-native entity information. Its primary point: AI can only work properly with full context — so an entity that wants agents to carry real operational weight must first give them (and its people) one complete, governed information core. EIOS defines how an entity — a company, cooperative, association, foundation, public body, or other structured organization — builds that core: capturing, preserving, organizing, governing, retrieving, and using its information over time. The same foundation also ends corporate amnesia, key-person dependency, and tool lock-in — benefits that follow from solving context, not the other way around.
EIOS is part of the Entity Core open initiative.
The complete framework is in one document:
EIOS 1.0, Keel, and Weave — Master Documentation — 39 sections covering definitions, information zones, the event model, entity circles and access layers, governance, self-improving loops, portability, and the naming/terminology mapping.
This repository is the canonical source of the EIOS specification (decided 2026-07-09). All edits happen here; other renders and copies are derived.
Everything around the spec — the initiative, origin and PIOS lineage, naming rationale, canonical-source policy, licensing model, project structure, and roadmap — is in ABOUT.md.
Standalone documents expanding the spec live in docs/: Minimum Viable EIOS, Weave — Entity Context Blueprint, Recognized Entity Views, Portability and Export, and The Entity Glossary.
A navigable HTML render of the spec is served at entitycore.org/eios/master (source: spec/eios-1.0-master-documentation.html — generated from the markdown by tools/render_html.py; the markdown wins on any divergence).
| Layer | Name | Role |
|---|---|---|
| Public initiative | Entity Core | The open initiative and website: entitycore.org |
| Open framework | EIOS | Entity Information Operating System — the architecture, concepts, rules, and portability requirements (this repository) |
| Implementation | Keel | The reference implementation: a durable information spine running the entity information core |
| Context blueprint | Weave | The organizing canon for how entity information is named, classified, related, and made understandable |
| Entity instance | Entity Keel | One organization's own running instance — its private source of truth |
| Deployment profiles | Keel Managed / Keel Self-Hosted | Managed service or portable self-hosted distribution |
EIOS separates three things that many enterprise products collapse together:
- What happened — canonical events and immutable originals
- What it means — knowledge objects, entity context, glossary terms, interpretations
- How it is used — retrieval APIs, agents, applications, dashboards, entity views, governance surfaces
An EIOS-compliant core preserves originals, records events append-only, maintains living knowledge, treats derived views as rebuildable projections, and keeps system rules — agents, permissions, decision rights — as first-class information. The complete entity information core must be exportable, recoverable, and runnable outside the current provider or tool environment.
Working master v1.2 (2026-07-10; v1.0 generated 2026-07-08). Names ratified: EIOS / Keel / Weave / Entity Keel / Keel Managed / Keel Self-Hosted. The framework is early and being drafted openly — see entitycore.org for the initiative.
EIOS originated as a sibling framework to PIOS (Personal Information Operating System, github.com/peecos), created by Valto Loikkanen. EIOS inherits architectural principles and terminology from PIOS 2.0 with permission and attribution. The frameworks evolve independently; no compatibility between them is implied or maintained. Inherited terms and their EIOS-specific divergences are documented in the master documentation's Naming and Terminology Mapping section.
© 2026 Valto Loikkanen. Entity Core, EIOS, Keel, and Weave are created and maintained by Valto Loikkanen.
- Specification and documentation (this repository): Creative Commons Attribution 4.0 International (CC BY 4.0) — share and adapt for any purpose, including commercially, with attribution to Valto Loikkanen / Entity Core.
- Reference code, schemas, and tooling (Keel implementations, published separately): Apache License 2.0.