# Presentation-cadence refinement within the authorized FPS task The original plan/scope/caps and sealed0.4.0/0.4.1 remain unchanged. The four frozen physical/controller/protocol files and original sim.render_interval=20 remain unchanged. This document is separately authenticated in each subsequent approval. Measured pure application optimization:4500tick GUI baseline113.5415s → epoch92.1030s → combined75.7835s, all with cProfile. All three complete trace files have identical SHA256;70tensors. Combined sampled strict float32-bit Jacobian qualification33samples passed; not an all-input proof. Full CPU1536passed6skipped. Combined original campaign/strict postexit passed,4427protectedfiles unchanged. Render submissions are still only225 per9simulatedseconds, so about3 per WALLsecond. Faster loop alone is not adequate GUI responsiveness. New combined_display mode retains original interval20 renders and adds a genuine render on other ticks, only after the original safety checks and synchronous complete500Hz evidence succeed. Thus each moving render represents a NEW actually integrated and checked physical tick; no interpolation, repeated-state filler frames, synthetic FPS, movie playback, sleep/frame cap, environment enlargement or dummy GPU load. It calls sim.render, never sim.step, scene.update/reset, controller refresh, time scaling, teleport or parameter mutation. The pinned KitVisualizer disables player physics while pumping the app. The expected concrete Kit visualizer must remain a member, running, not closed and not paused before/after added rendering, before each subsequent physical call, after each control/original interval20 rendering, and during/following final viewing. SDK-swallowed visualizer failures must fail closed without counting missing paints. Original GUIclose finalization and exactSHA/liveGPU shutdown handoff remain mandatory. Early close during an added frame before total_ticks returns the original GUIabort cause before another step. Final-tick close retains completion semantics. This intentionally separates UI responsiveness from simulation throughput. More rendering may LOWER physics ticks/wallsecond; actual real-time factor and render submissions/wallsecond MUST both be reported, with startup/finalhold/profile overhead separated. Do not label submissions as independently measured display-present FPS. Genuine Kit-window screenshots/video/overlay and sampled GPUutil/power/clocks are separate evidence. This does not promise1x physical time,60displayFPS or100%GPU utilization. Before qualification: CPU sequencing/negative tests and read-only review. Then one fresh serial full analyticS1GUI run (27000actualticks,profiledisabled), full trace/audit/counter/continuity/source checks against old sameprotocol evidence, actual finalview/close/wait and strict cleanup. Same-source analyticS1headless regression follows, subject to original aggregate12Kit/120000calls/24GiB/6h. No training/u256/current-source fullmatrix qualification is implied. No source/config/plan edits during an active bound run.