About / Dimitri Lafleur

Building systems for critical infrastructure and markets.

I work in real-time gas SCADA and founded Wall Street Silver, building tools and workflows that stay legible under load. My work usually lives where telemetry, operational safety, market intelligence, and applied simulation overlap.

Telemetry point lifecycles, historian behavior, alarm reliability
Market signal research, sentiment processing, analytics, audience tooling
Simulation protocol workflows, PLC logic, deterministic test environments
Current lane Critical infrastructure

Real-time gas SCADA work centered on telemetry trust, historian behavior, and operator-facing reliability.

Parallel build Wall Street Silver

Market research systems, signal tooling, and public-facing infrastructure for a market community.

Default mode Deterministic systems

Small, inspectable tools that make hidden assumptions visible before they become operational risk.

Pictures

Dimitri in a navy suit giving a thumbs up
Earlier portrait of Dimitri
Dimitri standing with Rand Paul at a Young Americans for Liberty event
With Rand Paul

Three lanes, one working style.

Whether the surface is industrial operations or public-market research, the throughline is the same: preserve signal, make system state obvious, and build tools that can be trusted in motion.

01

Critical infrastructure

Real-time gas SCADA work across telemetry, point quality, alarm behavior, historian logic, and operationally safe data flow.

02

Markets and media systems

Research, analytics, and community-scale information systems through Wall Street Silver, with an emphasis on usable signal over noise.

03

Simulation and experimentation

Control-system simulation, PLC logic modeling, protocol tooling, and small engineering environments for learning by building.

Deterministic thinking for noisy systems.

I like environments where reliability matters and failure modes are worth understanding. That usually means explicit state, deterministic behavior, and tooling that explains itself instead of forcing operators to guess.

On the market side, I focus on research workflows, sentiment processing, and systems that help scale information without flattening nuance. On the engineering side, I keep coming back to simulation because it makes hidden assumptions visible.

How collaboration works best

The best work usually sits between direct system ownership and exploratory problem-solving: enough ambiguity to matter, enough structure to build something durable.

01

Work from the real operating state

Start with the plant, workflow, or market behavior itself before polishing the interface around it.

02

Prefer explicit rules to implicit magic

Systems get calmer when their constraints, transitions, and failure modes can be inspected directly.

03

Prototype to learn, not to decorate

Small simulators, test harnesses, and compact tools are how hidden assumptions show up early.

04

Make outputs usable under pressure

The end result should help an operator, analyst, or reader decide more clearly when conditions are noisy.

Open lines for engineering, research, and collaboration.

Email is the cleanest line for direct outreach.