MRGI PRESENT / WORKFLOW FIELD GUIDE
Update an executive briefing
Refresh approved figures without erasing the deliberate edits that make a deck useful to its audience.
01 / FROM INPUT TO HANDOFF
Follow the decisions.
This walkthrough describes the intended MRGI product behavior. The browser demo illustrates a small part of the workflow; it does not run the complete application.
- 01
Start from approved material
- Start with
- An Author summary and Grid table.
- Work through
- Select the passages and metrics relevant to the audience.
- Result
- A deck draft with linked source elements.
- 02
Make the story yours
- Start with
- The slide draft.
- Work through
- Edit the headline and mark it as an intentional override.
- Result
- A presentation with a visible local change.
- 03
Compare the refresh
- Start with
- A newer approved dataset and report section.
- Work through
- Review proposed slide changes and resolve each overridden element.
- Result
- An updated deck with explicit choices.
- 04
Approve the delivery
- Start with
- The deck and its source references.
- Work through
- Check the narrative and output before distribution.
- Result
- A reviewed presentation revision.
02 / INPUTS & INTERCHANGE
What travels with the work.
These are foundation formats and intended handoff contracts. Support and fidelity must be confirmed for each released build.
| Artifact | Role | Review consideration |
|---|---|---|
| PPTX | Editable presentation interchange | Animations, fonts, charts, and theme fidelity need acceptance tests. |
| Approved report sections | Author handoff | Retain the version and approval context. |
| Distribution copy | A static export does not retain all interactive presentation behavior. |
A deliberate cross-app boundary
Start from Author sections and Grid figures, then send the reviewed presentation to an Evidence distribution packet.
The intended handoff should identify the selected resource, its version, the destination, and the user’s authorization. A linked application should not inherit unrestricted file access.
Explore the connected applications ↗03 / BOUNDARIES & READINESS
Know what this example establishes.
- No live PowerPoint parsing or rendering in this demo.
- An override is an editing decision, not a guarantee that the content remains current.
- Slide synchronization and export fidelity remain planned engineering work.
Development status
The source foundation is imported. Present is the next intended integration target after the initial evidence workflow; the pictured interface is a concept.
Before a production release
Validate real-file behavior and platform support, implement the stated authorization and review rules, and document the tested acceptance scope. The interactive website is a product demonstration, not a release candidate for the application.
04 / PRODUCT QUESTIONS
The details that matter.
Can only some objects be linked?
That is the intended model: selected objects can be source-bound while the rest of the slide remains manually authored.
What if I keep an outdated override?
The proposed review should retain its source context and warn that the connected source changed. The presenter decides whether the override is still valid.
Open-source foundation
Slides, charts, animation, PPTX/PDF, and a command registry exist in DeckCraft. Controlled source synchronization is the proposed MRGI addition. Read the credits and foundation mapping.
Keep exploring Present.
Return to the product breakdown or try the local interactive example.