Understand
Index studies, spreadsheets, regulations and prior reports so evidence can be read across documents, not one file at a time.
Mining technical reporting, built for engineer review
From mine data to engineer-ready reports.
MineLex reads your drilling data, engineering studies and the applicable reporting standard, drafts source-traceable report sections, and flags what doesn't add up. A qualified engineer reviews, edits and signs.
Project workspace Copper open pit, PeruIllustrative example, not a real project
JurisdictionPeru: permitting and environmental requirementsMapped
Reporting frameworkCRIRSCO-aligned code, selected for the intended disclosure venueMapped
Required sections17 identified from the framework template17 / 17
Reference currency2 clauses should be re-checked against the current editionVerify
Competent / Qualified personRole and credentials required by the selected codeAwaiting engineer
Estimate report: 412 holes used. Drill database export: 397 holes with assays.
Sources: Resource_Estimate_v3 §6.2, drillhole_export_2025.csv
Action: engineer to confirm which holes are in scope.
Sources: Resource_Estimate_v3 §6.2, drillhole_export_2025.csv
Action: engineer to confirm which holes are in scope.
Tonnage calculation references density by domain. No measurements found for oxide.
Section is held back. It cannot be completed without engineer input.
Section is held back. It cannot be completed without engineer input.
Geotechnical report: inter-ramp 46°. Pit design memo: 49°.
Check which value was used in the economic model.
Check which value was used in the economic model.
Values flagged for review. Figures come from the calculation engine, not from the language model.
Showing 4 of 7 example findings. Select one to see its source trace.
MineLex draft generated, with sources linked to each claimDone
Automated validation and deterministic calculations runDone
Qualified engineer reviews findings and edits sectionsIn review
Engineer approves and signs. MineLex does not sign.Pending
Report issued with a full audit trailPending
A technical report is a chain of evidence.
Every figure in the executive summary rests on a study, a dataset or an assumption somewhere else. Reports go wrong where the links between those documents break, and finding those breaks by hand takes weeks.
Drilling and assaysQA/QC, database
Geological modeldomains, density
Resource estimatecut-off, classification
Pit design and geotechnical basisslope angles
Metallurgy and processingrecovery
EconomicsCAPEX, OPEX, NPV
Permits and regulationper jurisdiction
Validate
Find missing inputs, contradictory assumptions, outdated references and cross-document mismatches before final review.
Prepare
Draft structured sections with sources, assumptions and open review items attached, ready for the responsible engineer.
Six steps. The last one belongs to an engineer.
Steps one to five run in MineLex. Step six is a professional decision that stays with a person.
Project intake
Country, commodity, mining method, report purpose and available data.
Standards mapping
Identify the reporting framework and jurisdiction-specific requirements.
Technical reasoning
Extract and connect evidence across geology, mining, metallurgy and economics.
Validation
Flag gaps, unsupported claims and contradictions.
Report generation
Draft structured, source-traceable sections.
Engineer review and sign-off
A qualified engineer reviews, edits, approves and signs.
Green line: human professional responsibility.
One workflow, many reporting codes.
MineLex is designed as a global platform with country- and standard-specific modules. The core workflow stays the same, and the module defines what a compliant report must contain.
JORCAustralasia
NI 43-101 / CIMCanada
S-K 1300United States, SEC
SAMRECSouth Africa
PERCPan-European
CRIRSCO-alignedOther national codes
Initial framework coverage is a design target. MineLex does not claim support for every country today, and it is not a certified or accredited reporting body in any jurisdiction. Modules are added and reviewed with local professionals.
AI prepares. Engineers decide.
Technical reports carry professional liability. MineLex is built so that responsibility is never ambiguous.
MineLex
- Reads and connects project evidence
- Drafts sections with a source for each claim
- Flags missing data and inconsistencies
- Refuses to invent inputs it does not have
- Keeps an audit trail of every change
The qualified engineer
- Supplies missing inputs and judgement
- Reviews and edits every section
- Resolves flagged findings
- Approves and signs the final report
- Holds professional responsibility
Where Claude fits in the architecture.
MineLex is built on Claude for the work that needs reading, reasoning and tool use. Numerical work that must be exact goes to dedicated engineering code.
Claude
Reasoning and orchestration
Technical reports run to hundreds of pages and cite each other, so long-context reading is the core need.
- Long-document understanding
- Extraction and classification of technical evidence
- Cross-document consistency checks
- Agent orchestration and tool calls
- Source-grounded report drafting
Deterministic engine
Calculation
Claude decides which calculation is needed and calls it. It does not do the arithmetic itself, and then explains the result in engineering language.
- Tonnage, grade and metal content
- Factor of safety
- NPV, IRR and sensitivity
- Cut-off and survey calculations
Work with us on a pilot project.
We are working with a small number of engineers and consultancies to shape the first modules. Tell us which reporting code and report type matter most to you.