Owns LMC module text, definitions, exposure classes, terminology, and acceptance rules.
Board and change control
Governance
How LMC standards are proposed, reviewed, versioned, certified, renewed, retired, and bridged into MSRX research records.
Governance model
Separate standards, certification, evidence, and research.
LMC is strongest when each function has a clear authority boundary. Standards define requirements. Certification applies them. Labs produce evidence. Registry publishes public state. MSRX archives research and formal research.
Issues certificate state: review, active, renewed, suspended, retired, or failed.
Controls evidence record grammar, evidence seals, evidence classes, and review trail requirements.
Qualifies lab capability claims and maps test evidence to specific LMC standards.
Publishes public-safe certificate metadata and keeps registry records buyer-readable.
Links research papers, standard rationale, theorem records, and public technical notes to MineSpace.us/MSRX.
Change control
No silent standard drift.
Change request with reason, affected standard, affected certificate classes, and risk note.
Customer impact, supplier impact, lab impact, renewal impact, MSRX citation impact.
New version text with public diff, effective date, and transition rules.
Updated standard, registry notice, certificate renewal rules, and research bridge.
Public cadence
Standards stay useful when change is visible.
LMC governance presents each change as a public state: proposed, under review, scheduled, active, transitional, or retired.
A supplier, lab, buyer, or mission team identifies a material gap.
The effect on existing certificates, labs, and procurement records is reviewed.
Customers receive the date and transition window before the change applies.
The standard version becomes the current reference for new certificates.
Older versions remain citable for older certificate records.
Governance record