Concepts

This page introduces the three ideas the rest of the platform is built on.

Runtime

The Twynel runtime is the shared layer that apps talk to. It is meant to run locally or as a hosted control plane, with the same public SDK in either case. The runtime, not a prompt, enforces how an avatar is allowed to act.

Expected primitives (design, not a shipped API yet): identity and ownership, a control plane (modes, approvals, live handoff, kill-switch), scoped memory, and a typed action or capability interface.

Avatar

An avatar is a long-lived hybrid agent with a single owner. It can carry a portable identity and memory, and it can be used from more than one app when the owner consents. The avatar is not the same thing as a single chat session, and it is not tied to one model vendor or one renderer.

Human+AI pairing

A Twynel avatar pairs a person with an AI counterpart. Control can sit with the human, with the AI, or in a hybrid mode where the AI drafts or acts and the human approves, takes over, or stops the work. Handoff and a kill-switch are first-class, not an afterthought in the user interface.