The announcement of Pega GenAI Blueprint™ to modernize legacy systems based on screenshots, documentation, videos sounds very promising. As these source artifacts can be difficult to keep current / detailed, I was interested in discussing the application of Blueprint to specifically modernize legacy Pega applications. 

Long-running Pega apps are challenging to maintain / refactor  / analyze to take advantage of modern capabilities likes Stage-based case management, Constellation, AI, security etc.  Since the application code is the best source of truth, is it valid to assume that Blueprint would/could be a key component of future Pega upgrades? 

Some potential areas of coverage:

- recommend refactoring suggestions (effort / risk / impacts): data structures, APIs, process flows, UX, accessibility, DevSecOps, automation, migrations / transformations of legacy data

- understanding in-use and potential use of framework applications to minimize / remove / reduce customizations

- understand PDC data to optimize hardware / infrastructure  

- auto-generate enhanced user documentation / training guides / automated testing etc

- options / suggestions to create a brand new application versus refactoring existing

- Utilize Pega GenAI Blueprint™ as a platform plugin / capability in existing apps?

Modernizing Pega apps is an increasingly complex task, so the use of Pega GenAI Blueprint™ would be of great benefit.

Thanks!