Scheinman
Measure. Correct. Measure again.
Original frontend design. Sample data.
The problem.
A useful engineering finding needs a measured value, an applicable rule and a source. A proposed correction also needs proof that the delivered geometry satisfies the supported checks.
What I built.
A CAD inspection prototype that links findings to evidence and checks its own corrections.
- My role
- Product concept, system architecture and evidence workflow
- For
- Engineering research and supported-part inspection
How it connects.
Source-linked checks with an explicit correction loop and refusal outcomes.
Read the connections as text
- STEP + context → Measure
- Measure → Check
- Source-linked rules → Check
- Check → Bounded correction: Supported violation
- Bounded correction → Remeasure
- Remeasure → Report + files: Verified outcome
- Check → Report + files: Pass or report
- Measure → Report + files: Refuse unsupported
Built in stages.
Current geometry scope: flat plates with round through-holes.
Broader geometry and stronger evaluation remain development work.
Inside the product.
Open a module to see its capabilities,
decisions and boundaries.
Rule evidenceKeep each rule connected to the official material behind it.
Official sources
Source-linked facts extracted from official engineering documents
Independent readings
Independent readings and machine checks of source provenance
Human review
Human review of extracted statements with the source excerpt visible
Rule scope
Explicit applicability, limitations and severity for each rule
Evidence status
An evidence page separating source replay from human validation
Part inspectionInspect only the geometry that the prototype can measure faithfully.
STEP intake
STEP upload with material-series and static or cyclic loading context
Supported geometry
Measurement of flat plates with round through-holes
Rule evaluation
Measured values compared with applicable geometric rules
Measured findings
Findings with required values, source citations and severity
Explicit refusal
Explicit refusal of unsupported, corrupt or multi-part geometry
Correction & verificationA change is accepted only after the reconstructed part is measured again.
Parameter changes
Bounded parameter changes for supported violations
Faithful reconstruction
Reconstruction checks that preserve the intended supported geometry
Remeasurement
Remeasurement of the actual corrected file
Explicit outcomes
Clear Passed, Corrected, Reported or Refused outcomes
Advisory findings
Advisory findings retained in the report without silently changing the part
Reports & archiveReturn an inspectable result, with the files and history behind it.
Inspection report
Inspection report with measured findings and linked rules
Corrected STEP
Corrected STEP file when the correction can be proven
Refused correction
Original file and explanation when correction is refused
Job progress
Job progress and result pages
Job archive
Owner archive of previous jobs and their findings
Access & operationA web intake connected to a separately executed inspection engine.
Protected access
Password-protected prototype dashboard, inspection and evidence areas
Cloud execution
Cloud execution of the inspection engine through GitHub Actions
Intake limits
Upload and usage limits with human verification at intake
Timeout outcomes
Timeouts that report unfinished jobs as Not Run
Operational monitoring
Failed-job alerts, external daily monitoring and deployed-version identification
Tools & systems.
Python / build123d / Pydantic / Cloudflare Workers / GitHub Actions / STEP geometry
Where the project stands.
- The prototype covers flat plates with round through-holes.
- It does not provide general CAD certification or autonomous engineering approval.
- Unsupported or unfaithfully reconstructable geometry is explicitly refused.