Entities
Things with identity, lifecycle, permissions, and meaning inside the domain.
OntahíComing soon
Ontahí
Executable domains, from everyday apps to autonomous systems.
Ontahí models software through entities, relations, operations, policies, and events. When work needs time, resources, or autonomy, the same model grows into durable, observable executions. No special Actor primitive required.
Living Systems
To build a system is to enter a long conversation with change.
The first Ontahí essay starts before frameworks and actors. It asks why systems evolve, how requirements reveal hidden dimensions, and what it means for a model to change without losing itself.
Read Why Systems EvolveCore model
A small application can still deserve an ontology.
Ontahí is useful before autonomy enters the picture. A domain becomes easier to build when its names, boundaries, transformations, and history are explicit.
Relations
Connections that make the system navigable as a graph, not a pile of tables.
Operations
Possible transformations, named as domain actions rather than raw endpoints.
Events
Facts that preserve what happened and make change observable.
Executions
Invocations that happen in time, with identity, status, result, and history.
Emissions
Values produced while an execution advances toward its final result.
Resources
Cost, capacity, quotas, and scale modeled explicitly when they matter.
Policies
Rules for admission, authority, limits, priority, and implementation choice.
Emergent autonomy
An actor is not a new kind of thing.
Autonomous behavior emerges when an entity has operations whose executions can be scheduled, observed, limited, and resolved over time. Some domains need this. Many only need a better way to name and execute their domain.
- Identity & memoryAn entity carries state, context, and history across many executions.
- OperationsIts capabilities are operations, or useful views over related operations.
- ExecutionsWork can persist, stream values, retry, cancel, and remain observable over time.
- Resources & policiesAvailability, budgets, limits, priorities, and implementations stay explicit.