autolearn

# Autolearn ## Contract | Field | Bound contract | |---|---| | Trigger | A non-trivial fix has been verified (observed working, not hoped working), or explicit autolearn or refresh invocation. | | Authority | Reversible local: writes only the operating repo's docs/solutions/ and repo-root CONCEPTS.md; rollback is version control. No remote mutation. | | Side effect | Writes or refreshes docs/solutions/ learning docs and CONCEPTS.md; stages only the surfaces this skill wrote or edited. | | Done | A validated learning or concept entry exists, or an explicit determination that nothing qualifies. | ## Inputs - The verified fix or solved problem, from conversation history or codebase. Must be supplied or derivable from context. - Optional: `mode:refresh [scope]` to maintain existing docs; `mode:headless` for non-interactive operation. - Optional: an injected auto-memory block (supplementary context, not primary evidence). ## Procedure ### 0. Route the mode Strip `mode:` tokens from arguments before treating the remainder as context or scope. - **Capture** (default): document one solved problem into docs/solutions/. - Vocabulary capture: a durable, reusable project term surfaces; reconcile CONCEPTS.md. - Memory handoff: a fact about the user, preferences, or cross-project context surfaces; do not write it into docs/solutions/ or CONCEPTS.md; surface it as a memory-handoff candidate for the memory system to capture. - Refresh: maintain existing docs/solutions/ and CONCEPTS.m...