Causal Basis ​

A new transition in Realith must not hang in the air. If it is not the primary creation of an object, it must have a causal basis.

This means the network must be able to answer at least two questions:

• from which active version the new step is built;
• from which previously recognized basis it is derived.

Without a causal basis, any new record could claim the status of the current version simply by existing. The model would then quickly collapse into the crude formula “last update wins.”

Realith must retain a different discipline:

• the new step must be linked to a distinguishable prior basis;
• that link must be explainable;
• a break in the causal line must not be disguised as a normal transition.

What may serve as a causal basis ​

At the conceptual level, causal basis may include:

• the previous active version of the object;
• a previously accepted transition;
• an admissible primary basis of creation;
• an allowed basis of derivation;
• a separate conflict-resolution act.

At the current stage of the project, the important thing is not to enumerate all future formats, but to retain the principle itself: a new version must be derivable from a recognized basis.

Why a signature is not enough ​

A signature confirms who initiated an action or agreed to it. But a signature by itself does not answer the question from what the transition is derived and whether it is compatible with the already recognized line of the object.

Therefore, a signed update without a causal basis must not automatically become the new canon.

Causality and conflict ​

It is precisely causal basis that makes it possible to distinguish:

• a normal next step;
• competing candidates for the same next position;
• a separate conflict branch;
• a special act of conflict resolution.

Without it, conflict cannot be expressed architecturally at all: it will hide as an accidental order of delivery or a private processing queue.