aget-record-lesson

To capture session lessons as searchable markdown documents, you classify the insight as Framework or Domain and generate a templated markdown file with metadata in .aget/evolution or knowledge/patterns for traceability and reuse.

Indexing for lessons learned involves reading and updating .aget/evolution/index.json to assign sequential IDs to Framework lessons, maintaining discoverability and traceability across agent sessions.

Classifying knowledge capture insights as Framework or Domain depends on reusability: Framework lessons apply across AGETs and require index updates, while Domain lessons are specific to the principal and stored without indexing.

Yes, you can use markdown templates for knowledge capture without git dependencies because the Skill only requires explicit user classification and file creation in local directories, though committing to git improves traceability.

You need to update index.json during the lesson recording process only when adding Framework lessons, ensuring sequential IDs are maintained for cross-project agent discovery and reuse.

Classifying lessons as Domain instead of Framework affects storage because Domain lessons are stored in knowledge/patterns without index updates, whereas Framework lessons require .aget/evolution and index.json modifications for traceability.