SEAS Core Template
This skill implements the Meta-Specification. It is designed to be a "living" instruction set that improves based on its own execution history, using the Meta-Specification as the primary reference for agents to understand the boundaries and logic of self-evolution.
Guidelines
- Always Log: Create a journal entry for ANY non-trivial failure or complex success.
- Fact vs. Reason: Keep
case.mdobjective andexperience.mdsubjective. - Verification is Mandatory: NEVER commit an evolution change without passing
test_command. - Snapshot Before Change: Before editing instructions or scripts, ensure a backup exists or use the archival system to track state.
Procedures
Phase 1: Journaling (Real-time)
If an error occurs or a new pattern is discovered:
mkdir -p journals/$(date +%Y%m%d-%H%M%S)- Document the facts in
case.md. - Document the reasoning/fix in
experience.md.
Phase 2: Meditation (Triggered)
If count(journals/) >= meditation_threshold:
- Aggregate: Run
python3 scripts/meditate.py. - Analyze: Read the aggregated report and identify patterns.
- Decide: Choose to
UPDATE(instructions),FIX(code), orDEFER(wait for more data).
Phase 3: Action & Verification
- Execute: Apply the chosen changes to
SKILL.md,scripts/, orreferences/. - Verify: Run
python3 scripts/verify_integrity.py. - Rollback: If verification fails, revert changes and log the failure.
Phase 4: Archival
- Archive: After successful verification, run
python3 scripts/archive.pyto move processed journals to long-term storage and updatearchives/HISTORY.md.