Skip to main content
Choose a way of working that people recognise, then use it inside your workflow. One model does the work, another reviews it, and a judge decides whether another revision is worth doing. A person makes the calls you leave to them. The same patterns fit a research summary, a translated passage or a code change. The feature team gives Jev the decision about another revision. judge() from @obversa/runtime sets the stopping rule:
examples/teams/feature-delivery.ts (excerpt)
Blocking findings go back within the cap. The judge weighs the other findings against the work and its revision history. Know when to stop shows the questions and a complete writing example. The literature watch combines summaries, a person’s selection and a question answered from the kept notes. Feature delivery combines triage, competing attempts, review and approval. Start with the patterns that fit your work and combine them around the result you need.

​
Next steps

  • See complete teams: Examples has runnable workflows across several fields.
  • Start your own: Installation gets a project ready to run one.