FIELD NOTE / INSTAGRAM
The PLC oracle measures behavior, not intent.
The complete written thought and the evidence behind it. The video edition will follow its public release.
The written argument is here.
This approved Instagram edition is on the journal now. Its video player and original platform link will appear after each public release is verified.
The PLC oracle measures behavior, not intent.
Video caption
The PLC oracle measures behavior, not intent.
Valid signal shape is not valid current state.
Each input fault needs a physical expected result.
Only controlled site observation closes it.
#EricFieldNotes
Full written post / accessibility read
An AI-generated test can say the jam branch fired. The machine requirement may say the conveyor must reach an approved stopped state within a defined window. Between those claims sit input freshness, scan timing, output mapping, drive response and physical feedback.
In this fictional conveyor, the jam bit remains high after a communications delay. A unit test passes because the PLC sees high. The acceptance question is whether the controller recognized stale data, moved to the owner-approved state and prevented an unapproved restart.
For fresh-high, stale-high, contradictory feedback and restart, record the required command, observed motion proxy, deadline and alarm. Run the cases in an offline model and on an authorized isolated controller bench. Keep mismatches rather than averaging them away.
Use simulation and bench evidence to reduce commissioning risk. Let qualified site owners authorize the change window and read back installed behavior. Do this because test coverage is valuable only when the oracle matches the effect being promised.
#EricFieldNotes
Four-beat scene transcript
1. The PLC oracle measures behavior, not intent.
An AI-generated test can say the jam branch fired. The machine requirement may say the conveyor must reach an approved stopped state within a defined window. Between those claims sit input freshness, scan timing, output mapping, drive response and physical feedback.
Visual: A controller command is only one link in the chain.
2. A stale sensor can make the trace lie.
In this fictional conveyor, the jam bit remains high after a communications delay. A unit test passes because the PLC sees high. The acceptance question is whether the controller recognized stale data, moved to the owner-approved state and prevented an unapproved restart.
Visual: Valid signal shape is not valid current state.
3. Build a fault-to-observation matrix.
For fresh-high, stale-high, contradictory feedback and restart, record the required command, observed motion proxy, deadline and alarm. Run the cases in an offline model and on an authorized isolated controller bench. Keep mismatches rather than averaging them away.
Visual: Each input fault needs a physical expected result.
4. Accept the physical claim last.
Use simulation and bench evidence to reduce commissioning risk. Let qualified site owners authorize the change window and read back installed behavior. Do this because test coverage is valuable only when the oracle matches the effect being promised.
Visual: Only controlled site observation closes it.
Research and claim limits
- Siemens Automation Framework documentation (S140)
- NIST: Credibility Consideration for Digital Twins in Manufacturing (S141)
The examples identified as illustrative or simulated are design probes, not reported incidents. Vendor specifications do not establish workload performance.