A P&ID PDF becomes an evidence-bearing engineering graph.

Recognition is only the first boundary. The product preserves where each observation came from while recovering identity, direction, conditional state and topology.

Concept illustration of a detailed P&ID sheet being traced into physical directed gas-path evidence
Concept illustration — no customer drawing is shown; public product proof requires a fresh approved fixture and its evidence package.

01 / OBSERVATION CONTRACT

OCR can copy marks. Engineering understanding must preserve meaning.

A symbol name without location, a line without direction or a connection without operating condition is not enough to drive physical design. MST records observations before it permits inference.

SOURCEPage + regionEvery accepted object points back to the PDF evidence that produced it.
IDENTITYTag + typeCandidate identity stays separate from approved engineering identity.
STATEDirection + conditionArrows, branches, bypasses and operating states remain explicit.
UNCERTAINTYReview or refuseUnsupported certainty becomes a visible engineering decision.

Source-grounded semantics

A graph node is not trustworthy until it can point home.

The typed graph retains the source pointer and the reasoning boundary used to create each node and edge.

PDF SOURCEpage_014 / region_07HASH BOUND
OBSERVATIONsymbol · tag · lineworkLOCATED
SEMANTICStyped object · port · stateQUALIFIED
TOPOLOGYdirected edge · branch · continuationCONNECTED
GATEaccept / review / fail closedEXPLICIT

02 / DIRECTED & CONDITIONAL GRAPH

Connectivity alone is not process intent.

The graph preserves flow direction, equipment and instrument roles, branching, bypass logic, cross-page continuation and declared operating conditions. It does not flatten the drawing into an undirected network.

Node contractIdentity, type, ports, state, source pointer and qualification status.
Edge contractFrom/to port, direction, connection class, condition and source linework.
Continuation contractCross-page references stay unresolved until both endpoints can be evidenced.
Ambiguity contractCompeting identities or connections are ranked for review, never silently promoted.

03 / CURRENT BOUNDARY

What this page proves—and what it does not claim.

In scopeApproved semiconductor process-equipment P&ID fixtures, typed symbol vocabularies and project-reviewed rules.
Not claimedUniversal recognition of arbitrary drawing conventions without qualification.
OutputEvidence-bearing observations plus directed and conditional engineering topology.
Human authorityEngineers approve vocabulary, unresolved ambiguity and release boundaries.
NEXT CONTRACT

Turn process intent into a physical XYZ realization.

Open 3D Physical Layout