Keep business state beside the work that changes it.
Declare the records, relationships, queries, and files the system needs. Apps, workflows, and agents use that same named state.
The system needs a shared meaning for its data.
External tools can remain the source of truth for their records. The Swirls project defines how those facts become the state your Apps and workflows use.
Name the facts once. Use them across the system.
One project can define stored records, queries over connected systems, and the Apps, workflows, and agents that use the result.
Example: An operations system can combine account, support, usage, and billing facts in one view, then use the same state to trigger workflows and reviews.
Swirls owns the production work behind it.
Declared managed storage, supported access enforcement, background execution, and run history.
Keep provenance
Preserve what each external record means and where it came from.
Define meaning
Define the relationships and business meaning the operation needs.
Use it everywhere
Put the same state into Apps, workflows, agents, and reviews.
- Business records
- Relationships
- Queries and views
- Files and durable state
- Connected source data
You own
Which facts matter, what they mean, how they relate, and what the business should do when they change.
Define the facts the system depends on.
Name the records, their relationships, and the work that should happen when their state changes.