Agents / Robotic Compliance / Specimen
See it in practice
One release, checked end to end.
A real update of Nav2, the open-source navigation stack many mobile robots are built on,
run through the pipeline for a fictional warehouse robot, AMR-1. The code changes are real.
The robot, its safety file and its limits are a specimen.
For the CTO: the release gate
Pull request check
#482 Bump Nav2 to 1.3.11
Specimen. Illustrative CI check.
Checks: 4 passed · 1 waiting for approval
- Passed
build / colcon (Jazzy)Passed in 6m 12s
- Passed
test / unit + integration1,284 passed
- Passed
security / SBOM + vulnerability scan44 components updated · 0 new vulnerabilities
- Passed
compliance / foreseen-modification limitsWithin limits (FML-02, FML-05)
- Waiting
compliance / safety reviewSafety lead approval required
Review
compliance / safety review
2 changes affect credited risk-reduction measures. Merge blocked until approved.
Release gate · AMR-1 · 1.3.10 → 1.3.11
REVIEW 3fc1600c collision monitor height now in base frame
→ M-03 slowdown zone · H-04 low obstacles
→ re-run test T-M03-01
REVIEW 3320ebf7 obstacle marking range now 2D cell distance
→ M-05 obstacle avoidance · H-04, H-06
→ re-run test T-M05-02
OK SF-01 protective stop (safety scanner): unchanged
OK within foreseen-modification limits: no notified body needed
Approver: safety lead · Evidence stored signed, retained 10 years
Open release impact report
Approve
Request changes
For the safety lead: every change traced
Change detail
Commit 3fc1600c: fix Z base frame transformation
Specimen. Real Nav2 commit.
nav2_collision_monitor/src/pointcloud.cpp · +5 lines · in Nav2 1.3.11
tf2::Vector3 p_v3_b = tf_transform * p_v3_s;
+ // Still need to transfer height from "z" field if not using global height
+ if (!use_global_height_) {
+ data_height = p_v3_b.z();
+ }
+
// Refill data array
if (data_height >= min_height_ && data_height <= max_height_) {
What changes in behaviour. Before, point heights were taken from the sensor frame. On AMR-1 the 3D camera is mounted 0.42 m high and tilted, so low obstacles could fall outside the min_height / max_height window and be ignored. After this fix, heights are measured from the robot base, and more low obstacles are detected.
Traceability
Foreseen-modification check
Assessment. Likely a safety improvement, but it changes detection behaviour, so the risk assessment entry for H-04 needs review.
For the CEO: one verdict per release
Your logo
- Document
- AMR1-RIR-1.3.11
- Revision
- 1
- Date
- 23 Jan 2026
- Classification
- Internal
Release impact report
AMR-1 navigation 1.3.11
Specimen. Built on the real open-source Nav2 stack (ROS 2 Jazzy); the code changes are real.
| Release | Nav2 1.3.11 (23 Jan 2026), compared with 1.3.10 (23 Oct 2025) |
|---|
| Scope | 13 commits · 129 files · 44 packages updated |
|---|
| Safety functions affected | 0 safety-rated · 2 credited risk-reduction measures |
|---|
| Foreseen-modification limits | Within limits (FML-02) |
|---|
| SBOM | 44 components updated · 0 added · 0 removed |
|---|
| Known vulnerabilities | 0 new (illustrative) |
|---|
Review
Verdict: Review
Two changes alter how obstacles are detected. Both affect measures credited in the risk assessment, not the safety-rated protective stop. Safety lead approval and a re-run of tests T-M03-01 and T-M05-02 are required before release. No notified body involvement needed: the change stays within the documented limits of foreseen modifications.
Changes by impact
Next steps
- Safety lead reviews 2 changes: approve or reject.
- Re-run T-M03-01 and T-M05-02 on the test track and attach the results.
- Technical file and Declaration of Conformity draft regenerate automatically after approval.
Based on real Nav2 releases: compare 1.3.10 and 1.3.11, or see the collision monitor fix on GitHub.
Specimen for illustration. AMR-1, its safety functions, hazards, tests and limits are fictional, and the vulnerability figure is illustrative. Code excerpts from Nav2 (ros-navigation/navigation2), Apache License 2.0. Independent example, not affiliated with or endorsed by the Nav2 project. Mapping to legal requirements and standard clauses is verified by a safety engineer in every client project.
