✨ Open infrastructure for self-healing robots and software-defined machines.

selfpatch is an open, practical attempt to build the missing “nervous system” for robots and SDVs:
diagnostics, introspection, and update flows that are good enough for humans and for AI agents to reason about.

This GitHub organization hosts the open-source core and experiments around that idea.

Modern robots and SDVs run on complex stacks:

• ROS 2 graphs, nodes, topics, actions
• Mixed hardware (MCUs, ECUs, edge HPC, cloud)
• Many protocols (DDS, Zenoh, WebSockets, Iceoryx, UDS, OPC UA, CAN/J1939, …)

Yet diagnostics and updates are often:

• Fragmented per vendor / per subsystem
• Hard to introspect at runtime
• Designed for humans clicking through tools, not for automation or AI

selfpatch aims to change that by providing:

1. A modern diagnostic & introspection layer

   • Runtime discovery of components, apps, topics, health, configuration
   • API-first approach: HTTP/REST + schemas instead of ad-hoc scripts

2. A foundation for safe self-healing flows

   • Clear, machine-readable model of the system
   • Hooks for health checks, mitigation actions, and OTA-style updates
   • Designed so that AI agents can understand and justify their actions

3. Bridges instead of rewrites

   • Integrations with existing ecosystems (ROS 2, UDS, SOVD, OPC UA, …)
   • Evolution over revolution: start where your robots are today.

🚧 Everything here is early-stage and evolving. APIs and layouts may change.

Goal: A ROS 2–native diagnostics and introspection layer that can act as a foundation for self-healing.

Key capabilities:

• 🔍 Discovery of nodes, components, and apps as a diagnostic tree
• 📊 Exposure of relevant state and configuration via a clean API
• 🔌 Compatibility with SOVD concepts (Areas, Components, Functions, Apps)
• 🌉 Bridge between ROS 2 introspection and higher-level tools / cloud services

Repository: github.com/selfpatch/ros2_medkit ⭐

More projects will be added as the ecosystem grows.

• Robotics teams using ROS 2 who need better remote diagnostics and update workflows
• SDV / mobility engineers looking to modernize diagnostics without rewriting everything
• Tooling & platform teams building monitoring, OTA, or AI-driven operations on top of robots and vehicles
• Researchers & tinkerers exploring self-healing, digital twins, and autonomous remediation

If you’ve ever thought “we can’t safely automate fixes because we don’t really understand what’s running where”,
you’re in the right place.

Right now, the main focus is on:

• Bootstrapping the first repositories (starting with ros2_medkit)
• Designing a simple but extensible diagnostics model
• Prototyping real integrations with ROS 2–based robots

You can help by:

• ⭐ Starring the repositories in this org
• Opening issues with use-cases, pain points, and ideas
• Contributing code, docs, or examples once repos are live
• Sharing feedback from real robots / fleets

For now, the best way to follow the project and reach out is:

• Watch this organization on GitHub for new repositories and releases
• Use issues and (soon) Discussions in the repositories to propose ideas and share feedback

If you’re working on robots, SDV platforms, or tooling and this resonates,
don’t hesitate to open an issue or start a discussion – collaboration is the whole point of this effort.