MaintenanceStrategiesCert
plain-language theorem explainer
The certificate structure certifies that exactly five maintenance strategies exist in the Recognition Science operations model. Operations researchers would cite it when verifying that the configuration dimension matches the enumerated strategies. The definition is a direct wrapper around the cardinality of the inductive type listing reactive, preventive, predictive, condition-based, and reliability-centered strategies.
Claim. Let the set of maintenance strategies consist of the five elements reactive, preventive, predictive, condition-based, and reliability-centered. The certificate structure asserts that the cardinality of this set equals 5.
background
The module establishes five canonical maintenance strategies tied to configuration dimension 5. These comprise reactive (run-to-failure), preventive (schedule-based), predictive (model-based), condition-based (sensor-based), and reliability-centered (system-criticality-based) approaches. The inductive type enumerates precisely these five cases and derives the Fintype instance used for cardinality checks. This construction sits in the operations depth of the Recognition Science model, supplying a concrete enumeration that aligns abstract dimension parameters with practical protocols.
proof idea
This is a structure definition that packages the single field asserting Fintype.card of the strategy type equals 5. It relies on the automatic Fintype derivation for the inductive type with five constructors. No lemmas or tactics are invoked beyond the built-in instance.
why it matters
The structure supplies the type for the downstream definition that witnesses the five-strategy count. It fills the operations-level claim that configuration dimension equals 5 by explicit enumeration. In the framework this specializes the dimension-forcing steps to maintenance protocols while leaving the spatial dimension fixed at 3; no open questions are resolved here.
Switch to Lean above to see the machine-checked source, dependencies, and usage graph.