RoboticSubsystem
plain-language theorem explainer
RoboticSubsystem enumerates the five canonical subsystems required for robotic systems under Recognition Science. Engineers modeling autonomous navigation as J-cost minimization would cite this when checking subsystem completeness against configDim D=5. The declaration is a direct inductive definition that derives Fintype cardinality, decidable equality, and related instances automatically.
Claim. The inductive type RoboticSubsystem consists of the five constructors sensing, actuation, computation, communication, and power.
background
The Robotics from RS module defines five canonical robotic subsystems (sensing, actuation, computation, communication, power) as configDim D=5. Robot control is a J-cost minimization loop and autonomous navigation seeks minimum cumulative J. The upstream power definition supplies spectral amplitude scaling (ps.amplitude times wavenumber power law) from the primordial spectrum, though it is not invoked in this declaration.
proof idea
The declaration is an inductive definition that introduces the five constructors and uses a deriving clause to obtain DecidableEq, Repr, BEq, and Fintype instances.
why it matters
This supplies the type for the five_subsystems field in RoboticsCert and is used by the roboticSubsystemCount theorem establishing Fintype.card RoboticSubsystem = 5. It fills the E1 Applied Engineering step, connecting to the framework's D=3 spatial dimensions via the 6-DOF = cube faces relation. No open scaffolding questions are addressed.
Switch to Lean above to see the machine-checked source, dependencies, and usage graph.