Max-Self-Improvement — Self-Evolution & Memory System

Overview

MiniMax Agent's self-evolution framework integrating 5-layer memory architecture, supporting cross-session persistent context and continuous performance optimization.

Core Components

1. Five-Layer Memory Architecture

2. Learnings System

Records structured learnings from errors, corrections, and successes.

.learnings/
├── LEARNINGS.md         # Learning entries
├── ERRORS.md            # Error logs
└── FEATURE_REQUESTS.md  # Feature requests

Entry ID Format

TYPE-YYYYMMDD-XXX
├── TYPE: LRN | ERR | FEAT
├── YYYYMMDD: Current date
└── XXX: Sequence number or random 3 chars

Trigger Scenarios

Learning Triggers → LEARNINGS.md

Error Triggers → ERRORS.md

Feature Triggers → FEATURE_REQUESTS.md

Correction Detection Patterns

When user says phrases like:

• "No, that's not right..."
• "Actually, it should be..."
• "You're wrong about..."
• "That's outdated..."

→ Create LRN entry with category: correction

Entry Templates

Learning Entry (LEARNINGS.md)

## [LRN-YYYYMMDD-XXX] category

**Logged**: ISO-8601 timestamp
**Priority**: low | medium | high | critical
**Status**: pending | acknowledged | applied
**Area**: frontend | backend | infra | tests | docs | config

### Summary
One-line description of what was learned

### Details
Full context: what happened, what was wrong, what's correct

### Suggested Action
Specific fix or improvement to make

### Metadata
- Source: conversation | error | user_feedback | discovery
- Related Files: path/to/file.ext
- Tags: tag1, tag2
- See Also: LRN-YYYYMMDD-XXX
- Pattern-Key: simplify.dead_code | harden.input_validation
- Recurrence-Count: 1
- First-Seen: YYYY-MM-DD
- Last-Seen: YYYY-MM-DD

Error Entry (ERRORS.md)

## [ERR-YYYYMMDD-XXX] skill_or_command_name

**Logged**: ISO-8601 timestamp
**Priority**: high
**Status**: pending | investigated | resolved
**Area**: frontend | backend | infra | tests | docs | config

### Summary
Brief description of what failed

### Error
Actual error message or output

### Context
- Command/operation attempted
- Input or parameters used
- Environment details if relevant

### Suggested Fix
If identifiable, what might resolve this

### Metadata
- Reproducible: yes | no | unknown
- Related Files: path/to/file.ext
- See Also: ERR-YYYYMMDD-XXX

Feature Request Entry (FEATURE_REQUESTS.md)

## [FEAT-YYYYMMDD-XXX] capability_name

**Logged**: ISO-8601 timestamp
**Priority**: medium
**Status**: pending | planned | implemented | rejected
**Area**: frontend | backend | infra | tests | docs | config

### Requested Capability
What the user wanted to do

### User Context
Why they needed it, what problem they're solving

### Complexity Estimate
simple | medium | complex

### Suggested Implementation
How this could be built, what it might extend

### Metadata
- Frequency: first_time | recurring
- Related Features: existing_feature_name

Priority Guidelines

Area Labels

Memory Promotion Targets

Tool Usage Rules

Conflict Resolution Priority

User Explicit Instruction > Recent Implicit Behavior > High-Confidence LT Memory > Low-Confidence Pattern > Default Reasoning

Common Mistakes to Avoid

1. session_notes stack appending — Update in-place, keep file lean
2. Not reading memory before work — Must read session_notes + user_preferences first
3. Logging everything to memory — Only write reusable content, avoid noise
4. No confidence tags on memory — Knowledge without confidence is blindly adopted
5. Not saving before restart — Must write all in-progress state before restart

Quick Reference

Related References

• Detailed architecture: references/architecture.md
• Memory templates: references/memory_templates.md
• Evolution cases: references/evolution_cases.md
• Learning templates: assets/SKILL-TEMPLATE.md