AUIP is the application-session and typed-action protocol used by Amadeus to let an AI companion observe and participate in interactive applications through declared state, actions, and execution receipts.
Status — September 2026: experimental v0, implemented in Amadeus and evolving through real application sessions and development validation. This repository documents that progress. The implementation, bundled SDK code, examples, and integration tests live in the Amadeus repository; there is no independently versioned AUIP SDK release here yet.
An application exposes a compact view of its state and a manifest of typed
actions. Amadeus attaches it to an identified AppSession, interprets the
user's intent, checks the requested action against current authority and
state, and sends the action to the application. The application validates
its own rules and returns a receipt describing the outcome.
Verified application artifact
-> authorized attach and registration
-> AppSession with revisioned state and declared actions
-> Host validation and action request
-> application acceptance or rejection
-> verified receipt and user-facing response
The application owns its mechanics, domain rules, and state changes. The Host owns session identity, permissions, action dispatch, and receipt verification. The conversational model interprets and explains; its words alone do not establish that an action happened.
AUIP's focus is continuing interaction with an application: what state is current, which actions are available, what actually changed, and when the session ends. An application does not need to become a Work Provider or an MCP server to participate.
These links point to the existing Amadeus implementation, not to separate packages released from this repository.
| Entry point | What to inspect |
|---|---|
| Application-session guide | Attach, manifests, authority boundaries, and disconnect behavior |
| Web SDK | Browser application binding |
| Managed Core | Transport-neutral commit mechanics, revisions, and application-owned actions |
| Gomoku | Board-game application example |
| 2048 | Grid and directional-action example |
| Reactor | Simulation and control example |
For evidence boundaries, current limitations, and SDK release criteria, read Development status.
The proposed next milestone is a small, independently versioned reference SDK with a documented Host contract, a minimal runnable example, and conformance checks. Existing SDK source is the starting point. An independent package would still need a compatible Host for session and permission services; it would not include the whole Amadeus runtime.
There is no release date or stable compatibility promise yet. Current work is documenting the implementation and learning from actual use before committing external developers to a separately supported API.
This update publishes documentation and links only. Private development history, raw real-session transcripts, credentials, personal character or voice material, and application assets without redistribution rights are not imported. Public examples above are existing source examples, not transcripts of private sessions.
The linked Amadeus files remain under their own repository's license and notices. Until the first reviewed source release adds an explicit license, this repository does not grant permission to use, modify, or redistribute future code or media. Release planning and general discussion currently live in the main Amadeus repository.