update-docs

To close documentation drift, you need to reconcile actual session outcomes with original plans and update affected artifacts in place. This process reconstructs completed actions, identifies stale documents, and appends precise as-built notes to preserve original intent.

Updating stale plans after a work session involves reconstructing actual work from discussion and artifacts, then updating the work ledger with precise as-built notes. This ensures plans, architecture, and implementation docs accurately reflect reality.

Generating an as-built record requires running a session wrap-up that reconciles planned work with actual outcomes. It guides you through rebuilding the narrative, closing work ledger gaps, and appending notes while preserving original intent.

Yes, you can update architecture and code documentation at the end of any session by reconciling actual outcomes with original plans. This ensures all affected artifacts reflect reality and closes gaps across implementation and documentation.

Work ledger gaps occur when actual implementation diverges from original plans without updating documentation. Reconciling session outcomes and appending precise as-built notes closes these gaps while preserving original intent.

You need to reconcile planned work with actual outcomes at the end of any work session. This ensures documentation stays aligned with implementation by identifying stale artifacts and updating plans, decisions, and as-built notes.