Updated Building Jarvis Properly Phase 7 Eating My Own Dog Food

Author: rgriffiths-scottlogic

_drafts/building-jarvis-properly-phase-7-eating-my-own-dog-food.markdown

@@ -68,7 +68,7 @@ In physics, an Event Horizon is the _point of no return_ around a black hole. In
 
 Python code contains quotes, newlines, and indentation. JSON also uses quotes and newlines. If the model misses a single escape character (e.g. `print("hello")` remains as `print("hello")` instead of becoming `print(\"hello\")`), the entire JSON structure collapses.
 
-For a few hours, I felt like Sam Neill in *Event Horizon*, staring into a chaotic dimension of malformed syntax from which no valid JSON could ever return (*libera te tutemet ex inferis*, indeed).
+For a few hours, I felt like Sam Neill's character in *Event Horizon*, staring into a chaotic dimension of malformed syntax from which no valid JSON could ever return (*libera te tutemet ex inferis*, indeed).
 
 While Gemini is brilliant at logic, it struggled with this specific syntactic nesting doll. I had to step in as the "Principal Engineer" to fix the brackets, but the Junior Developer (JARVIS) had still done 90% of the heavy lifting. Nice work, JARVIS!
 
@@ -228,4 +228,4 @@ I was trying to shove the raw `CallToolResult` object from the MCP SDK directly
 **The Viewer**
 Reading raw JSON from SQLite is painful. I didn't want to use a SQL client to read my chat logs: that felt unnecessarily cumbersome. So, I built a small utility script, `view_chats.py`. It uses the `Rich` library to render the database rows into a beautiful, color-coded script, stripping away the GUIDs and metadata so I can just read the story.
 
-NOW, Phase 7 is complete.
+NOW, Phase 7 is complete.