Loading the checked-in report…
Integration experiment / 24
An agent can call a function. Who decides the action?
A2UI names a catalog function and authorizes the caller. A host-owned invocation claim and ĀML check the call ID, exact destination, and approval before the callback runs.
This page replays nine project-authored local cases from the checked-in report. The callback simulates an effect. It sends no real message and does not run a full A2UI renderer. A2UI v1.0 is a candidate specification.Agent → renderer → host
01 A2UI catalog · allowedCallers
↓
02 Host ID claim + ĀML action rule
↓
03 Host callback · receipt
A host-owned ID claim and exact action gate before dispatch.
9reproducible scenarios
v1.0pinned A2UI message shape
0live external tool calls
Change the call. Follow the gate.
Select a recorded case to inspect the request, response, AML plan, receipt, and actual callback count.
What this proves: this repository's adapter can compose A2UI's agent-call catalog boundary, a local ID claim, and an exact AML host action boundary in these nine scenarios. Full catalog validation, session negotiation, durable cross-worker ID uniqueness, authentication, real approval, delivery, and independent conformance remain the host's responsibility.