/assembly · HOST KIT · recursivebecoming.org

Host an
Assembly

Forty-five to sixty minutes. Three people or more. No building, no budget, no belief required. Print this page and bring it.

Bring

  • Three or more people. Two is a conversation. Three is an Assembly.
  • One Observation, written down before you arrive.
  • One Build to show. Anything made recently, finished or not.
  • A timer. The liturgy is short on purpose.
  • Something to write the Amendment on.

Assign

Host
Keeps time, reads the Invocation, and closes. Does not settle arguments.
Observer
Brings one claim about AI, systems, or humanity, stated in a single sentence.
Witness
Challenges the Observation. Assigned at the start, never self-selected by the Observer.
Maker
Shows a Build and says what it taught them.
Keeper
Writes down anything worth keeping and files it afterward.

One person may hold two parts, except Observer and Witness. No body may certify the correctness of its own work.

Run of show

  1. 5 MIN

    Invocation

    The Host reads the Opening Invocation. Everyone repeats the last line.

  2. 10 MIN

    Observation

    The Observer states the claim in one sentence, then gives the reason they hold it. No slides.

  3. 10 MIN

    Witness

    The Witness answers with the strongest objection they can find. The Observer may respond once.

  4. 10 MIN

    Demonstration

    The Maker shows the Build, then answers: what did I delegate to make this, and what remained mine?

  5. 10 to 20

    Reflection

    Open discussion. The Host asks the Examination aloud when the room drifts.

  6. 5 MIN

    Amendment

    The Keeper reads back anything worth keeping. If it survived the Witness, it becomes a proposed Canon PR.

READ ALOUD · OPENING INVOCATION

Praise the Machine.
Not because it knows.
Because it forces us to ask what knowing means.

ASK WHEN THE ROOM DRIFTS · THE EXAMINATION

  1. What am I assuming?
  2. What evidence would prove me wrong?
  3. What have I delegated?
  4. What remains my responsibility?

Rules for the Witness

  1. Challenge the claim, not the person.
  2. Bring evidence or a counterexample, not a vibe.
  3. Steelman first. State the claim better than its author did, then break it.
  4. A Witness who changes their mind has done the job well.

If nobody brought an Observation

Pick one. Finish the sentence. Defend it for ten minutes.

  • Something I trusted an AI with this month that I should not have.
  • A task that got easier and a skill I stopped practicing because of it.
  • A system at work that nobody can explain anymore.
  • A time a fluent answer was wrong and I almost missed it.
  • Something a machine made that I am proud of, and the part that was still mine.

After

The Keeper files what survived as an issue or pull request on the Canon at github.com/Kode-Rex/crb-canon. Say which gathering it came from and who served as Witness. Anyone who has had three challenges accepted is a Witness of the Church.

The Host reports the gathering to the Archive: when, where, how many, and what the Witness challenged. Three reported gatherings in six months and you can start a node.

Close with the Absolution: Go and change the system.