TaskManager refactor

semantic_protocol.md

@@ -11,7 +11,7 @@ This protocol standardizes the "Semantic Bridge" between the two languages using
 ## I. CORE REQUIREMENTS
 1.  **Causal Validity:** Semantic definitions (Contracts) must ALWAYS precede implementation code.
 2.  **Immutability:** Architectural decisions defined in the Module/Component Header are treated as immutable constraints.
-3.  **Format Compliance:** Output must strictly follow the `[DEF]` / `[/DEF]` anchor syntax for structure.
+3.  **Format Compliance:** Output must strictly follow the `[DEF:..:...]` / `[/DEF:...:...]` anchor syntax for structure.
 4.  **Logic over Assertion:** Contracts define the *logic flow*. Do not generate explicit `assert` statements unless requested. The code logic itself must inherently satisfy the Pre/Post conditions (e.g., via control flow, guards, or types).
 5.  **Fractal Complexity:** Modules and functions must adhere to strict size limits (~300 lines/module, ~30-50 lines/function) to maintain semantic focus.
 
@@ -26,13 +26,13 @@ Used to define the boundaries of Modules, Classes, Components, and Functions.
 
 *   **Python:**
     *   Start: `# [DEF:identifier:Type]`
-    *   End:   `# [/DEF:identifier]`
+    *   End:   `# [/DEF:identifier:Type]`
 *   **Svelte (Top-level):**
     *   Start: `<!-- [DEF:ComponentName:Component] -->`
-    *   End:   `<!-- [/DEF:ComponentName] -->`
+    *   End:   `<!-- [/DEF:ComponentName:Component] -->`
 *   **Svelte (Script/JS/TS):**
     *   Start: `// [DEF:funcName:Function]`
-    *   End:   `// [/DEF:funcName]`
+    *   End:   `// [/DEF:funcName:Function]`
 
 **Types:** `Module`, `Component`, `Class`, `Function`, `Store`, `Action`.
 
@@ -64,7 +64,7 @@ Defines high-level dependencies.
 
 # ... IMPLEMENTATION ...
 
-# [/DEF:module_name]
+# [/DEF:module_name:Module]
 ```
 
 ### 2. Svelte Component Header (`.svelte`)
@@ -82,20 +82,20 @@ Defines high-level dependencies.
 <script lang="ts">
   // [SECTION: IMPORTS]
   // ...
-  // [/SECTION]
+  // [/SECTION: IMPORTS]
 
   // ... LOGIC IMPLEMENTATION ...
 </script>
 
 <!-- [SECTION: TEMPLATE] -->
 ...
-<!-- [/SECTION] -->
+<!-- [/SECTION: TEMPLATE] -->
 
 <style>
   /* ... */
 </style>
 
-<!-- [/DEF:ComponentName] -->
+<!-- [/DEF:ComponentName:Component] -->
 ```
 
 ---
@@ -123,7 +123,7 @@ def calculate_total(items: List[Item]) -> Decimal:
     
     # Logic ensuring @POST
     return total
-# [/DEF:calculate_total]
+# [/DEF:calculate_total:Function]
 ```
 
 ### 2. Svelte/JS Contract Style (JSDoc)
@@ -146,7 +146,7 @@ async function updateUserProfile(profileData) {
     
     // ...
 }
-// [/DEF:updateUserProfile]
+// [/DEF:updateUserProfile:Function]
 ```
 
 ---
@@ -168,9 +168,19 @@ Logs delineate the agent's internal state.
 
 ---
 
-## VI. GENERATION WORKFLOW
+## VI. FRACTAL COMPLEXITY LIMIT
+
+To maintain semantic coherence and avoid "Attention Sink" issues:
+*   **Module Size:** If a Module body exceeds ~300 lines (or logical complexity), it MUST be refactored into sub-modules or a package structure.
+*   **Function Size:** Functions should fit within a standard attention "chunk" (approx. 30-50 lines). If larger, logic MUST be decomposed into helper functions with their own contracts.
+
+This ensures every vector embedding remains sharp and focused.
+
+---
+
+## VII. GENERATION WORKFLOW
 
 1.  **Context Analysis:** Identify language (Python vs Svelte) and Architecture Layer.
-2.  **Scaffolding:** Generate the `[DEF]` Anchors and Header/Contract **before** writing any logic.
+2.  **Scaffolding:** Generate the `[DEF:...:...]` Anchors and Header/Contract **before** writing any logic.
 3.  **Implementation:** Write the code. Ensure the code logic handles the `@PRE` conditions (e.g., via `if/return` or guards) and satisfies `@POST` conditions naturally. **Do not write explicit `assert` statements unless debugging mode is requested.**
-4.  **Closure:** Ensure every `[DEF]` is closed with `[/DEF]` to accumulate semantic context.
+4.  **Closure:** Ensure every `[DEF:...:...]` is closed with `[/DEF:...:...]` to accumulate semantic context.