Keel · Implementation
A durable information spine for the entity.
Keel is the reference implementation of EIOS. It preserves originals, records events, holds knowledge objects, and serves derived views to humans and agents.
Definitions
- Keel
- The reference implementation and durable spine that carries entity information through time.
- Entity Keel
- One organization’s own running instance of Keel — its entity memory in operation.
- Portability
- An Entity Keel should be exportable, recoverable, and runnable outside any single provider.
Source to memory to action
How information flows through an Entity Keel.
Sources
- · meetings
- · emails
- · systems
- · agreements
- · financials
- · signals
Entity Keel
- · originals
- · events
- · knowledge
- · derived views
- · system rules
Use
- · humans
- · agents
- · dashboards
- · workflows
- · reports
- · decisions
Building blocks
What lives inside Keel.
Layer
Source preservation
Originals kept unchanged: contracts, minutes, statements, messages.
Layer
Event log
Append-only history of what happened, when, and by whom.
Layer
Knowledge objects
Living entries for customers, agreements, decisions, risks, and more.
Layer
Derived views
Reports, dashboards, and summaries rebuilt from originals and events.
Layer
Agents & apps
Humans and AI agents acting within governed context and boundaries.
Layer
System rules
Access, sensitivity, decision rights, and governance policies.
Deployment
Managed or self-hosted.
Managed Entity Keel
Hosted for the entity, with export and portability guarantees so the memory remains the entity’s own.
Self-hosted Entity Keel
Run inside the entity’s own environment, following the Keel reference architecture.