Q3 Close: Where SyngaPure Got To, What Moves Next, and What Is Still Open

An update on SyngaPure, in three parts: where we got to, what moves next, and what is still open. The third part is the one that matters most.

Where we got to in Q3

Component prototyping started on the catalytic tar reforming stage, exactly as planned in the mid-year update. That is the whole achievement, and it is worth stating plainly: the plan said prototyping would begin this quarter, and prototyping began.

Bench work is now generating the two data sets that have to exist before anything scales — durability and conversion. Neither is interesting on its own. Together they determine whether a catalyst is a candidate or a dead end, and no amount of system architecture compensates for the wrong answer.

Research partnerships on catalyst and sorbent materials moved from conversation to defined work packages. That transition is less visible than a hardware milestone and matters more. A conversation produces enthusiasm. A work package produces a deliverable, an owner and a date.

What moves next in Q4

Two things.

The sorptive pollutant binding stage joins the bench programme. Sulfur, chlorine and ammonia removal moves from material selection into measured performance on real conditions.

The control loop starts running against real sensor data rather than simulated inputs. This is the step we are most interested in. A control model behaves very differently once the noise is real. Simulated inputs are clean, stationary and forgiving. Plant sensor data is none of those things. The model that was validated in simulation has to prove it still holds when the signal is irregular and the disturbances have no script.

What is still open

Two honest question marks.

Catalyst durability under genuinely variable feedstock. Bench conditions are stable by construction. Real feedstock is not. Waste-derived syngas shifts in composition, moisture and contaminant load, and a catalyst that holds for a thousand hours under fixed conditions may not hold for half that under variable ones. Lab conditions flatter every system, including ours. We would rather name that now than discover it at commissioning.

Model size against decision latency in the local control layer. The control layer runs on site, not in the cloud, and that constraint is deliberate. It also means every increase in model capability costs response time. A smarter model that answers too slowly is worse than a simpler one that answers in time. Getting that trade-off right is an engineering problem, not a marketing one, and it is not finished.

Why we report this way

None of this is dramatic. Deep tech rarely is.

It is a sequence of small validations that either hold or do not, and the discipline is in reporting both — the ones that held and the ones still in question. Progress reported only in wins is not progress reporting. It is a forecast with the uncertainty removed, which is exactly the thing that gets plants burned later.

SyngaPure's development is backed by the BMWK go-inno programme, with research partnerships active on catalyst and sorbent work.

Next update at the close of Q4.

Over to you

What are you carrying into Q4 that you had hoped to close in Q3?

www.zero-x.co