MRGI AUTHOR / WORKFLOW FIELD GUIDE
Refresh a recurring research report
Update selected figures while keeping the report’s claims and approvals aligned with the evidence.
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
Draft around a snapshot
- Start with
- An approved Grid table and a report outline.
- Work through
- Insert the table with its source identity and explain the result in prose.
- Result
- A draft with explicit data references.
- 02
Attach the evidence
- Start with
- A supporting brief and selected observations.
- Work through
- Link the relevant passages and record enough context for a reviewer to locate them.
- Result
- A navigable claim-to-source trail.
- 03
Review an update
- Start with
- A newer approved table version.
- Work through
- Compare the values, accept or defer the update, and reconsider affected prose.
- Result
- A new report revision with visible source changes.
- 04
Release a section
- Start with
- A reviewed report revision.
- Work through
- Select the material that Present and Evidence may reuse.
- Result
- Approved sections with source and revision references.
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 |
|---|---|---|
| DOCX | Editable document interchange | Pagination, fields, charts, and embedded content require fidelity tests. |
| Approved tables | Grid handoff | Stable identifiers and units must survive insertion. |
| Report section references | Presentation and packet reuse | Downstream work needs the approved version, not merely the latest text. |
A deliberate cross-app boundary
Bring Grid snapshots and Evidence sources into the report, then share approved sections with Present.
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.
- Citations do not establish that generated or human-written statements are true.
- Source synchronization and approval invalidation are proposed product behavior.
- Document layout fidelity remains a validation task.
Development status
The source foundation is imported. A shared prototype can generate a report; the living editor, synchronization, and approval interface are planned.
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.
Does a source refresh rewrite my prose?
The intended workflow updates selected linked material after review. It should flag affected interpretation rather than silently rewrite the author’s argument.
Can a report remain local?
Local-first editing is the design direction. Optional remote assistance would need explicit provider and resource choices.
Open-source foundation
Rich document models, bibliography, revisions, comments, and DOCX reading/writing exist in WordCraft. MRGI is proposing an evidence-bound report workflow around those foundations. Read the credits and foundation mapping.
Keep exploring Author.
Return to the product breakdown or try the local interactive example.