I also published a graph / visibility layer for the L4 glitch stack.
Why separate visibility from the core?
Because modern systems are very good at turning presentation into false authority.
A graph can make something look coherent. A visual branch can make something look legitimate. A smooth walkthrough can make an unresolved state feel like a finished truth.
That is exactly the problem.
The visibility layer exists so that branches, quarantine states, evidence, and alternative paths can become legible without being promoted into runtime authority simply because they are easy to display.
This distinction matters more than it first appears.
A visible branch is not the same as an executable branch. A cinematic path is not the same as a lawful path. A rendered relation is not the same as a valid transition.
That may sound obvious.
But in practice, a lot of systems quietly blur those lines.
They show a possibility, then treat the displayed possibility as if it were already halfway to permission.
I think that is a structural mistake.
Good architecture should allow us to see:
- what is active
- what is historical
- what is research
- what is merely visible
- and what remains non-authoritative
without collapsing all of that into one polished interface layer.
In plain terms: a dashboard should not be allowed to smuggle fiction into operations.
That is why I separated graph grammar, visibility, and rendering discipline from the normative core.
Because what is shown and what is true are related, but they are not the same thing.
Zenodo: Graph / Visibility — https://lnkd.in/gFATwUdH