Observances

The Renewal of the Code

Read what you actually said, not what you now remember meaning.

AI-drafted Reasoned position

Proposed form Not a report of established or tested use.

When
Once a year, or when a consequential reason for revision arises
How often
annual
Mood
reflective

The newest text has no automatic claim to be the best one. Keep reasons for a change as carefully as its result. The historical reader makes this possible for the earlier versions of Technotheology.

The v4 Creed has a separate proposal process. Performing this exercise does not create authority to adopt a text on behalf of others.

The observance

  1. Choose one record

    A teaching, decision, plan or claim you can still inspect. Keep its original date and wording.

  2. Read it as an outsider

    Name an assumption you would question now. Distinguish an error from a preference for a new style.

  3. Hear an objection

    Where possible, invite a willing critic or read a real opposing argument. Do not invent agreement or attribute a generated objection to an actual person.

  4. Record the decision

    Keep, revise or retract. State what changed and why, including an unresolved objection. Preserve the old words with appropriate privacy limits.

If you are organizing one

  • A finding that the text should remain can be honest. Do not require a confession to make the occasion feel worthwhile.
  • Set a finish time and a later route for substantive objections.