refactor

To detect configuration drift, compare your live ops/config.yaml against the ops/derivation.md baseline. This identifies every changed dimension and feature flag across the 8 structural dimensions, highlighting exactly where your vault has diverged from the design baseline.

Plan a vault restructuring by running a staged workflow that maps detected dimension changes to affected artifacts. This generates a phase-based restructuring plan with an integrated risk assessment and a validated rollback path to ensure safe execution.

Config drift detection is the process of identifying structural divergences across granularity, organization, linking, processing, navigation, maintenance, schema, and automation dimensions. It compares your live configuration against the design baseline to list all feature and structural changes.

No, executing vault restructuring requires explicit approval. The workflow follows a strict sequence: detect, plan, present, approve, execute, and validate, ensuring all restructuring changes are reviewed before they are applied to your artifacts.

You need the live configuration file in ops/config.yaml and the design baseline in ops/derivation.md. These two files provide the necessary inputs to compare dimensions, assess risks, and output a precise restructuring plan with rollback guidance.

You should avoid automated restructuring when configuration drift involves high-risk dimension changes that lack a validated rollback path. The workflow requires explicit approval and traceability to ensure unsafe structural modifications are not executed without proper risk assessment.