Browse Source
docs: upgrade Memory Update Protocol to v1.1 and expand v1.1 "Ares" Chronicles
docs: upgrade Memory Update Protocol to v1.1 and expand v1.1 "Ares" Chronicles
- Overhauled intel/memory_update.md with v1.1 protocol:
- Implemented "Trigger Identification" thresholds (Structural, Physical, Behavioral).
- Added "AI Search Optimization" requirements (Keyword Density, Structural Consistency).
- Mandated "Doc-Code Parity" verification checklist.
- Standardized absolute file:/// URIs for instant cross-document navigation.
- Established "Rule of Thumb" for Chronicles executive summary length (10-12%).
- Expanded CHRONICLES.md Executive Summary:
- Added high-density briefings for Architecture (Stage-based), Radar (Shenron Iterations), Data Export (MCAP Metrology), Dashboard (SSE), and the new Physics Layer.
- Synchronized gemini.md, Shenron_debug.md, and dashboard.md with v1.1 "Ares" architecture:
- Documented VideoStage, centralized physics.py, and new telemetry tags.
- Resolved legacy "Pending Issues" in calibration logs.
main
4 changed files with 120 additions and 60 deletions
-
56gemini.md
-
23intel/CHRONICLES.md
-
67intel/memory_update.md
-
34intel/radar/diagnostics/Shenron_debug.md
@ -1,45 +1,56 @@ |
|||||
# 🧠 Agent Memory Update Protocol |
|
||||
|
# 🧠 Agent Memory Update Protocol (v1.1) |
||||
|
|
||||
This document instructs future AI agents on how to maintain the repository's documentation and "memory" files. Follow these steps after every significant feature implementation, technical breakthrough, or calibration milestone. |
|
||||
|
This document ensures that the repository's "Digital Soul"—its architecture, physics rationale, and technical history—remains synchronized with the code. Follow these steps to maintain high-fidelity situational awareness for both human and AI developers. |
||||
|
|
||||
--- |
--- |
||||
|
|
||||
## 📂 Target Files |
|
||||
|
## 📂 1. Core Memory Targets |
||||
|
|
||||
| File | Purpose | Update Context | |
|
||||
|
| File | Context Layer | Purpose | |
||||
| :--- | :--- | :--- | |
| :--- | :--- | :--- | |
||||
| `intel/CHRONICLES.md` | The Project Saga | Git milestones, technical "Why" & "How," bug post-mortems. | |
|
||||
| `gemini.md` | Source of Truth | Architecture changes, new components, active file rules. | |
|
||||
| `intel/radar/diagnostics/Shenron_debug.md` | Calibration Log | Radar iterations (01-XX), specific physics fixes. | |
|
||||
| `intel/scenarios/*.md` | Scenario Guides | Decision rationale for specific testing maneuvers. | |
|
||||
|
| `gemini.md` | **Structural** | The high-level Source of Truth. Update when layout or dependencies change. | |
||||
|
| `intel/CHRONICLES.md` | **Historical** | The "Saga." Explains the *Why* behind the *What.* Captures math/physics breakthroughs. | |
||||
|
| `intel/radar/diagnostics/` | **Scientific** | Iteration logs for radar calibration, SNR tuning, and coordinate fixes. | |
||||
|
| `intel/internal/[version]/` | **Versioned** | Snapshots of major releases (Walkthroughs, Changelogs). | |
||||
|
|
||||
--- |
--- |
||||
|
|
||||
## 🔄 Update Procedure |
|
||||
|
## 🔄 2. The 4-Step Update Procedure |
||||
|
|
||||
### Step 1: Analyze Evolution |
|
||||
Run the following to understand what changed: |
|
||||
```powershell |
|
||||
git log --pretty=format:"%ad | %s | %b" --date=short -n 10 |
|
||||
``` |
|
||||
|
### Step 1: Trigger Identification |
||||
|
Determine if your changes meet the "Memory Threshold": |
||||
|
- [ ] **Structural**: Did you move files or add new components (e.g., `src/pipeline`)? |
||||
|
- [ ] **Physical**: Did you change a formula, gain offset, or coordinate transform? |
||||
|
- [ ] **Behavioral**: Did you change how the Dashboard or Orchestrator interacts with the system? |
||||
|
|
||||
### Step 2: Extract Rationale |
|
||||
Don't just log *what* happened. Documentation must explain: |
|
||||
- **The Problem**: What was breaking or inaccurate? |
|
||||
- **The Decision**: Why was this specific technical path taken over others? |
|
||||
- **The Physics/Math**: What formulas or logical constraints were applied? |
|
||||
|
### Step 2: Contextual Extraction |
||||
|
Don't just log the change. Extract the **Rationale**: |
||||
|
- **The Problem**: What was breaking, blurry, or inaccurate? |
||||
|
- **The Decision**: Why this path? (e.g., "Used `Pathlib` over `os.path` for robust Windows pathing"). |
||||
|
- **The Physics**: Document formulas using LaTeX: $P_{rec} = \frac{P_{tx} G^2 \lambda^2 \sigma}{(4\pi)^3 R^4}$. |
||||
|
|
||||
### Step 3: Atomic Updates |
|
||||
- **Chronicles**: Append new daily entries to Section 6. If a major milestone was reached, create a dedicated Deep-Dive in Section 4. |
|
||||
- **Iteration Log**: If working on the Shenron radar, update the Iteration Table (01-XX) with the latest physics impacts. |
|
||||
- **Gemini**: Update the "Repository Layout" if new directories or scripts are added. |
|
||||
|
### Step 3: Atomic Synthesis |
||||
|
- **Chronicles**: Append daily entries to Section 6. Update Section 4 with architectural deep-dives. **Rule of Thumb:** Maintain the "Executive Summary" at ~10-12% of the document's total length to ensure it remains a high-density standalone briefing. |
||||
|
- **Gemini**: Ensure the "Repository Layout" and "Component Reference" match the current `tree /f`. |
||||
|
- **Linking**: Cross-link documents using absolute `file:///` URIs to allow instant agent navigation. |
||||
|
|
||||
|
### Step 4: Verification (Doc-Code Parity) |
||||
|
Perform a final "Sanity Check": |
||||
|
- [ ] Does the documentation reflect the *current* state of the code? |
||||
|
- [ ] Are any legacy "Knobs or Dials" still documented that were removed? |
||||
|
- [ ] Did you update the "Last Updated" timestamp in `gemini.md`? |
||||
|
|
||||
--- |
--- |
||||
|
|
||||
## 🎨 Style Guide |
|
||||
- **Premium Aesthetic**: Use GitHub alerts (Note, Important, Tip) to highlight key insights. |
|
||||
- **Technical Rigor**: Use LaTeX math for physics formulas. |
|
||||
- **No Fluff**: Keep descriptions concise but info-dense. |
|
||||
|
## 🎨 3. Style & Search Optimization |
||||
|
|
||||
|
### For the Human Reader: |
||||
|
- **Premium Aesthetics**: Use GitHub alerts (`> [!IMPORTANT]`) and Mermaid diagrams for flows. |
||||
|
- **Media**: Embed screenshots or `mcap` recording clips for visual proof of calibration. |
||||
|
|
||||
|
### For the AI Agent: |
||||
|
- **Keyword Density**: Use specific terms like "coordinate system," "RHS conversion," and "sync mode" to aid semantic search. |
||||
|
- **Structural Consistency**: Keep headers predictable so future agents can regex the chronology efficiently. |
||||
|
|
||||
--- |
--- |
||||
*Generated by Antigravity AI | Repository Memory System | 2026-04-15* |
|
||||
|
*Generated by Antigravity AI | Fox Memory System | Updated: 2026-04-23* |
||||
Write
Preview
Loading…
Cancel
Save
Reference in new issue