Section 12Simulation Runtime
Material System requirements
Defines engineering material properties, pair interactions, provenance, validity, wetness effects, and future failure-related behavior.
Section relationships
| ID | Name | Priority | Requirement | Verification |
|---|---|---|---|---|
| MAT-001 | Visual and engineering separation | MVP | Visual appearance SHALL be stored separately from engineering material behavior. | Inspection |
| MAT-002 | Stable material identity | MVP | An engineering material SHALL have a stable identifier and revision independent of its display name. | Test |
| MAT-003 | Density | MVP | A bulk material SHALL support density with units, source, uncertainty, and applicable conditions. | Inspection |
| MAT-004 | Surface friction | MVP | A surface material SHALL support the friction parameters required by the selected contact model. | Inspection |
| MAT-005 | Restitution | MVP | A surface material SHALL support restitution with applicable impact conditions and provenance. | Inspection |
| MAT-006 | Aerodynamic coefficients | MVP | A material or aerodynamic surface SHALL support documented drag and optional lift coefficients without conflating them with visual properties. | Inspection |
| MAT-007 | Material-pair behavior | MVP | Contact behavior SHALL be resolvable from the ordered or unordered pair of interacting surface materials under a documented rule. | Test |
| MAT-008 | State-dependent property relation | MVP | An active condition- or state-dependent property relation SHALL declare its independent variables, units, and validity domain and, when represented by sampled or tabulated data, its interpolation and extrapolation policy. | Test |
| MAT-009 | Consistent elastic properties | Beta | An elastic material SHALL declare its symmetry class and independent elastic parameters; redundant moduli SHALL be derived or checked within a declared consistency tolerance. | Test |
| MAT-010 | Thermal properties | Beta | An engineering material SHALL support heat capacity, thermal conductivity, emissivity, and temperature limits when required by an enabled model. | Inspection |
| MAT-011 | Consistent electrical properties | Beta | An engineering material SHALL support an independent conductivity or resistivity representation, derive or consistency-check its reciprocal, and declare dielectric and temperature-coefficient data when required by an enabled model. | Test |
| MAT-012 | Strength and inelastic properties | Future | An engineering material MAY support yield, ultimate strength, hardening, ductility or formability, creep, viscoelasticity, fatigue, fracture, plasticity, and damage data. | Inspection |
| MAT-013 | Uncertainty | MVP | Every engineering property SHALL be able to carry an uncertainty or explicitly state that uncertainty is unknown. | Inspection |
| MAT-014 | Provenance | MVP | Every published catalog property SHALL identify its source, source revision, extraction method, and curator. | Inspection |
| MAT-015 | Validity conditions | MVP | A property SHALL be able to declare temperature, rate, orientation, treatment, and other conditions that bound its applicability. | Inspection |
| MAT-016 | Catalog revisioning | Beta | Material catalog updates SHALL create a new revision without silently changing completed run manifests. | Test |
| MAT-017 | User material | MVP | A user SHALL be able to define a project-local engineering material without modifying the built-in catalog. | Demonstration |
| MAT-018 | Calibrated surface pair | Beta | A user SHALL be able to calibrate a material-pair interaction while retaining raw observations and the uncalibrated source values. | Demonstration |
| MAT-019 | Out-of-envelope warning | MVP | Use of a material property outside its declared validity conditions SHALL be included in run diagnostics and the fidelity card. | Test |
| MAT-020 | Solver-consumed property namespace | MVP | Constitutive, transport, resistive or dissipative, surface or interfacial, and other solver-consumed material-model data SHALL be versioned, namespaced, and capability checked rather than treated as universal material constants. | Test |
| MAT-021 | Wet-friction relation | MVP | A surface-material pair used with evolving wetness SHALL define a dry-to-wet friction relation, provenance, and validity range. | Analysis |
| MAT-022 | Multiphysics property namespace envelope | MVP | Canonical material definitions SHALL reserve versioned namespaces for inertial, contact, constitutive, transport, resistive or dissipative, thermal, electrical, magnetic, optical or radiative, and chemical or degradation property-model families without implying standardized family semantics or active solver support. | Test |
| MAT-023 | Declared property evaluation inputs | MVP | A state-dependent engineering property relation SHALL evaluate only from its declared committed-state inputs and declared internal history or state where applicable. | Test |
Change rationale (MAT-008, MAT-012, MAT-020, MAT-022, MAT-023): BeforeMetal must make room for broad engineering property semantics—including drag and friction inputs, conductivity and resistivity, and typed plasticity, ductility, or hardening relations—without inventing one universal “malleability” scalar, standardizing every family in MVP, or promoting every specialist solver into MVP scope. Recognized property types follow MODEL-037; unknown namespaced data follows MODEL-021 and MODEL-028 at their stated priorities. Active state dependence is an MVP contract because wetness, motors, batteries, and sensors already depend on committed state; general elastic, thermal, electrical, plastic, deformable, CFD, FEA, diffusion, and failure solvers retain their existing priorities.
Generated from the canonical specification. Edit section metadata or prose in docs/requirements.md; the website rebuilds this page and its relationships automatically.