<?xml version="1.0" encoding="UTF-8"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>roughcut.dev · Pradeep Kaushik</title><link>https://roughcut.dev/</link><description>Notes on physical AI, simulation, digital twins, industrial systems, and developer tools.</description><language>en-us</language><lastBuildDate>Sat, 29 Aug 2026 00:00:00 GMT</lastBuildDate><atom:link href="https://roughcut.dev/rss.xml" rel="self" type="application/rss+xml" /><item><title>Most Robot Policies Don&apos;t Need Tactile Input. The Test Is Whether Vision Can See What Decides the Task.</title><link>https://roughcut.dev/writing/most-robot-tasks-dont-need-touch</link><guid isPermaLink="true">https://roughcut.dev/writing/most-robot-tasks-dont-need-touch</guid><pubDate>Thu, 27 Aug 2026 00:00:00 GMT</pubDate><description>Years of MES work taught me where automation stops: at tasks whose decisive state cannot be written down or seen. Tactile input earns its place when it reveals that missing state; contact alone is not enough.</description><category>Physical AI</category><category>Industrial Systems</category></item><item><title>I Took the Order Away From the Agent. Then I Learned Order Wasn&apos;t Enough.</title><link>https://roughcut.dev/projects/i-took-the-order-away-from-the-agent-then-learned-order-wasnt-enough</link><guid isPermaLink="true">https://roughcut.dev/projects/i-took-the-order-away-from-the-agent-then-learned-order-wasnt-enough</guid><pubDate>Sat, 22 Aug 2026 00:00:00 GMT</pubDate><description>Anchor stopped my agent from skipping declared steps. Ratchet came from the next question: after an interrupted or overlapping run, could I prove what happened and restart without making it worse?</description><category>Agentic Systems</category></item><item><title>Building Ratchet Runtime: What a Safe Restart Has to Prove</title><link>https://roughcut.dev/projects/building-ratchet-runtime</link><guid isPermaLink="true">https://roughcut.dev/projects/building-ratchet-runtime</guid><pubDate>Sat, 22 Aug 2026 00:00:00 GMT</pubDate><description>A technical look at the small execution runtime I built for overlapping and interrupted agent workflows: ownership, effect recovery, verified completion and the limits of a local alpha.</description><category>Agentic Systems</category></item><item><title>A Gaussian Splat Is Not Yet a Digital Twin</title><link>https://roughcut.dev/projects/a-gaussian-splat-is-not-yet-a-digital-twin</link><guid isPermaLink="true">https://roughcut.dev/projects/a-gaussian-splat-is-not-yet-a-digital-twin</guid><pubDate>Fri, 21 Aug 2026 00:00:00 GMT</pubDate><description>A Gaussian splat can reproduce a place convincingly while knowing almost nothing about its identity, scale or behavior. This article separates reconstruction, visual readiness, operational readiness and simulation readiness—and defines the boundary SplatStage is designed to cross.</description><category>Simulation &amp; Digital Twins</category></item><item><title>Building SplatStage: From Edited Gaussians to OpenUSD</title><link>https://roughcut.dev/projects/building-splatstage-from-edited-gaussians-to-openusd</link><guid isPermaLink="true">https://roughcut.dev/projects/building-splatstage-from-edited-gaussians-to-openusd</guid><pubDate>Fri, 21 Aug 2026 00:00:00 GMT</pubDate><description>SplatStage turns a Gaussian reconstruction into a versioned editing workflow, exports the selected PLY as an OpenUSD Gaussian ParticleField, and composes it with replaceable engineered assets. The hardest bug was at the seam between editing and export.</description><category>Simulation &amp; Digital Twins</category></item><item><title>What 5.8 Million Gaussians Taught Me About Building a Visual Twin</title><link>https://roughcut.dev/projects/what-5-8-million-gaussians-taught-me-about-building-a-visual-twin</link><guid isPermaLink="true">https://roughcut.dev/projects/what-5-8-million-gaussians-taught-me-about-building-a-visual-twin</guid><pubDate>Fri, 21 Aug 2026 00:00:00 GMT</pubDate><description>One Garden scene made the promises and gaps in SplatStage measurable: 2.07 million Gaussians removed, an edited OpenUSD particle field, three composed assets, a dependency-complete stage—and no measured scale, colliders or external runtime proof.</description><category>Simulation &amp; Digital Twins</category></item><item><title>What Kind of Truth Does Your Digital Twin Need?</title><link>https://roughcut.dev/writing/what-kind-of-truth-does-your-digital-twin-need</link><guid isPermaLink="true">https://roughcut.dev/writing/what-kind-of-truth-does-your-digital-twin-need</guid><pubDate>Sat, 15 Aug 2026 00:00:00 GMT</pubDate><description>Every digital twin needs a usable digital starting point. CAD, LiDAR, photogrammetry and Gaussian splatting preserve different kinds of truth, so the representation should follow the decision. Part 1 of a three-part series.</description><category>Simulation &amp; Digital Twins</category><category>Industrial Systems</category></item><item><title>From Camera Media to Gaussian Splats: Building ReconStudio</title><link>https://roughcut.dev/projects/from-camera-media-to-gaussian-splats-building-reconstudio</link><guid isPermaLink="true">https://roughcut.dev/projects/from-camera-media-to-gaussian-splats-building-reconstudio</guid><pubDate>Sat, 15 Aug 2026 00:00:00 GMT</pubDate><description>ReconStudio turns camera media into Gaussian splats and OpenUSD through a browser and job API. I built it to expose reconstruction stages, retain experiment evidence and test where on-demand GPU execution fits. Part 2 of a three-part series.</description><category>Simulation &amp; Digital Twins</category></item><item><title>What I Learned from 24 Gaussian Splat Jobs</title><link>https://roughcut.dev/projects/what-i-learned-from-24-gaussian-splat-jobs</link><guid isPermaLink="true">https://roughcut.dev/projects/what-i-learned-from-24-gaussian-splat-jobs</guid><pubDate>Sat, 15 Aug 2026 00:00:00 GMT</pubDate><description>I built ReconStudio, then used 24 job records across six scenes to test its evidence. Metric bugs, repeated runs and paired-frame comparisons changed what I could claim about training, capture and GPU capacity. Part 3 of a three-part series.</description><category>Simulation &amp; Digital Twins</category></item><item><title>What Industrial Maintenance Demands From Robot Capture</title><link>https://roughcut.dev/writing/what-industrial-maintenance-demands-from-robot-capture</link><guid isPermaLink="true">https://roughcut.dev/writing/what-industrial-maintenance-demands-from-robot-capture</guid><pubDate>Sat, 08 Aug 2026 00:00:00 GMT</pubDate><description>A refinery valve operation shows why robot capture should begin with the task: preserve the motion, contact, timing and measurements the policy will need.</description><category>Physical AI</category><category>Industrial Systems</category></item><item><title>A VLA Benchmark Is Not a Commissioning Package</title><link>https://roughcut.dev/writing/a-vla-benchmark-is-not-a-commissioning-package</link><guid isPermaLink="true">https://roughcut.dev/writing/a-vla-benchmark-is-not-a-commissioning-package</guid><pubDate>Sun, 02 Aug 2026 00:00:00 GMT</pubDate><description>Robot foundation models are getting better at handling situations they were not shown. That makes the old commissioning questions more important: where is the model valid, how do I know it has left that range, and what happens next?</description><category>Physical AI</category><category>Industrial Systems</category></item><item><title>Task success is not the same as safe behavior</title><link>https://roughcut.dev/links#foresightsafety-vla</link><guid isPermaLink="true">https://roughcut.dev/links#foresightsafety-vla</guid><pubDate>Sat, 01 Aug 2026 00:00:00 GMT</pubDate><description>A robot can finish the task and still behave unsafely along the way. That distinction makes this benchmark worth reading.</description><category>Physical AI</category><category>Industrial Systems</category></item><item><title>My Agent Kept Skipping Steps. The Fix Was Taking the Order Away From It.</title><link>https://roughcut.dev/projects/my-agent-kept-skipping-steps</link><guid isPermaLink="true">https://roughcut.dev/projects/my-agent-kept-skipping-steps</guid><pubDate>Tue, 21 Jul 2026 00:00:00 GMT</pubDate><description>A repeatable agent workflow kept skipping different steps on different runs. The fix wasn&apos;t a stronger prompt; it was moving the plan into a DAG and letting deterministic code control sequence and verification.</description><category>Agentic Systems</category></item><item><title>NVIDIA&apos;s Hardware Line Looks Like a Catalog. It&apos;s One Architecture in Many Boxes.</title><link>https://roughcut.dev/writing/nvidia-hardware-is-one-architecture-in-many-boxes</link><guid isPermaLink="true">https://roughcut.dev/writing/nvidia-hardware-is-one-architecture-in-many-boxes</guid><pubDate>Sun, 19 Jul 2026 00:00:00 GMT</pubDate><description>People keep asking me a version of the same question: what NVIDIA hardware should I be thinking about for a digital twin, from a developer build at my desk all the way to production? I always had an answer but no clean model behind it, just a pile of product names, three of which are confusingly all called DGX. So I built the model I wanted: NVIDIA develops one architecture family a year and expresses it across many kinds of computer, from a gaming card to a liquid-cooled rack. These are my rough notes, in case you&apos;re coming at it from the software side and asking the same thing.</description><category>Physical AI</category><category>Simulation &amp; Digital Twins</category></item><item><title>Testing the Robot Training Loop I Drew</title><link>https://roughcut.dev/projects/testing-the-robot-training-loop</link><guid isPermaLink="true">https://roughcut.dev/projects/testing-the-robot-training-loop</guid><pubDate>Sat, 11 Jul 2026 00:00:00 GMT</pubDate><description>A month ago I drew a five-stage loop for a robot training center and admitted most of it was an educated guess I hadn&apos;t tested. So I built the loop as a real, orchestrated pipeline on one GPU and carried two tasks around it — a pole that balances by trial and error, and a Franka arm that learns to stack cubes by copying demonstrations. This is the environment, the stack, the architecture, and what actually ran. Part 1 of two.</description><category>Physical AI</category><category>Simulation &amp; Digital Twins</category></item><item><title>What Testing the Robot Training Loop Taught Me</title><link>https://roughcut.dev/projects/what-the-robot-training-loop-taught-me</link><guid isPermaLink="true">https://roughcut.dev/projects/what-the-robot-training-loop-taught-me</guid><pubDate>Sat, 11 Jul 2026 00:00:00 GMT</pubDate><description>Running the training loop for real surfaced one concept the diagram doesn&apos;t capture: the same five stages take two different shapes depending on how the robot learns — by trial and error (reinforcement learning) or by copying demonstrations (imitation). This part is the mechanism behind that fork, grounded in the two tasks I ran, plus the open questions the build left unproven. Part 2 of two.</description><category>Physical AI</category></item><item><title>Most Teams Reach for Fine-Tuning Too Early</title><link>https://roughcut.dev/writing/most-teams-reach-for-fine-tuning-too-early</link><guid isPermaLink="true">https://roughcut.dev/writing/most-teams-reach-for-fine-tuning-too-early</guid><pubDate>Wed, 08 Jul 2026 00:00:00 GMT</pubDate><description>When a general-purpose LLM (or an agent built on it) doesn&apos;t fit the problem, the reflex is to fine-tune it. I think that&apos;s usually the third thing to try, not the first. There are three ways to close the gap: grounding context, harness optimization, and fine-tuning, and which one you reach for should depend on the need in front of you: domain knowledge, agent behavior, or raw performance.</description><category>Agentic Systems</category></item><item><title>Is Physical AI the Next Level for MES? I Think It Is</title><link>https://roughcut.dev/writing/is-physical-ai-the-next-level-for-mes</link><guid isPermaLink="true">https://roughcut.dev/writing/is-physical-ai-the-next-level-for-mes</guid><pubDate>Tue, 07 Jul 2026 00:00:00 GMT</pubDate><description>MES was never really about running the machines. It was about improving the operation, and it was limited by how much had to be modeled by hand and decided by people. Physical and agentic AI can change that, but only if the plant&apos;s systems are joined through shared operational context.</description><category>Industrial Systems</category><category>Agentic Systems</category></item><item><title>World models are becoming an investment category</title><link>https://roughcut.dev/links#world-models-capital-shift</link><guid isPermaLink="true">https://roughcut.dev/links#world-models-capital-shift</guid><pubDate>Fri, 03 Jul 2026 00:00:00 GMT</pubDate><description>The useful signal is not that world models are solved. It is that investors and research leaders increasingly see predictive models of physical dynamics as a distinct bottleneck worth funding.</description><category>Physical AI</category></item><item><title>I Built a Live USD Viewer That Never Launches Kit</title><link>https://roughcut.dev/projects/live-usd-viewer</link><guid isPermaLink="true">https://roughcut.dev/projects/live-usd-viewer</guid><pubDate>Thu, 02 Jul 2026 00:00:00 GMT</pubDate><description>A browser-based USD viewer, RTX-rendered server-side and streamed over WebRTC, built to see if the library-first pitch holds up under real interactivity.</description><category>Simulation &amp; Digital Twins</category></item><item><title>Physical AI&apos;s bottleneck isn&apos;t the model anymore</title><link>https://roughcut.dev/writing/physical-ai-bottleneck-isnt-the-model</link><guid isPermaLink="true">https://roughcut.dev/writing/physical-ai-bottleneck-isnt-the-model</guid><pubDate>Wed, 01 Jul 2026 00:00:00 GMT</pubDate><description>We finally have models that can watch the physical world, reason about it, and predict what happens next. Walk a real automotive parts-kitting task through what they actually solve, and the thing still standing between a demo and a working line isn&apos;t a smarter model: it&apos;s the policy you have to train for your machine, and the system that keeps it trained.</description><category>Physical AI</category><category>Industrial Systems</category></item><item><title>You No Longer Need to Build an App to Use Omniverse</title><link>https://roughcut.dev/writing/no-longer-need-an-app</link><guid isPermaLink="true">https://roughcut.dev/writing/no-longer-need-an-app</guid><pubDate>Wed, 24 Jun 2026 00:00:00 GMT</pubDate><description>Kit and libraries used to be the same choice for building on Omniverse. They&apos;re not anymore, and that&apos;s a bigger change than it looks, with a real before/after from a Kit extension I built.</description><category>Simulation &amp; Digital Twins</category></item><item><title>The Omniverse Licensing Change You Might Have Missed</title><link>https://roughcut.dev/writing/the-omniverse-license-change-you-might-have-missed</link><guid isPermaLink="true">https://roughcut.dev/writing/the-omniverse-license-change-you-might-have-missed</guid><pubDate>Wed, 17 Jun 2026 00:00:00 GMT</pubDate><description>Since May 2026, Omniverse is free for production, not just development. It&apos;s a clean, sensible change, but it landed quietly, and I keep meeting customers and partners who don&apos;t know it happened yet. The paid-production requirement is gone; the license and optional enterprise support remain.</description><category>Simulation &amp; Digital Twins</category></item><item><title>A Robot Training Center Looks Like Ten Projects. It&apos;s One Loop.</title><link>https://roughcut.dev/writing/a-robot-training-center-is-one-loop</link><guid isPermaLink="true">https://roughcut.dev/writing/a-robot-training-center-is-one-loop</guid><pubDate>Mon, 15 Jun 2026 00:00:00 GMT</pubDate><description>Someone asked me how you&apos;d build a training center for industrial robots from scratch, and my first reaction was that it isn&apos;t one project, it&apos;s ten. What untangled it was seeing that they aren&apos;t ten separate things at all. They&apos;re five stages of one loop that turns real work into robot skills and feeds what happens back in. This is where I&apos;ve gotten so far, still learning, sharing it in case you&apos;re walking the same road.</description><category>Physical AI</category></item><item><title>Omniverse Is Not a Rendering Tool</title><link>https://roughcut.dev/writing/omniverse-is-not-a-rendering-tool</link><guid isPermaLink="true">https://roughcut.dev/writing/omniverse-is-not-a-rendering-tool</guid><pubDate>Wed, 03 Jun 2026 00:00:00 GMT</pubDate><description>From the industrial systems I know, rendering is only one part of Omniverse. The harder job is connecting source data, giving teams a shared context, and reusing it for visibility, simulation, optimization and Physical AI.</description><category>Simulation &amp; Digital Twins</category><category>Industrial Systems</category></item></channel></rss>