Replay Guide

What you would see: imagine one passive SLED carrying a payload on the active surface. The SLED is not driving itself. The floor is shaping the magnetic field underneath it and asking that same payload to handle a progressively stronger acceleration command.

Why the lines rise: the Commanded Demand card shows the ramped variable: commanded acceleration. As that request increases, the floor must spend more force and stability margin to keep the SLED coupled, aligned, and controlled.

Primary cards: Commanded Demand shows why the trace gets harder. Dispatch Prices show scarcity pressure. DSE Admittance shows alpha, the admitted fraction of the requested command. DSE Band / Authorization shows ring_level and ok. Normal Force and Force Rate show the hold/coupling response. Cost / Price Weight shows internal cost and response weighting.

L/R meaning: for a SLED or payload, L/R means left/right equivalent contact channels of the simplified payload interface, not literal legs. If the viewer shows a combined L/R line, it means the two channels are identical or overlapping enough to be drawn as one truthful combined series.

Interpretation note: the payload is not turning on a gyroscope or changing internally. The experiment gets harder because the command is ramped, not because the object itself changes. A combined line does not mean a missing signal; it means the left/right channels are moving together in this trace.

What you would see: imagine a crew member stepping on an active surface with passive compatible footwear. The surface does not simply stick the foot down. It recognizes a contact phase, applies hold/coupling force, then tapers that contact so the foot can release without a harsh peel-off sensation.

Why the lines change: the trace is stepping through capture, stance, and release timing. Normal force appears as contact pulses rather than one continuous ramp. Force-rate lines may look jagged because the model is updating in discrete ticks and alternating contact phases.

Primary cards: Dispatch Prices show force and force-rate scarcity. Engagement State shows which contact lane is active. Normal Force shows the contact pulses. Force Rate shows how abruptly each hold force changes. Viscous / Impedance Diagnostics shows control weighting and speed terms behind the damped contact response.

L/R meaning: in this trace, L/R can be read as left/right foot-like contact channels in the simplified human embodiment model. The Engagement State card is useful because it shows the alternating contact rhythm directly.

Interpretation note: a rising viscous/damping weight does not mean the floor gets stickier the longer someone walks. It is a control weighting used in this trace to demonstrate damping influence. Likewise, some force-rate jaggedness is not automatically bad; the important question is whether the changes are bounded and replayable.

What you would see: imagine two compatible cargo agents trying to use overlapping floor authority in the same local ZonePack. Agent B is already asking for a steady share. Agent A starts with a smaller request and then ramps upward.

Why the lines rise or flatten: as Agent A demands more, the shared authority pool becomes more expensive. Shared Dispatch Prices rise because both agents are drawing from the same limited force supply. Shared Utilization rises as more of that pool is consumed. Flattening can mean the pricing/allocation state has reached a governed regime.

Primary cards: Shared Dispatch Prices and Shared Utilization tell the shared-resource story. Agent Demand shows Agent A ramping while Agent B holds steady. Agent Alpha shows how much of each agent’s requested demand is admitted. Agent Cost shows scarcity cost per agent. DSE Band / Authorization shows each agent’s governance band and authorization state.

Agent meaning: Agent A and Agent B are the two competing agents. This experiment no longer needs the generic L/R embodiment panels as primary evidence, because the important split is AgentA/AgentB, not left/right contact channels.

Interpretation note: ring_level is not a physical ring on the floor. It is the DSE safety/governance band of the evaluated agent state under the current demand and local floor conditions. alpha shows how much of the requested command is admitted; ok shows whether the evaluated state is authorized.

What you would see: imagine a steady stream of cargo SLEDs running the same lane, one after another, with little time for the floor to cool between them. Each pass is a brief contact, but the lane never fully recovers, so heat builds in the reused corridor pass by pass.

Why the charts change: Active Surface Authority shows repeated per-pass pulses (not one static plateau) as each SLED runs the lane. The Coil Thermal Map shows a hot corridor– the reused coils– warming pass by pass: first to the ~41 °C PCM melt band (which buffers the mid-convoy traffic), then climbing toward the cap. The Thermal & Electrical Load chart shows the hottest-coil temperature stepping upward across passes, approaching ~44.9 °C late in the run while the busiest feed stays comfortably under 190 A. As headroom tightens, Dispatch Prices rise and DSE Admittance steps down– the governor spacing and derating the lane near the cap.

The brief zero dips are pass boundaries, not failures: between SLED passes the corridor is empty for a few ticks, so Active Surface Authority, Feed Current, and the DSE Band ring fall to zero. These are intentional inter-pass clearance frames (short convoy spacing)– ok stays true, no infeasible_reason is set, and the corridor temperature holds across them. The viewer renders the force and feed lines with a gap at these ticks (a pass boundary) and labels the Current Tick card as inter-pass gap, so they are not misread as thermal refusal or loss of authority.

Why it matters: it shows the favourable operational case– the floor handling sustained heavy logistics traffic– and demonstrates that the thermal governor protects a busy lane gracefully: full admittance while headroom exists, then progressive spacing / derating as the hottest coils approach the 45 °C cap. No single ordinary pass approaches the cap; it is reached only after high-throughput reuse, exactly the regime where lane management matters.

What you would see: imagine a large or awkward payload being handled with MPM assistance. The payload is not just a normal single SLED move; the assist geometry gives the floor more ways to stabilize the body as demand increases.

Why the lines reset and rise: the Commanded Demand card is a two-pass ramp. The reset is intentional. It lets the replay compare demand behavior across two passes rather than showing one continuous maneuver. As each ramp rises, the payload-plus-assist system must spend more support, force, and stabilization authority.

