learnings-write

To document architectural decisions into project memory, use a structured curation process that validates schemas, filters PII, and deduplicates entries before appending to local memory files for searchable team access.

Filtering PII when saving project learnings requires a dedicated curator agent that performs deduplication and PII filtering before appending validated data to memory stores, ensuring compliant knowledge management.

A curator agent deduplicates knowledge management entries by spawning a dedicated process that validates incoming learnings against project schemas and existing memory files before appending, preventing fragmented records and maintaining a clean architectural decision store.

Yes, you can write learnings to a user-global memory layer to store cross-project patterns. This operates alongside project-specific memory, allowing the curator agent to validate and persist broader architectural insights for cross-project knowledge management.

Schema validation is required to record lessons learned. The memory-curator agent enforces schema compliance and memory-discipline rules to ensure structured, validated, and deduplicated data persistence across project-specific and global memory layers.

Automated curation for knowledge capture should be avoided when entries cannot adhere to memory-discipline rules or schema validation. The curator agent strictly enforces PII filtering and deduplication, which may reject non-compliant architectural decision inputs.