edi-self-improve

You can extract tacit knowledge from an editing session by analyzing implicit editorial decisions and converting them into explicit, reusable rules. This process identifies why decisions were made and validates them for stability across future sessions.

Turning implicit editorial decisions into reusable rules requires capturing the hidden reasoning behind them during a session. New rules are written in imperative form and validated for applicability across future work.

Routing new editorial rules to knowledge layers like EDITORIAL.md or STYLE.md involves assigning extracted candidates to the appropriate file based on their function. This prevents duplicating documented rules and ensures proper memory routing.

Yes, you can analyze a current session to identify why editorial decisions were made. By providing the session for analysis, the system extracts tacit knowledge and applies it across the current project to preserve reasoning for future auditing.

To avoid duplicating documented rules when extracting session knowledge, the process checks existing entries across EDITORIAL.md, LEXICON.jsonl, STYLE.md, and blueprints. It ensures new imperative rules are distinct and reflected in memory.