The model in five sentences
An Order is the change that you want. A workflow takes the Order through nodes, the steps that do the work. A callback gate asks for a structured answer before work continues. Evidence records the checks and decisions you use to judge the result. The runtime runs the graphs and stores their events and artifacts.Your tools stay yours
Your editor holds the code. Your terminal host supplies the panes, layout, and keybindings. Obversa is a guest in those tools. Engine plugins connect the runtime to agents and model services. You choose the plugins and credentials for your workflow. A local review surface gives you a place to inspect a diff and return comments. The runtime runs on your computer with your repositories. An engine plugin can call an external model service.You choose the process
A small fix and a large feature need different work. You define the steps, dependencies, checks, and decisions that fit each one. The workflow bank gives you runnable examples to copy and change. Physical production can need batches to justify changing tools. Software work can move one change at a time. You can follow an Order from request to result, with feedback along the way.Read next
- Orders: Define the change you want.
- Workflows: Describe how the work moves.
- Callback gates: Ask for a decision.
- Surfaces: Give a person a place to answer.
- The runtime: Run the graph and keep its record.