Sims Implementation Map

Where the math here meets the code there. Each row links a research page (this wiki) to the
module that implements it in the sims (code) wiki, tagged by subsystem (the
subsystem_decomposition axis) and pointed at the logged
evidence (evidence_map). A one-directional, external window via the
sims_wiki/ / sims_logs/ symlinks — schemas stay distinct, this is a map, not a merge. Code/log
links resolve in Obsidian (through the symlinks), not on GitHub.

Research page (here)Code page (sims wiki)SubsystemEvidenceWhy linked
subsystem_decompositioncom_controller · breve_controller[com, base, ee]com_smokeThe spine: the CoM + base+EE split these modules implement.
coordinated_controlbreve_controller[com, base, ee]com_smokeThe circumcentroidal coordinated base+arm control law.
generalized_jacobianrobot[base, ee] traceJacobian assembly + the conditioning that’s measured/logged.
circumcentroidal_decouplingcom_controller[com, base, ee]com_smokeThe transform decoupling CoM from attitude+EE.
singularity_threshold_cascadebreve_controller[base, ee] / derateThe layered derate stack (incl. Tikhonov) engaged near a singularity.
discretization_stability_omega_bbreve_controller[base, ee] in com_smokeThe forward-Euler ripple — cured in code by implicit base-damping integration.
reaction_null_spacerobot[base]Null-space kernel of the (redundant) generalized Jacobian.
steady_state_error_floorbase_guidance[base, ee]The cruise-lag error floor set by the outer guidance loop.
trajectory_trackingee_guidance[ee]Closed-loop end-effector tracking error dynamics + feedforward.
next_best_viewtarget_finder[ee]Inspection viewpoint / target selection.

Add a row when a new result or topic gains an implementation. Keep the why to one line; tag the
subsystem it touches ([base, ee] for circumcentroidal-block claims — never one alone) and point
at logged evidence when it exists.