MRGI GRID / WORKFLOW FIELD GUIDE
Publish quarterly operating figures
Give report and presentation authors a reviewed version of the figures while analysis continues.
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
Choose the input
- Start with
- A synthetic hours-by-team CSV.
- Work through
- Record the source version and select the columns needed for the calculation.
- Result
- A scoped input table.
- 02
Explain the calculation
- Start with
- Hours for three fictional teams.
- Work through
- Inspect the summation and compare the result with the source rows.
- Result
- A result with visible calculation context.
- 03
Publish a snapshot
- Start with
- A reviewed table and formula set.
- Work through
- Freeze the selected values into a named version; record the review decision.
- Result
- A stable snapshot for downstream work.
- 04
Handle the next revision
- Start with
- A changed working table.
- Work through
- Compare the proposed new snapshot and allow consumers to choose when to update.
- Result
- A new version without silently rewriting the previous one.
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 |
|---|---|---|
| CSV | Simple tabular input | CSV carries no formulas or type schema by itself. |
| XLSX | Workbook interchange | Macros, external links, styles, and formula compatibility need separate acceptance tests. |
| Snapshot JSON | Approved table handoff | The schema, units, and calculation version must accompany the values. |
A deliberate cross-app boundary
Send approved tables to Author, chart data to Present, or a reviewed dataset to Layout.
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.
- External APIs and credentials are not connected by this site.
- A preserved snapshot is not proof that the formulas are correct.
- Large workbooks and native/browser parity need target-specific testing.
Development status
The source foundation is imported. Full calculation lineage, external connectors, and the redesigned Grid 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.
What happens when the source changes?
The proposed workflow creates a candidate snapshot and a comparison. Consumers remain bound to the prior approved version until they accept the update.
Is approval a formula audit?
No. Approval records a decision. The team still needs to review units, assumptions, formula behavior, and source quality.
Open-source foundation
Workbook models, formulas, calculation, CSV/XLSX, charts, and automation exist in GridCraft. Governed snapshot publishing is the proposed MRGI focus. Read the credits and foundation mapping.
Keep exploring Grid.
Return to the product breakdown or try the local interactive example.