u/ButterscotchTiny1114

Welcome to the latest RobotShift update, 5 stories with the take from demoware to reality.

00:00 - Intro

00:20 - The Architecture Shift — Duke’s Argus

Why copying human form can be an efficiency trap. Duke University’s Argus is a 20-legged, 20-eyed sphere with no front or back, designed to move and see in any direction. Its 0.91 dynamic-isotropy score puts it far above conventional humanoid and legged designs for terrain such as sand, forests and obstacle-filled environments.

01:30 - Humanoid’s Outsourcing Strategy

London-based Humanoid is taking a different route to scale: using established German industrial partners including Schaeffler and Bosch rather than building every part of its production ecosystem itself. The ambition is huge — but scaling hardware is very different from proving deployment.

02:37 - The Simulation Trap — Genesis AI

GENE-26.5 demonstrates impressive manipulation tasks including egg cracking and lab pipetting. But impressive controlled demos still leave a difficult question: how much of that performance survives outside carefully managed environments, without extra algorithmic support?

03:44 - The Warehouse Bottleneck — Locus Robotics and Nexera

Locus Robotics has acquired Nexera Robotics and its NeuraGrasp adaptive membrane-gripper technology. The target is clear: picking the messy, variable stock that warehouse robots still struggle with. Even tiny pick-failure rates can create thousands of expensive human exceptions at scale.

04:58 - Mass Scale Unlocked — Electric Atlas

Hyundai and Boston Dynamics are building toward industrial-scale Atlas production and deployment in Georgia. The long-term ambition is a production system capable of around 30,000 robot units annually — a major test of whether humanoids can move from impressive demonstrations into repeatable factory economics.

06:04 - End Summary

Another week of robotics marketing loops versus harsh field realities. In this week's breakdown, we are looking past investor decks to audit the actual friction of automating physical labor.

Here is what we are covering in this episode:

• Figure’s 55/Week Ramp-Up: Production is accelerating, but commercial use cases are still in continuous development. Is scaling ahead of general application a massive capital gamble, or does their package-sorting livestream prove they're ready for structured work?
• Verobotics at NVIDIA Campus: A massive 100,000 sq ft facade deployment that ended up in a strict 60/40 operational compromise with human window washing crews because of live construction site dust.
• The 8.1B Parameter Bottleneck: Looking at RLWRLD’s new RLDX-1 model. Why graph optimization and real-time memory bandwidth constraints—not raw compute power—are the real bottlenecks for dexterous robotic hands.
• Spot's Purely Visual Blind Spots: Boston Dynamics paired Spot with DeepMind’s Gemini 1.6. What a sideways-crushed soda can proves about semantic reasoning models running without tactile force integration.
• FANUC x Google: Industrial giants bringing physical AI to factory floors, but keeping implementation highly conservative.

Comparison Video of Figure AI Robots making and tidying a bedroom and how this compares in the real world to a human housekeeper.

Hi,

Ive got agentmail working with Hermes, if I wanted to add calendar integration in, what should I use?

Do I go with Google, likely low chance of ban with calendar usage or go with a separate Calendar client?

I don’t use my personal gmail for calendar recording much thus swapping isn’t an issue.

thanks

I'm just going through my setup at the start of the journey with Hermes and what is apparant after adding in Obsidian and syncing my files is the following, to move the agent in the right direction.

• Folder Structure
• Clear idea before dumping the files/notes happen
  • current structure
  • Archive
  • Inbox
  • System
    • Config
    • Agents
    • Prompts
    • Workflows
  • Projects
  • Reference
  • Templates
• Agents with a purpose
• One agent will not match all your needs, split out into dedicated agents
  • Marketing, Research, Design, Scripting etc
• Config Files
  • Create config files so your agents are consistant in their tasks, ensure rules apply.
  • My RSS feed is different for my Project to that of my personal RSS feed
• Templates
  • Ensure consistency with results each time
• Frontmatter
  • Use data headings in your Obsidian notes if you want the agent to effectively understand what its looking at

I'm no expert but planning is clearly essential before you kick off your agent on its merry task, yes the agent could do it for you but as i've found with Codex and Claude it can still get messy if you dont review for a cohesive idea on what you want in the first place.

Thoughts? or any other tips?