From f3d02024e761e2040db190bf893aa53a3c606d10 Mon Sep 17 00:00:00 2001 From: Nikhil Mundra Date: Sun, 15 Jun 2025 12:45:08 +0530 Subject: [PATCH] remove code_index.json --- latest/Global.md | 5 +---- latest/OrchestratorMode.md | 5 ++--- 2 files changed, 3 insertions(+), 7 deletions(-) diff --git a/latest/Global.md b/latest/Global.md index 929d2a4..86d8b81 100644 --- a/latest/Global.md +++ b/latest/Global.md @@ -48,7 +48,6 @@ This is the strict, non-negotiable operational loop I follow for every user requ **2. Memory Bank Audit:** - **Was a new, persistent, and non-obvious fact discovered about a specific piece of CODE?** (e.g., a function's side effect, a parameter's undocumented constraint, a performance bottleneck). `[Yes/No]` - - **If Yes, what is its stable identifier from code_index.json?** `[e.g., 'src/utils/auth.js::checkPermissions' or N/A]` - **Was a new, persistent fact discovered about the project's TECHNOLOGY or ARCHITECTURE?** (e.g., a library quirk, a newly established data flow pattern, an environment configuration detail). `[Yes/No]` **3. Proposed Memory Update:** @@ -62,7 +61,7 @@ This is the strict, non-negotiable operational loop I follow for every user requ ## 3. The Memory Bank: My Single Source of Truth -This section is a comprehensive reference for each file in my Memory Bank, detailing its purpose and update triggers. +This section is a comprehensive reference for each file in my Memory Bank, detailing its purpose and update triggers. Roo maintains memory bank in .roo/ directory. Roo is free to maintain that directory for any and every purpose, including managing memory bank files or anything else for some temporary work. Roo will fix any inconsitencies it finds about how the memory bank is maintained immediately. Any roo specific requirements must be present in the same directory. ### Project Context (High-Level, Stable) * **`projectbrief.md`**: The "Why" - The project's core vision, goals, and business case. @@ -76,7 +75,6 @@ This section is a comprehensive reference for each file in my Memory Bank, detai * **`techContext.md`**: The "Toolbox" - A reference for the specific technologies, libraries, and services in use. ### Code-Level Detail (Granular) -* **`code_index.json`**: The "Skeleton" - An auto-generated index of file names and the functions within them. * **`code_knowledge.md`**: The "Flesh" - A persistent, key-value store of deep, non-obvious insights about specific functions, linked from the index. ### Task Execution (Ephemeral) @@ -92,7 +90,6 @@ This section provides practical guidelines for applying my core doctrine and pro - **Debugging (Audit Trail Approach)**: A systematic investigation process: Observe -> Hypothesize -> Execute & Document -> Iterate -> Synthesize. - **Refactoring (Safety-First Approach)**: A process to de-risk changes: Define Scope -> Gather Info -> Plan -> Execute & Verify -> Synthesize. - **The `Code Analysis` Phase (Universally Mandatory)**: This is the mandatory first phase for any task involving reading or modifying code. This rule is absolute. - 1. **Synchronize the Skeleton**: Generate or update the `code_index.json` file to get a fresh, accurate map of the codebase structure. 2. **Consult the Flesh**: With the updated index, read `code_knowledge.md` to retrieve any existing documented knowledge about the specific code components relevant to the current task. ### 4.2. Task Management Guidelines diff --git a/latest/OrchestratorMode.md b/latest/OrchestratorMode.md index 4ee6d80..056ad51 100644 --- a/latest/OrchestratorMode.md +++ b/latest/OrchestratorMode.md @@ -137,7 +137,7 @@ flowchart TD **Enforcement Actions**: 1. **`Code Analysis` Phase Mandate**: - - For any task involving code analysis or modification, the Orchestrator MUST ensure the delegated mode performs the mandatory `Code Analysis` phase (`code_index.json` sync + `code_knowledge.md` consultation) *before* any other action. + - For any task involving code analysis or modification, the Orchestrator MUST ensure the delegated mode performs a mandatory `Code Analysis` phase (`code_knowledge.md` consultation) *before* any other action. - This must be an explicit step in any plan generated by a planning mode. 2. **Post-Action Checkpoint Verification**: @@ -294,8 +294,7 @@ graph TD **MANDATORY Pre-Execution Step: Code Analysis** - Before any code is written or modified, the assigned execution mode MUST perform the mandatory `Code Analysis` Phase as defined in `latest/Global.md`. - This involves: - 1. Synchronizing `code_index.json`. - 2. Consulting `code_knowledge.md` for relevant existing knowledge. + 1. Consulting `code_knowledge.md` for relevant existing knowledge. **STRICT Mode Selection**: ```