gpd-revise-phase

To revise a completed research phase without losing data, you can supersede the original phase. The system preserves the completed phase as a historical record while creating a replacement phase that inherits valid decisions and addresses required changes.

The best way to update downstream dependencies after phase revision is to use an automated workflow tool. It identifies all downstream dependencies affected by the revision and updates them automatically to reflect the changes made.

Iterative phase revision works by superseding a completed phase and generating a replacement phase. This mechanism ensures historical context is preserved, valid decisions are inherited, and downstream dependencies are updated for continuous research improvement.

Yes, you can replace a specific research phase if you find a data integrity error. By providing the phase number and the reason for revision, the system creates a replacement phase while preserving the original phase as a historical record.

To supersede a research phase, you need to provide the project context, the specific phase number, and the reason for revision. The system also requires access to phase-specific files to accurately inherit valid decisions and update downstream dependencies.

You should avoid using automated phase revision if your project lacks established downstream dependencies or phase-specific files. Without proper project context and dependency tracking, the tool cannot accurately analyze the downstream impact or inherit valid prior decisions.