Updated blog image

Author: kirit93

docs/assets/reachy-mini-openshell/hero.svg

@@ -32,10 +32,10 @@ hide:
       <span>Latest from the team</span>
     </div>
     <article class="dev-note-card dev-note-card--featured dev-note-card--edge-ai">
-      <a class="dev-note-card__link" href="posts/2026-07-13-policy-controlling-reachy-mini-with-openshell/">
+      <a class="dev-note-card__link" href="posts/2026-07-20-policy-controlling-reachy-mini-with-openshell/">
       <div class="dev-note-card__visual dev-note-card__visual--edge-ai" aria-hidden="true">
         <span class="dev-note-card__visual-label">Field note / Edge AI</span>
-        <span class="dev-note-card__visual-index">2026.07.13</span>
+        <span class="dev-note-card__visual-index">2026.07.20</span>
         <span class="dev-note-card__visual-mark">&gt;_</span>
       </div>
       <div class="dev-note-card__copy">

docs/dev-notes/index.md

@@ -42,6 +42,8 @@ card_tags:
 </div>
 <!-- dev-note:byline:end -->
 
+![Bringing Privacy and Security to the Edge with OpenShell: a stylized Reachy Mini robot with two green camera eyes inside an OpenShell boundary ring.](../../assets/reachy-mini-openshell/hero.svg)
+
 Useful AI agents now run for long periods of time, taking on critical tasks to accomplish goals. They call tools, learn new skills, write code, and keep working while no one is watching. How do you give autonomy to such a highly capable agent?
 
 OpenShell is the secure runtime for autonomous agents. It solves this problem by moving the security layer outside the agent. OpenShell runs your agent in a sandbox and sits in the path of everything the agent does. A policy layer, configured separately from the agent, governs what processes the agent can start, which hosts and ports it can reach, which models it can call, and which other services it needs to invoke along its network path.

docs/dev-notes/posts/2026-07-20-policy-controlling-reachy-mini-with-openshell.md

@@ -12,7 +12,7 @@ robot-native audio and camera bridge, fixed REST actions, an optional Gradio
 diagnostic UI, and OpenShell policy enforcement for physical robot tools.
 
 **Want the edge architecture and engineering story?** Read
-[Designing OpenShell for the Edge](../dev-notes/posts/2026-07-13-policy-controlling-reachy-mini-with-openshell.md).
+[Designing OpenShell for the Edge](../dev-notes/posts/2026-07-20-policy-controlling-reachy-mini-with-openshell.md).
 
 **Building it on a robot?** Follow the
 [project-local onboard setup tutorial](https://github.com/NVIDIA/OpenShell-Research/blob/kirit93/reachy-implementation/projects/reachy-mini-openshell/ONBOARD_SETUP.md).

docs/projects/index.md

@@ -3,7 +3,7 @@
 The original combined guide has been split into two focused documents:
 
 - Read **[Designing OpenShell for the Edge: Why Policy Has to Live Next to the
-  Action](../dev-notes/posts/2026-07-13-policy-controlling-reachy-mini-with-openshell.md)**
+  Action](../dev-notes/posts/2026-07-20-policy-controlling-reachy-mini-with-openshell.md)**
   for the reusable edge architecture, design decisions, challenges, and results.
 - Follow the **[project-local onboard setup
   tutorial](https://github.com/NVIDIA/OpenShell-Research/blob/kirit93/reachy-implementation/projects/reachy-mini-openshell/ONBOARD_SETUP.md)**

docs/projects/reachy-mini-openshell-demo-tutorial.md

@@ -6,4 +6,4 @@ The canonical tutorial now lives beside the runnable project:
 
 For the engineering story and reusable edge architecture, read
 [Designing OpenShell for the Edge: Why Policy Has to Live Next to the
-Action](../dev-notes/posts/2026-07-13-policy-controlling-reachy-mini-with-openshell.md).
+Action](../dev-notes/posts/2026-07-20-policy-controlling-reachy-mini-with-openshell.md).

