Done

Key Ideas

• Completed Work: done means the Gap has reached its intended outcome.
• Evidence Retained: completion should preserve what changed and why it is considered complete.
• Not Forgotten: done work remains part of history, rollups, and future reasoning.

Purpose

Done exists to close the loop on work. Refine should be able to say not only that a Gap existed, but that the actual-to-target difference was resolved with evidence.

Expected Role

Done should preserve final state, logs, quality evidence, merge or review context, and relevant Feature rollups. It should reduce active workflow pressure while keeping the work inspectable.

Done should not erase context. Future agents may need to understand why something was changed, what evidence existed, and whether later work depends on it.

What Happens

When a Gap is done:

• Refine removes it from active workflow consideration.
• The final state, evidence, logs, quality results, review decisions, and merge context remain inspectable.
• Feature rollups, dashboards, and summaries should reflect the completed work.
• Any node claims or active execution tied to the Gap should be closed.
• Future agents should be able to inspect why the work was considered complete.

Future Direction

Future done behavior may support richer completion summaries, release notes, provenance, dependency updates, and post-merge monitoring. The state should remain the clear signal that the Gap's intended outcome has been satisfied.