Semantic visualization prototype | Section 6
When the plugin asks Amp to draw.
The active child requests an interface action across the existing transport. Amp handles the request and owns the rendered presentation.
Active relationship
The request crosses from child to Amp before the panel appears. The readiness gate and two lanes are the same geometry and transport established earlier.
Request direction and rendering ownership
- Plugin prepares the request.
The active child initiates a supported interface action.
- Request crosses toward Amp.
It uses the existing plugin-to-Amp message lane.
- Amp handles the request.
The request has reached the main process; no second transport is introduced.
- Amp renders the panel.
Only now does the interface panel appear, inside the Amp frame.
- Ownership stays split.
The plugin owns the request. Amp owns the presentation.
Reverse RPC names the request direction across the existing transport. It is not a second channel. No intermediary or rendering framework is part of this mental model. See the official Amp Plugins guide for the supported plugin UI surface.
Phase 1 of 5: Plugin prepares UI request