Put the work in front of the people doing it.
Declare the app beside the data, workflows, agents, and access rules behind it. People get one hosted place to see state, take action, and review consequential work.
The interface lives in the system source.
Define the records, actions, views, and decisions in the same .swirls project as the work they control. The runtime keeps the interface and its behavior on one system model.
Every screen points to declared resources.
An App can read and change named business data, start a workflow, show its progress, and return a review to an authorized person. The live interface uses the resources declared in the same source.
Example: A CRM can show an account, the work in progress, and the next approval on one screen. The same source also defines what happens when someone acts.
Swirls owns the production work behind it.
Hosting the supported App, connecting it to declared state and actions, enforcing supported resource boundaries, and running the work behind it.
Show state
Put the records and status for the job in one view.
Start work
Connect interface actions to named workflows.
Route reviews
Send approvals and exceptions to the authorized person.
- Dashboards and record views
- Forms and actions
- Human review
- Role-aware interfaces
- Live workflow state
You own
What people need to see and do, the business rules behind each action, and the result the app must produce.
Define the screen and the work behind it together.
Bring the records, actions, and decisions the job requires. Keep them in the same system source.