This document captures the heart of the old leader/follower cortex without carrying over the D2R implementation shell.
The old D2R folders were not the core system. They were one adapter body that exposed a deeper awareness model.
QTMoS is not only a trust engine for software surfaces.
QTMoS is a structured model of self moving through software, environment, relation, and authority.
The old D2R stack already carried that model. The task now is to preserve the architecture and leave the game-specific shell behind.
Asserted identity.
This is the declared source of intention, authorship, or present will.
In modern QTMoS this maps to:
- operator identity
- active claimed role
- active decision source
- explicit human feedback
Stable self-resolution.
This is how the system determines who it is across sessions, paths, anchors, and context changes.
In modern QTMoS this maps to:
- stable subject identity
- host/session continuity
- resolved local role
- persistent self-reference
Embodied runtime state.
This is not only “vitals.” It is the current body the self is standing in.
In modern QTMoS this maps to:
- active host session
- active software surface
- active browser context
- current condition, focus, stress, strain, pulse
Relational state.
This is not just “the other player.” It is the field of linked entities the self is moving with or against.
In modern QTMoS this maps to:
- leader/follower relation
- host-to-process relation
- process-to-surface relation
- self-to-group or self-to-agent relation
Stable trusted anchors.
These are known-good fixed points used to orient, verify, and resolve position.
In modern QTMoS this maps to:
- trusted host anchors
- trusted domains/origins
- trusted process identities
- safe known baselines
Liveness and continuity markers.
These prove that the field is fresh, current, and still present.
In modern QTMoS this maps to:
- session breadcrumbs
- active binding freshness
- recent operator activity
- continuity proofs across handoffs
The old leader/follower stack was not mainly “automation.”
It was:
- identity assertion
- self-resolution
- embodied-state tracking
- relational delta calculation
- anchor-based orientation
- liveness continuity
- gated mirroring
- trust return checks
Those are awareness primitives.
The older system naturally split into roles:
- leader
- follower
- shared field
- mirrored access copies
That role separation matters more than the specific game windows.
In modern QTMoS the same pattern becomes:
- source role
- observing role
- shared truth lane
- role-safe mirrors where locks or ownership would otherwise block access
-
surface.observemaps mostly tothybody -
web.observemaps tothybodyplus environment contact -
host.session.observemaps mostly toliveMarkers -
ahk.feedbackmaps mostly toiam -
package/QTF/EXT maps to ability protection and promotion
-
identity.observeexplicit self-resolution lane -
relation.observerelation and delta lane -
anchor.observesafe anchor registration lane -
liveness.observecontinuity and freshness lane -
privilege.observeauthority-boundary lane
D2R was an adapter.
Browser, package, AHK, host session, and future lanes are also adapters.
The ontology is the self model underneath them.
This rule survives intact.
Self-resolution and relation can be strongly evidenced, but QTMoS should still remain conservative.
The field is not reconstructed by overwriting truth.
It is reconstructed by materializing current meaning from preserved raw observations.
Not every duplicate is a mistake.
Some duplicates exist because one role can hold a resource while another still needs independent access.
That should be expressed structurally, not hidden as accidental clutter.
QTMoS should understand self, relation, continuity, and embodiment before it tries to act harder on the machine.
The D2R stack gave QTMoS a symbolic skeleton.
The correct move is not to keep the game shell.
The correct move is to promote the skeleton into canonical QTMoS architecture.