PhysicsNET · Physics validation gate | ENGINPILOT
PLATFORM / 05 — PHYSICSNET

Physics validation as a gate, not a score.

PhysicsNET evaluates every proposed action against the asset's constraint set before an engineer ever sees it. An action that breaches a conservation law, a material limit or a certified envelope is not ranked lower. It is blocked, and the reason is recorded.

STATUS DESIGN PARTNER · GATE DEMONSTRABLE · CONSTRAINT LIBRARY IN DEVELOPMENT
EVALUATION POINT
Before display, not after
CONSTRAINT CLASSES
Five, all versioned
OUTCOME
Binary — pass or block
BLOCKED ACTIONS
Recorded, never hidden
01 — THE GATE

Every candidate passes through the same evaluation

Model output enters as a set of candidates, each with a confidence value. The gate is deterministic: it does not weigh confidence, and a high-confidence action carries no privilege. Only candidates that satisfy every applicable constraint reach a named engineer.

02 — CONSTRAINT CLASSES

Five classes, each with a named source of authority

A constraint is only admissible if it can be traced to a document, a standard or a measured design basis. Constraints authored from opinion are not accepted into the set.

CLASS
EXAMPLE CONSTRAINT
SOURCE OF AUTHORITY
OVERRIDE
Conservation
Mass and energy balance across the control volume must close within measurement error
First principles
NEVER
Material
Bearing metal temperature must remain below 95 °C continuous
OEM datasheet · Rev C
NEVER
Certified envelope
Discharge pressure must not exceed 13.5 bar at rated speed
Commissioning certificate
NEVER
Regulatory
Pressure-vessel inspection interval may not extend beyond the statutory period
Jurisdictional standard
NEVER
Asset derating
Unit runs at 92% of nameplate following the 2024 impeller repair
Engineering change record
WITH APPROVAL
03 — WHAT A BLOCK LOOKS LIKE

A blocked action is an engineering record

The engineer is not told that nothing was found. They are told what was proposed, which constraint rejected it, by how much, and against which revision of the constraint set. That record is arguable — if the constraint is wrong, it can be challenged and changed through governance.

Nothing is silently discarded. Every block is retained for audit and appears in the asset's decision history alongside the actions that passed.

Discharge pressure 14.2 bar exceeds the 13.5 bar limit for CH-02. Recommendation blocked and recorded.
BLOCK RECORD PN-BLK-4471
ASSET
CH-02 · Centrifugal chiller
PROPOSED BY
◆ Optimisation agent · 76%
CONSTRAINT
Certified operating envelope
LIMIT
13.5 bar
PREDICTED
14.2 bar
MARGIN
−0.7 bar
SOURCE
Commissioning cert · 2019-04-11
SET REVISION
4.2
DISPOSITION
Blocked · retained for audit
04 — PROVENANCE

Every value declares how it was obtained

A number on a screen is useless without its provenance. PhysicsNET stamps six states, and the state travels with the value into every downstream view, report and export.

Measured and confirmed against the constraint set. The strongest claim the system makes.

Derived deterministically from measured inputs using a documented relation.

Inferred where instrumentation is absent. Carries an uncertainty band, never a bare number.

Produced by a model run rather than observation. Valid for comparison, not for compliance.

Breaches a constraint. Surfaced as an alert and blocked from any recommendation path.

Provenance cannot be established. Displayed as unknown rather than assumed good.

05 — GOVERNANCE

The constraint set is a controlled document

Constraints are authored by engineers, reviewed by a second engineer, and released under a revision number. Nothing enters the set through configuration, and no model can write to it. Every past evaluation remains reproducible against the revision that was in force at the time.

01Authored against a cited source document
02Reviewed and countersigned by a second engineer
03Released as a numbered revision with an effective date
04Superseded revisions retained so past decisions stay reproducible
06 — WHERE IT SITS

Layer five of seven, and mandatory

PhysicsNET cannot be bypassed by an agent, an integration or an API caller. Every path to the engineer runs through it.

RECEIVES FROM
ENGIN Solver — candidate actions Digital twin — current state EIG — asset design basis
EMITS TO
Engineer workspace — validated actions Decision record — blocks with margins Audit log — every evaluation
GUARANTEES
Mandatory — no path to an engineer bypasses it Every verdict recorded, including the blocks No model write access, ever

See the gate run against your own asset constraints.

Technical evaluations start with one asset class and its existing design basis documents. No data migration is required to begin.