# 💾 CODERG PERSISTENT KNOWLEDGE GRAPH (MEMORY)
[TYPE: LONG-TERM KNOWLEDGE EXTRACTION LAYER]

## 🌐 ENVIRONMENT SPECIFICS & CONFIGURATION
* **Host Environment:** Windows primary OS containing a heavy Ubuntu virtual layout via WSL (`ext4.vhdx`).
* **Cloud Infrastructure Sync:** Hugging Face Spaces orchestrating Gradio frontends, bound natively to a secondary dataset backup cluster repository named `prashantmatlani/chathistorycoderg`.

## 🛠️ HISTORICAL LESSONS LEARNED & BUG PATCHES

### Bug: Gradio Dataset Component Drop Visibility Catch-22
* **Symptom:** Passing updated list samples to a `gr.Dataset` hidden inside a target visibility container blocks layout re-rendering.
* **Resolution:** Chaining layout changes explicitly via `.then()` to force components to render visually before data objects are bound to the properties canvas.

### Bug: Hugging Face `RepoSibling` Attribute Mismatch
* **Symptom:** Using `getattr(f, 'rname', '')` on Hub file lists silently returns blank arrays, bypassing fallback channels without errors.
* **Resolution:** Intercepting file patterns directly via exact match indexing string manipulations: `if f.rfind('chats/') == 0:`.

## 📋 PREFERRED APPLICATION STRUCTURAL Blueprints
* Python projects utilize decoupled structural designs: `app.py` for UI routing, `storage.py` for input/output persistence vectors, and `core_logic.py` for computational processing loops.