open source
Chemical Engineering Work Gets a Versioned Agent Substrate
ChemE-as-Code links calculations, files and provenance while making automated checks admit the faults they cannot see.
Summary
ChemE-as-Code links calculations, files and provenance while making automated checks admit the faults they cannot see.
The open-source environment connects tools for catalysis, process simulation, layout, HAZOP and life-cycle assessment to versioned, machine-readable engineering files. Calculations run outside the language model, and each value records its origin. In an illustrative ammonia case, agents assembled a preliminary engineering package for a reported $224 in API cost; planted changes showed the checks caught only what their rules covered. No independent engineer reviewed the design, so the work presents an auditable substrate—not a certified plant.
Why it matters
ChemE-as-Code links calculations, files and provenance while making automated checks admit the faults they cannot see.
Limits and context
- In an illustrative ammonia case, agents assembled a preliminary engineering package for a reported $224 in API cost; planted changes showed the checks caught only what their rules covered.
- No independent engineer reviewed the design, so the work presents an auditable substrate—not a certified plant.
Key claims
ChemE-as-Code links calculations, files and provenance while making automated checks admit the faults they cannot see.
Qualification: In an illustrative ammonia case, agents assembled a preliminary engineering package for a reported $224 in API cost; planted changes showed the checks caught only what their rules covered.
Evidence: source-2026-11-07-010
Sources
- arXiv preprint 2611.07947, original v1arXiv · primary research
Corrections
: Publication note: This November 7 edition was assembled before its scheduled 9:00 AM America/Detroit reveal but is being published late after recovery from a local build interruption. Its original reporting, image-generation times and scheduled publishAt are preserved.