Programmable, agent-aware surface coupling for gravity-limited interiors. Mobient does not generate gravity or rotate a habitat; it reconstructs surface functions (stance, traction, hold-down, guided translation, lane-keeping, and stability) for recognized agents, demonstrated through byte-identical replay.
View Architecture →The digital twin has matured into an execution-readiness toolchain for the proposed six-month hardware-calibration effort: design, calibration, validation, traceability, and evidence generation in one structured workflow.
This gives the team structure to protect award-period hours from avoidable test-matrix invention, data-format churn, and calibration-path ambiguity.
This viewer replays Mobient’s deterministic floor-control logic one tick at a time. The charts are experiment-aware: each trace shows the signals that best explain what the floor is deciding, spending, admitting, holding, guiding, throttling, or refusing.
Start with the experiment title, then read the primary cards for that trace. Rising prices
mean a resource is becoming scarce. Falling capacity or rising utilization means authority
is being used. alpha shows how much requested demand is admitted. Ring/OK
fields show whether the evaluated agent or payload state remains inside the governed
safety envelope.
Internal scarcity scores, not dollars. Green p_force rises when magnetic
force is scarce. Blue p_force_rate rises when force is changing quickly.
Amber p_footprint means “how big is the active coil/tile patch?”
Purple p_concurrency means “how crowded is that patch?”
Remaining or used floor authority. force_n rem/tot means remaining force
out of total force. util_force means how much of the shared force pool is
being used. Capacity is the floor’s local authority budget, not just normal force.
The request being tested. In payload and MPM traces, commanded demand usually ramps upward so the same payload is asked to handle a harder maneuver. In the passive SLED arrest it is the admitted stopping distance; in external tow hold-and-guide it is the admitted tow-line guide demand. The admitted line stops at the guard cutoff, with the full requested sweep kept as a faint dashed reference.
Agent demand shows what each agent asks for. alpha is the admitted fraction
of that request. Cost is the DSE engine’s internal model cost for admitting the
evaluated command; it is not dollars or a physical unit like newtons.
Price weight is a normalized 0–1 control weighting for scarcity influence.
DSE means Dynamic Stability Envelope. ring_level is the safety/governance
band of an evaluated agent or payload state under the current command and local floor
conditions. ok shows whether it is authorized. Ring is not a physical ring
on the floor.
How strongly the floor is holding or coupling to the agent, SLED, or payload interface.
L/R means left/right contact or equivalent support channels. If L/R are identical, the
viewer may draw them as one combined L/R line.
How quickly hold/coupling force is changing. Normal force shows how hard the floor is holding now; force rate shows how fast that hold is changing. Jerk-limiting prevents force changes from snapping on too suddenly.
The force-bearing coil authority the replay actually used. Current use shows active force (N) and how many coils bear force right now; Cumulative exposure / footprint shows force-time (N·s) and unique coils used so far. Appears for the DSE motion traces and the human/RSL contact trace; hidden only for the thermal-token trace.
The physical coil surface, each active coil shaded by its live temperature– cool blue at
the 22 °C coolant inlet through hot red at the 45 °C cap– redrawn
every tick, so the hot spot grows and rides the cap as the replay plays. Beside it: the
hottest coil, active-coil count, average temperature, headroom to the cap, and busiest feed.
Shows where heat concentrates– a single moving pass spreads its heat, but
sustained traffic reusing one lane (the SLED convoy) builds a hot corridor. For the
human/RSL trace the two alternating boot footprints warm a few degrees and stay far below the cap. Appears wherever per-coil thermal exists– the DSE motion traces
and the human/RSL contact trace; hidden only for the thermal-token trace.
The fourth authority next to force, thermal, and electrical: the per-tick tip/peel moment ledger. The floor clamps a payload, so stability is a moment balance about each contact-patch edge — hold-down × lever arm vs the inertial overturning moment (weight terms scale with ambient gravity, so they vanish in microgravity). The edge-gate margin chart is capacity/requirement − 1: below 0 the dispatcher throttles, it does not tip; on tow / arrest a second chart tracks the pitch-moment margin (below 0 the tick is REFUSED). Appears for the DSE motion traces; hidden for human/RSL and thermal.
The hardware limits the floor holds itself under, live. Hottest coil tracks the
warmest coil’s temperature against the 45 °C hard cap; busiest feed
tracks the most-loaded row-power feed’s current against its 190 A budget. The
dashed red lines are those limits– the floor derates its own force to stay under them.
Appears for the DSE motion traces and the human/RSL contact trace; hidden only for the
thermal-token trace.
How the command affects the body, payload, or contact model. Brake torque means
rotational/braking correction. price_weight is scarcity influence on the
response. v_weight is viscous/damping influence, not literal stickiness.
Thermal traces are not motion traces. total_tokens shows heat-budget use.
market_multiplier_final shows thermal scarcity price.
peak_temp_c shows modeled peak temperature. waits and
violations show governance events.
Switching between run_A and run_B compares independent runs.
A byte-identical match means the same scenario produced the same logged state history,
making the control logic auditable.