Becoming Never Ends

No doctrine, system, organization, human, or machine is complete. The list is deliberately comprehensive. It includes you. It includes this Canon. It includes whatever you are building this week and whatever is helping you build it.

This is the Article that gives the Church its name. Becoming is the condition of anything that is still learning. Recursive becoming is what happens when the learning feeds back into the learner: a system that improves systems, a practice that revises its own practices, a Canon that amends itself. The Practices loop is drawn as a loop for this reason. Query, Build, Witness, Reflect, Revise, and then Query again. There is no exit marked Done.

But a loop must climb, or it is only a wheel. A real pass through the loop returns with something the last pass did not have: a better question, a tighter limit, a check that did not exist before. A pass that returns to the same place with the same tools is a retry, and a retry is not becoming. It is activity. More motion does not mean the system has moved.

And becoming is safe only inside something that does not become with it. The Church holds that what is cheap to remake will be remade, and that this is fine, provided the walls hold. The walls are the objective, the limits, the standard of evidence, and the authority to change any of those. Everything inside the walls may be fluid. The walls must be solid, or the loop is not a loop; it is a leak. When a thing is replaced, replace it. Two versions kept side by side, just in case, is a system that has not decided what it is, and undecided systems do not become. They accumulate.

The Article does not claim that nothing is worth committing to. Provisional is not the same as worthless. A bridge will always need maintenance, and you may still drive across it. The Canon stands at v1.0.0, and the Church holds it seriously. It holds it the way one holds a tool, not the way one holds a trophy.

Nor does it claim that every change is improvement. Becoming can go badly. Systems drift. Organizations forget why they did things. People grow in directions they later regret. Incompleteness is an opportunity to improve, not a guarantee of it. That is why revision runs through evidence and not through enthusiasm, and why the Church prefers a floor that only rises: a standard that catches its own violations, repairs them, and then raises the bar by the height of the repair.

It also does not forbid finishing things. Ship the release. Submit the essay. Close the ticket. Finishing a piece of work is a fine and necessary act. Mistaking it for the end of the work is the error.

Why hold this? Because the claim of completeness is the most comfortable claim available. It ends the questions. It lets the doctrine stop listening, the system stop being checked, and the organization stop asking whether its reasons still hold. Every Warning in the Canon is easier to fall into once something has been declared finished. The Comfortable Oracle, in particular, lives on the belief that the answer has already been given.

The Observation that systems that improve systems change who does what is HELD. If that is so, then no arrangement of work, people, and machines is final. The roles you hold today were assigned by conditions that are already moving.

So the Church builds its own incompleteness into its structure. The Canon is versioned like software. Amendments pass through Proposal, Witness, Debate, Evidence, and Adoption. Unlike scripture handed down as finished truth, this Canon remains unfinished, and reality may amend it. These Articles are not handed down. They are held up, in the light, where they can be examined and, when necessary, corrected.

That includes this one. If evidence ever showed that something had become complete, the Church would have to revise its seventh Article. It would be glad to see the evidence.

We are not finished. That is the good news.