← Back to Auturis

Use Cases

What the "What is Right?" track does with a rule proposed for a group.

Two worked examples, shown end to end. Other cases that were here have been withdrawn while they are revised: they were built on an earlier form of the rights check and showed figures the tool no longer produces.

Kestrel Ridge Rights Test

Worked demonstration

An invented case about a nonprofit hospital whose leadership proposes two rules: a strategy for growth, and an exception for times of crisis. Auturis checks what each rule would do to the capacity of the six groups affected by the hospital's decisions to thrive. Each rule is shown beside the app's own report, unedited.

Read the case study

Extends this case

Nova Scotia, 1760: A Rights Test

Historical case

A test of one reading of the Treaty of Peace and Friendship of 1760: that it gave the British Crown title to the land of Nova Scotia. Auturis checks what that reading would do to the capacity of ten groups of the time to thrive, then takes a second look at its own findings and checks again.

Read the case study

Rewriting Salem's Rule

Classroom lesson

A lesson plan for a unit on The Crucible, in which small groups of students write their own replacement for the rule by which the Salem court judged evidence, check it against the people of the play whom it would bind, and compare what each group found. The plan has not yet been taught to a real class.

See the classroom cases

Have a case of your own?

Send a real governance rule or policy dispute — yours, your organization's, or one you've read about — and I'll run it through the hindrance check myself and write back with the result and the reasoning behind it.

The result is only as trustworthy as what I have to build from, so please include, as best you can:

  1. The rule itself stated generally — who has the authority, what they'd do, under what conditions — not just an account of one specific incident.
  2. Every stakeholder the rule would actually affect, not only the two obvious sides.
  3. For each one, their real interest stated concretely — what's at stake and how, specifically. Vague summaries produce unreliable results.
  4. Roughly the same level of detail for every stakeholder you want compared against each other.
  5. For real situations: what's documented fact versus your own read of it.

A clean two-sided dispute, well described, is something I can stand behind. A case with several stakeholders needs multiple runs and a consistency check before I'd trust it, so I may ask follow-up questions rather than run something too thin — that's not gatekeeping, it's what keeps a verdict from being blamed on the system when it was really an underspecified case. No cost, no signup, and no promises on turnaround; I'm one person doing this by hand. If it turns out to be a good case, I'll ask before publishing it here — attributed or anonymized, your call.

Submit a case