refactor

Detect configuration drift by comparing ops/config.yaml against ops/derivation.md to reveal dimension changes and feature flag differences. This comparison identifies mismatches between your expected and actual vault setup.

Assess impacted artifacts across notes, templates, context, MOC structure, and hooks during vault restructuring. Generate a detailed, risk-scored plan with content impact and timelines to ensure structural integrity.

Execute vault refactors safely by enforcing hard blocks, soft warnings, and cascade checks. This produces a validation-backed execution plan with rollback guidance to prevent data loss during structural changes.

No manual validation is required post-generation. The system produces a validation-backed execution plan that automatically assesses content impact and timelines while enforcing safety through hard blocks and cascade checks.

Yes, assess feature flag differences before execution. The drift detection phase identifies these differences early, generating a risk-scored plan that evaluates content impact and timelines prior to any structural changes.

Use an automated refactor plan when configuration drift impacts multiple artifacts like notes, templates, and MOC structure. It provides necessary cascade checks and rollback guidance that manual restructuring lacks.