Client pack lands. PDFs indexed in private cloud only.
Final UI
What analysts actually use.
Beyond the method: information architecture, the upload-to-commit journey, and the six screens where human and model hand work back and forth.
Information architecture
Three roles. One gate before legacy.
Analyst extracts and reviews. Lead watches the pipeline. Compliance exports the trail. Every path still stops at human approval before data touches the old database.
Aura home
Live pipeline
Document analysis + copilot
ESG report
Field-level approval
Immutable decision log
Analyst journey
Upload to commit.
RAG pulls Scope 2, factors, citations, confidence.
Sarah opens the page-level source beside the number.
Approve or flag at field level. Named, timestamped.
API overlay writes approved fields. Legacy stays intact.
Julian pulls the log for GDPR and CSRD review.
Screens
Oversight, analysis, report, gate, trail.
Thomas's pipeline
1.4hAvg cycle
12In review
8%AI override
4.8Trust score
MMC-EU-4471Ready for approval
MMC-EU-4488Low confidence, 67%
MMC-EU-4492Extracting
Sarah's analysis + copilot
Scope 2847 tCO₂e/yr
SourceBill_Q3_2024.pdf, p.7
Vs sector14.3% above benchmark
AURA COPILOT
Scope 2 identified from the Q3 utility bill. Citation pinned. Confidence 94%.
Approve field · Flag field
Approval gate and decision log
Every field is its own decision. Julian's log stores who approved, what source was cited, and whether the model was overridden. That is the product Legal would actually defend.
14:22 · Sarah M.Approved Scope 2 · 94%
14:24 · Sarah M.Flagged factor table v3
14:31 · Thomas K.Released case MMC-EU-4471