CLAIMBOUND / SOURCE-PUBLICATION EVIDENCE
Robotics
Every card identifies what it proves, what it does not prove, its exact quote, locator, source hash, and local rerun command.
1. NASA Robotic Interface Best Practices and Lessons Learned for Surface Operations · PDF page 9
Narrow public claim
The purpose of this document is to provide guidance for designing and organizing interfaces between robotic systems, crew operations, and cargo/payloads for use on the lunar or Martian surface.
What this card proves
The exact quoted statement occurred in the named official PDF fetched on 2026-08-04, and the complete PDF matched the recorded SHA-256.
What this card does not prove
It does not independently establish the underlying model capability, safety, comparison, or real-world truth. This is a retrospective single-maintainer source-publication audit.
- Primary source
- NASA Robotic Interface Best Practices and Lessons Learned for Surface Operations
- Section locator
PDF page 9- Captured
- 2026-08-04
- Source SHA-256
fee6644426a6db1a72984d7ec2224288899582b03f04dae7b041a01b4eacffb8- Reproduction
- Maintainer run only; no independent operator rerun is registered.
Repeat this exact check locally
Download the PDF to a local file, then run the committed verifier. A changed PDF is reported as drift rather than silently accepted.
python scripts/verify_primary_public_claim_group.py artifacts/cb7k_dom007_t01_primary_claims.json --source-file <local-raw-pdf>Exact source quote
The purpose of this document is to provide guidance for designing and organizing interfaces between robotic systems, crew operations, and cargo/payloads for use on the lunar or Martian surface.
2. NASA Robotic Interface Best Practices and Lessons Learned for Surface Operations · PDF page 9
Narrow public claim
They are meant to inform design choices to make an interface that is “robotic-forward” and increase the likelihood that an interface will be compatible with a future, yet-to-be-designed robotic system.
What this card proves
The exact quoted statement occurred in the named official PDF fetched on 2026-08-04, and the complete PDF matched the recorded SHA-256.
What this card does not prove
It does not independently establish the underlying model capability, safety, comparison, or real-world truth. This is a retrospective single-maintainer source-publication audit.
- Primary source
- NASA Robotic Interface Best Practices and Lessons Learned for Surface Operations
- Section locator
PDF page 9- Captured
- 2026-08-04
- Source SHA-256
fee6644426a6db1a72984d7ec2224288899582b03f04dae7b041a01b4eacffb8- Reproduction
- Maintainer run only; no independent operator rerun is registered.
Repeat this exact check locally
Download the PDF to a local file, then run the committed verifier. A changed PDF is reported as drift rather than silently accepted.
python scripts/verify_primary_public_claim_group.py artifacts/cb7k_dom007_t01_primary_claims.json --source-file <local-raw-pdf>Exact source quote
They are meant to inform design choices to make an interface that is “robotic-forward” and increase the likelihood that an interface will be compatible with a future, yet-to-be-designed robotic system.
3. NASA Robotic Interface Best Practices and Lessons Learned for Surface Operations · PDF page 9
Narrow public claim
The more of these BPs and LLs that can be accommodated in an interface design, the simpler a robotic system can be to successfully make use of the interfaces on the lunar or Martian surface.
What this card proves
The exact quoted statement occurred in the named official PDF fetched on 2026-08-04, and the complete PDF matched the recorded SHA-256.
What this card does not prove
It does not independently establish the underlying model capability, safety, comparison, or real-world truth. This is a retrospective single-maintainer source-publication audit.
- Primary source
- NASA Robotic Interface Best Practices and Lessons Learned for Surface Operations
- Section locator
PDF page 9- Captured
- 2026-08-04
- Source SHA-256
fee6644426a6db1a72984d7ec2224288899582b03f04dae7b041a01b4eacffb8- Reproduction
- Maintainer run only; no independent operator rerun is registered.
Repeat this exact check locally
Download the PDF to a local file, then run the committed verifier. A changed PDF is reported as drift rather than silently accepted.
python scripts/verify_primary_public_claim_group.py artifacts/cb7k_dom007_t01_primary_claims.json --source-file <local-raw-pdf>Exact source quote
The more of these BPs and LLs that can be accommodated in an interface design, the simpler a robotic system can be to successfully make use of the interfaces on the lunar or Martian surface.
4. NASA Robotic Interface Best Practices and Lessons Learned for Surface Operations · PDF page 9
Narrow public claim
Once the process of designing a new interface and/or a robotic system has been initiated, requirements will need to be documented.
What this card proves
The exact quoted statement occurred in the named official PDF fetched on 2026-08-04, and the complete PDF matched the recorded SHA-256.
What this card does not prove
It does not independently establish the underlying model capability, safety, comparison, or real-world truth. This is a retrospective single-maintainer source-publication audit.
- Primary source
- NASA Robotic Interface Best Practices and Lessons Learned for Surface Operations
- Section locator
PDF page 9- Captured
- 2026-08-04
- Source SHA-256
fee6644426a6db1a72984d7ec2224288899582b03f04dae7b041a01b4eacffb8- Reproduction
- Maintainer run only; no independent operator rerun is registered.
Repeat this exact check locally
Download the PDF to a local file, then run the committed verifier. A changed PDF is reported as drift rather than silently accepted.
python scripts/verify_primary_public_claim_group.py artifacts/cb7k_dom007_t01_primary_claims.json --source-file <local-raw-pdf>Exact source quote
Once the process of designing a new interface and/or a robotic system has been initiated, requirements will need to be documented.
5. NASA Robotic Interface Best Practices and Lessons Learned for Surface Operations · PDF page 10
Narrow public claim
This document is a Data Managed (DM) product that is managed by the product owners and does not require board approval to be changed.
What this card proves
The exact quoted statement occurred in the named official PDF fetched on 2026-08-04, and the complete PDF matched the recorded SHA-256.
What this card does not prove
It does not independently establish the underlying model capability, safety, comparison, or real-world truth. This is a retrospective single-maintainer source-publication audit.
- Primary source
- NASA Robotic Interface Best Practices and Lessons Learned for Surface Operations
- Section locator
PDF page 10- Captured
- 2026-08-04
- Source SHA-256
fee6644426a6db1a72984d7ec2224288899582b03f04dae7b041a01b4eacffb8- Reproduction
- Maintainer run only; no independent operator rerun is registered.
Repeat this exact check locally
Download the PDF to a local file, then run the committed verifier. A changed PDF is reported as drift rather than silently accepted.
python scripts/verify_primary_public_claim_group.py artifacts/cb7k_dom007_t01_primary_claims.json --source-file <local-raw-pdf>Exact source quote
This document is a Data Managed (DM) product that is managed by the product owners and does not require board approval to be changed.
6. NASA Robotic Interface Best Practices and Lessons Learned for Surface Operations · PDF page 10
Narrow public claim
The intention is to continually update this document as the robotics community learns more about the use of new robotic systems, especially in lunar environments.
What this card proves
The exact quoted statement occurred in the named official PDF fetched on 2026-08-04, and the complete PDF matched the recorded SHA-256.
What this card does not prove
It does not independently establish the underlying model capability, safety, comparison, or real-world truth. This is a retrospective single-maintainer source-publication audit.
- Primary source
- NASA Robotic Interface Best Practices and Lessons Learned for Surface Operations
- Section locator
PDF page 10- Captured
- 2026-08-04
- Source SHA-256
fee6644426a6db1a72984d7ec2224288899582b03f04dae7b041a01b4eacffb8- Reproduction
- Maintainer run only; no independent operator rerun is registered.
Repeat this exact check locally
Download the PDF to a local file, then run the committed verifier. A changed PDF is reported as drift rather than silently accepted.
python scripts/verify_primary_public_claim_group.py artifacts/cb7k_dom007_t01_primary_claims.json --source-file <local-raw-pdf>Exact source quote
The intention is to continually update this document as the robotics community learns more about the use of new robotic systems, especially in lunar environments.
7. NASA Robotic Interface Best Practices and Lessons Learned for Surface Operations · PDF page 10
Narrow public claim
A reference document is a document that provides additional information for the reader and may contain other interoperability standards or best practices outside the scope of this document (Ex.
What this card proves
The exact quoted statement occurred in the named official PDF fetched on 2026-08-04, and the complete PDF matched the recorded SHA-256.
What this card does not prove
It does not independently establish the underlying model capability, safety, comparison, or real-world truth. This is a retrospective single-maintainer source-publication audit.
- Primary source
- NASA Robotic Interface Best Practices and Lessons Learned for Surface Operations
- Section locator
PDF page 10- Captured
- 2026-08-04
- Source SHA-256
fee6644426a6db1a72984d7ec2224288899582b03f04dae7b041a01b4eacffb8- Reproduction
- Maintainer run only; no independent operator rerun is registered.
Repeat this exact check locally
Download the PDF to a local file, then run the committed verifier. A changed PDF is reported as drift rather than silently accepted.
python scripts/verify_primary_public_claim_group.py artifacts/cb7k_dom007_t01_primary_claims.json --source-file <local-raw-pdf>Exact source quote
A reference document is a document that provides additional information for the reader and may contain other interoperability standards or best practices outside the scope of this document (Ex.
8. NASA Robotic Interface Best Practices and Lessons Learned for Surface Operations · PDF page 11
Narrow public claim
Definition Document (IDSS IDD) Lunar Surface Command and Control M2M-43025 Baseline Interoperability (LuCCI) Project Interoperability Requirements Classifications and Requirements for Testing NASA-STD-1008 Baseline Systems and Hardware to Be Exposed to Dust in Planetary Environments NASA Spaceflight Human-System Standard NASA-STD-3001 Volume 2, Rev.
What this card proves
The exact quoted statement occurred in the named official PDF fetched on 2026-08-04, and the complete PDF matched the recorded SHA-256.
What this card does not prove
It does not independently establish the underlying model capability, safety, comparison, or real-world truth. This is a retrospective single-maintainer source-publication audit.
- Primary source
- NASA Robotic Interface Best Practices and Lessons Learned for Surface Operations
- Section locator
PDF page 11- Captured
- 2026-08-04
- Source SHA-256
fee6644426a6db1a72984d7ec2224288899582b03f04dae7b041a01b4eacffb8- Reproduction
- Maintainer run only; no independent operator rerun is registered.
Repeat this exact check locally
Download the PDF to a local file, then run the committed verifier. A changed PDF is reported as drift rather than silently accepted.
python scripts/verify_primary_public_claim_group.py artifacts/cb7k_dom007_t01_primary_claims.json --source-file <local-raw-pdf>Exact source quote
Definition Document (IDSS IDD) Lunar Surface Command and Control M2M-43025 Baseline Interoperability (LuCCI) Project Interoperability Requirements Classifications and Requirements for Testing NASA-STD-1008 Baseline Systems and Hardware to Be Exposed to Dust in Planetary Environments NASA Spaceflight Human-System Standard NASA-STD-3001 Volume 2, Rev.
9. NASA Robotic Interface Best Practices and Lessons Learned for Surface Operations · PDF page 12
Narrow public claim
The definitions in Section 3.1 are a combination of definitions from other documents that are summarized here for completeness and several terminology definitions from within NASA that are critical to understanding some of the best practices and lessons learned within this document.
What this card proves
The exact quoted statement occurred in the named official PDF fetched on 2026-08-04, and the complete PDF matched the recorded SHA-256.
What this card does not prove
It does not independently establish the underlying model capability, safety, comparison, or real-world truth. This is a retrospective single-maintainer source-publication audit.
- Primary source
- NASA Robotic Interface Best Practices and Lessons Learned for Surface Operations
- Section locator
PDF page 12- Captured
- 2026-08-04
- Source SHA-256
fee6644426a6db1a72984d7ec2224288899582b03f04dae7b041a01b4eacffb8- Reproduction
- Maintainer run only; no independent operator rerun is registered.
Repeat this exact check locally
Download the PDF to a local file, then run the committed verifier. A changed PDF is reported as drift rather than silently accepted.
python scripts/verify_primary_public_claim_group.py artifacts/cb7k_dom007_t01_primary_claims.json --source-file <local-raw-pdf>Exact source quote
The definitions in Section 3.1 are a combination of definitions from other documents that are summarized here for completeness and several terminology definitions from within NASA that are critical to understanding some of the best practices and lessons learned within this document.
10. NASA Robotic Interface Best Practices and Lessons Learned for Surface Operations · PDF page 12
Narrow public claim
The coordinate frames used within this document are as defined in Section 3.2 and Figure 3-1 through Figure 3-5.
What this card proves
The exact quoted statement occurred in the named official PDF fetched on 2026-08-04, and the complete PDF matched the recorded SHA-256.
What this card does not prove
It does not independently establish the underlying model capability, safety, comparison, or real-world truth. This is a retrospective single-maintainer source-publication audit.
- Primary source
- NASA Robotic Interface Best Practices and Lessons Learned for Surface Operations
- Section locator
PDF page 12- Captured
- 2026-08-04
- Source SHA-256
fee6644426a6db1a72984d7ec2224288899582b03f04dae7b041a01b4eacffb8- Reproduction
- Maintainer run only; no independent operator rerun is registered.
Repeat this exact check locally
Download the PDF to a local file, then run the committed verifier. A changed PDF is reported as drift rather than silently accepted.
python scripts/verify_primary_public_claim_group.py artifacts/cb7k_dom007_t01_primary_claims.json --source-file <local-raw-pdf>Exact source quote
The coordinate frames used within this document are as defined in Section 3.2 and Figure 3-1 through Figure 3-5.
11. NASA Robotic Interface Best Practices and Lessons Learned for Surface Operations · PDF page 12
Narrow public claim
(From EHP-10012 RV B) The ability of a system to achieve goals in a dynamic environment while operating independently of external Autonomy controls; includes the deliberate allocation of authority and responsibility for specific functions or behaviors to an Actor (or agent).
What this card proves
The exact quoted statement occurred in the named official PDF fetched on 2026-08-04, and the complete PDF matched the recorded SHA-256.
What this card does not prove
It does not independently establish the underlying model capability, safety, comparison, or real-world truth. This is a retrospective single-maintainer source-publication audit.
- Primary source
- NASA Robotic Interface Best Practices and Lessons Learned for Surface Operations
- Section locator
PDF page 12- Captured
- 2026-08-04
- Source SHA-256
fee6644426a6db1a72984d7ec2224288899582b03f04dae7b041a01b4eacffb8- Reproduction
- Maintainer run only; no independent operator rerun is registered.
Repeat this exact check locally
Download the PDF to a local file, then run the committed verifier. A changed PDF is reported as drift rather than silently accepted.
python scripts/verify_primary_public_claim_group.py artifacts/cb7k_dom007_t02_primary_claims.json --source-file <local-raw-pdf>Exact source quote
(From EHP-10012 RV B) The ability of a system to achieve goals in a dynamic environment while operating independently of external Autonomy controls; includes the deliberate allocation of authority and responsibility for specific functions or behaviors to an Actor (or agent).
12. NASA Robotic Interface Best Practices and Lessons Learned for Surface Operations · PDF page 12
Narrow public claim
(From EHP-10012 REV B) While not considered requirements, best practices are highly desirable for the design of hardware compatibility Best Practice with future robotics interfaces.
What this card proves
The exact quoted statement occurred in the named official PDF fetched on 2026-08-04, and the complete PDF matched the recorded SHA-256.
What this card does not prove
It does not independently establish the underlying model capability, safety, comparison, or real-world truth. This is a retrospective single-maintainer source-publication audit.
- Primary source
- NASA Robotic Interface Best Practices and Lessons Learned for Surface Operations
- Section locator
PDF page 12- Captured
- 2026-08-04
- Source SHA-256
fee6644426a6db1a72984d7ec2224288899582b03f04dae7b041a01b4eacffb8- Reproduction
- Maintainer run only; no independent operator rerun is registered.
Repeat this exact check locally
Download the PDF to a local file, then run the committed verifier. A changed PDF is reported as drift rather than silently accepted.
python scripts/verify_primary_public_claim_group.py artifacts/cb7k_dom007_t02_primary_claims.json --source-file <local-raw-pdf>Exact source quote
(From EHP-10012 REV B) While not considered requirements, best practices are highly desirable for the design of hardware compatibility Best Practice with future robotics interfaces.
13. NASA Robotic Interface Best Practices and Lessons Learned for Surface Operations · PDF page 13
Narrow public claim
Lessons learned come from the experiences of various robotic experts and provide insight into how a particular Lesson Learned design choice or action may have either adversely or positively affected the outcome of a robotic task.
What this card proves
The exact quoted statement occurred in the named official PDF fetched on 2026-08-04, and the complete PDF matched the recorded SHA-256.
What this card does not prove
It does not independently establish the underlying model capability, safety, comparison, or real-world truth. This is a retrospective single-maintainer source-publication audit.
- Primary source
- NASA Robotic Interface Best Practices and Lessons Learned for Surface Operations
- Section locator
PDF page 13- Captured
- 2026-08-04
- Source SHA-256
fee6644426a6db1a72984d7ec2224288899582b03f04dae7b041a01b4eacffb8- Reproduction
- Maintainer run only; no independent operator rerun is registered.
Repeat this exact check locally
Download the PDF to a local file, then run the committed verifier. A changed PDF is reported as drift rather than silently accepted.
python scripts/verify_primary_public_claim_group.py artifacts/cb7k_dom007_t02_primary_claims.json --source-file <local-raw-pdf>Exact source quote
Lessons learned come from the experiences of various robotic experts and provide insight into how a particular Lesson Learned design choice or action may have either adversely or positively affected the outcome of a robotic task.
14. NASA Robotic Interface Best Practices and Lessons Learned for Surface Operations · PDF page 13
Narrow public claim
This includes the opening of any isolation devices and joining of electrical and data pins and sockets necessary to provide full umbilical services.
What this card proves
The exact quoted statement occurred in the named official PDF fetched on 2026-08-04, and the complete PDF matched the recorded SHA-256.
What this card does not prove
It does not independently establish the underlying model capability, safety, comparison, or real-world truth. This is a retrospective single-maintainer source-publication audit.
- Primary source
- NASA Robotic Interface Best Practices and Lessons Learned for Surface Operations
- Section locator
PDF page 13- Captured
- 2026-08-04
- Source SHA-256
fee6644426a6db1a72984d7ec2224288899582b03f04dae7b041a01b4eacffb8- Reproduction
- Maintainer run only; no independent operator rerun is registered.
Repeat this exact check locally
Download the PDF to a local file, then run the committed verifier. A changed PDF is reported as drift rather than silently accepted.
python scripts/verify_primary_public_claim_group.py artifacts/cb7k_dom007_t02_primary_claims.json --source-file <local-raw-pdf>Exact source quote
This includes the opening of any isolation devices and joining of electrical and data pins and sockets necessary to provide full umbilical services.
15. NASA Robotic Interface Best Practices and Lessons Learned for Surface Operations · PDF page 13
Narrow public claim
To aid in visualization and application to any specific future system, the placement of coordinate frames has been described and illustrated in such a way that any potential system, regardless of purpose, sensor package, or size should be able to be placed within the frames for reader comprehension.
What this card proves
The exact quoted statement occurred in the named official PDF fetched on 2026-08-04, and the complete PDF matched the recorded SHA-256.
What this card does not prove
It does not independently establish the underlying model capability, safety, comparison, or real-world truth. This is a retrospective single-maintainer source-publication audit.
- Primary source
- NASA Robotic Interface Best Practices and Lessons Learned for Surface Operations
- Section locator
PDF page 13- Captured
- 2026-08-04
- Source SHA-256
fee6644426a6db1a72984d7ec2224288899582b03f04dae7b041a01b4eacffb8- Reproduction
- Maintainer run only; no independent operator rerun is registered.
Repeat this exact check locally
Download the PDF to a local file, then run the committed verifier. A changed PDF is reported as drift rather than silently accepted.
python scripts/verify_primary_public_claim_group.py artifacts/cb7k_dom007_t02_primary_claims.json --source-file <local-raw-pdf>Exact source quote
To aid in visualization and application to any specific future system, the placement of coordinate frames has been described and illustrated in such a way that any potential system, regardless of purpose, sensor package, or size should be able to be placed within the frames for reader comprehension.
16. NASA Robotic Interface Best Practices and Lessons Learned for Surface Operations · PDF page 13
Narrow public claim
While any future system need not follow the coordinate frames described herein, they are recommended as they align with existing space robotic operational and design practices.
What this card proves
The exact quoted statement occurred in the named official PDF fetched on 2026-08-04, and the complete PDF matched the recorded SHA-256.
What this card does not prove
It does not independently establish the underlying model capability, safety, comparison, or real-world truth. This is a retrospective single-maintainer source-publication audit.
- Primary source
- NASA Robotic Interface Best Practices and Lessons Learned for Surface Operations
- Section locator
PDF page 13- Captured
- 2026-08-04
- Source SHA-256
fee6644426a6db1a72984d7ec2224288899582b03f04dae7b041a01b4eacffb8- Reproduction
- Maintainer run only; no independent operator rerun is registered.
Repeat this exact check locally
Download the PDF to a local file, then run the committed verifier. A changed PDF is reported as drift rather than silently accepted.
python scripts/verify_primary_public_claim_group.py artifacts/cb7k_dom007_t02_primary_claims.json --source-file <local-raw-pdf>Exact source quote
While any future system need not follow the coordinate frames described herein, they are recommended as they align with existing space robotic operational and design practices.
17. NASA Robotic Interface Best Practices and Lessons Learned for Surface Operations · PDF page 14
Narrow public claim
The positive direction on this axis should be in the direction most towards any electrical connectors on the Outer Mold Line (OML) of the EE as shown on an example EE in Figure 3-2.
What this card proves
The exact quoted statement occurred in the named official PDF fetched on 2026-08-04, and the complete PDF matched the recorded SHA-256.
What this card does not prove
It does not independently establish the underlying model capability, safety, comparison, or real-world truth. This is a retrospective single-maintainer source-publication audit.
- Primary source
- NASA Robotic Interface Best Practices and Lessons Learned for Surface Operations
- Section locator
PDF page 14- Captured
- 2026-08-04
- Source SHA-256
fee6644426a6db1a72984d7ec2224288899582b03f04dae7b041a01b4eacffb8- Reproduction
- Maintainer run only; no independent operator rerun is registered.
Repeat this exact check locally
Download the PDF to a local file, then run the committed verifier. A changed PDF is reported as drift rather than silently accepted.
python scripts/verify_primary_public_claim_group.py artifacts/cb7k_dom007_t02_primary_claims.json --source-file <local-raw-pdf>Exact source quote
The positive direction on this axis should be in the direction most towards any electrical connectors on the Outer Mold Line (OML) of the EE as shown on an example EE in Figure 3-2.
18. NASA Robotic Interface Best Practices and Lessons Learned for Surface Operations · PDF page 14
Narrow public claim
If the entire end effector is perfectly symmetric, then a clocking feature should be added to the design on the OML or mating plane.
What this card proves
The exact quoted statement occurred in the named official PDF fetched on 2026-08-04, and the complete PDF matched the recorded SHA-256.
What this card does not prove
It does not independently establish the underlying model capability, safety, comparison, or real-world truth. This is a retrospective single-maintainer source-publication audit.
- Primary source
- NASA Robotic Interface Best Practices and Lessons Learned for Surface Operations
- Section locator
PDF page 14- Captured
- 2026-08-04
- Source SHA-256
fee6644426a6db1a72984d7ec2224288899582b03f04dae7b041a01b4eacffb8- Reproduction
- Maintainer run only; no independent operator rerun is registered.
Repeat this exact check locally
Download the PDF to a local file, then run the committed verifier. A changed PDF is reported as drift rather than silently accepted.
python scripts/verify_primary_public_claim_group.py artifacts/cb7k_dom007_t02_primary_claims.json --source-file <local-raw-pdf>Exact source quote
If the entire end effector is perfectly symmetric, then a clocking feature should be added to the design on the OML or mating plane.
19. NASA Robotic Interface Best Practices and Lessons Learned for Surface Operations · PDF page 14
Narrow public claim
This is shown on an example EE in Figure 3-3 Figure 3-1: Robotic System End Effector Standard Operational Coordinate Frame for End Effectors with Alignment sensors.
What this card proves
The exact quoted statement occurred in the named official PDF fetched on 2026-08-04, and the complete PDF matched the recorded SHA-256.
What this card does not prove
It does not independently establish the underlying model capability, safety, comparison, or real-world truth. This is a retrospective single-maintainer source-publication audit.
- Primary source
- NASA Robotic Interface Best Practices and Lessons Learned for Surface Operations
- Section locator
PDF page 14- Captured
- 2026-08-04
- Source SHA-256
fee6644426a6db1a72984d7ec2224288899582b03f04dae7b041a01b4eacffb8- Reproduction
- Maintainer run only; no independent operator rerun is registered.
Repeat this exact check locally
Download the PDF to a local file, then run the committed verifier. A changed PDF is reported as drift rather than silently accepted.
python scripts/verify_primary_public_claim_group.py artifacts/cb7k_dom007_t02_primary_claims.json --source-file <local-raw-pdf>Exact source quote
This is shown on an example EE in Figure 3-3 Figure 3-1: Robotic System End Effector Standard Operational Coordinate Frame for End Effectors with Alignment sensors.
20. NASA Robotic Interface Best Practices and Lessons Learned for Surface Operations · PDF page 15
Narrow public claim
If applicable, the mating interface frame +z-axis should point radially away from a selected alignment sensor or feature.
What this card proves
The exact quoted statement occurred in the named official PDF fetched on 2026-08-04, and the complete PDF matched the recorded SHA-256.
What this card does not prove
It does not independently establish the underlying model capability, safety, comparison, or real-world truth. This is a retrospective single-maintainer source-publication audit.
- Primary source
- NASA Robotic Interface Best Practices and Lessons Learned for Surface Operations
- Section locator
PDF page 15- Captured
- 2026-08-04
- Source SHA-256
fee6644426a6db1a72984d7ec2224288899582b03f04dae7b041a01b4eacffb8- Reproduction
- Maintainer run only; no independent operator rerun is registered.
Repeat this exact check locally
Download the PDF to a local file, then run the committed verifier. A changed PDF is reported as drift rather than silently accepted.
python scripts/verify_primary_public_claim_group.py artifacts/cb7k_dom007_t02_primary_claims.json --source-file <local-raw-pdf>Exact source quote
If applicable, the mating interface frame +z-axis should point radially away from a selected alignment sensor or feature.
21. NASA Robotic Interface Best Practices and Lessons Learned for Surface Operations · PDF page 15
Narrow public claim
The mating coordinate frame should be identifiable to an approaching crew member or autonomous system by an alignment reference marking (arrow, light, etc.) on the system the interface is placed upon.
What this card proves
The exact quoted statement occurred in the named official PDF fetched on 2026-08-04, and the complete PDF matched the recorded SHA-256.
What this card does not prove
It does not independently establish the underlying model capability, safety, comparison, or real-world truth. This is a retrospective single-maintainer source-publication audit.
- Primary source
- NASA Robotic Interface Best Practices and Lessons Learned for Surface Operations
- Section locator
PDF page 15- Captured
- 2026-08-04
- Source SHA-256
fee6644426a6db1a72984d7ec2224288899582b03f04dae7b041a01b4eacffb8- Reproduction
- Maintainer run only; no independent operator rerun is registered.
Repeat this exact check locally
Download the PDF to a local file, then run the committed verifier. A changed PDF is reported as drift rather than silently accepted.
python scripts/verify_primary_public_claim_group.py artifacts/cb7k_dom007_t03_primary_claims.json --source-file <local-raw-pdf>Exact source quote
The mating coordinate frame should be identifiable to an approaching crew member or autonomous system by an alignment reference marking (arrow, light, etc.) on the system the interface is placed upon.
22. NASA Robotic Interface Best Practices and Lessons Learned for Surface Operations · PDF page 17
Narrow public claim
EVRBP-0001 Keep Out Zones During concurrent EVA and EVR operations, EVA keep-out zones should be clearly defined and indicated around the worksite in a manner perceivable by the robotic system.
What this card proves
The exact quoted statement occurred in the named official PDF fetched on 2026-08-04, and the complete PDF matched the recorded SHA-256.
What this card does not prove
It does not independently establish the underlying model capability, safety, comparison, or real-world truth. This is a retrospective single-maintainer source-publication audit.
- Primary source
- NASA Robotic Interface Best Practices and Lessons Learned for Surface Operations
- Section locator
PDF page 17- Captured
- 2026-08-04
- Source SHA-256
fee6644426a6db1a72984d7ec2224288899582b03f04dae7b041a01b4eacffb8- Reproduction
- Maintainer run only; no independent operator rerun is registered.
Repeat this exact check locally
Download the PDF to a local file, then run the committed verifier. A changed PDF is reported as drift rather than silently accepted.
python scripts/verify_primary_public_claim_group.py artifacts/cb7k_dom007_t03_primary_claims.json --source-file <local-raw-pdf>Exact source quote
EVRBP-0001 Keep Out Zones During concurrent EVA and EVR operations, EVA keep-out zones should be clearly defined and indicated around the worksite in a manner perceivable by the robotic system.
23. NASA Robotic Interface Best Practices and Lessons Learned for Surface Operations · PDF page 17
Narrow public claim
Rationale: The crew’s Situation Awareness (SA) may be stretched while performing EVA and having clearly defined keep-out zones that are indicated in some way (ex., labels, lights, etc.) will provide an added buffer for the crew’s safety and awareness, and enable robotic systems to comprehend areas that are dangerous to operate in when crew are present.
What this card proves
The exact quoted statement occurred in the named official PDF fetched on 2026-08-04, and the complete PDF matched the recorded SHA-256.
What this card does not prove
It does not independently establish the underlying model capability, safety, comparison, or real-world truth. This is a retrospective single-maintainer source-publication audit.
- Primary source
- NASA Robotic Interface Best Practices and Lessons Learned for Surface Operations
- Section locator
PDF page 17- Captured
- 2026-08-04
- Source SHA-256
fee6644426a6db1a72984d7ec2224288899582b03f04dae7b041a01b4eacffb8- Reproduction
- Maintainer run only; no independent operator rerun is registered.
Repeat this exact check locally
Download the PDF to a local file, then run the committed verifier. A changed PDF is reported as drift rather than silently accepted.
python scripts/verify_primary_public_claim_group.py artifacts/cb7k_dom007_t03_primary_claims.json --source-file <local-raw-pdf>Exact source quote
Rationale: The crew’s Situation Awareness (SA) may be stretched while performing EVA and having clearly defined keep-out zones that are indicated in some way (ex., labels, lights, etc.) will provide an added buffer for the crew’s safety and awareness, and enable robotic systems to comprehend areas that are dangerous to operate in when crew are present.
24. NASA Robotic Interface Best Practices and Lessons Learned for Surface Operations · PDF page 17
Narrow public claim
When robotic systems are in use (automated, IVA operated, or ground operated), they should be able to respond to stimulus (external) or on-board recognition such that when crew enter an area of operations and breaches a robotic workspace (keep-out zone), the robotic system pauses in a safe configuration until crew exits the area.
What this card proves
The exact quoted statement occurred in the named official PDF fetched on 2026-08-04, and the complete PDF matched the recorded SHA-256.
What this card does not prove
It does not independently establish the underlying model capability, safety, comparison, or real-world truth. This is a retrospective single-maintainer source-publication audit.
- Primary source
- NASA Robotic Interface Best Practices and Lessons Learned for Surface Operations
- Section locator
PDF page 17- Captured
- 2026-08-04
- Source SHA-256
fee6644426a6db1a72984d7ec2224288899582b03f04dae7b041a01b4eacffb8- Reproduction
- Maintainer run only; no independent operator rerun is registered.
Repeat this exact check locally
Download the PDF to a local file, then run the committed verifier. A changed PDF is reported as drift rather than silently accepted.
python scripts/verify_primary_public_claim_group.py artifacts/cb7k_dom007_t03_primary_claims.json --source-file <local-raw-pdf>Exact source quote
When robotic systems are in use (automated, IVA operated, or ground operated), they should be able to respond to stimulus (external) or on-board recognition such that when crew enter an area of operations and breaches a robotic workspace (keep-out zone), the robotic system pauses in a safe configuration until crew exits the area.
25. NASA Robotic Interface Best Practices and Lessons Learned for Surface Operations · PDF page 17
Narrow public claim
EVRBP-0002 Softgoods Restraints Softgoods (ex., EVA handles, tethers), cables, and hoses that are not intended for robotic interaction should be constrained in such a way that they are kept clear of robotic grasp areas, targets, and worksites even after incidental contact or under dynamic conditions.
What this card proves
The exact quoted statement occurred in the named official PDF fetched on 2026-08-04, and the complete PDF matched the recorded SHA-256.
What this card does not prove
It does not independently establish the underlying model capability, safety, comparison, or real-world truth. This is a retrospective single-maintainer source-publication audit.
- Primary source
- NASA Robotic Interface Best Practices and Lessons Learned for Surface Operations
- Section locator
PDF page 17- Captured
- 2026-08-04
- Source SHA-256
fee6644426a6db1a72984d7ec2224288899582b03f04dae7b041a01b4eacffb8- Reproduction
- Maintainer run only; no independent operator rerun is registered.
Repeat this exact check locally
Download the PDF to a local file, then run the committed verifier. A changed PDF is reported as drift rather than silently accepted.
python scripts/verify_primary_public_claim_group.py artifacts/cb7k_dom007_t03_primary_claims.json --source-file <local-raw-pdf>Exact source quote
EVRBP-0002 Softgoods Restraints Softgoods (ex., EVA handles, tethers), cables, and hoses that are not intended for robotic interaction should be constrained in such a way that they are kept clear of robotic grasp areas, targets, and worksites even after incidental contact or under dynamic conditions.
26. NASA Robotic Interface Best Practices and Lessons Learned for Surface Operations · PDF page 18
Narrow public claim
EVRBP-0004 Shared EVA and EVR Interface Loads The forces and torques required for actuation (Push, Pull, Twist, or combinations) and insertion of/into interfaces should be minimized where practical and should not exceed the maximum EVA loads defined within EHP-10028 and NASA-STD-3001.
What this card proves
The exact quoted statement occurred in the named official PDF fetched on 2026-08-04, and the complete PDF matched the recorded SHA-256.
What this card does not prove
It does not independently establish the underlying model capability, safety, comparison, or real-world truth. This is a retrospective single-maintainer source-publication audit.
- Primary source
- NASA Robotic Interface Best Practices and Lessons Learned for Surface Operations
- Section locator
PDF page 18- Captured
- 2026-08-04
- Source SHA-256
fee6644426a6db1a72984d7ec2224288899582b03f04dae7b041a01b4eacffb8- Reproduction
- Maintainer run only; no independent operator rerun is registered.
Repeat this exact check locally
Download the PDF to a local file, then run the committed verifier. A changed PDF is reported as drift rather than silently accepted.
python scripts/verify_primary_public_claim_group.py artifacts/cb7k_dom007_t03_primary_claims.json --source-file <local-raw-pdf>Exact source quote
EVRBP-0004 Shared EVA and EVR Interface Loads The forces and torques required for actuation (Push, Pull, Twist, or combinations) and insertion of/into interfaces should be minimized where practical and should not exceed the maximum EVA loads defined within EHP-10028 and NASA-STD-3001.
27. NASA Robotic Interface Best Practices and Lessons Learned for Surface Operations · PDF page 18
Narrow public claim
EVRBP-0005 Robotic Interoperability Standardization Robotic system interfaces should adopt a set of unified design standards emphasizing interface commonality and interoperability, where feasible, for both the human-robot interface and the robot-hardware interface design.
What this card proves
The exact quoted statement occurred in the named official PDF fetched on 2026-08-04, and the complete PDF matched the recorded SHA-256.
What this card does not prove
It does not independently establish the underlying model capability, safety, comparison, or real-world truth. This is a retrospective single-maintainer source-publication audit.
- Primary source
- NASA Robotic Interface Best Practices and Lessons Learned for Surface Operations
- Section locator
PDF page 18- Captured
- 2026-08-04
- Source SHA-256
fee6644426a6db1a72984d7ec2224288899582b03f04dae7b041a01b4eacffb8- Reproduction
- Maintainer run only; no independent operator rerun is registered.
Repeat this exact check locally
Download the PDF to a local file, then run the committed verifier. A changed PDF is reported as drift rather than silently accepted.
python scripts/verify_primary_public_claim_group.py artifacts/cb7k_dom007_t03_primary_claims.json --source-file <local-raw-pdf>Exact source quote
EVRBP-0005 Robotic Interoperability Standardization Robotic system interfaces should adopt a set of unified design standards emphasizing interface commonality and interoperability, where feasible, for both the human-robot interface and the robot-hardware interface design.
28. NASA Robotic Interface Best Practices and Lessons Learned for Surface Operations · PDF page 18
Narrow public claim
Ethercat, Controller Area Network (CAN), MIL STD 1553), along with limiting the number of physical interface variants, simplifies mission logistics by reducing the need to carry, maintain, and replace multiple unique and/or specialized supporting parts or adapters in environments where mass and volume are at a premium.
What this card proves
The exact quoted statement occurred in the named official PDF fetched on 2026-08-04, and the complete PDF matched the recorded SHA-256.
What this card does not prove
It does not independently establish the underlying model capability, safety, comparison, or real-world truth. This is a retrospective single-maintainer source-publication audit.
- Primary source
- NASA Robotic Interface Best Practices and Lessons Learned for Surface Operations
- Section locator
PDF page 18- Captured
- 2026-08-04
- Source SHA-256
fee6644426a6db1a72984d7ec2224288899582b03f04dae7b041a01b4eacffb8- Reproduction
- Maintainer run only; no independent operator rerun is registered.
Repeat this exact check locally
Download the PDF to a local file, then run the committed verifier. A changed PDF is reported as drift rather than silently accepted.
python scripts/verify_primary_public_claim_group.py artifacts/cb7k_dom007_t03_primary_claims.json --source-file <local-raw-pdf>Exact source quote
Ethercat, Controller Area Network (CAN), MIL STD 1553), along with limiting the number of physical interface variants, simplifies mission logistics by reducing the need to carry, maintain, and replace multiple unique and/or specialized supporting parts or adapters in environments where mass and volume are at a premium.
29. NASA Robotic Interface Best Practices and Lessons Learned for Surface Operations · PDF page 19
Narrow public claim
EVRBP-0006 Sequential Mating Concepts of Operations Interfaces should not expect robotic systems to be able to provide multiple simultaneous actions.
What this card proves
The exact quoted statement occurred in the named official PDF fetched on 2026-08-04, and the complete PDF matched the recorded SHA-256.
What this card does not prove
It does not independently establish the underlying model capability, safety, comparison, or real-world truth. This is a retrospective single-maintainer source-publication audit.
- Primary source
- NASA Robotic Interface Best Practices and Lessons Learned for Surface Operations
- Section locator
PDF page 19- Captured
- 2026-08-04
- Source SHA-256
fee6644426a6db1a72984d7ec2224288899582b03f04dae7b041a01b4eacffb8- Reproduction
- Maintainer run only; no independent operator rerun is registered.
Repeat this exact check locally
Download the PDF to a local file, then run the committed verifier. A changed PDF is reported as drift rather than silently accepted.
python scripts/verify_primary_public_claim_group.py artifacts/cb7k_dom007_t03_primary_claims.json --source-file <local-raw-pdf>Exact source quote
EVRBP-0006 Sequential Mating Concepts of Operations Interfaces should not expect robotic systems to be able to provide multiple simultaneous actions.
30. NASA Robotic Interface Best Practices and Lessons Learned for Surface Operations · PDF page 19
Narrow public claim
Items such as 38999 connectors should be avoided if possible as they require fine alignment, moderate force, and rotation all at the same time.
What this card proves
The exact quoted statement occurred in the named official PDF fetched on 2026-08-04, and the complete PDF matched the recorded SHA-256.
What this card does not prove
It does not independently establish the underlying model capability, safety, comparison, or real-world truth. This is a retrospective single-maintainer source-publication audit.
- Primary source
- NASA Robotic Interface Best Practices and Lessons Learned for Surface Operations
- Section locator
PDF page 19- Captured
- 2026-08-04
- Source SHA-256
fee6644426a6db1a72984d7ec2224288899582b03f04dae7b041a01b4eacffb8- Reproduction
- Maintainer run only; no independent operator rerun is registered.
Repeat this exact check locally
Download the PDF to a local file, then run the committed verifier. A changed PDF is reported as drift rather than silently accepted.
python scripts/verify_primary_public_claim_group.py artifacts/cb7k_dom007_t03_primary_claims.json --source-file <local-raw-pdf>Exact source quote
Items such as 38999 connectors should be avoided if possible as they require fine alignment, moderate force, and rotation all at the same time.
31. NASA Robotic Interface Best Practices and Lessons Learned for Surface Operations · PDF page 19
Narrow public claim
EVRBP-0008 Unique Identification of Payloads and Respective Interfaces Items that will be grasped by a robotic system should be identifiably distinct from other nearby objects.
What this card proves
The exact quoted statement occurred in the named official PDF fetched on 2026-08-04, and the complete PDF matched the recorded SHA-256.
What this card does not prove
It does not independently establish the underlying model capability, safety, comparison, or real-world truth. This is a retrospective single-maintainer source-publication audit.
- Primary source
- NASA Robotic Interface Best Practices and Lessons Learned for Surface Operations
- Section locator
PDF page 19- Captured
- 2026-08-04
- Source SHA-256
fee6644426a6db1a72984d7ec2224288899582b03f04dae7b041a01b4eacffb8- Reproduction
- Maintainer run only; no independent operator rerun is registered.
Repeat this exact check locally
Download the PDF to a local file, then run the committed verifier. A changed PDF is reported as drift rather than silently accepted.
python scripts/verify_primary_public_claim_group.py artifacts/cb7k_dom007_t04_primary_claims.json --source-file <local-raw-pdf>Exact source quote
EVRBP-0008 Unique Identification of Payloads and Respective Interfaces Items that will be grasped by a robotic system should be identifiably distinct from other nearby objects.
32. NASA Robotic Interface Best Practices and Lessons Learned for Surface Operations · PDF page 20
Narrow public claim
EVRBP-0009 Connection Success Alerts Verification of successful connections from inserting or plugging in any connector should be provided in at least two dissimilar modalities to the robotic system on the surface.
What this card proves
The exact quoted statement occurred in the named official PDF fetched on 2026-08-04, and the complete PDF matched the recorded SHA-256.
What this card does not prove
It does not independently establish the underlying model capability, safety, comparison, or real-world truth. This is a retrospective single-maintainer source-publication audit.
- Primary source
- NASA Robotic Interface Best Practices and Lessons Learned for Surface Operations
- Section locator
PDF page 20- Captured
- 2026-08-04
- Source SHA-256
fee6644426a6db1a72984d7ec2224288899582b03f04dae7b041a01b4eacffb8- Reproduction
- Maintainer run only; no independent operator rerun is registered.
Repeat this exact check locally
Download the PDF to a local file, then run the committed verifier. A changed PDF is reported as drift rather than silently accepted.
python scripts/verify_primary_public_claim_group.py artifacts/cb7k_dom007_t04_primary_claims.json --source-file <local-raw-pdf>Exact source quote
EVRBP-0009 Connection Success Alerts Verification of successful connections from inserting or plugging in any connector should be provided in at least two dissimilar modalities to the robotic system on the surface.
33. NASA Robotic Interface Best Practices and Lessons Learned for Surface Operations · PDF page 20
Narrow public claim
EVRBP-0011 Mechanical Alignment Aids Mating or alignment operations should be assisted by guiding features included on the objects being aligned.
What this card proves
The exact quoted statement occurred in the named official PDF fetched on 2026-08-04, and the complete PDF matched the recorded SHA-256.
What this card does not prove
It does not independently establish the underlying model capability, safety, comparison, or real-world truth. This is a retrospective single-maintainer source-publication audit.
- Primary source
- NASA Robotic Interface Best Practices and Lessons Learned for Surface Operations
- Section locator
PDF page 20- Captured
- 2026-08-04
- Source SHA-256
fee6644426a6db1a72984d7ec2224288899582b03f04dae7b041a01b4eacffb8- Reproduction
- Maintainer run only; no independent operator rerun is registered.
Repeat this exact check locally
Download the PDF to a local file, then run the committed verifier. A changed PDF is reported as drift rather than silently accepted.
python scripts/verify_primary_public_claim_group.py artifacts/cb7k_dom007_t04_primary_claims.json --source-file <local-raw-pdf>Exact source quote
EVRBP-0011 Mechanical Alignment Aids Mating or alignment operations should be assisted by guiding features included on the objects being aligned.
34. NASA Robotic Interface Best Practices and Lessons Learned for Surface Operations · PDF page 21
Narrow public claim
EVRBP-0012 Marking and Identification of Interface Grasp Location Grasp locations on the object being robotically manipulated should be visually distinct with contrasting colors and other identifiable features from the rest of the object and the surrounding environment.
What this card proves
The exact quoted statement occurred in the named official PDF fetched on 2026-08-04, and the complete PDF matched the recorded SHA-256.
What this card does not prove
It does not independently establish the underlying model capability, safety, comparison, or real-world truth. This is a retrospective single-maintainer source-publication audit.
- Primary source
- NASA Robotic Interface Best Practices and Lessons Learned for Surface Operations
- Section locator
PDF page 21- Captured
- 2026-08-04
- Source SHA-256
fee6644426a6db1a72984d7ec2224288899582b03f04dae7b041a01b4eacffb8- Reproduction
- Maintainer run only; no independent operator rerun is registered.
Repeat this exact check locally
Download the PDF to a local file, then run the committed verifier. A changed PDF is reported as drift rather than silently accepted.
python scripts/verify_primary_public_claim_group.py artifacts/cb7k_dom007_t04_primary_claims.json --source-file <local-raw-pdf>Exact source quote
EVRBP-0012 Marking and Identification of Interface Grasp Location Grasp locations on the object being robotically manipulated should be visually distinct with contrasting colors and other identifiable features from the rest of the object and the surrounding environment.
35. NASA Robotic Interface Best Practices and Lessons Learned for Surface Operations · PDF page 21
Narrow public claim
EVRBP-0013 Interface Orientation Preference Objects with preferred orientations or directions of motion should have those preferences clearly marked.
What this card proves
The exact quoted statement occurred in the named official PDF fetched on 2026-08-04, and the complete PDF matched the recorded SHA-256.
What this card does not prove
It does not independently establish the underlying model capability, safety, comparison, or real-world truth. This is a retrospective single-maintainer source-publication audit.
- Primary source
- NASA Robotic Interface Best Practices and Lessons Learned for Surface Operations
- Section locator
PDF page 21- Captured
- 2026-08-04
- Source SHA-256
fee6644426a6db1a72984d7ec2224288899582b03f04dae7b041a01b4eacffb8- Reproduction
- Maintainer run only; no independent operator rerun is registered.
Repeat this exact check locally
Download the PDF to a local file, then run the committed verifier. A changed PDF is reported as drift rather than silently accepted.
python scripts/verify_primary_public_claim_group.py artifacts/cb7k_dom007_t04_primary_claims.json --source-file <local-raw-pdf>Exact source quote
EVRBP-0013 Interface Orientation Preference Objects with preferred orientations or directions of motion should have those preferences clearly marked.
36. NASA Robotic Interface Best Practices and Lessons Learned for Surface Operations · PDF page 21
Narrow public claim
EVRBP-0014 Visual Grasp Target Identification When utilizing visual targets to localize interfaces (ex. fiducial markers, retro-reflective tape), targets should be placed non-planar (relative to the grasp interface) whenever possible.
What this card proves
The exact quoted statement occurred in the named official PDF fetched on 2026-08-04, and the complete PDF matched the recorded SHA-256.
What this card does not prove
It does not independently establish the underlying model capability, safety, comparison, or real-world truth. This is a retrospective single-maintainer source-publication audit.
- Primary source
- NASA Robotic Interface Best Practices and Lessons Learned for Surface Operations
- Section locator
PDF page 21- Captured
- 2026-08-04
- Source SHA-256
fee6644426a6db1a72984d7ec2224288899582b03f04dae7b041a01b4eacffb8- Reproduction
- Maintainer run only; no independent operator rerun is registered.
Repeat this exact check locally
Download the PDF to a local file, then run the committed verifier. A changed PDF is reported as drift rather than silently accepted.
python scripts/verify_primary_public_claim_group.py artifacts/cb7k_dom007_t04_primary_claims.json --source-file <local-raw-pdf>Exact source quote
EVRBP-0014 Visual Grasp Target Identification When utilizing visual targets to localize interfaces (ex. fiducial markers, retro-reflective tape), targets should be placed non-planar (relative to the grasp interface) whenever possible.
37. NASA Robotic Interface Best Practices and Lessons Learned for Surface Operations · PDF page 21
Narrow public claim
EVRBP-0015 Defining Interface Misalignment Envelope based on Perception Accuracy The precision/accuracy of the inputs to the pose estimation (ex. sensors), and the precision/accuracy of the localization methodology itself, should be used to quantify requirements for allowable grasp misalignment.
What this card proves
The exact quoted statement occurred in the named official PDF fetched on 2026-08-04, and the complete PDF matched the recorded SHA-256.
What this card does not prove
It does not independently establish the underlying model capability, safety, comparison, or real-world truth. This is a retrospective single-maintainer source-publication audit.
- Primary source
- NASA Robotic Interface Best Practices and Lessons Learned for Surface Operations
- Section locator
PDF page 21- Captured
- 2026-08-04
- Source SHA-256
fee6644426a6db1a72984d7ec2224288899582b03f04dae7b041a01b4eacffb8- Reproduction
- Maintainer run only; no independent operator rerun is registered.
Repeat this exact check locally
Download the PDF to a local file, then run the committed verifier. A changed PDF is reported as drift rather than silently accepted.
python scripts/verify_primary_public_claim_group.py artifacts/cb7k_dom007_t04_primary_claims.json --source-file <local-raw-pdf>Exact source quote
EVRBP-0015 Defining Interface Misalignment Envelope based on Perception Accuracy The precision/accuracy of the inputs to the pose estimation (ex. sensors), and the precision/accuracy of the localization methodology itself, should be used to quantify requirements for allowable grasp misalignment.
38. NASA Robotic Interface Best Practices and Lessons Learned for Surface Operations · PDF page 22
Narrow public claim
EVRBP-0016 Flexible Goods Interfaces Flexible goods (ex. straps, Velcro, fabric handles) should not be utilized by robotic systems as an interface.
What this card proves
The exact quoted statement occurred in the named official PDF fetched on 2026-08-04, and the complete PDF matched the recorded SHA-256.
What this card does not prove
It does not independently establish the underlying model capability, safety, comparison, or real-world truth. This is a retrospective single-maintainer source-publication audit.
- Primary source
- NASA Robotic Interface Best Practices and Lessons Learned for Surface Operations
- Section locator
PDF page 22- Captured
- 2026-08-04
- Source SHA-256
fee6644426a6db1a72984d7ec2224288899582b03f04dae7b041a01b4eacffb8- Reproduction
- Maintainer run only; no independent operator rerun is registered.
Repeat this exact check locally
Download the PDF to a local file, then run the committed verifier. A changed PDF is reported as drift rather than silently accepted.
python scripts/verify_primary_public_claim_group.py artifacts/cb7k_dom007_t04_primary_claims.json --source-file <local-raw-pdf>Exact source quote
EVRBP-0016 Flexible Goods Interfaces Flexible goods (ex. straps, Velcro, fabric handles) should not be utilized by robotic systems as an interface.
39. NASA Robotic Interface Best Practices and Lessons Learned for Surface Operations · PDF page 22
Narrow public claim
EVRBP-0017 Adding Compliance to Relieve Misalignment Loads If alignment is required between two interfaces, the contact point between those interfaces should be designed with some level of force and torque compliance when possible.
What this card proves
The exact quoted statement occurred in the named official PDF fetched on 2026-08-04, and the complete PDF matched the recorded SHA-256.
What this card does not prove
It does not independently establish the underlying model capability, safety, comparison, or real-world truth. This is a retrospective single-maintainer source-publication audit.
- Primary source
- NASA Robotic Interface Best Practices and Lessons Learned for Surface Operations
- Section locator
PDF page 22- Captured
- 2026-08-04
- Source SHA-256
fee6644426a6db1a72984d7ec2224288899582b03f04dae7b041a01b4eacffb8- Reproduction
- Maintainer run only; no independent operator rerun is registered.
Repeat this exact check locally
Download the PDF to a local file, then run the committed verifier. A changed PDF is reported as drift rather than silently accepted.
python scripts/verify_primary_public_claim_group.py artifacts/cb7k_dom007_t04_primary_claims.json --source-file <local-raw-pdf>Exact source quote
EVRBP-0017 Adding Compliance to Relieve Misalignment Loads If alignment is required between two interfaces, the contact point between those interfaces should be designed with some level of force and torque compliance when possible.
40. NASA Robotic Interface Best Practices and Lessons Learned for Surface Operations · PDF page 22
Narrow public claim
Rationale: When robots are aligning two interfaces, there will likely be some amount of misalignment, which might be somewhat mitigated if there are guiding features on the interfaces (see EVRBP-11 and EVRBP-15).
What this card proves
The exact quoted statement occurred in the named official PDF fetched on 2026-08-04, and the complete PDF matched the recorded SHA-256.
What this card does not prove
It does not independently establish the underlying model capability, safety, comparison, or real-world truth. This is a retrospective single-maintainer source-publication audit.
- Primary source
- NASA Robotic Interface Best Practices and Lessons Learned for Surface Operations
- Section locator
PDF page 22- Captured
- 2026-08-04
- Source SHA-256
fee6644426a6db1a72984d7ec2224288899582b03f04dae7b041a01b4eacffb8- Reproduction
- Maintainer run only; no independent operator rerun is registered.
Repeat this exact check locally
Download the PDF to a local file, then run the committed verifier. A changed PDF is reported as drift rather than silently accepted.
python scripts/verify_primary_public_claim_group.py artifacts/cb7k_dom007_t04_primary_claims.json --source-file <local-raw-pdf>Exact source quote
Rationale: When robots are aligning two interfaces, there will likely be some amount of misalignment, which might be somewhat mitigated if there are guiding features on the interfaces (see EVRBP-11 and EVRBP-15).
41. NASA Robotic Interface Best Practices and Lessons Learned for Surface Operations · PDF page 22
Narrow public claim
EVRBP-0018 Grasping in a Gravity Field When handling large payloads in the presence of gravity, grasp alignment should be such that the gravity vector goes through the grasping interaction point and the center of mass as closely as possible to limit the torques reacted at the interface.
What this card proves
The exact quoted statement occurred in the named official PDF fetched on 2026-08-04, and the complete PDF matched the recorded SHA-256.
What this card does not prove
It does not independently establish the underlying model capability, safety, comparison, or real-world truth. This is a retrospective single-maintainer source-publication audit.
- Primary source
- NASA Robotic Interface Best Practices and Lessons Learned for Surface Operations
- Section locator
PDF page 22- Captured
- 2026-08-04
- Source SHA-256
fee6644426a6db1a72984d7ec2224288899582b03f04dae7b041a01b4eacffb8- Reproduction
- Maintainer run only; no independent operator rerun is registered.
Repeat this exact check locally
Download the PDF to a local file, then run the committed verifier. A changed PDF is reported as drift rather than silently accepted.
python scripts/verify_primary_public_claim_group.py artifacts/cb7k_dom007_t05_primary_claims.json --source-file <local-raw-pdf>Exact source quote
EVRBP-0018 Grasping in a Gravity Field When handling large payloads in the presence of gravity, grasp alignment should be such that the gravity vector goes through the grasping interaction point and the center of mass as closely as possible to limit the torques reacted at the interface.
42. NASA Robotic Interface Best Practices and Lessons Learned for Surface Operations · PDF page 23
Narrow public claim
Furthermore, when the line of action for grasp and insertion/extraction is in line with the EE xaxis (See Figure 3-4), it aligns the vector of force application with the strongest axis of a robotic system.
What this card proves
The exact quoted statement occurred in the named official PDF fetched on 2026-08-04, and the complete PDF matched the recorded SHA-256.
What this card does not prove
It does not independently establish the underlying model capability, safety, comparison, or real-world truth. This is a retrospective single-maintainer source-publication audit.
- Primary source
- NASA Robotic Interface Best Practices and Lessons Learned for Surface Operations
- Section locator
PDF page 23- Captured
- 2026-08-04
- Source SHA-256
fee6644426a6db1a72984d7ec2224288899582b03f04dae7b041a01b4eacffb8- Reproduction
- Maintainer run only; no independent operator rerun is registered.
Repeat this exact check locally
Download the PDF to a local file, then run the committed verifier. A changed PDF is reported as drift rather than silently accepted.
python scripts/verify_primary_public_claim_group.py artifacts/cb7k_dom007_t05_primary_claims.json --source-file <local-raw-pdf>Exact source quote
Furthermore, when the line of action for grasp and insertion/extraction is in line with the EE xaxis (See Figure 3-4), it aligns the vector of force application with the strongest axis of a robotic system.
43. NASA Robotic Interface Best Practices and Lessons Learned for Surface Operations · PDF page 23
Narrow public claim
In some instances when robotic systems are handling payloads/connectors with cables, avoiding system singularities can create issues in completing the task as the cables may prevent or limit rotations of ±180 degrees (ex. joint reposition or flip).
What this card proves
The exact quoted statement occurred in the named official PDF fetched on 2026-08-04, and the complete PDF matched the recorded SHA-256.
What this card does not prove
It does not independently establish the underlying model capability, safety, comparison, or real-world truth. This is a retrospective single-maintainer source-publication audit.
- Primary source
- NASA Robotic Interface Best Practices and Lessons Learned for Surface Operations
- Section locator
PDF page 23- Captured
- 2026-08-04
- Source SHA-256
fee6644426a6db1a72984d7ec2224288899582b03f04dae7b041a01b4eacffb8- Reproduction
- Maintainer run only; no independent operator rerun is registered.
Repeat this exact check locally
Download the PDF to a local file, then run the committed verifier. A changed PDF is reported as drift rather than silently accepted.
python scripts/verify_primary_public_claim_group.py artifacts/cb7k_dom007_t05_primary_claims.json --source-file <local-raw-pdf>Exact source quote
In some instances when robotic systems are handling payloads/connectors with cables, avoiding system singularities can create issues in completing the task as the cables may prevent or limit rotations of ±180 degrees (ex. joint reposition or flip).
44. NASA Robotic Interface Best Practices and Lessons Learned for Surface Operations · PDF page 24
Narrow public claim
A means of robotically securing the cover away from the active worksite is desirable to avoid impeding the main robotic task, though it also adds time to the overall operation.
What this card proves
The exact quoted statement occurred in the named official PDF fetched on 2026-08-04, and the complete PDF matched the recorded SHA-256.
What this card does not prove
It does not independently establish the underlying model capability, safety, comparison, or real-world truth. This is a retrospective single-maintainer source-publication audit.
- Primary source
- NASA Robotic Interface Best Practices and Lessons Learned for Surface Operations
- Section locator
PDF page 24- Captured
- 2026-08-04
- Source SHA-256
fee6644426a6db1a72984d7ec2224288899582b03f04dae7b041a01b4eacffb8- Reproduction
- Maintainer run only; no independent operator rerun is registered.
Repeat this exact check locally
Download the PDF to a local file, then run the committed verifier. A changed PDF is reported as drift rather than silently accepted.
python scripts/verify_primary_public_claim_group.py artifacts/cb7k_dom007_t05_primary_claims.json --source-file <local-raw-pdf>Exact source quote
A means of robotically securing the cover away from the active worksite is desirable to avoid impeding the main robotic task, though it also adds time to the overall operation.
45. NASA Robotic Interface Best Practices and Lessons Learned for Surface Operations · PDF page 25
Narrow public claim
Over the life of the ISS, ground testing has uncovered several significant design issues in robotic mechanisms that were not caught by analysis and/or CAD inspections.
What this card proves
The exact quoted statement occurred in the named official PDF fetched on 2026-08-04, and the complete PDF matched the recorded SHA-256.
What this card does not prove
It does not independently establish the underlying model capability, safety, comparison, or real-world truth. This is a retrospective single-maintainer source-publication audit.
- Primary source
- NASA Robotic Interface Best Practices and Lessons Learned for Surface Operations
- Section locator
PDF page 25- Captured
- 2026-08-04
- Source SHA-256
fee6644426a6db1a72984d7ec2224288899582b03f04dae7b041a01b4eacffb8- Reproduction
- Maintainer run only; no independent operator rerun is registered.
Repeat this exact check locally
Download the PDF to a local file, then run the committed verifier. A changed PDF is reported as drift rather than silently accepted.
python scripts/verify_primary_public_claim_group.py artifacts/cb7k_dom007_t05_primary_claims.json --source-file <local-raw-pdf>Exact source quote
Over the life of the ISS, ground testing has uncovered several significant design issues in robotic mechanisms that were not caught by analysis and/or CAD inspections.
46. NASA Robotic Interface Best Practices and Lessons Learned for Surface Operations · PDF page 25
Narrow public claim
Repeated experiences have shown that analysis and inspection are not adequate to verify or validate robotic interfaces against their requirements.
What this card proves
The exact quoted statement occurred in the named official PDF fetched on 2026-08-04, and the complete PDF matched the recorded SHA-256.
What this card does not prove
It does not independently establish the underlying model capability, safety, comparison, or real-world truth. This is a retrospective single-maintainer source-publication audit.
- Primary source
- NASA Robotic Interface Best Practices and Lessons Learned for Surface Operations
- Section locator
PDF page 25- Captured
- 2026-08-04
- Source SHA-256
fee6644426a6db1a72984d7ec2224288899582b03f04dae7b041a01b4eacffb8- Reproduction
- Maintainer run only; no independent operator rerun is registered.
Repeat this exact check locally
Download the PDF to a local file, then run the committed verifier. A changed PDF is reported as drift rather than silently accepted.
python scripts/verify_primary_public_claim_group.py artifacts/cb7k_dom007_t05_primary_claims.json --source-file <local-raw-pdf>Exact source quote
Repeated experiences have shown that analysis and inspection are not adequate to verify or validate robotic interfaces against their requirements.
47. NASA Robotic Interface Best Practices and Lessons Learned for Surface Operations · PDF page 26
Narrow public claim
As alluded to in EVRBP-05, it is critical that systems should standardize robotic interfaces which emphasize commonality and interoperability.
What this card proves
The exact quoted statement occurred in the named official PDF fetched on 2026-08-04, and the complete PDF matched the recorded SHA-256.
What this card does not prove
It does not independently establish the underlying model capability, safety, comparison, or real-world truth. This is a retrospective single-maintainer source-publication audit.
- Primary source
- NASA Robotic Interface Best Practices and Lessons Learned for Surface Operations
- Section locator
PDF page 26- Captured
- 2026-08-04
- Source SHA-256
fee6644426a6db1a72984d7ec2224288899582b03f04dae7b041a01b4eacffb8- Reproduction
- Maintainer run only; no independent operator rerun is registered.
Repeat this exact check locally
Download the PDF to a local file, then run the committed verifier. A changed PDF is reported as drift rather than silently accepted.
python scripts/verify_primary_public_claim_group.py artifacts/cb7k_dom007_t05_primary_claims.json --source-file <local-raw-pdf>Exact source quote
As alluded to in EVRBP-05, it is critical that systems should standardize robotic interfaces which emphasize commonality and interoperability.
48. NASA Robotic Interface Best Practices and Lessons Learned for Surface Operations · PDF page 26
Narrow public claim
Two principal interface types were developed and have widespread use, one clocked and circular (Micro-conical in Figure 5-3) and one rectangular with aggressive chamfers (H-Fixture and Micro-fixture in Figure 5-3).
What this card proves
The exact quoted statement occurred in the named official PDF fetched on 2026-08-04, and the complete PDF matched the recorded SHA-256.
What this card does not prove
It does not independently establish the underlying model capability, safety, comparison, or real-world truth. This is a retrospective single-maintainer source-publication audit.
- Primary source
- NASA Robotic Interface Best Practices and Lessons Learned for Surface Operations
- Section locator
PDF page 26- Captured
- 2026-08-04
- Source SHA-256
fee6644426a6db1a72984d7ec2224288899582b03f04dae7b041a01b4eacffb8- Reproduction
- Maintainer run only; no independent operator rerun is registered.
Repeat this exact check locally
Download the PDF to a local file, then run the committed verifier. A changed PDF is reported as drift rather than silently accepted.
python scripts/verify_primary_public_claim_group.py artifacts/cb7k_dom007_t05_primary_claims.json --source-file <local-raw-pdf>Exact source quote
Two principal interface types were developed and have widespread use, one clocked and circular (Micro-conical in Figure 5-3) and one rectangular with aggressive chamfers (H-Fixture and Micro-fixture in Figure 5-3).
49. NASA Robotic Interface Best Practices and Lessons Learned for Surface Operations · PDF page 26
Narrow public claim
However, the OTCM of the SPDM on orbit (Figure 5-4) can only natively interface with the latter rectangular connectors which are interoperable to one another.
What this card proves
The exact quoted statement occurred in the named official PDF fetched on 2026-08-04, and the complete PDF matched the recorded SHA-256.
What this card does not prove
It does not independently establish the underlying model capability, safety, comparison, or real-world truth. This is a retrospective single-maintainer source-publication audit.
- Primary source
- NASA Robotic Interface Best Practices and Lessons Learned for Surface Operations
- Section locator
PDF page 26- Captured
- 2026-08-04
- Source SHA-256
fee6644426a6db1a72984d7ec2224288899582b03f04dae7b041a01b4eacffb8- Reproduction
- Maintainer run only; no independent operator rerun is registered.
Repeat this exact check locally
Download the PDF to a local file, then run the committed verifier. A changed PDF is reported as drift rather than silently accepted.
python scripts/verify_primary_public_claim_group.py artifacts/cb7k_dom007_t05_primary_claims.json --source-file <local-raw-pdf>Exact source quote
However, the OTCM of the SPDM on orbit (Figure 5-4) can only natively interface with the latter rectangular connectors which are interoperable to one another.
50. NASA Robotic Interface Best Practices and Lessons Learned for Surface Operations · PDF page 26
Narrow public claim
Due to the lack of upfront standardization, the only way to utilize Micro-conical interfaces is with an adapter or tool called the Remote Micro Conical Tool (RMCT), Figure 5-5.
What this card proves
The exact quoted statement occurred in the named official PDF fetched on 2026-08-04, and the complete PDF matched the recorded SHA-256.
What this card does not prove
It does not independently establish the underlying model capability, safety, comparison, or real-world truth. This is a retrospective single-maintainer source-publication audit.
- Primary source
- NASA Robotic Interface Best Practices and Lessons Learned for Surface Operations
- Section locator
PDF page 26- Captured
- 2026-08-04
- Source SHA-256
fee6644426a6db1a72984d7ec2224288899582b03f04dae7b041a01b4eacffb8- Reproduction
- Maintainer run only; no independent operator rerun is registered.
Repeat this exact check locally
Download the PDF to a local file, then run the committed verifier. A changed PDF is reported as drift rather than silently accepted.
python scripts/verify_primary_public_claim_group.py artifacts/cb7k_dom007_t05_primary_claims.json --source-file <local-raw-pdf>Exact source quote
Due to the lack of upfront standardization, the only way to utilize Micro-conical interfaces is with an adapter or tool called the Remote Micro Conical Tool (RMCT), Figure 5-5.
51. NASA Robotic Interface Best Practices and Lessons Learned for Surface Operations · PDF page 27
Narrow public claim
If varying sensor modalities and concept of operations are needed to localize different interfaces, then a robotic system may not be able to use all needed interfaces.
What this card proves
The exact quoted statement occurred in the named official PDF fetched on 2026-08-04, and the complete PDF matched the recorded SHA-256.
What this card does not prove
It does not independently establish the underlying model capability, safety, comparison, or real-world truth. This is a retrospective single-maintainer source-publication audit.
- Primary source
- NASA Robotic Interface Best Practices and Lessons Learned for Surface Operations
- Section locator
PDF page 27- Captured
- 2026-08-04
- Source SHA-256
fee6644426a6db1a72984d7ec2224288899582b03f04dae7b041a01b4eacffb8- Reproduction
- Maintainer run only; no independent operator rerun is registered.
Repeat this exact check locally
Download the PDF to a local file, then run the committed verifier. A changed PDF is reported as drift rather than silently accepted.
python scripts/verify_primary_public_claim_group.py artifacts/cb7k_dom007_t06_primary_claims.json --source-file <local-raw-pdf>Exact source quote
If varying sensor modalities and concept of operations are needed to localize different interfaces, then a robotic system may not be able to use all needed interfaces.
52. NASA Robotic Interface Best Practices and Lessons Learned for Surface Operations · PDF page 27
Narrow public claim
Forethought should be put into the types of sensing equipment that robotic systems will have in the anticipated operational environment and into standards for alignment built for the operational environment.
What this card proves
The exact quoted statement occurred in the named official PDF fetched on 2026-08-04, and the complete PDF matched the recorded SHA-256.
What this card does not prove
It does not independently establish the underlying model capability, safety, comparison, or real-world truth. This is a retrospective single-maintainer source-publication audit.
- Primary source
- NASA Robotic Interface Best Practices and Lessons Learned for Surface Operations
- Section locator
PDF page 27- Captured
- 2026-08-04
- Source SHA-256
fee6644426a6db1a72984d7ec2224288899582b03f04dae7b041a01b4eacffb8- Reproduction
- Maintainer run only; no independent operator rerun is registered.
Repeat this exact check locally
Download the PDF to a local file, then run the committed verifier. A changed PDF is reported as drift rather than silently accepted.
python scripts/verify_primary_public_claim_group.py artifacts/cb7k_dom007_t06_primary_claims.json --source-file <local-raw-pdf>Exact source quote
Forethought should be put into the types of sensing equipment that robotic systems will have in the anticipated operational environment and into standards for alignment built for the operational environment.
53. NASA Robotic Interface Best Practices and Lessons Learned for Surface Operations · PDF page 28
Narrow public claim
Micro MTC Conical Target Collets [x6] Fitting ~ Micro Interface 7/ 16" Drive Bolt Figure 5-5: The RMCT was designed, in part, to adapt between the Micro Interface which the OTCM can grasp, and the Micro Conical Fitting.
What this card proves
The exact quoted statement occurred in the named official PDF fetched on 2026-08-04, and the complete PDF matched the recorded SHA-256.
What this card does not prove
It does not independently establish the underlying model capability, safety, comparison, or real-world truth. This is a retrospective single-maintainer source-publication audit.
- Primary source
- NASA Robotic Interface Best Practices and Lessons Learned for Surface Operations
- Section locator
PDF page 28- Captured
- 2026-08-04
- Source SHA-256
fee6644426a6db1a72984d7ec2224288899582b03f04dae7b041a01b4eacffb8- Reproduction
- Maintainer run only; no independent operator rerun is registered.
Repeat this exact check locally
Download the PDF to a local file, then run the committed verifier. A changed PDF is reported as drift rather than silently accepted.
python scripts/verify_primary_public_claim_group.py artifacts/cb7k_dom007_t06_primary_claims.json --source-file <local-raw-pdf>Exact source quote
Micro MTC Conical Target Collets [x6] Fitting ~ Micro Interface 7/ 16" Drive Bolt Figure 5-5: The RMCT was designed, in part, to adapt between the Micro Interface which the OTCM can grasp, and the Micro Conical Fitting.
54. NASA Robotic Interface Best Practices and Lessons Learned for Surface Operations · PDF page 28
Narrow public claim
These outboard rails were removed from the ISS baseline during manifest reviews ahead of Space Shuttle retirement in 2011.
What this card proves
The exact quoted statement occurred in the named official PDF fetched on 2026-08-04, and the complete PDF matched the recorded SHA-256.
What this card does not prove
It does not independently establish the underlying model capability, safety, comparison, or real-world truth. This is a retrospective single-maintainer source-publication audit.
- Primary source
- NASA Robotic Interface Best Practices and Lessons Learned for Surface Operations
- Section locator
PDF page 28- Captured
- 2026-08-04
- Source SHA-256
fee6644426a6db1a72984d7ec2224288899582b03f04dae7b041a01b4eacffb8- Reproduction
- Maintainer run only; no independent operator rerun is registered.
Repeat this exact check locally
Download the PDF to a local file, then run the committed verifier. A changed PDF is reported as drift rather than silently accepted.
python scripts/verify_primary_public_claim_group.py artifacts/cb7k_dom007_t06_primary_claims.json --source-file <local-raw-pdf>Exact source quote
These outboard rails were removed from the ISS baseline during manifest reviews ahead of Space Shuttle retirement in 2011.
55. NASA Robotic Interface Best Practices and Lessons Learned for Surface Operations · PDF page 28
Narrow public claim
As a result, ISS robotics are limited to basepoints inboard of the solar arrays, and ~60 of 250 robotically compatible ORUs are now out of robotic reach thus requiring EVA to replace.
What this card proves
The exact quoted statement occurred in the named official PDF fetched on 2026-08-04, and the complete PDF matched the recorded SHA-256.
What this card does not prove
It does not independently establish the underlying model capability, safety, comparison, or real-world truth. This is a retrospective single-maintainer source-publication audit.
- Primary source
- NASA Robotic Interface Best Practices and Lessons Learned for Surface Operations
- Section locator
PDF page 28- Captured
- 2026-08-04
- Source SHA-256
fee6644426a6db1a72984d7ec2224288899582b03f04dae7b041a01b4eacffb8- Reproduction
- Maintainer run only; no independent operator rerun is registered.
Repeat this exact check locally
Download the PDF to a local file, then run the committed verifier. A changed PDF is reported as drift rather than silently accepted.
python scripts/verify_primary_public_claim_group.py artifacts/cb7k_dom007_t06_primary_claims.json --source-file <local-raw-pdf>Exact source quote
As a result, ISS robotics are limited to basepoints inboard of the solar arrays, and ~60 of 250 robotically compatible ORUs are now out of robotic reach thus requiring EVA to replace.
56. NASA Robotic Interface Best Practices and Lessons Learned for Surface Operations · PDF page 29
Narrow public claim
Just as an interface can drive robotic system requirements, so too can robotic capabilities influence interface designs.
What this card proves
The exact quoted statement occurred in the named official PDF fetched on 2026-08-04, and the complete PDF matched the recorded SHA-256.
What this card does not prove
It does not independently establish the underlying model capability, safety, comparison, or real-world truth. This is a retrospective single-maintainer source-publication audit.
- Primary source
- NASA Robotic Interface Best Practices and Lessons Learned for Surface Operations
- Section locator
PDF page 29- Captured
- 2026-08-04
- Source SHA-256
fee6644426a6db1a72984d7ec2224288899582b03f04dae7b041a01b4eacffb8- Reproduction
- Maintainer run only; no independent operator rerun is registered.
Repeat this exact check locally
Download the PDF to a local file, then run the committed verifier. A changed PDF is reported as drift rather than silently accepted.
python scripts/verify_primary_public_claim_group.py artifacts/cb7k_dom007_t06_primary_claims.json --source-file <local-raw-pdf>Exact source quote
Just as an interface can drive robotic system requirements, so too can robotic capabilities influence interface designs.
57. NASA Robotic Interface Best Practices and Lessons Learned for Surface Operations · PDF page 29
Narrow public claim
In practice such requirements are cyclical in nature prior to PDR unless an a-priori interface or robotic system is known.
What this card proves
The exact quoted statement occurred in the named official PDF fetched on 2026-08-04, and the complete PDF matched the recorded SHA-256.
What this card does not prove
It does not independently establish the underlying model capability, safety, comparison, or real-world truth. This is a retrospective single-maintainer source-publication audit.
- Primary source
- NASA Robotic Interface Best Practices and Lessons Learned for Surface Operations
- Section locator
PDF page 29- Captured
- 2026-08-04
- Source SHA-256
fee6644426a6db1a72984d7ec2224288899582b03f04dae7b041a01b4eacffb8- Reproduction
- Maintainer run only; no independent operator rerun is registered.
Repeat this exact check locally
Download the PDF to a local file, then run the committed verifier. A changed PDF is reported as drift rather than silently accepted.
python scripts/verify_primary_public_claim_group.py artifacts/cb7k_dom007_t06_primary_claims.json --source-file <local-raw-pdf>Exact source quote
In practice such requirements are cyclical in nature prior to PDR unless an a-priori interface or robotic system is known.
58. NASA Robotic Interface Best Practices and Lessons Learned for Surface Operations · PDF page 30
Narrow public claim
Therefore, it is best to consider the available computational needs of a system early in the design cycle.
What this card proves
The exact quoted statement occurred in the named official PDF fetched on 2026-08-04, and the complete PDF matched the recorded SHA-256.
What this card does not prove
It does not independently establish the underlying model capability, safety, comparison, or real-world truth. This is a retrospective single-maintainer source-publication audit.
- Primary source
- NASA Robotic Interface Best Practices and Lessons Learned for Surface Operations
- Section locator
PDF page 30- Captured
- 2026-08-04
- Source SHA-256
fee6644426a6db1a72984d7ec2224288899582b03f04dae7b041a01b4eacffb8- Reproduction
- Maintainer run only; no independent operator rerun is registered.
Repeat this exact check locally
Download the PDF to a local file, then run the committed verifier. A changed PDF is reported as drift rather than silently accepted.
python scripts/verify_primary_public_claim_group.py artifacts/cb7k_dom007_t06_primary_claims.json --source-file <local-raw-pdf>Exact source quote
Therefore, it is best to consider the available computational needs of a system early in the design cycle.
59. NASA Robotic Interface Best Practices and Lessons Learned for Surface Operations · PDF page 30
Narrow public claim
While initial prototyping may be exceptionally easy with terrestrial products, the code and system will have to undergo qualification testing to show its robustness to space, lunar, and Martian environments.
What this card proves
The exact quoted statement occurred in the named official PDF fetched on 2026-08-04, and the complete PDF matched the recorded SHA-256.
What this card does not prove
It does not independently establish the underlying model capability, safety, comparison, or real-world truth. This is a retrospective single-maintainer source-publication audit.
- Primary source
- NASA Robotic Interface Best Practices and Lessons Learned for Surface Operations
- Section locator
PDF page 30- Captured
- 2026-08-04
- Source SHA-256
fee6644426a6db1a72984d7ec2224288899582b03f04dae7b041a01b4eacffb8- Reproduction
- Maintainer run only; no independent operator rerun is registered.
Repeat this exact check locally
Download the PDF to a local file, then run the committed verifier. A changed PDF is reported as drift rather than silently accepted.
python scripts/verify_primary_public_claim_group.py artifacts/cb7k_dom007_t06_primary_claims.json --source-file <local-raw-pdf>Exact source quote
While initial prototyping may be exceptionally easy with terrestrial products, the code and system will have to undergo qualification testing to show its robustness to space, lunar, and Martian environments.
60. NASA Robotic Interface Best Practices and Lessons Learned for Surface Operations · PDF page 31
Narrow public claim
When interfaces are in use with a robotic system they serve as active mechanical systems, subjected to all the environmental challenges that accompany spaceflight mechanisms.
What this card proves
The exact quoted statement occurred in the named official PDF fetched on 2026-08-04, and the complete PDF matched the recorded SHA-256.
What this card does not prove
It does not independently establish the underlying model capability, safety, comparison, or real-world truth. This is a retrospective single-maintainer source-publication audit.
- Primary source
- NASA Robotic Interface Best Practices and Lessons Learned for Surface Operations
- Section locator
PDF page 31- Captured
- 2026-08-04
- Source SHA-256
fee6644426a6db1a72984d7ec2224288899582b03f04dae7b041a01b4eacffb8- Reproduction
- Maintainer run only; no independent operator rerun is registered.
Repeat this exact check locally
Download the PDF to a local file, then run the committed verifier. A changed PDF is reported as drift rather than silently accepted.
python scripts/verify_primary_public_claim_group.py artifacts/cb7k_dom007_t06_primary_claims.json --source-file <local-raw-pdf>Exact source quote
When interfaces are in use with a robotic system they serve as active mechanical systems, subjected to all the environmental challenges that accompany spaceflight mechanisms.
61. NASA Robotic Interface Best Practices and Lessons Learned for Surface Operations · PDF page 31
Narrow public claim
This can even be seen at equatorial high noon during Apollo missions, Figure 6-1. '-~ ,,..~, Figure 6-1: Image of Apollo LRV near Lunar Noon showcasing Shadow Darkness Areas at the south pole are lit at extremely oblique angles between 1 and 2 degrees of altitude.
What this card proves
The exact quoted statement occurred in the named official PDF fetched on 2026-08-04, and the complete PDF matched the recorded SHA-256.
What this card does not prove
It does not independently establish the underlying model capability, safety, comparison, or real-world truth. This is a retrospective single-maintainer source-publication audit.
- Primary source
- NASA Robotic Interface Best Practices and Lessons Learned for Surface Operations
- Section locator
PDF page 31- Captured
- 2026-08-04
- Source SHA-256
fee6644426a6db1a72984d7ec2224288899582b03f04dae7b041a01b4eacffb8- Reproduction
- Maintainer run only; no independent operator rerun is registered.
Repeat this exact check locally
Download the PDF to a local file, then run the committed verifier. A changed PDF is reported as drift rather than silently accepted.
python scripts/verify_primary_public_claim_group.py artifacts/cb7k_dom007_t07_primary_claims.json --source-file <local-raw-pdf>Exact source quote
This can even be seen at equatorial high noon during Apollo missions, Figure 6-1. '-~ ,,..~, Figure 6-1: Image of Apollo LRV near Lunar Noon showcasing Shadow Darkness Areas at the south pole are lit at extremely oblique angles between 1 and 2 degrees of altitude.
62. NASA Robotic Interface Best Practices and Lessons Learned for Surface Operations · PDF page 32
Narrow public claim
While this document neither covers the specific regional temperatures to design interfaces to nor expected temperature differentials at grasp/mate, the Design Specification for Natural Environments (DSNE) and Lunar Surface Databook documents called out in the reference material can help provide those specifics.
What this card proves
The exact quoted statement occurred in the named official PDF fetched on 2026-08-04, and the complete PDF matched the recorded SHA-256.
What this card does not prove
It does not independently establish the underlying model capability, safety, comparison, or real-world truth. This is a retrospective single-maintainer source-publication audit.
- Primary source
- NASA Robotic Interface Best Practices and Lessons Learned for Surface Operations
- Section locator
PDF page 32- Captured
- 2026-08-04
- Source SHA-256
fee6644426a6db1a72984d7ec2224288899582b03f04dae7b041a01b4eacffb8- Reproduction
- Maintainer run only; no independent operator rerun is registered.
Repeat this exact check locally
Download the PDF to a local file, then run the committed verifier. A changed PDF is reported as drift rather than silently accepted.
python scripts/verify_primary_public_claim_group.py artifacts/cb7k_dom007_t07_primary_claims.json --source-file <local-raw-pdf>Exact source quote
While this document neither covers the specific regional temperatures to design interfaces to nor expected temperature differentials at grasp/mate, the Design Specification for Natural Environments (DSNE) and Lunar Surface Databook documents called out in the reference material can help provide those specifics.
63. NASA Robotic Interface Best Practices and Lessons Learned for Surface Operations · PDF page 32
Narrow public claim
For a local reference, Seasonal Temperature Averages for the Lunar South Pole are Shown in Figure 6-3.
What this card proves
The exact quoted statement occurred in the named official PDF fetched on 2026-08-04, and the complete PDF matched the recorded SHA-256.
What this card does not prove
It does not independently establish the underlying model capability, safety, comparison, or real-world truth. This is a retrospective single-maintainer source-publication audit.
- Primary source
- NASA Robotic Interface Best Practices and Lessons Learned for Surface Operations
- Section locator
PDF page 32- Captured
- 2026-08-04
- Source SHA-256
fee6644426a6db1a72984d7ec2224288899582b03f04dae7b041a01b4eacffb8- Reproduction
- Maintainer run only; no independent operator rerun is registered.
Repeat this exact check locally
Download the PDF to a local file, then run the committed verifier. A changed PDF is reported as drift rather than silently accepted.
python scripts/verify_primary_public_claim_group.py artifacts/cb7k_dom007_t07_primary_claims.json --source-file <local-raw-pdf>Exact source quote
For a local reference, Seasonal Temperature Averages for the Lunar South Pole are Shown in Figure 6-3.
64. NASA Robotic Interface Best Practices and Lessons Learned for Surface Operations · PDF page 34
Narrow public claim
All systems will need to maintain some level of autonomy to be able to manage themselves, and robotics are no exception.
What this card proves
The exact quoted statement occurred in the named official PDF fetched on 2026-08-04, and the complete PDF matched the recorded SHA-256.
What this card does not prove
It does not independently establish the underlying model capability, safety, comparison, or real-world truth. This is a retrospective single-maintainer source-publication audit.
- Primary source
- NASA Robotic Interface Best Practices and Lessons Learned for Surface Operations
- Section locator
PDF page 34- Captured
- 2026-08-04
- Source SHA-256
fee6644426a6db1a72984d7ec2224288899582b03f04dae7b041a01b4eacffb8- Reproduction
- Maintainer run only; no independent operator rerun is registered.
Repeat this exact check locally
Download the PDF to a local file, then run the committed verifier. A changed PDF is reported as drift rather than silently accepted.
python scripts/verify_primary_public_claim_group.py artifacts/cb7k_dom007_t07_primary_claims.json --source-file <local-raw-pdf>Exact source quote
All systems will need to maintain some level of autonomy to be able to manage themselves, and robotics are no exception.
65. NASA Robotic Interface Best Practices and Lessons Learned for Surface Operations · PDF page 34
Narrow public claim
When planning to operate a system through robotics, the concept of operations must be robust to this lack of real time oversight.
What this card proves
The exact quoted statement occurred in the named official PDF fetched on 2026-08-04, and the complete PDF matched the recorded SHA-256.
What this card does not prove
It does not independently establish the underlying model capability, safety, comparison, or real-world truth. This is a retrospective single-maintainer source-publication audit.
- Primary source
- NASA Robotic Interface Best Practices and Lessons Learned for Surface Operations
- Section locator
PDF page 34- Captured
- 2026-08-04
- Source SHA-256
fee6644426a6db1a72984d7ec2224288899582b03f04dae7b041a01b4eacffb8- Reproduction
- Maintainer run only; no independent operator rerun is registered.
Repeat this exact check locally
Download the PDF to a local file, then run the committed verifier. A changed PDF is reported as drift rather than silently accepted.
python scripts/verify_primary_public_claim_group.py artifacts/cb7k_dom007_t07_primary_claims.json --source-file <local-raw-pdf>Exact source quote
When planning to operate a system through robotics, the concept of operations must be robust to this lack of real time oversight.
66. NASA Robotic Interface Best Practices and Lessons Learned for Surface Operations · PDF page 35
Narrow public claim
The keys to managing lunar surface dust effects on interfaces are the ability to 1) Tolerate dust Exposure through resilient systems and dust tolerant mechanisms, 2) Have the ability to detect or monitor dust on sensors and interfaces, 3) Minimize dust ingress into systems, 4) Have the ability to remove dust, if it is determined to be detrimental to operation.
What this card proves
The exact quoted statement occurred in the named official PDF fetched on 2026-08-04, and the complete PDF matched the recorded SHA-256.
What this card does not prove
It does not independently establish the underlying model capability, safety, comparison, or real-world truth. This is a retrospective single-maintainer source-publication audit.
- Primary source
- NASA Robotic Interface Best Practices and Lessons Learned for Surface Operations
- Section locator
PDF page 35- Captured
- 2026-08-04
- Source SHA-256
fee6644426a6db1a72984d7ec2224288899582b03f04dae7b041a01b4eacffb8- Reproduction
- Maintainer run only; no independent operator rerun is registered.
Repeat this exact check locally
Download the PDF to a local file, then run the committed verifier. A changed PDF is reported as drift rather than silently accepted.
python scripts/verify_primary_public_claim_group.py artifacts/cb7k_dom007_t07_primary_claims.json --source-file <local-raw-pdf>Exact source quote
The keys to managing lunar surface dust effects on interfaces are the ability to 1) Tolerate dust Exposure through resilient systems and dust tolerant mechanisms, 2) Have the ability to detect or monitor dust on sensors and interfaces, 3) Minimize dust ingress into systems, 4) Have the ability to remove dust, if it is determined to be detrimental to operation.
67. NASA Robotic Interface Best Practices and Lessons Learned for Surface Operations · PDF page 35
Narrow public claim
Additional information on how to test systems in dust can be found in NASA-STD-1008, which is detailed in Table 2-1: Reference Documents.
What this card proves
The exact quoted statement occurred in the named official PDF fetched on 2026-08-04, and the complete PDF matched the recorded SHA-256.
What this card does not prove
It does not independently establish the underlying model capability, safety, comparison, or real-world truth. This is a retrospective single-maintainer source-publication audit.
- Primary source
- NASA Robotic Interface Best Practices and Lessons Learned for Surface Operations
- Section locator
PDF page 35- Captured
- 2026-08-04
- Source SHA-256
fee6644426a6db1a72984d7ec2224288899582b03f04dae7b041a01b4eacffb8- Reproduction
- Maintainer run only; no independent operator rerun is registered.
Repeat this exact check locally
Download the PDF to a local file, then run the committed verifier. A changed PDF is reported as drift rather than silently accepted.
python scripts/verify_primary_public_claim_group.py artifacts/cb7k_dom007_t07_primary_claims.json --source-file <local-raw-pdf>Exact source quote
Additional information on how to test systems in dust can be found in NASA-STD-1008, which is detailed in Table 2-1: Reference Documents.
68. NASA Robotic Interface Best Practices and Lessons Learned for Surface Operations · PDF page 36
Narrow public claim
APPENDIX A: Acronyms and Abbreviations and Glossary of Terms Table 7-1: Acronyms and Abbreviation List BP Best Practice CAN Control Area Network CDR Critical Design Review CFS Coordinate Frame System CPU Central Processing Unit CTB Cargo Transfer Bag DOF Degree of Freedom DOF Degree Of Freedom EE End Effector EVA Extra-Vehicular Activity EVR Extra-Vehicular Robotic activity Ex.
What this card proves
The exact quoted statement occurred in the named official PDF fetched on 2026-08-04, and the complete PDF matched the recorded SHA-256.
What this card does not prove
It does not independently establish the underlying model capability, safety, comparison, or real-world truth. This is a retrospective single-maintainer source-publication audit.
- Primary source
- NASA Robotic Interface Best Practices and Lessons Learned for Surface Operations
- Section locator
PDF page 36- Captured
- 2026-08-04
- Source SHA-256
fee6644426a6db1a72984d7ec2224288899582b03f04dae7b041a01b4eacffb8- Reproduction
- Maintainer run only; no independent operator rerun is registered.
Repeat this exact check locally
Download the PDF to a local file, then run the committed verifier. A changed PDF is reported as drift rather than silently accepted.
python scripts/verify_primary_public_claim_group.py artifacts/cb7k_dom007_t07_primary_claims.json --source-file <local-raw-pdf>Exact source quote
APPENDIX A: Acronyms and Abbreviations and Glossary of Terms Table 7-1: Acronyms and Abbreviation List BP Best Practice CAN Control Area Network CDR Critical Design Review CFS Coordinate Frame System CPU Central Processing Unit CTB Cargo Transfer Bag DOF Degree of Freedom DOF Degree Of Freedom EE End Effector EVA Extra-Vehicular Activity EVR Extra-Vehicular Robotic activity Ex.
69. NASA Robotic Interface Best Practices and Lessons Learned for Surface Operations · PDF page 38
Narrow public claim
APPENDIX C: Planned Forward Work Table 7-3: List of Forward Work for Document FWD Planned work ID FWD Work Description Release Expected voltage differentials for mating power connectors that have a supplied voltage are expected to be covered in another document (Ex.
What this card proves
The exact quoted statement occurred in the named official PDF fetched on 2026-08-04, and the complete PDF matched the recorded SHA-256.
What this card does not prove
It does not independently establish the underlying model capability, safety, comparison, or real-world truth. This is a retrospective single-maintainer source-publication audit.
- Primary source
- NASA Robotic Interface Best Practices and Lessons Learned for Surface Operations
- Section locator
PDF page 38- Captured
- 2026-08-04
- Source SHA-256
fee6644426a6db1a72984d7ec2224288899582b03f04dae7b041a01b4eacffb8- Reproduction
- Maintainer run only; no independent operator rerun is registered.
Repeat this exact check locally
Download the PDF to a local file, then run the committed verifier. A changed PDF is reported as drift rather than silently accepted.
python scripts/verify_primary_public_claim_group.py artifacts/cb7k_dom007_t07_primary_claims.json --source-file <local-raw-pdf>Exact source quote
APPENDIX C: Planned Forward Work Table 7-3: List of Forward Work for Document FWD Planned work ID FWD Work Description Release Expected voltage differentials for mating power connectors that have a supplied voltage are expected to be covered in another document (Ex.
70. NASA Robotic Interface Best Practices and Lessons Learned for Surface Operations · PDF page 38
Narrow public claim
However, any interface will likely have a voltage FWD- differential at contact due to electrostatic accumulation.
What this card proves
The exact quoted statement occurred in the named official PDF fetched on 2026-08-04, and the complete PDF matched the recorded SHA-256.
What this card does not prove
It does not independently establish the underlying model capability, safety, comparison, or real-world truth. This is a retrospective single-maintainer source-publication audit.
- Primary source
- NASA Robotic Interface Best Practices and Lessons Learned for Surface Operations
- Section locator
PDF page 38- Captured
- 2026-08-04
- Source SHA-256
fee6644426a6db1a72984d7ec2224288899582b03f04dae7b041a01b4eacffb8- Reproduction
- Maintainer run only; no independent operator rerun is registered.
Repeat this exact check locally
Download the PDF to a local file, then run the committed verifier. A changed PDF is reported as drift rather than silently accepted.
python scripts/verify_primary_public_claim_group.py artifacts/cb7k_dom007_t07_primary_claims.json --source-file <local-raw-pdf>Exact source quote
However, any interface will likely have a voltage FWD- differential at contact due to electrostatic accumulation.