crux-skill-memory-crud

Frontmatter validation for AI agent memory files requires enforcing schema rules for memory identifiers, types, dates, tags, and sizes. This ensures consistent metadata handling and prevents schema drift during memory record creation or updates.

Memory lifecycle management involves applying structured create, read, update, delete, and validate workflows to memory records. This maintains reliable storage by enforcing directory placement rules and preserving immutable metadata.

Schema enforcement prevents metadata errors by verifying memory identifiers, types, and transitions while preserving immutable metadata. This validation ensures memory files maintain required frontmatter fields and consistent directory placement rules.

Updating memory records while preserving immutable metadata requires applying type transitions and reference tracking during the update workflow. This ensures memory file modifications maintain schema consistency without altering protected frontmatter fields.

Directory placement rules and size checks are needed when creating or updating CRUX memory files to ensure reliable memory storage. These validation constraints prevent schema drift and maintain consistent memory record structure.

Memory file validation fails on schema drift because frontmatter fields no longer match enforced rules for identifiers, types, dates, tags, or sizes. Consistent validation workflows catch these mismatches to prevent metadata corruption.