persistlisted

## Intent Execute **persist** to write stable learnings, decisions, and patterns to durable storage for future recall and consistency. **Success criteria:** - Content is written to the correct destination - Existing content is preserved or properly merged - New content follows established structure/format - Metadata (timestamp, source) is recorded - Write is verified successfully **Compatible schemas:** - `schemas/output_schema.yaml` ## Inputs | Parameter | Required | Type | Description | |-----------|----------|------|-------------| | `content` | Yes | string\|object | What to persist: decision, pattern, fact, or structured knowledge | | `destination` | No | string | Where to write: `CLAUDE.md`, file path, or `auto` (determine best location). Default: `CLAUDE.md` | | `section` | No | string | Section within destination to write to (e.g., "Decisions", "Patterns", "Facts") | | `content_type` | No | enum | Type of content: `decision`, `pattern`, `fact`, `context`. Default: auto-detect | | `merge_strategy` | No | enum | How to handle existing content: `append`, `replace`, `merge`. Default: `append` | ## Procedure 1) **Validate content**: Ensure content is appropriate for persistence - Check content is non-empty and meaningful - Verify content type classification - Ensure no sensitive data (credentials, PII) is being persisted - Validate content structure if object 2) **Determine destination**: Select where to write - `CLAUDE.md`: Project-level decisions an