For the first edition, a tour of what it takes to make intelligent systems dependable after the demo: planning through world models, gathering and evaluating robot experience, serving a policy on-device, and measuring whether language agents remember and repeat what matters. A few older research pieces are here because their mechanisms illuminate the newer engineering reports.
A world model can predict future states yet remain hard to plan through. GRASP makes long-horizon optimization less brittle by relaxing trajectories and avoiding unreliable state gradients. Read the Push-T comparison for the gain and its simulation-bound limit.
Physical Intelligence compresses a VLA representation into an RL token so small actor and critic networks can refine precise manipulation through online practice. The Ethernet-insertion result is striking; read the four-task evaluation before generalizing it to other hands or jobs.
Physical AI, robotics, and language models—with a view beyond your own discipline.
Robot learning needs demonstrations before clever policies. Grabette describes a buildable handheld gripper, synchronized capture, SLAM processing, and LeRobot export. Read the end-to-end cup-grasp example, while keeping the proposed large shared dataset separate from what is demonstrated today.
A practical navigation workflow across robot embodiments: register the scene, verify maps and clearance, run a one-environment smoke test, then train and evaluate under matched conditions. Read for its explicit evidence gates, especially before moving from synthetic scenes to a target robot.
On-device control is a tradeoff, not a slogan. This tutorial shows a 4B policy producing action chunks on Jetson Thor, alongside 22.9% success on a 120-task simulated suite and substantial post-training compute. Read the receding-horizon loop and the limits behind its real-time claim.
LeRobot v0.6 links world-model policies, reward models, simulation benchmarks, richer datasets, and a rollout CLI. Read it as a map of the practical robot-learning loop: imagine, measure success, collect corrections, and try again. Follow the linked docs for the individual methods.
ABBEL treats a long-running agent summary as a belief state and trains it to preserve useful observations. Its coding benchmark narrows, but does not erase, the gap to full context. Read for a measured answer to what an agent should remember while working over many steps.
Tokenization becomes visible when training and serving scale. This measured Rust redesign changes splitting, caching, and the merge loop while preserving token IDs. Read the benchmark method and workload assumptions before carrying its speedups into your own inference stack.
Average task success can hide whether an agent will succeed again. IBM resamples decision points from a recorded trace and generates guidelines for unstable choices. Read the Pass^5 evaluation, then ask how far its AppWorld result carries to your own agent environment.
GitHub shows why shorter tool output can cost more if it forces extra agent turns. Its harness changes were tested offline and online; one prompt compression initially caused agents to run sequentially. Read for the measurement loop and the regression, not only the token savings.
A small differential fuzzer for Rust regex finds one known bug and another unexpected one. Read how the author builds an oracle and varies tiny inputs; it is a concrete lesson in making generative tests reveal a class of failures.
GitHub's move from CSS-in-JS to CSS Modules is a rollout and measurement story. Read for the compatibility wrappers, feature flags, visual regression checks, and server-rendering gains that let a widely used design system change in stages.