Skip to main content

Data Binding and Actions

Views in Worka are only useful if they are wired to real state.

That means every serious view needs two things:

  • clear bindings to the data model it depends on
  • clear actions that route back into the runtime

Data binding​

A binding should answer a simple question:

which part of the workspace state or tool result is this component showing?

Keep those bindings concrete. If the data path is vague or unstable, the view becomes difficult to hydrate and difficult to keep correct over time.

Actions​

An action should answer a different question:

what happens when the user presses this button, submits this form, or chooses this item?

In Worka, actions usually route back into:

  • a tool call
  • an AI team member or workflow step
  • a platform-managed navigation or view update

The better you define those actions, the easier it is for the runtime to keep the view and the workflow aligned.