Flagship experimental system / Hanoi
AELIA
A life
that continues.
AELIA — Autonomous Embodied Life & Intelligence Architecture — is an experimental architecture for persistent, autonomous artificial entities.
Memory · Identity · Social cognition · Self-directed behavior
RUNTIME 02 / INTERPRET
Not a chatbot with more tools. Tools are its hands, not its purpose.
AELIA explores how an artificial entity could maintain a history, build models of people and the world, develop internal states, form relationships, and increasingly decide when and how to act.
AELIA is an experimental research architecture, not a claim of consciousness, sentience, or AGI. Its subsystems are expected to change as the research develops.
Continuous existence model
A response is only one moment in a continuous loop.
The difference is not a longer prompt. It is the ability for interpretation, memory, belief, state, and consequence to remain in play.
- 01Perceive
Notice an event, person, message, or environmental change.
- 02Interpret
Relate what happened to context, history, and uncertainty.
- 03Remember
Store or revise traces that may matter later.
- 04Update beliefs
Change working models of self, people, and world.
- 05Update state
Rebalance attention, goals, priorities, and social stance.
- 06Decide
Choose whether action is warranted — including silence.
- 07Act
Speak, use a tool, continue a task, or leave space.
- 08Observe
Track the consequences of action in the environment.
- 09Learn
Let experience reshape later behavior.
- 10Continue
The system remains a process, not a completed reply.
A runtime,
not a single model.
AELIA treats the language model as one component in a larger cognitive system. The architecture is designed as a loop rather than a pipeline ending in a response.
events / people / messages
browser / code / APIs / communication
What does an artificial entity do when nobody is asking?
AELIA investigates a life loop where activity can emerge from memory, goals, curiosity, social impulses, unfinished work, personality, environment, and opportunity — not from a hardcoded “if idle, do X” rule.
Current experimental runtime
Built in public
with room to change.
The current research runtime uses a worker-based architecture with a runtime coordinator, event bus, memory worker, state workers, dialogue engine, affect evaluator, social context, and tool/MCP interfaces across platforms such as Discord and Telegram.
This is not a final architecture. Components are expected to be refactored, replaced, or removed as the research progresses.