knowie-consolidate

name	knowie-consolidate
description	Human-initiated — consolidate a ripe draft out into the long-term tier (the symmetric OUT to capture's IN)
user-invocable	true
argument-hint	[a draft to consolidate; empty = scan draft/ for ripe ones]

Knowie Consolidate

The human-initiated OUT of the dispatch pipe: take a ripe draft/ topic and consolidate it into the long-term tier — the memory-formation move from working memory (draft) to the long-term store. (capture is the IN — encoding new thinking → draft; consolidate is the OUT — mature draft → concept / principle / experience / roadmap / history. Together with next's retrieval they form the canonical cycle: encode → consolidate → retrieve.)

You run this when you feel a draft is ready — captured ≠ committed, and committing is the human's call. (judge tidies drafts as maintenance; next detects ripe ones while planning; this is the focused, human-driven consolidate.)

Steps

1. Find the ripe. Given a draft (or scan draft/), judge maturity by the recognition chain: a design settled enough → its exit is the vision roadmap (a human commits to building it; not direct consolidation); an insight verified → a concepts/ file / an experience lesson / a derived principle; a problem now answered → it becomes a design or experience. Not ripe → leave it in draft/ (incubate or decay).
2. Plan the dispatch — split, don't relocate (see core: Consolidating is dispatch). Consolidation works by dispatch, not by collapsing into one: one draft usually holds several kinds: recurring concept → concepts/; lesson → experience; decision-transition + rejected options → history/; brainstorming scene, if recall-worthy → episodes/; committed direction → the roadmap. Show the plan first.
3. Human confirms, then write. Writing into the long-term tier (or amending root principles) is the human's irreversible, semantic call — propose; never commit on your own. Moving/retiring files (reversible) is yours.
4. Retire the draft. Once every piece is dispatched, let the draft go — its durable why now lives in the long-term tier; record the transition in history/ if it was a decision. Exception: a design promoted to the roadmap keeps its draft as in-flight rationale until the item is done (judge §4).

Invariants

• Captured ≠ committed — consolidate only what the human confirms is settled.
• Dispatch, not dump — route each piece to where it belongs; don't collapse a multi-perspective draft into one file.
• A design's exit is the roadmap, not a straight build (the human-commit gate).

Output

Show the dispatch plan (what goes where, what retires) first; do draft/ moves directly, but write into the long-term tier or root principles only on confirmation.