From fbaef6c1bb361306be3289dc5cda3f715102fdf2 Mon Sep 17 00:00:00 2001 From: Ed_ Date: Wed, 6 May 2026 14:08:12 -0400 Subject: [PATCH] docs(guidelines): Add Data-Oriented Python heuristics --- conductor/product-guidelines.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/conductor/product-guidelines.md b/conductor/product-guidelines.md index e2f75cc..a51d818 100644 --- a/conductor/product-guidelines.md +++ b/conductor/product-guidelines.md @@ -15,6 +15,8 @@ ## Code Standards & Architecture - **Data-Oriented & Immediate Mode Heuristics:** Align with the architectural values of engineers like Casey Muratori and Mike Acton. + - **The "Less Python Does, the Better" Rule:** Python should act primarily as a procedural semantic definer (similar to how ImGui defines a UI DAG), delegating heavy lifting to efficient data structures, vectorized operations, or lower-level primitives. + - Minimize Python JIT overhead by favoring bulk data processing over fine-grained object-oriented manipulation. - The GUI (`gui_2.py`) must remain a pure visualization of application state. It should not *own* complex business logic or orchestrator hooks (strive to decouple the 'Application' controller from the 'View'). - Treat the UI as an immediate mode frame-by-frame projection of underlying data structures. - Optimize for zero lag and never block the main render loop with heavy Python JIT work.