VALIDATION REGISTER
What has been checked — and what has not.
Validation is reported by method, evidence type and product stage. It does not mean universally valid or suitable for every site.
Evidence by method and stage.
| Method or layer | Reference | Evidence | Public status |
|---|---|---|---|
| Kirsch elastic stress solution | Published workflow · DOI 10.3390/app16052347 | Analytical equations and literature comparison | Published workflow |
| Generalized Hoek–Brown criterion | Published workflow · DOI 10.3390/app16052347 | Equation, parameter and literature checks | Published workflow |
| Software implementation checks | Method-specific automated test suites | Units, required inputs, regression and known cases | Ongoing per release |
| Site or pilot field validation | No public result yet | Representative field comparison and partner review | Planned |
REPORTING RULES
Evidence stays attached to its boundary.
- A passing software test is evidence for a defined implementation, not proof of site suitability.
- Each method keeps its source, units, assumptions and warnings visible.
- Field or pilot evidence is not marked complete until a real comparison and approval exist.
- Version-specific evidence must be repeated when relevant calculation logic changes.
REVIEW QUESTIONS
Questions a reviewer should be able to answer.
- 01Can another engineer reconstruct the input and unit trail?
- 02Can intermediate values be compared with a primary source or reference case?
- 03Are assumptions and out-of-range warnings visible before a decision?
- 04Is the final engineering judgement clearly assigned to a qualified practitioner?
Have a reference case or an independent check that can strengthen this register?