The World of Splectrum

Home > Engineering > Mycelium > Subject Reality

Subject Reality

A subject reality is a mycelium fabric embedded within a git repository. Git provides the hard boundary — identity, history, integrity. Mycelium provides the referential structure — cross-referencing, entity-world relations, process capabilities woven into the data state. Git holds it. Mycelium makes it alive.

The Boundary

The git repository constitutes the subject reality as a distinct entity. Within the boundary, data is structured but not ontological — the folder tree and context notes define functional scope. What you see is what there is. No hidden data, no hidden process, no encapsulated state.

There is no central data world. Only subject realities exist. The totality of data is a logical concept, never a physical repository. Shared reality is produced through shared data state, not through process.

Self-Contained from Birth

The embedding of referential structure and process capabilities means a clone is immediately operational. Different reality, same experience input streams. No setup, no configuration — the reality is self-contained.

At the point of clone: same input streams, same experience. Divergence comes through use — different encounters, different data state changes triggering different processes, different convergence patterns emerging. The two realities drift apart naturally. Closer to cell division than anything else — identical at the split, divergent through life.

Point of View

The working directory sets the point of view (POV). POV determines what the subject can see and how it identifies it. Resources are relative to POV — paths go forward, never backward above POV.

The subject never touches the data world directly. It accesses reality only through the local fabric interface, through its protocols, from its POV.

References

When a resource is behind POV but access is required, cascading references bring it into view. A reference creates a local identity for a remote resource. References are read-only — modification uses copy-on-write to the local context. Read wide, write local.

The graph of references defines the reachable set from any POV. No reference, no access — structure determines visibility, not permissions.

Reality Operations

Git operations serve as reality operations:

Clone — spawn a new subject reality, complete with full history and embedded process.
Branch — diversify within a reality without losing the original.
Merge — reconcile divergent realities. Conflicts as how decentralised realities deal with divergence — not prevented, resolved when the realities meet.
Fork — a new subject emerges from an existing one, carries its history.

No central authority needed for any of them. These are git operations read through the framework.

Git’s Limits and Where Mycelium Bridges

Git is snapshot-based — commit, store, done. No concept of continuous flow. For streaming data, high-frequency state changes, or high-volume operational data, git is ill suited.

But git is not asked to be a database. It is asked to be a container for a fabric.

Git holds the structure, the references, the embedded process definitions, the historicity. Remote sources hold the heavy data, the streaming feeds, the high-volume operational state. The fabric describes what’s there, where it is, how it relates. The data itself can live elsewhere. The scene is local, the resources can be anywhere. Mycelium’s referential layer does not care where the data physically lives. It cares about the relations.