Primary cards: Commanded Demand shows the two-pass ramp. Dispatch Prices show scarcity pressure. DSE Admittance shows alpha, the admitted fraction of demand. DSE Band / Authorization shows ring_level and ok. Normal Force and Force Rate show hold/coupling response. Cost / Price Weight shows internal cost and response weighting.

L/R meaning: L/R does not mean two physical MPMs. It represents left/right equivalent support channels for the payload-plus-assist geometry. One MPM, two MPMs, or a larger assist arrangement can be reduced into these net support channels for replay.

Interpretation note: matching or combined left/right force lines are not a defect. They indicate coordinated two-sided support in the simplified contact model. The story is assisted stability and envelope governance, not necessarily one-sided tipping.

What you would see: a passive deck coasting in 0G that the floor must bring to rest. The floor is the only actor– it vector-subtracts the deck's own inertial reaction across up to a 49-coil / 8-feed footprint (~6.1 kN coil authority, peak feed ~174 A under the 190 A budget). Nothing pulls or pushes the deck externally.

Why the refusal appears: a shorter demanded stop needs a higher deceleration (a = v²/2s), so a higher braking force and a bigger bow-dive moment at the deck CoM height. Below a minimum safe stopping distance (~7 mm) the anti-tip pitch-moment gate trips: ok becomes false and the twin refuses rather than simulate a stop that would tip the deck.

Inertial reaction vs realized magnetic force: the deck rides the floor under the magnetic hold-down clamp, so its own contact friction (μN, N = magnetic clamp + ambient weight) helps decelerate it. The twin reports reality by decoupling two quantities: the inertial reaction m·a = m·v²/2s — what sets the friction-independent bow-dive pitch gate — and the realized magnetic shear the coils actually supply, m·a − μN, reduced by that friction assist (a constant ~59 N here in microgravity). The Braking Force Decoupling card plots both: the inertial reaction sits above the realized magnetic force by exactly the friction assist. This is the twin presenting what physically happens, not the gate counting on friction — the pitch gate reads the inertial reaction, so the minimum-safe-stopping-distance refusal is unchanged.

Reading the cards: Stopping Demand shows the requested stop distance (faint dashed) and the admitted stop (solid), which goes null at the refusal. Braking Force Decoupling shows the inertial reaction (amber), the realized magnetic shear (green), and the contact-friction assist (cyan). Dispatch Prices and Cost / Price Weight show the rising scarcity as the stop tightens. DSE Band / Authorization shows ring_level, ok, and the guard transition. Active Surface Authority shows the per-coil braking force recruited, then withdrawn to zero at the cutoff.

Interpretation note: the refusal is a physics-gated anti-tip limit (bow-dive prevention), not a capacity collapse. In a real system the cutoff hands the deck to the passive brake / recovery logic. Phase I-class numbers; coil authority is estimated, not bench-calibrated.

What you would see: a heavy rack or cargo SLED pulled by a winch, crawler, crew force, or MPM force. The floor does not drag the payload; it keeps it coupled, bounded, aligned, and guarded while the external tow supplies translation. The tow attaches ~0.6 m up on the tall deck, so even a modest off-lane pull induces a pitch/yaw moment the floor must counter.

Why the guide cutoff appears: the trace is a guard-threshold test. The floor admits the hold-and-guide while the tow-line disturbance stays inside the modeled envelope. When the induced pitch/yaw moment would exceed the floor's guide authority– at ~9.7 kN disturbance (~0.49 g on the 2,000 kg deck)– ok becomes false and the unsafe guide state is refused. About 80% of the sweep is feasible.

Reading the cards: Tow / Guide Demand shows the requested off-lane disturbance (faint dashed) and the admitted guide (solid), which goes null at the cutoff. Dispatch Prices show the cost of maintaining hold-and-guide. DSE Band / Authorization shows the band and whether the guide state remains authorized. Active Surface Authority shows the distributed coil authority used (~15 kN peak, ~126 N/coil avg), which falls to zero after the cutoff.

Chart naming: the demand chart and the engine's internal fields keep the legacy tow name for determinism. Here "tow" means an externally-moved hold-and-guide: the floor supplies coupling and guide authority, never the towing force itself.

Interpretation note: the refusal is a stability limit– not the floor failing to tow the load, and not a system failure. In a real controller, cutoff hands the operation to safe hold / recovery (hold, reduce demand, re-vector, re-index, or add MPM assistance). Coil authority is estimated, not bench-calibrated.

What you would see: physically, you would not see a payload move. Imagine a tile controller being asked to schedule heat-producing coil jobs while tracking modeled thermal headroom.

Why the charts change: each thermal job consumes tokens and affects modeled headroom. Market Multiplier can rise as thermal activity becomes more expensive. Peak Temperature rises as heat accumulates. Waits appear when the thermal governor delays work to protect the surface.

Primary cards: Thermal Tokens shows heat-budget use by job. Market Multiplier shows thermal scarcity price. Peak Temperature shows modeled maximum temperature. Waits / Violations shows governance events. Cost / Steps shows accounting cost and duration. Thermal Summary gives the overall result at a glance.

L/R meaning: L/R motion cards do not apply here. This is a thermal accounting test, not a foot, SLED, payload, or tow-motion trace.

Why it matters: Thermal governance is what prevents the floor from treating coil commands as free. Even when no payload is moving, the twin is proving that heat budget, scarcity pricing, waits, and violations can be logged deterministically before higher-power hardware tests.