Skip to main content

Use Cases

Five canonical workflows. Each maps to a real customer motion and a specific page set.

1. PR-gated test CI with requirement coverage

The day-to-day developer loop. Every PR runs your tests; the GitHub Check Run reports the requirement coverage delta.

2. Closing the requirements gap

You have requirements (from a ReqIF export or a PDF of the standard) and you want to know which ones lack a confirming test.

3. Per-release audit-ready evidence

A regulated customer needs an evidence pack to file as part of their technical file or supplier-acceptance package.

4. Standards-amendment response

A new edition of ISO 10218 publishes. Which of your requirements are touched?
  • Pin the standard at project creation via the standards feed.
  • Receive the alert (Slack, PagerDuty, or in-app) on the amendment.
  • Open the diff view; re-verify the impacted requirements.
  • Regenerate the evidence pack for the updated Declaration of Conformity.

5. Internal QA-led release gate

You don’t certify externally, but your internal release-gate policy demands evidence retention.

Industry-specific patterns

See the Compliance Patterns section for end-to-end workflows for:

Who’s using Roboticks

  • Industrial-robot OEMs chasing ISO 10218-1:2025 conformity.
  • AMR vendors pursuing ISO 3691-4 and ANSI/RIA R15.08.
  • Cobot integrators demonstrating ISO/TS 15066 force/pressure limits.
  • Service-robotics startups preparing for EU Machinery Regulation 2023/1230 (January 2027).
  • Research labs and universities on the Sponsored tier.