OMNI_VM_ROOT {ovm-root-0001}
> description: Root node for the Omni-Processor distributed virtual machine
concept, a system that routes bounded execution state across a mesh network
rather than fetching remote data.
> 
CORE_ARCHITECTURE {ovm-core-0001}
> description: The foundational 128-bit instruction set environment. Each
instruction consists of a 32-bit macro-opcode, two 32-bit mesh-routable
pointers, N-registers for local scratchpad math, and an n-depth stack for
retaining exact context during remote execution and suspension.
> type: specification
> status: conceptual
> tags: [isa, bytecode, opcode, registers, stack]
> 
DATA_GRAVITY_ROUTER {ovm-mesh-0001}
> description: The dynamic execution layer responsible for evaluating whether
to fetch data or teleport the bytecode. It weighs payload mass, topology
latency, compute asymmetry, reference locality, and quarantine egress rules to
route the serialized program state directly to the target node.
> type: routing-engine
> status: conceptual
> tags: [teleportation, heuristics, data-gravity, mobile-agents]
> depends_on: [ovm-core-0001]
> 
TRANSACTIONAL_MEMORY {ovm-sync-0001}
> description: The resilience layer preventing data corruption during node
failures mid-teleportation. It implements a caller-retained ghost copy of the
execution state, a timeout epoch monitor, temporary scratchpad memory for a
two-phase commit, and a poison pill protocol to discard stale results from
reconnecting zombie nodes.
> type: module
> status: conceptual
> tags: [two-phase-commit, fault-tolerance, state-recovery, ghost-copy]
> depends_on: [ovm-mesh-0001]
>