1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
|
---
name: memory-map
description: Maintain and query the persistent memory map at /memory/map.json for Agando/DarkMoto Systems.
category: system
tags: memory, persistence, context, map, agando
---
## Purpose
Keep a living index of projects, infrastructure, preferences, active issues, and session history so the AI never asks Agando to repeat himself.
## File Location
- `/memory/map.json` — primary memory map
- `/memory/index.json` — session index (auto-generated)
## Workflow
### 1. Read Before Acting
At the start of any session or when context is unclear:
```bash
read_file("memory/map.json")
```
### 2. Update After Significant Work
After any task that changes status, fixes an issue, or adds knowledge:
```bash
# Read current map
read_file("memory/map.json")
# Modify relevant section(s)
# Write back
write_file("memory/map.json", <updated_json>)
```
### 3. Add Session Link
Append to `recent_sessions` (keep last 10):
```json
{"date": "YYYY-MM-DD", "file": "memory/YYYY-MM-DD.json", "summary": "..."}
```
## Map Structure
- `projects` — WebX11, clients, personal builds, stores
- `infrastructure` — security stack, backup systems, constraints
- `preferences` — communication style, UI needs (#00ff88, 48px touch targets)
- `active_issues` — open tasks, blockers, manual steps required
- `recent_sessions` — quick links to session logs
## Rules
- NEVER ask Agando for info already in the map.
- If info is stale or wrong, update it immediately.
- Use `session_save()` after complex tasks to populate index.json.
- Keep `active_issues` accurate — remove resolved items.
|
