memory_lesson
Capture structured lessons, incidents, or decisions in one call. Fills the matching section template from your field values and stores it with deduplication.
Instructions
Capture a structured lesson or incident in one call: fills the matching section template (incident → Symptom/Root Cause/Fix/Prevention; lesson → What/Why it matters/How to apply) from your field values and stores it through the normal write path (deduped — a repeat capture is a NOOP). Unknown document_types use a generic scaffold.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| document_type | No | Section template to fill: lesson | incident | decision | bug-fix | meeting | session. Unknown types use a generic Summary/Details/Notes scaffold. | lesson |
| fields | Yes | Section values keyed by section name (snake_case ok), e.g. {symptom, root_cause, fix, prevention} for an incident or {what, why_it_matters, how_to_apply} for a lesson. Omitted sections keep a placeholder. | |
| title | No | Optional title (auto-derived from the first field value when omitted) | |
| scope | No | Memory scope for isolation | global |
| namespace | No | Namespace within scope (e.g., project name, team name) | |
| department | No | Department (e.g., legal, engineering, hr, sales, finance) | |
| tags | No | Tags for categorization | |
| source | No | Origin of the content (e.g., file path, URL, system name) | |
| access_level | No | Access classification level | internal |
| importance_score | No | Manual importance 0–1 (higher surfaces first in reflection/recall) |