pm-restructure

To convert reflection recommendations into structural changes, extract proposed actions from the report and apply them as split, merge, archive, or create operations on PM units, requiring explicit user approval for each change to maintain governance and traceability.

The best way to split or merge PM units without content loss is to validate changes against the current state and update indices automatically while preserving existing content. This ensures structural operations maintain integrity during the governance approval process.

Yes, you can apply structural changes to a project unit registry and defer content edits. The workflow handles structural operations like unit creation or archiving first, then defers content-level modifications to a later update step.

Yes, you need explicit user approval for each PM unit split, merge, or archive operation. This approval-driven governance ensures that structural changes to the project state and unit index are intentional, traceable, and safely applied.

To update the pm-index file when archiving obsolete project management units, apply the approved archive action directly to the current unit registry. The system automatically updates the index and project state files while preserving existing content.

You should not use approval-driven restructuring for content-level edits or minor updates. It is designed specifically for structural operations like splitting, merging, archiving, and creating units, and defers content modifications to standard update processes.