Structured decisions in an agent workflow

Agent workflows mix two different jobs: deciding which declared action fits a request, and carrying out that action. Siliqun Rotor provides the decision and flow surface. The calling application remains in control of permissions, credentials, and execution.

For a bounded question, send the observed state and the choices or criteria the application is prepared to handle. Read the returned outcome:

decided identifies one selected answer and its available evidence.
unresolved preserves multiple supported answers.
refused reports that none of the declared answers was supported.

This boundary is useful for routing, selecting among declared tools, and checking required inputs. It does not turn an open-ended reasoning problem into a bounded question. When the request requires generation, outside knowledge, or an action with side effects, keep those steps in the caller's chosen service and application.

The HTTP API and SDKs preserve the request and response structures described in the protocol. See the agent harness concepts for how a saved workflow separates a decision from executing the approved action.