<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"><channel><title>Torus field notes and engineering briefs</title><description>Notes from Torus, the agentic engineering surface EPC engineers use to draft complete engineering packages: standards revisions, interfaces between scopes, what we are learning.</description><link>https://usetorus.com/</link><item><title>ASME B31.3 vs the line list: where the disagreement starts</title><link>https://usetorus.com/blog/2026-05-19-asme-b31-3-cross-discipline/</link><guid isPermaLink="true">https://usetorus.com/blog/2026-05-19-asme-b31-3-cross-discipline/</guid><description>When ASME B31.3 changes, the line list and piping classes drafted from it must move too. Four checks Torus runs while drafting to keep the package in step.</description><pubDate>Tue, 19 May 2026 00:00:00 GMT</pubDate></item><item><title>Why FEL2 tie-points are where projects bleed</title><link>https://usetorus.com/blog/2026-05-19-tie-point-validation-fel2/</link><guid isPermaLink="true">https://usetorus.com/blog/2026-05-19-tie-point-validation-fel2/</guid><description>A tie-point table looks like a checklist. It is the contract between two scopes. Three FEL2 patterns that cost months, and the checks a drafted package needs.</description><pubDate>Tue, 19 May 2026 00:00:00 GMT</pubDate></item></channel></rss>