context-cleanup-steward

To reconcile documentation drift, align Notion ticket metadata with current runtime code, repo docs, and route reality. You apply a cleanup workflow after deployment validation or closing ticket batches to update indexes and resolve conflicting references.

Archive drifted repository documents before deleting them to preserve the source of truth. Run this consolidation process when the workspace accumulates duplicate or conflicting documents, ensuring Notion tickets and Drive context remain accurate without losing history.

The best way to clean up stale Drive context and UI references is to run a post-deployment validation cleanup. This aligns Stitch references used by UI work with runtime routes and updates Drive context indexes to eliminate stale context.

Yes, the documentation cleanup process preserves source-of-truth ownership. When drift cannot be fully resolved, it archives the conflicting documents before deletion and updates Notion tickets and Drive indexes to reflect the current validated state.

To update Notion ticket metadata, run a cleanup steward workflow after closing a batch of tickets. This reduces drift by comparing ticket details against runtime code and route reality, then updating the metadata and Drive context accordingly.

Documentation drift occurs because code, Notion metadata, and Drive context evolve independently during development. Applying a consolidation workflow after deployment validation detects and remediates this drift by aligning all references to the current route reality.