Bridge Checkpoint: Name the Missing Integration Evidence

A common systems mistake is to jump from two matching observations to an integration claim.

You may have:

Java threshold: 0.5
ROS parameter:   0.5

That is not enough to say the Java application receives its value from ROS 2.

Draw the missing path

Represent the claim you want to prove:

ROS parameter
→ integration mechanism
→ Java value
→ decision method

Now mark every arrow as either observed, documented, or assumed.

If the integration mechanism is blank, the claim is incomplete.

Stronger evidence

Useful evidence could include:

• source showing the adapter or bridge;
• runtime logs identifying the value transfer;
• a controlled change where modifying the ROS-side value predictably changes the Java-side state;
• a trace that identifies the process and interface carrying the value.

A screenshot showing identical numbers on two screens is weaker evidence.

Deliverable

Write a four-sentence Integration Gap Note:

1. what the Java side proves;
2. what the ROS side proves;
3. what remains unobserved between them;
4. the next experiment that would test the integration claim.

The bridge skill is knowing when to stop claiming and start asking for the next piece of evidence.