continuous-learning

To document an architectural decision record (ADR), use provided ADR templates to formalize insights and recurring patterns into explicit standards. This captures architectural decisions and builds a reusable knowledge base during post-solution reflections or cross-project reviews.

The three-time rule for pattern promotion requires solving the same problem successfully three times before generalizing a recurring instinct into an explicit standard. This ensures repeated success validates the pattern before formalizing it into your engineering best practices.

Tracking an instinct with a confidence score implements an instinct lifecycle where informal engineering feelings are logged and scored. As evidence accumulates across sessions, high-confidence instincts become eligible for promotion into formal, documented patterns or standards.

Capture recurring patterns for continuous learning when writing an ADR, documenting a discovered anti-pattern after solving complex problems, or during end-of-session archival. Triggers include phrases like 'remember this pattern' or 'this keeps coming up' to preserve reusable solutions.

The best way to preserve reusable solutions at the end of a session is using an end-of-session review protocol to archive discovered patterns and instincts. This updates your knowledge base by formalizing evidence logs and promoting validated instincts into standards.

Yes, continuous learning operates without external dependencies, using internal ADR templates and evidence logs for cross-project reviews. It archives reusable solutions directly within your project structure to build a standalone, reusable knowledge base.