On an inclined plane, gravity has a component along the slope and another perpendicular to it. The saved source uses mass times nine point eight one times the sine of the angle for the parallel force, and cosine for the normal force. At two kilograms and thirty degrees these are nine point eight one and sixteen point nine nine newtons. Friction is point one five times the normal force, about two point five five newtons. Subtracting friction and dividing by mass gives about three point six three meters per second squared. The colored vectors illustrate direction; their lengths here are illustrative. The numerical equations explain the displayed cards. Both driving force and friction contain the same mass factor. Dividing the nonnegative net force by mass cancels it, so doubling mass from two to four kilograms doubles the forces but leaves acceleration unchanged at the same angle and friction coefficient. Increasing angle instead changes both sine and cosine. The plotted values use the source equation at five degree intervals from five through sixty degrees. The vertical scale is thirty-two pixels per meter per second squared. At five degrees the formula would be negative before clipping, so the source returns zero acceleration. This is a simplified constant friction model; it does not separately model static and kinetic friction. Read the animation separately from the force equations. The source computes traveled distance as one half acceleration times time squared, scaled by fifteen pixels, then caps it at ramp length minus sixty. But its position expression starts the block near the bottom and moves it uphill as this distance grows. That direction is a source inconsistency, not downhill physics. The pendulum and spring views use cosine motion while their sidebar metrics still calculate the incline equations. The optics scene is a static sketch. Freehand recognition only shows a processing message, waits four hundred milliseconds, and restores the selected preset name. There is no stroke classifier or model call. PNG export uses the actual p5 canvas when available; the offline environment blocks its remote dependency, so canvas playback and export are not proved here.