Reason Commons, explained with itselfsnapshot

authors

Guided walk9 steps · through the record itself

Where you are

This is a real Reason Commons record, published as a snapshot on September 10, 2026. The record cannot change; anything you try stays in your own copy, in this browser. This panel is a 9-step walk through it.

Thinking partner

The worked example on the landing page was another team's record, in the same four views you are about to read. This commons' subject is Reason Commons itself — the product explaining itself with its own instrument. The landing page promised to separate proposals from warranted reliance. That separation has two names here: Standing is what the team accepts, reliance is what it is willing to act on, and at step 6 you meet them as two separate switches. I will take you through the record in the order the reasoning asks for: what it is for and how it is counted first, because everything after is judged against that.

skip to the judgment

Step 1 of 9
What this commons stands behind
Start where a newcomer starts. Standing is the account of what the team currently accepts, told from the record rather than written by anyone.
Read the status sentence, then the explanation. Every underlined phrase opens the record behind it — the idea, the evidence, the person.
Open Standing

0 of 9 steps · kept on this device

read along · to take part, start your own commons →

Published snapshotSep 10 · shared by David Joseph · with Rufus Pollock · model v6This snapshot cannot change. Anything you record here stays in this browser tab and changes nothing published.Start your own commons →

meet reality

Act & Learn

Commit an expectation before acting. Record what happened before explaining it.

Observable now · reality check due Dec 31

The outcome can now be observed.

Read Standing, then open the goal's measure in the header. We expected: You can state this commons' goal and the unit it counts.

Checking in before the window closes records an incomplete test: the answer stands, and the record says the window had not run its course.

Observable now · reality check due Dec 31

The outcome can now be observed.

In Model, open the relationship between accepting a claim and acting on it, and read the assumption it rests on. We expected: You can say why accepting a claim does not by itself authorize acting on it.

Checking in before the window closes records an incomplete test: the answer stands, and the record says the window had not run its course.

Before we rely on an action· 4 of 7 without an expectation

These 4 actions have no expectation committed yet. Nothing may rely on an action until one is.

In Decide, examine the judgment that is waiting and read what would change if you stood behind it.
In Act & Learn, record what happened against the expectation this commons sealed about your first step.
Step the model back to an earlier version and find what the authors changed their minds about.
Download this commons as a file.

Effects reality has confirmed

reality agreed

A reader stepping back to an earlier version can still read the wording that was replaced.

We expected: A reader stepping back to an earlier version can still read the wording that was replaced.

we’re observing

You can state this commons' goal and the unit it counts.

We expected: You can state this commons' goal and the unit it counts.

we’re observing

You can say why accepting a claim does not by itself authorize acting on it.

We expected: You can say why accepting a claim does not by itself authorize acting on it.

still a prediction

You can name the two separate acts a decision here records.

still a prediction

One loop has closed: an expectation committed before you arrived was answered by what you did.

still a prediction

You can point to a correction that kept the earlier reasoning readable.

still a prediction

You hold the reasoning in a form no particular model owns.

Work reported done

Draft this commons so a correction supersedes the earlier wording instead of replacing it.
Reported completed Sep 10

Completed work is not confirmed change. Closing an issue records completion, never success.

The record

Every accepted action with its expected effect, execution and evidence. Choose an action to inspect it.

What do we actually do, and what should each step produce?

Read downward: each action sits above the effect it should produce.

main chain→ … 6 more steps … →

model details ▸

Actions · Transition Tree — its job is to show concrete actions and their intended effects. The chain above is the action and what it should produce. 17 ideas · 16 relationships ·

Reality so far✓ 1 effect confirmed◐ 2 effects under observation○ 4 effects with windows not yet opencounted in effects reality has confirmed — never in actions closed

Drawing the reasoning…

These are the steps above, grouped by what you can do about each one.

Ready to do

Attempted

1doing and observing stay separate

David JosephDavid Joseph · took this on

Three questions, never one number

the three rates

none of these substitutes for another

what the system produced

a reader who has closed one loop here per week — no measurement under this definition yet

baseline 0 · measured at v1

goal units produced by the modeled system per period, read from The reader's own device record. This snapshot carries no readings; a live commons would read them from its observations.

what the plan made real

1 effect confirmed by a fair check-in

1 action attempted — work done, which is not throughput

validated movement through the change plan

what we found out

1 fair test · 0 contradictions

33% of expectations answered · 1h from doing to knowing

how quickly reality's answers become resolved model consequences