Bridge Checkpoint: Defend the Component Boundary

Finish this route with a Component Boundary Card comparing one plain Java object, one WPILib subsystem, and one ROS 2 node.

For each, include:

• runtime or framework owner;
• responsibility;
• evidence source;
• visible interfaces;
• one unsupported claim.

Then answer this challenge:

If all three components are named RangeSensor, what evidence prevents you from treating them as the same runtime entity?

A strong answer refers to process/framework/graph evidence, not naming.

Use this pattern:

Java object: proved by ...
WPILib subsystem: proved by ...
ROS node: proved by ...
Integration between them: [proved / supported but incomplete / not demonstrated]
Physical sensor behavior: [status + missing evidence]

The route is complete when another engineer can see exactly where each component exists and where the evidence stops.

Do not add more object-oriented language instruction here. The prerequisite course owns that material.