Alt3r3dP3rc3ption/email-project-memory ? reverse-engineered prompt

Build me a simple workflow for turning exported Microsoft 365 project emails into a durable project memory.

I want each project to have one main correspondence register where every email gets turned into a short summary, any decision, any action item, who owns it, and when it is due. The raw email export should be treated like evidence, not something the assistant keeps rereading. The assistant should first propose updates in a reviewable file, then wait for approval before adding anything to the register and regenerating the project memory files like open items, daily log, and project context.

Please include a clean starter template for a new project, plus a working example so I can see the expected flow. I also want a way to ask what is due today, what is overdue, and who is waiting on what, with clear references back to the register. If anything is unclear, flag it and ask me instead of guessing. If you need to, look up current docs online for Microsoft 365 export formats.