GRI Engine · Native results and factor library wireframes (spec iii)

What this wireframe set covers

The computed-results experience for a GRI reporting cycle, end to end. The first three pages show the results a cycle produces: the dashboard with the headline figures, the computed figures table where every number opens into its full traceability, and the results that need attention worklist for figures that are refused, out of date, or not entered. The next five pages show what the calculation is set up from and fed with: the methodology lock that fixes the factor edition, the activity data entries, the contract instruments behind the market-based figure, the revenue denominator and intensity setup, and the compute runs themselves. The last three pages leave tenant navigation entirely: they are the Evercomm-internal factor library screens where operators manage sources, import and validate editions, and browse the factor rows.

Companion sets, already reviewed and closed: GRI Reporting Cycles admin wireframes (spec i) and GRI Catalog Admin wireframes (spec ii). Every tenant page here reuses their page chrome and annotation conventions.

How to read these pages

Anything drawn in plain product styling is proposed UI. Anything amber-tinted with a dashed border is review scaffolding and would never ship:

The tenant is Bluefin Foods Group, a fictional SG-headquartered food producer. Every organization, person, figure, date, and identifier is invented, and all eleven wireframe pages draw the same invented world: one active cycle, one completed compute run, one factor edition. The people are Mei Tan (Sustainability Admin), Priya Nair (Sustainability Admin), and Daniel Ong (Site Manager, the data-entry role). No real client, company, or colleague appears anywhere in this wireframe set.

GRI standard and disclosure numbers are identifiers and are drawn as they really are (GRI 305-1, 302-3). Every title and description is composed in our own words, and any guidance-like text is a labelled placeholder. Do not review the wording of composed text as copy; review the surfaces.

Pages

Twelve pages: this index, then the eleven wireframes below. Prev and next links in the dark bar walk them in order.

1. The cycle's results
2. 01
   The cycle dashboard

   The headline figures, the previous cycle comparison, the per-unit breakdown, and the evidence position of the active cycle at a glance.
3. 02
   Computed figures table

   Every computed figure with separate own and consolidated values, and one row opened to show the full lineage behind a number.
4. 03
   Results that need attention

   The triage worklist: the figures that are refused, out of date, or not entered, why each one is, and the concrete action that clears it.
5. Setting up and feeding the calculation
6. 04
   Methodology lock

   The lock card that fixes the factor edition, warming potentials, boundary approach, energy convention, and calculation rules a cycle computes with.
7. 05
   Activity data

   The activity entries feeding the calculation, including the entries still waiting on evidence or a stated basis.
8. 06
   Instruments and the market-based figure

   Contract instruments such as RECs and PPAs, their server-derived match chips, and the entered market-based Scope 2 figure they back.
9. 07
   Denominators and intensity setup

   The cycle-level revenue fact and the intensity configuration that divides emissions and energy by it.
10. 08
    Compute runs

    The explicit compute trigger, the run states in plain words, and what a failed or timed out run looks like.
11. Internal factor library (Evercomm operators)
12. 09
    Factor sources and subscription

    Internal: the factor sources behind an edition and the subscription reference that licenses one of them.
13. 10
    Factor editions: import, validation, publish

    Internal: importing source files, the validation findings on a staging edition, and publishing an edition.
14. 11
    Factor browser

    Internal: the factor rows, GWP sets, and FX rates inside a published edition.

Decided vocabulary

What this wireframe set is drawn against

• Source of record. Build spec iii, v5: the native computation engine, its results contract, and the factor library. Every drawn figure, refusal, stamp, and state traces to a numbered section, and the citation sits in the annotation next to it.
• The Panel 3 navigation decision, updated in round 2. The sidebar on every tenant page draws the accepted Panel 3 tree, with all tenant pages of this wireframe set living under Reporting Cycles. Round 2 folds in the decided cycle submenu (W2-1): Reporting Cycles carries an always-visible sub-group (Cycle dashboard, Results, Methodology lock, Activity data, Instruments, Denominators, Compute runs) with the current cycle named at its top and a Switch link, and each page carries a breadcrumb line above its title. The sidebar is settled input here, not a proposal. The one navigation proposal in this wireframe set is on the internal pages: the Factor Library item under an internal operations group, following the Companies pattern for operator-only surfaces.
• The FY2025 Bluefin fact sheet. One invented world across all pages: the active cycle "FY2025 GRI report" (Jan 2025 to Dec 2025), its methodology lock completed 20 Feb 2026 by Mei Tan against factor edition 2026.1, and its latest compute run 000318 finished 4 Mar 2026 at 10:12. Every page shows the same numbers for the same figures, so cross-page consistency itself can be reviewed.

Open items for your review

• The dashboard's per-org table density. Page 01 draws the per-unit breakdown as a compact four-row table under the headline cards. With more organization nodes it could need grouping or a collapsed default. Say whether the drawn density is acceptable as the pattern.
• The internal operator nav placement proposal. Pages 09 to 11 place Factor Library under a single internal operations group, following the Companies pattern. The placement is a proposal you can move; the operator-only access rule behind it is not.
• Help entries. Help entries for these pages are authored at build time under the guidance spec's classification rules.