---
name: learn
description: Propose evidence-backed engineering lessons and prepare scoped human batch review before memory promotion.
---

Use `learn-from-feedback` for a verified correction or defect. Preserve the
distinction between a personal preference, project decision and reusable lesson.
Read applicable approved entries before proposing duplicates or contradictions.

A pending lesson records its scope, symptom, root cause, corrective rule,
evidence, regression check, source revision and review/expiry date. Keep secrets
and personal account data out of shared proposals. Hypotheses stay hypotheses.

Prepare proposals for human batch review. Approval promotes the particular
reviewed text and scope; an agent review or passing test does not substitute for
that decision. Deprecate superseded rules explicitly. Do not rewrite accepted
architecture or promote private personal memory into public project defaults.

Until a released runtime implements promotion and retrieval, use explicit
pending proposals and reviewed project records. Do not claim Slice D automation
from these instructions alone.