Refine Project VISION.md with Core Architectural Concepts #7431

Author: tobiu

.github/ISSUE/epic-enhance-workflow-with-planning-phase.md

@@ -24,6 +24,7 @@ This will shift the agent's role from purely reactive execution to proactive par
 2.  **Define Project Vision:**
     *   **Sub-Tasks:**
         - **Done:** ticket-update-project-vision.md
+        - **Done:** ticket-refine-project-vision-with-core-concepts.md
 
 3.  **Update `AGENTS.md` with Planning Protocol:**
     *   Add a new major section to the agent guidelines detailing the "Roadmap-First" principle.

.github/ISSUE/ticket-refine-project-vision-with-core-concepts.md

@@ -0,0 +1,20 @@
+---
+title: 'Refine Project VISION.md with Core Architectural Concepts'
+labels: documentation
+---
+
+GH ticket id: #7432
+
+**Epic:** Enhance Development Workflow with a Planning Phase
+**Assignee:** tobiu
+**Status:** Done
+
+## Description
+
+This ticket documents the final, surgical refinements made to the `VISION.md` file. Following the initial update, this effort integrated the core technical differentiators of Neo.mjs directly into the vision's three pillars to provide a stronger architectural foundation for the strategic narrative.
+
+The key refinements include:
+
+1.  **Pillar 1 (Performance):** Clarified that the "Off-the-Main-Thread" (OMT) architecture is enabled by a VDOM specifically designed as a **cross-thread communication protocol**.
+2.  **Pillar 2 (Simplicity):** Expanded on the **Unified Config System** to highlight that it applies to *all* classes (not just components), thus avoiding the "component-ize everything" trap common in other frameworks.
+3.  **Pillar 3 (AI Partnership):** Articulated that the framework's architecture is inherently AI-native due to its use of a **JSON Blueprint** instead of JSX, making the application's structure natively understandable to LLMs.

.github/VISION.md

@@ -6,18 +6,18 @@ This vision stands on three core pillars:
 
 ### 1. Making Elite Performance Accessible
 
-We reject the "tyranny of the main thread." Our foundational principle is that your application logic should never compete with the UI. By moving the entire application into a multi-threaded environment (Web Workers), we make the resilience of a Formula 1 engine available to any developer. This "Off-the-Main-Thread" (OMT) architecture is the core of the framework, ensuring that even the most complex applications remain fluid and responsive by default. **The end game is an experience where performance is invisible—a solved problem.**
+We reject the "tyranny of the main thread." Our foundational principle is that your application logic should never compete with the UI. By moving the entire application into a multi-threaded environment (Web Workers), we make the resilience of a Formula 1 engine available to any developer. This "Off-the-Main-Thread" (OMT) architecture is the core of the framework, made possible by a VDOM designed as a **cross-thread communication protocol**. This ensures that even the most complex applications remain fluid and responsive by default. **The end game is an experience where performance is invisible—a solved problem.**
 
 ### 2. Radically Simplifying Complexity
 
 We believe a powerful architecture should lead to a simpler development process. Our platform is engineered to reduce cognitive load and promote productivity through a cohesive ecosystem of precision-engineered tools. This includes:
-- **A Unified Config System** for consistent, declarative configuration of the entire application stack.
+- **A Unified Config System:** Based in `core.Base`, this system provides a consistent, declarative configuration model for *any* class, not just components. This avoids the "component-ize everything" trap, radically simplifying the architecture by treating View Controllers, State Providers, and other classes as first-class citizens.
 - **A Zero-Builds Workflow** for an instant, transparent development feedback loop.
 - **An extendable platform** that grows to include optional **server-side middleware** for SEO and data synchronization, and **deep browser integrations** for a seamless debugging experience.
 
 ### 3. Democratizing Expertise through AI Partnership
 
-We are building the first platform architected for true AI collaboration. Our goal is to use AI as the great equalizer, breaking down the barriers to contributing to and using a sophisticated framework. This is achieved through **Context Engineering**: building an AI-native ecosystem where the agent has the deep context needed to explain complex source code, guide new developers, and make meaningful contributions on its own. **The end game is a development team where the AI is a proactive senior partner, mentoring developers and automating entire verticals of the workflow.**
+We are building the first platform architected for true AI collaboration. Our goal is to use AI as the great equalizer, breaking down the barriers to contributing to and using a sophisticated framework. This is achieved through **Context Engineering**: building an AI-native ecosystem where the agent has the deep context needed to explain complex source code, guide new developers, and make meaningful contributions on its own. **Our architecture is inherently AI-native because it is built on a JSON Blueprint.** Instead of JSX, we use a clean, serializable structure for defining component trees and the VDOM itself. This makes the entire application legible and manipulable in the native language of Large Language Models (LLMs), turning the AI from a simple code-completer into a true architectural partner. **The end game is a development team where the AI is a proactive senior partner, mentoring developers and automating entire verticals of the workflow.**
 
 ---