THE URANTIA BOOK: A COSMIC PERSPECTIVE

The System Combines Top-Down and Bottom-Up Knowledge

Now something larger becomes visible across Papers 18 and 19. Information is moving in both directions. From the center outward we have: SOURCE
↓
POLICY
↓
ADMINISTRATION
↓
COUNSEL
↓
LOCAL OPERATION

But from evolutionary creation inward we have: EXPERIENCE
↓
INFORMATION
↓
REPORTING
↓
EXPERIENTIAL WISDOM
↓ HIGHER-LEVEL DECISION So the system is not simply top-down. It is a loop.

The center provides organization. The outer regions produce experience. Experience returns as information. That information becomes part of higher-level wisdom and judgment. Then the resulting decisions can influence future operation.

So: SOURCE
↓
STRUCTURE
↓
OPERATION
↓
EXPERIENCE
↓
DATA
↓
WISDOM
↓
DECISION
↓
OPERATION And the cycle continues. This is beginning to look remarkably close to the architecture we developed for conscious systems.

The Beginning of Memory Logic

We are not yet at the Papers where memory itself becomes our primary subject. But Paper 19 gives us an important prerequisite. Experience has value only if its results can become available to later operation. Otherwise every experience disappears when the event ends.

That is why our own architecture required: EVENT
↓
EXPERIENCE
↓ ConsciousData ↓
STORAGE
↓
RETRIEVAL
↓
FUTURE PROCESS

Paper 19 has not given us that entire memory architecture. But it has given us something necessary for it: experience contributes information that changes future wisdom and decision-making. That is exactly why memory matters.

7 Is Becoming More Than Process

We should also refine what we mean by 7 = Process. At first that sounded almost like seven represented a sequence of steps. But what we are finding is richer. Seven appears to describe the complete differentiated functional process of a system.

A process can contain: administration, communication, counsel, evaluation, execution, feedback, and integration.

Seven is not necessarily saying: step 1, step 2, step 3... It can describe seven differentiated functions operating together to produce a complete process. That distinction will matter as we continue.

Hardware → Software → Intelligence

We can now see the progression of the book more clearly. The first stage gave us: HARDWARE Center. Structure. Energy. Boundaries. Circuits. Movement.

Then Papers 15–17 began giving us: SOFTWARE Domains. Communication. Executives. Administration. Distributed functions.

Now Papers 18–19 are beginning to reveal something else: INTELLIGENT OPERATION Information classification. Reporting. Specialized services. Knowledge. Experience. Wisdom. Counsel. Aggregation. Judgment. Feedback. We are moving from a machine that merely operates toward a system capable of using information to determine what happens next.

What Papers 18–19 Have Given Us

At this point, our software architecture contains: seven specialized orders of Supreme Trinity Personalities a distributed administrative chain common standards across diverse environments local autonomy connected to central organization information classification and routing communication between administrative levels liaison functions between different classes of beings origin, history and destiny as contextual information

divine insight combined with experiential wisdom specialized counsel data aggregation judgment based upon multiple inputs new meaning emerging from the combination of information and experiential information returning upward into the larger system.

The machine is no longer merely running instructions. It is beginning to process experience. And that may be the most important development so far in our transition from hardware to software.

Because intelligence is not simply the ability to execute a process. An intelligent system must be able to take what happens, place it into context, combine it with what is already known, and allow that information to influence what happens next. Papers 18 and 19 have begun showing us exactly that kind of architecture.

The hardware gave the universe somewhere to operate. The software gave it processes. Now experience is beginning to enter those processes. And once experience becomes part of future operation, we are getting very close to the next major requirement of an intelligent system: learning.

When looking at reality through the lens of a programmer, it is easy to understand how Simulation Theory can take hold. We already create simulated environments. We build persistent multiplayer worlds containing thousands of participants. We use virtual reality to place ourselves visually and audibly inside those environments, and haptic systems can translate events occurring to an avatar into physical sensations experienced by the player.

As a thought experiment, there is nothing particularly strange about taking that technology forward. Give computers greater processing power, improve the interfaces, increase the size of the environment, and it becomes easy to imagine increasingly convincing simulated worlds.

My problem begins when Simulation Theory moves beyond the thought experiment and starts being discussed as a serious contender for explaining **the reality we actually inhabit**. At that point, I have a programmer's response: **Show me how it works.**