diff --git a/Topology-of-the-hardware-of-the-deep-future.md b/Topology-of-the-hardware-of-the-deep-future.md
index 579037b..811a8d2 100644
--- a/Topology-of-the-hardware-of-the-deep-future.md
+++ b/Topology-of-the-hardware-of-the-deep-future.md
@@ -1,4 +1,4 @@
-In thinking about how to write a software architecture that won't quickly become obsolescent, I find that I'm thinking increasingly about the hardware on which it will run.
+![HAL 9000 - a vision of the hardware of the deep future](https://vignette4.wikia.nocookie.net/2001/images/5/59/Hal_console.jpg/revision/latest?cb=20090823025755)In thinking about how to write a software architecture that won't quickly become obsolescent, I find that I'm thinking increasingly about the hardware on which it will run.
 
 In [[Post Scarcity Hardware]] I envisaged a single privileged node which managed main memory. Since then I've come to thing that this is a brittle design which will lead to bottle necks, and that each cons page will be managed by a separate node. So there needs to be a hardware architecture which provides the shortest possible paths between nodes.