Change the object just before an action chunk boundary, then repeat just after it. In one run, the next decision can use the new state. In the other, that decision may already be committed. Both runs can finish the task, so the final success flag hides the one chunk delay. The LingBot-VA 2.0 report says new observations update the cache between action chunks. Track the physical change, frame capture, model receipt, chunk commit, and first changed action on the same clock. Those points can separate capture and transport delay from a decision that was already committed. They still do not establish safety or generalization. submitted by /u/StillThese3747
Originally posted by u/StillThese3747 on r/ArtificialInteligence
You must log in or # to comment.