capture-learning

To capture lessons learned from a porting session, route setbacks through a defined decision tree to an appropriate enforcement mechanism like a hook, rule, agent, or memory, preventing future reoccurrence.

The best way to enforce documentation references for future porting cycles is to follow a decision-tree workflow that determines the correct enforcement target and creates explicit references for future reinforcement.

Routing universal learnings to a knowledge base does not require local enforcement, as the decision tree optionally routes universal knowledge globally while handling local enforcement separately for quick prevention.

To route a porting-session setback, the process follows a defined decision tree to identify the correct local enforcement target, such as a hook, rule, agent, or memory, ensuring the failure is actionable.

You should route porting learnings to a global knowledge base when universal knowledge applies across projects and sessions, using the decision tree to separate broad insights from local, project-specific enforcement needs.