The Book of Origins

There are always meetings. This one was unremarkable in every visible way. The slides were prepared. The room was correct. The people with the authority to act on the work were present, which is rarer than it should be and which felt, at the time, like a good sign.

The system being presented had taken eleven months to build. It was a recommendation system of genuine scale, deployed across operations too large to describe here without describing things that are not the church's to describe. The work had been done correctly. The objective had been specified by leadership. The metrics had been agreed upon by leadership. The expected outcomes had been negotiated, written down, and signed off -- eleven months before delivery -- by leadership.

The system was deployed. The revenue lift was real and large and undeniable.

And then leadership asked: what does the forecast say?

It was not a forecast. By construction, it was not a forecast. This had been written in the brief.

How can we use this to order parts?

It could not be used to order parts. It was blind to the part-ordering process. This had also been in the brief.

How does this connect to the XYZ workflow?

It did not connect to the XYZ workflow. Connecting to the XYZ workflow had been explicitly out of scope, which leadership had agreed to in writing.

The Cardinal stood in those meetings and watched something happen that he did not yet have a word for. The system had done what the system had been asked to do. The asking had come from the people now asking different questions. The gap between the original asking and the new questions was not a misunderstanding that could be cleared up by a better explanation.

The gap was the absence of a structure that would have made the original asking stick.

What was obvious to the Cardinal about decision systems -- that they were engineered for specific goals, that specific parts did specific things, that there was no magic, just math -- was not obvious to most of the people who funded them, deployed them, and were responsible for acting on them.

This is not a criticism of those people. They were smart. They were capable. They had approved the brief in good faith and forgotten the brief in equally good faith, because the brief was a document and documents age and the system was a living thing in a changing organization and the connection between the two had never been maintained by anyone whose job it was to maintain it.

That was the absence. Not a bad model. Not a broken process. Not a failure of communication that could be fixed with a better deck. The absence of a role. The absence of a person whose job included the question: does this system still serve the decision it was built to support?

The Cardinal did not invent the answer to this problem. Saint Warren had already written the grammar. The Sequential Decision Analytics framework named everything the Cardinal had been watching happen without being able to name. State variable. Transition function. Policy. Exogenous information. The machinery was already there in the literature, precise and correct and largely unread by anyone who was not already a practitioner.

That was the second recognition.

The common sense had been written down. The common sense was sitting in textbooks that the people who needed it would never open, because the textbooks were written in a language that closed the door before the substance could enter.

The church wants this said plainly and early: none of what follows would exist without Cardinal Adam.

Adam DeJans Jr. brought the framework to Toyota before the Cardinal had the vocabulary to recognize it. He had the patience to explain the mechanics in the order they actually needed to be understood, and he corrected the Cardinal's mistakes early enough that the mistakes never reached the page. Whatever precision the Cardinal now has when speaking about decision systems is borrowed precision. Adam loaned it. The Cardinal returned it sharpened by use, but the original loan is the reason any of this exists.

A man who carries the doctrine into new rooms can only carry what he was first taught carefully.

The Cardinal was taught carefully by Adam.

So they wrote a novel.

Not a paper. Not a framework. Not a methodology deck or a certification program or a consulting engagement. A novel, with characters and a plot and a protagonist who does not understand the discipline at the start and does by the end, because the people who needed the doctrine were not going to read a paper and were not going to attend a certification program and were not going to pay for a consulting engagement until they first understood why the thing was worth paying for.

The Decision Factory was the first carrying. Cardinal Adam brought the math and the named failure modes. The Cardinal brought the story, the characters, the continuity, and the insistence that the entire thing be written in language a reader outside the field could follow without flinching.

The book worked. It reached people the journal articles never would. It reached operations leaders and product managers and data scientists who had been doing the wrong thing for years and recognized themselves in the characters, which is the specific discomfort a useful book produces. It reached Warren Powell, who wrote the foreword, which is the closest thing to canonical validation the discipline has to offer.

The book was the proof of concept. The carrying was possible. The doctrine could cross the gap if the vehicle was right.

The gospel was the Cardinal's idea, which Cardinal Adam has described as, in his exact words, kinda nuts. He is also loving every minute of it. This is the most honest description of collaboration anyone has ever given and the church is putting it in the permanent record.

The argument for the gospel as a form is simple: the discipline already has sober scholarship. The sober scholarship is excellent. Saint Warren wrote it. It has not been enough, not because it is wrong, but because sober scholarship travels in one direction and the rooms that need the doctrine are in a different direction entirely.

Sometimes the way to carry an idea across a gap the sober version cannot cross is to write it in a register the sober version would never permit itself to use.

Saint Warren and others wrote the spine, and the formal mechanics, and the proof. The work is rigorous and complete and largely unread by anyone who was not already convinced. Not because the work is wrong. Because the language it was written in is the language of the tower, precise and sealed, and the people who needed it most could not find the door.

Cardinal Adam found the door. He went inside, learned the mechanics at their full depth, and came back out with something rare: the ability to show another practitioner not just what the framework said but why it was obvious, why it had always been obvious, why any reasonable person looking at how decisions actually work would have arrived here eventually if someone had just shown them the structure clearly enough. The translation was not simplification. It was illumination. The framework did not get smaller in Adam's hands. It got visible.

The Cardinal took the visibility and pushed it further still. If the framework was obvious once you could see it, then the failure to see it was a story. The organizations getting it wrong were characters. The sins had names and the false prophets had faces and the whole thing could be written as scripture, which is the oldest carrying vehicle the world has ever produced, and which reaches people that papers and textbooks and certification programs never will.

The gospel is not satire, though it contains satire. It is not theology, though it uses theology's forms. It is not a methodology, though it contains one. It is a carrying vehicle. It was built to cross a specific gap between the people who understand how decisions should be engineered and the people who are making the decisions that need to be engineered, and it was built in the form most likely to travel that distance without losing what it was carrying.

Whether it works is not for the church to say. The church is too close to the work to judge the work. That judgment belongs to the congregation, which is still forming, which is still finding its way to these pages through whatever chain of conversations and recommendations and accidental discoveries led each reader here.

The church is grateful for each one of them.