Interaction Framework

Target definitions hold the authoring data for points, variants, command rows, requirements, execution actions, policy profiles, theme colors, linked groups, composite surfaces, and widget payloads. The editor workflow starts from default rows so designers edit the interaction shape instead of building every nested entry manually.

Target components register interaction points, manage enabled state, cooldowns, busy state, variant overrides, save ids, and multi-participant routes. Interactor components resolve focus, visible handles, surfaces, paging, progress, and activation requests.

The UI module turns focused runtime surfaces into projection bundles, prompt entries, control entries, progress state, outcome state, and widget payload updates. Widget Blueprints based on the interaction widget base can render the supplied state without recreating runtime validation.

Blueprint and C++ teams can add custom requirements, command execution actions, prompt text providers, widget payloads, prompt widgets, save storage bridges, and editor-authored policy objects while keeping the target definition as the main content asset.