🧠 Agent Memory Update Protocol (v1.1)

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.

📂 1. Core Memory Targets

File	Context Layer	Purpose
`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).

🔄 2. The 4-Step Update Procedure

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: 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 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?

🎨 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 | Fox Memory System | Updated: 2026-04-23

2.9 KiB Raw Blame History