You can not select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
1.9 KiB
1.9 KiB
🧠 Agent Memory Update Protocol
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.
📂 Target Files
| File | Purpose | Update Context |
|---|---|---|
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. |
🔄 Update Procedure
Step 1: Analyze Evolution
Run the following to understand what changed:
git log --pretty=format:"%ad | %s | %b" --date=short -n 10
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 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.
🎨 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.
Generated by Antigravity AI | Repository Memory System | 2026-04-15