Skip to content

Causal Forge

v1.0
Learn
Sign in to save
What am I building?
NodeMathematical model

One event. Its value is how much of the diffusing quantity starts there — think of it as how much dye you pour in at that point before the simulation runs.

Try — Drag a node far away from its neighbours and re-run. Nothing moves on the panel — distance on screen is not distance in the model.

EdgeEstablished physics

A one-way link: this event can influence that one, and not the other way round. The arrow is the causal direction.

Try — Reverse one edge and re-run. Only causal consistency can react — that tells you exactly which part of the score is about causality and which part is about shape.

Edge weightMathematical model

How strongly two events are coupled. A heavier edge lets the quantity flow faster between its endpoints.

Try — Raise one weight sharply with Auto α off, then re-run. Stability falls without you touching α — the safe step size depends on the weights, not just the wiring.

SplitMathematical model

Turns one event into two that share its value and its connections. A way to make the structure finer without changing what it is connected to.

Try — Split a hub node and watch locality move. Refinement changes the triangle count, so a structure that was "the same idea" scores differently — worth knowing before you trust a locality reading.

MergeMathematical model

Collapses two events into one, adding their values and joining their connections. Useful for asking whether the big picture survives when you stop resolving fine detail.

Try — Merge two nodes and compare the metrics before and after. A reading that survives coarse-graining is a much stronger result than one that does not — that comparison is the closest thing this module has to a physics argument.

Closing a loopRejected solution

You are allowed to connect an event back to one of its own causes. The simulation will still run — and causal consistency will fall, because an event has become its own ancestor.

Try — Close a loop on purpose and watch causal consistency drop. It is the only metric you can drive to zero deliberately, and doing it once is the fastest way to see what the score is actually measuring.

What do these controls do?
SeedComputational experiment

The seed picks which random starting nudge the simulation gets. The same seed always gives the same run — that is the whole point of having one. It does nothing while Noise is 0.

Try — Set Noise to 0.5, run, then change only the seed and run again. The trajectory differs; every metric holds still. That gap is worth understanding before you trust any of the scores.

AlphaEstablished physics

How big a step the simulation takes each tick. Small steps are slow but safe; take steps that are too big and the values start swinging wildly instead of settling.

Try — Turn Auto α off and raise α until the Stability gauge collapses. The value where it goes is the real stability boundary of the integrator, not a scoring cutoff.

StepsEstablished physics

How many ticks to run. More steps means the values get closer to settling down; it does not change what they settle to.

Try — Push α just past its stable value and then raise Steps. Watching a divergence grow is a clearer lesson about explicit integrators than any number on the panel.

NoiseComputational experiment

How hard the seed nudges the starting values. At 0 — the default — every node starts exactly where you put it and the seed is inert. Turn it up and the seed starts to matter.

Try — Leave it at 0 unless you are deliberately exploring initial conditions. It is the switch that turns the seed on, not a difficulty setting.

Auto αEstablished physics

Picks a step size that is safe for the graph you have built, instead of making you find one by hand. Convenient, and it keeps the Stability gauge honest rather than high.

Try — Build a star graph, enable Auto α, then add spokes. The chosen α shrinks as the hub degree grows — the safe step size is a property of the graph, not a constant.