The outcome I actually want is easy to say and hard to build: a system that improves with use. Use leads to learning, learning to improvement, improvement back to use. Most systems never close that loop — every project re-learns lessons the last one already paid for.
Expert-in-the-loop is the discipline that closes it. It doesn’t change who designs or what tools they use; it changes whether learning compounds or resets. The whole trick is where the learning goes — not into new files, one-off decks, or forgotten conversations, but into system memory tied to an outcome.
Links from this note
Evidence · the loop, drawn

Use → learning → improvement → use. Expert-in-the-loop is what makes it compound instead of reset.
How it has been tended
Planted from Mind Over Tool.
Centered the note on the learning loop closing instead of 'more AI'.
drift: XiTL needs a concrete example, not just the principle.