docs/projects/reachy-mini-openshell-sandbox.md

@@ -8,7 +8,7 @@ physical effects on Reachy Mini.
 ## Start here
 
 Read **[Designing OpenShell for the Edge: Why Policy Has to Live Next to the
-Action](../../dev-notes/posts/2026-07-13-policy-controlling-reachy-mini-with-openshell.md)**
+Action](../../dev-notes/posts/2026-07-20-policy-controlling-reachy-mini-with-openshell.md)**
 for the reusable edge architecture, implementation decisions, challenges, and
 demo result.
 
@@ -36,7 +36,7 @@ The tutorial progressively adds:
 
 ## Project resources
 
-- [Implementation Dev Note](../../dev-notes/posts/2026-07-13-policy-controlling-reachy-mini-with-openshell.md)
+- [Implementation Dev Note](../../dev-notes/posts/2026-07-20-policy-controlling-reachy-mini-with-openshell.md)
 - [Onboard setup and troubleshooting tutorial](https://github.com/NVIDIA/OpenShell-Research/blob/kirit93/reachy-implementation/projects/reachy-mini-openshell/ONBOARD_SETUP.md)
 - [Application source and README](https://github.com/NVIDIA/OpenShell-Research/tree/kirit93/reachy-implementation/projects/reachy-mini-openshell)
 - [Motion-disabled policy](https://github.com/NVIDIA/OpenShell-Research/blob/kirit93/reachy-implementation/projects/reachy-mini-openshell/openshell/policy-motion-disabled.yaml)

docs/projects/reachy-mini-openshell/index.md

@@ -7,7 +7,7 @@ access; and OpenShell independently allows or denies the REST requests that can
 cause physical actions.
 
 For the implementation story, architecture decisions, and lessons from building
-the demo, read the [Dev Note](https://github.com/NVIDIA/OpenShell-Research/blob/kirit93/reachy-implementation/docs/dev-notes/posts/2026-07-13-policy-controlling-reachy-mini-with-openshell.md).
+the demo, read the [Dev Note](https://github.com/NVIDIA/OpenShell-Research/blob/kirit93/reachy-implementation/docs/dev-notes/posts/2026-07-20-policy-controlling-reachy-mini-with-openshell.md).
 
 The commands alternate between a **development machine** and **Reachy**. Build
 the wheel and ARM64 image on the development machine; install and run the final

projects/reachy-mini-openshell/ONBOARD_SETUP.md

@@ -7,7 +7,7 @@ deliberately small REST-controlled action surface.
 > **Building the OpenShell policy demo with a physical Reachy?** Follow the
 > [onboard setup tutorial](ONBOARD_SETUP.md). For the architecture, implementation
 > decisions, and lessons learned, read the
-> [Dev Note](../../docs/dev-notes/posts/2026-07-13-policy-controlling-reachy-mini-with-openshell.md).
+> [Dev Note](../../docs/dev-notes/posts/2026-07-20-policy-controlling-reachy-mini-with-openshell.md).
 
 Commands:
 

projects/reachy-mini-openshell/README.md

@@ -15,7 +15,7 @@ nav = [
     "dev-notes/index.md",
     {"Posts" = [
       # dev-notes:nav:start
-      {"Bringing Privacy and Security to the Edge with OpenShell" = "dev-notes/posts/2026-07-13-policy-controlling-reachy-mini-with-openshell.md"},
+      {"Bringing Privacy and Security to the Edge with OpenShell" = "dev-notes/posts/2026-07-20-policy-controlling-reachy-mini-with-openshell.md"},
       {"Making Dev Notes Repeatable" = "dev-notes/posts/2026-06-05-making-dev-notes-repeatable.md"},
       {"Bootstrapping OpenShell Research" = "dev-notes/posts/2026-06-04-bootstrapping-openshell-research.md"}
       # dev-notes:nav:end