Semantic visualization prototype · Section 5
Registration becomes readiness.
Registration changes, runtime readiness, fetching, and capability availability are four separate causal steps.
Acceptance scene
Availability is the result of the sequence. Neither registration changes nor runtime.ready carries capabilities into Amp.
- Registration changes. The five ordered groups—commands, tools, skills, events, modes—become pending in the child. Amp’s rack stays empty.
runtime.ready. One readiness event crosses the process boundary without containing capability tokens. The gate opens.- Amp fetches five groups. Amp requests commands, tools, skills, events, and modes from the child in that order.
- Capability available. Fetch results dock in Amp’s rack. Only now does the target capability become available.
Phase 1