> ## Documentation Index
> Fetch the complete documentation index at: https://docs.roboticks.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Use Cases

> Common Roboticks workflows - PR-gated test CI, requirement coverage, evidence-pack generation, standards-amendment response, internal release gates.

# 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.

* Connect the repo via the [GitHub App](/github-app/installation).
* Annotate tests with [`@confirms("REQ-id")`](/sdk/decorators).
* See the [Check Run output](/github-app/check-runs) on each PR.

## 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.

* [Upload requirements](/requirements/upload) from ReqIF, PDF, or YAML.
* Open the [Traceability Matrix](/traceability/matrix) filtered to `gap` state.
* Use [AI-suggested tests](/traceability/gaps) to bootstrap the missing test files.

## 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.

* Create a [Release](/evidence/release-scoping) (`draft → verifying → verified → shipped`).
* [Generate the evidence pack](/evidence/generation) in PDF + ReqIF.
* Hand it to the auditor with the [customer-handoff template](/evidence/customer-handoff).

## 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](/standards/feed).
* Receive the alert (Slack, PagerDuty, or in-app) on the amendment.
* Open the diff view; [re-verify](/compliance/re-conformity-on-amendment) 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.

* Use the [release state machine](/evidence/release-scoping) as the gate.
* Configure [internal release-gate](/compliance/internal-release-gate) with sign-off.
* Retain evidence packs for the liability tail (10+ years on Glacier Deep Archive).

```mermaid theme={null}
%%{init: {"theme": "neutral", "themeVariables": {"primaryColor": "#4040ff"}} }%%
flowchart LR
    PR[PR opened] --> CI[Roboticks CI]
    CI --> Matrix[Matrix updates]
    Matrix --> Check[GitHub Check Run]
    Check --> Merge[Merge to main]
    Merge --> Tag[Release tag]
    Tag --> Pack[Evidence pack]
    Pack --> Archive[10-year Glacier]
    Tag --> Amend{Standard<br/>amendment?}
    Amend -->|yes| Reverify[Re-verify impacted reqs]
    Reverify --> Pack
```

## Industry-specific patterns

See the [Compliance Patterns](/compliance/overview) section for end-to-end workflows for:

* [Industrial robot manufacturers (ISO 10218)](/compliance/industrial-robot-iso-10218)
* [Cobot integrators (ISO/TS 15066)](/compliance/cobot-iso-ts-15066)
* [AMR vendors (ISO 3691-4)](/compliance/amr-iso-3691-4)
* [EU MR 2023/1230 conformity](/compliance/eu-mr-2023-1230-conformity)

## 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](/pricing#sponsored--academic).