// RAIM: the base map.
The analyses, stories, and action guidelines share a map. RAIM separates what follows from physical constraints, what remains a hypothesis, and what enters as a declared choice. This is how it connects body, inference, coordination, and creation within a single architecture.
A simple idea, taken to the end.
RAIM starts with constraints we can test: every inference needs physical support, every organism pays costs in time and energy, and no finite agent has access to the territory's complete state. From there it follows the appearance of boundaries, predictive models, links among agents, and works that modify the environment.
The map does not claim that will, politics, or a life project follow inevitably from physics. L0 through L2 describe constraints and capacities. At the L2 to L3 junction, RAIM declares two choices: treating precision weighting as genuine volition and privileging long-horizon agentic persistence. From those premises it compares protocols and consequences. If you choose an end and a policy, the map helps trace the costs, capacities, and routes involved.
What separates an honest map from a trick.
Three constraints keep the causal chain and the status of each claim visible.
Zero magic
Every mechanism needs a causal chain to physical support. A declared premise may begin a derivation; an unexplained force hidden halfway through the stack may not.
Conditionals instead of cosmic commands
RAIM asks what happens if you choose an end and a policy. Physics constrains the options but does not select what is worth pursuing for you.
Visible premises and support levels
Logic, empirical evidence, hypotheses, and heuristics occupy different slots. When the evidence changes, the map rebases.
The same structure, two angles.
The first reading follows dependencies from the substrate toward the operations it enables. The second starts from an agent who perceives, coordinates, and builds. The layers operate at the same time: L4 does not wait for L3 to finish, and L3 does not create L2 agency from scratch.
Each higher operation needs conditions maintained by the lower layers.
You are situated inside the stack, with sensors, memory, resources, and partial alternatives.
From the bottom up.
Each level inherits physical dependencies and adds operational resolution. Higher layers are not more real and do not guarantee greater freedom. Some operations widen options while consuming time, attention, learning, infrastructure, or energy according to the task.
And how is this used?
This map helps separate constraint, hypothesis, premise, and choice before acting. The tools turn specific mechanisms into applicable tests. The narratives show how those mechanisms feel when capacity, access, and exercise stop matching.