A Raspberry Pi can host MD-OS (Artificial Prefrontal Cortex) v5.0 as a physical edge node.
MD-OS does not replace Raspberry Pi OS, Linux, systemd, device drivers, GPIO libraries, ROS 2, firmware, or safety systems. It runs above them as the agentic operating layer for memory, bounded action, audit, and continuity.
Raspberry Pi hardware
-> Raspberry Pi OS / Linux
-> systemd / shell / GPIO libraries / device APIs / ROS 2 when present
-> bounded MD-OS connectors
-> md-os/ops readable state
-> md-os/os deterministic builders
-> host runtime or local agent loop
The hardware and Linux stack provide execution, networking, device access, and low-level safety.
MD-OS provides:
A Raspberry Pi node is a good fit for:
sensor, device, local service, or human request
-> bounded connector
-> source snapshot in md-os/ops/sources/
-> deterministic builder
-> project state, agenda, journal, and continuity files
-> optional bounded action through an allowlisted connector
Actions should remain explicit and bounded. A Raspberry Pi connector can request or execute an allowed operation, but destructive or safety-critical behavior should stay behind dedicated device safety layers and human approval rules.
On reboot, the Raspberry Pi does not need hidden session memory to resume. A host runtime or local loop can read:
AGENTS.mdME.mdmd-os/kb/COGNITIVE_BOOTSTRAP.mdmd-os/kb/OPERATIONS.mdmd-os/ops/global_index.mdmd-os/ops/continuity.mdmd-os/ops/state.jsonmd-os/ops/projects/Then it can continue from readable filesystem state.
Use:
MD-OS on Raspberry Pi is a persistent Operating Filesystem above Linux for
bounded device coordination, memory, audit, and replay.
Avoid:
MD-OS replaces Raspberry Pi OS.
MD-OS is a real-time hardware operating system.
MD-OS replaces firmware, drivers, ROS 2, or safety systems.