Manish Sharma Current proof: LMD / DED

Industrial AI / decision systems Evidence-aware by design

I build AI systems for industrial decisions that need evidence, not just predictions.

Again and again, I found that a prediction alone did not settle the industrial question. My strongest public work today is in Laser Metal Deposition and Directed Energy Deposition at Exafuse, where I connect signals, models, engineering constraints, and human judgment to the next action and the evidence needed to check it.

Start with the LMD Decision Cockpit, then follow the method and current public work.

Illustrative LMD process schematic. Process signal to inspection evidence. Read from the deposition zone toward the evidence needed for technical review.
  1. Laser beam: Focused energy reaches the deposition zone.
  2. Melt pool: The local molten region is a process observation point.
  3. Deposited track: Material is added along the intended repair or build path.
  4. Process signal: Monitoring can flag a review question, not final quality.
  5. Inspection evidence: Inspection and expert review establish the next defensible claim.

Decision signal // live

Monitoring

  1. 01SenseSignals
  2. 02ModelAssumptions
  3. 03DecideEvidence plan
  4. 04VerifyInspection

Evidence status

A signal is not proof.

Process signals can support review. They do not replace inspection, testing, expert review, or release evidence.

Source note
Public context only

Active module

Decision Cockpit

  • Local session
  • Browser-local
  • Decision-support only
LMD Decision CockpitLMD Decision Brief v1.0Conservative output

Start with a rough LMD question. Leave with a brief.

Pick the situation, mark what is known, then expose missing information, risk flags, evidence needed, and an Exafuse review route. Inputs stay in this browser session only.

  • ;
  • ;

Example scenario: worn steel shaft near bearing seat.

Review the worked output, start your own brief here, or open the full workbench.

Repair damaged/worn part: start with LMD Repairability Quick Check. Not enough information. Missing information and risk flags remain visible in the brief.

How I work / signal to evidence

Sense → Model → Decide → Verify

To me, a prediction is only one part of the job. The next action, the missing context, and the verification path have to be clear too.

Decision support Evidence boundary
  1. 01 Sense Capture the process signal and its operating context.
  2. 02 Model Make assumptions visible.
  3. 03 Decide Plan the evidence needed.
  4. 04 Verify Use inspection evidence.

Current proof / decision routes

LMD/DED is my current proving ground

It is where signals, materials, machine vision, robotics, repair, inspection, and engineering judgment meet in decisions with real consequences.

Public source context Decision guidance

Documented examples

Current LMD/DED proof, with public source context

These public examples show why evidence planning matters. Commercial case details and RFQs remain with Exafuse.

CS15 Public Exafuse source

Duisburg Bridge Components

Use the pattern as context only; feasibility still depends on the actual part, material, service conditions, inspection needs, and expert review.

CS01 Public Exafuse source

Forging Hammer Repair

Use the pattern as context only; feasibility still depends on the actual part, material, service conditions, inspection needs, and expert review.

Personal platform

Explore the method, current work, and research questions.

I am studying how this approach can help with decisions based on incomplete physical signals, operational risk, and human responsibility. That is a research direction, not a cross-industry deployment claim.

Commercial boundary

For commercial LMD/DED services and RFQs, use Exafuse.

My current applied LMD/DED work is carried out through Exafuse. This site shares public methods and notes; company services, case studies, and engineering review belong there.