Subfracture × Assured Environmental

Tunnel Reporting Automation

Phase 1 demo · path forward

Dominic O'Carroll · Warwick Heathwood · Tyronne Curtis
April 2026
Where we are

The conversation so far

17 Apr Initial proposal — full system on one tunnel
20 Apr Dave reframes priority: "automating the reporting process from Airodis to Word doc templates" as highest immediate value
21 Apr Phasing restructured around that priority
Today Phase 1 demo — RIC March 2026, end-to-end
02 / 13
The pivot

One line.

Before

Attack the hard problem first.

Exclusion handling. One tunnel. Skeleton of the full system.

After

Breadth before depth.

All 12 tunnels drafted from exports first. The analytical judgment layer comes second — on a proven foundation.

03 / 13
Phase map

The sequence.

01
Export → template pipeline across all 12 tunnels. Every report drafted from exported data, ready for human review.
2–4 weeks
02
Exclusion handling, confidence intervals, audit log. The analytical judgment layer — on a Phase 1 already running.
4–8 weeks
03
Production hardening + independent operation.
Follow-up conversation

Phase 1 delivers 12 drafted reports before Phase 2 begins. Phase 2 tackles the hard analytical work on a running system — not on a hypothesis.

04 / 13
The demo

RIC March 2026.

One tunnel, end-to-end.

Inputs

  • Airodis .xlsx (the export)
  • CEMS Maintenance .xlsx
  • Microcosm monthly template .docx

Output

  • Fully drafted Word report
  • 12 narrative sections · 24 tables · 23 charts
  • ~2 minutes of machine time
  • Ready for human review
05 / 13
Under the hood
Not how.
What.

The code underneath this pipeline uses a different model for writing programs.

Worth three slides — because it changes who can maintain this over time.

06 / 13
Traditional software

Write every rule.

Every step. Every if-statement.

Rule 1 — if data exceeds limit and maintenance was active, exclude from average
Rule 2 — if the operator flagged the reading, flag for review
Rule 3 — if the sensor was calibrated within 7 days, include but annotate
… hundreds of rules. Each one a potential break point.

When the input changes — new export format, new tunnel, new regulatory tweak — rules break. Someone writes new rules.

Prescriptive. Brittle.

07 / 13
DSPy approach

Declare the what.

I declare what I want.
I provide examples of what good looks like.
The system learns the how.

signature:
  input:   sampling data digest
  output:  sampling methodology narrative
           — in the Assured voice

examples: [ your 12 months of historical reports ]

Declarative. Self-improving.

08 / 13
Example

One section.

Sampling methodology paragraph — one of twelve narrative sections in the report.

What I declared

  • Input — the monthly sampling data digest
  • Output — a narrative paragraph, Assured voice, matching template structure

What I did not write

  • No procedure
  • No template strings
  • No if-statements

What teaches the system

Your historical reports. As the team reviews and edits drafts, the system keeps refining what good means for Assured — specifically — not some generic engineering register.

09 / 13
Why this matters for Assured

What follows.

Ownership is real

The codebase is yours from day one. Documented, auditable, handed over — not a black box.

Phase 3 is credible

Independent operation when it's time — built on a declarative foundation that any Python developer can maintain with the materials we hand over.

10 / 13
Honest gaps

Transparency before surprise.

Called out on the last page of the demo draft:

  1. Maintenance & Calibration table flat — only RRY1 shape confirmed
  2. NMHC vs VOC label on RRY1 — standardisation call is yours
  3. Valid Data Exception Tables not rendered — explicitly Phase 2 scope
  4. Narrative phrasing first-iteration — Phase 2 optimises against your historical corpus
  5. Two boilerplate Airodis chart pages without RP attribution — suppressed for now

None of these block Phase 1 build-out across the remaining 11 tunnels.

11 / 13
Decision point

Two paths.

Your call.

Quality holds up greenlight Phase 1 build-out across the remaining 11 tunnels.

Gaps to close tell us what's missing. We iterate.

12 / 13
Ready when you are

Phase 1 SOW awaiting sign-off.

Lead
Dominic O'Carroll
Strategy
Warwick Heathwood
Operations
Tyronne Curtis

Subfracture × Assured Environmental