integrate-learning

Integrating recurring journal insights into permanent knowledge files is done by bridging source entries into durable identity documents like bio.md, CLAUDE.md, and universal journals to guide future work.

Maintaining learning continuity across coding sessions requires updating growth-related memory files and operational documents, which facilitates future session loading and preserves your accumulated knowledge patterns.

Using identity documents to guide operational patterns and paradigm-level knowledge is fully supported, allowing you to map insights specifically into bio.md for identity or CLAUDE.md for operational workflows.

Auto-memory integration handles quality criteria by evaluating source journal entries against defined integration levels and configuration-driven workflow targets before writing them into durable memory files.

Updating universal journals is appropriate for paradigm-level knowledge integration, whereas updating CLAUDE.md is reserved for capturing operational patterns that directly guide future work behaviors.

Learning integration requires a CLI and configuration setup to enforce configuration-driven workflows, ensuring that auto-memory targets and level-specific quality criteria are met consistently during the integration process.