> ## 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.
# Compliance Patterns
> End-to-end workflows by certification scenario. The matrix of pattern × standard, with deep links to the canonical workflow for each.
# Compliance Patterns
A **compliance pattern** is an opinionated, end-to-end workflow for a specific certification or audit scenario. It walks from project setup through evidence handoff and tells you, at each step, what to pin, what to derive, what to test, and what to package.
Patterns are not the only way to use Roboticks. They are recipes — common, well-worn paths that get most teams from a green-field project to a defensible audit posture without re-deriving the same architecture every time.
**Roboticks is audit-readiness tooling, not a certified toolchain.** We assemble the evidence your notified body, certification body, or QA process ingests. We do not replace tool qualification (DO-178C, ISO 26262-8 TCL) and we do not issue conformity assessments. Verify the regulatory interpretations on this page against the standard text and your accredited assessor.
## How to choose a pattern
Pick the pattern that matches your **product class** and your **conformance target**:
| If you are building... | And targeting... | Start here |
| ----------------------------------------------- | ------------------------------------------------- | ----------------------------------------------------------------------------- |
| Industrial robot (arm, controller, firmware) | ISO 10218-1:2025 conformity under EU MR 2023/1230 | [Industrial robot — ISO 10218-1:2025](/compliance/industrial-robot-iso-10218) |
| Collaborative robot (cobot) or cobot cell | ISO/TS 15066 + ISO 10218 under EU MR 2023/1230 | [Cobot — ISO/TS 15066](/compliance/cobot-iso-ts-15066) |
| Autonomous mobile robot (AMR / AGV) | ISO 3691-4 under EU MR 2023/1230 | [AMR — ISO 3691-4](/compliance/amr-iso-3691-4) |
| AMR for the US market | ANSI/RIA R15.08 | [AMR pattern](/compliance/amr-iso-3691-4) (R15.08 dual-claim variant) |
| Self-propelled machinery for EU market | EU MR 2023/1230 self-propelled | [EU MR 2023/1230 conformity](/compliance/eu-mr-2023-1230-conformity) |
| A product already shipped, standard has amended | Re-conformity | [Re-conformity on amendment](/compliance/re-conformity-on-amendment) |
| No external certification target | Internal QA release gate | [Internal release gate](/compliance/internal-release-gate) |
If your scenario is none of these, the closest pattern is a good starting point; deviate as needed.
## The matrix
Patterns × standards. A ● indicates the standard is central to the pattern; an ○ indicates the standard typically appears as a cross-reference.
| | ISO 10218 | ISO/TS 15066 | ISO 3691-4 | EU MR 2023/1230 | ISO 12100 | ISO 13849 | IEC 62061 | IEC 61496 | EU AI Act |
| ---------------------------------------------------------- | ---------- | ------------ | ---------- | --------------- | --------- | --------- | --------- | --------- | --------- |
| [Industrial robot](/compliance/industrial-robot-iso-10218) | ● | ○ | | ● | ● | ● | ● | ○ | ○ |
| [Cobot](/compliance/cobot-iso-ts-15066) | ● | ● | | ● | ● | ● | ● | ○ | ○ |
| [AMR](/compliance/amr-iso-3691-4) | | | ● | ● | ● | ● | ● | ● | ○ |
| [EU MR conformity](/compliance/eu-mr-2023-1230-conformity) | ○ | ○ | ○ | ● | ● | ○ | ○ | ○ | ○ |
| [Re-conformity](/compliance/re-conformity-on-amendment) | any pinned | | | | | | | | |
| [Internal release gate](/compliance/internal-release-gate) | any pinned | | | | | | | | |
## Patterns that cross-cut
Two patterns apply to every project regardless of the primary certification scenario:
Which requirements does this PR touch? Run it on every PR.
Pre-audit checklist. Run it the week before the auditor arrives.
## What a pattern delivers
Every pattern page has the same structure:
1. **Scenario** — who this is for, what conformance target it addresses.
2. **Prerequisites** — what risk assessment, what supplier certifications, what off-platform documentation is assumed.
3. **Project setup** — pinning, requirement ingest source, repository layout.
4. **Derivation** — which clauses to derive requirements from, structure for the requirements.
5. **Test patterns** — recommended `@confirms`, `@deadline`, fault-injection, and parameterised-scenario approaches.
6. **Release** — cutting the release, verification, evidence pack generation.
7. **Handoff** — packaging for the notified body or internal reviewer.
8. **Maintenance** — re-conformity on amendments, change-impact, periodic re-verification.
## A note on patterns and your specific situation
Patterns are recipes. They are correct in their structure for the common case. Your situation is specific — your product, your supply chain, your notified body's habits, your jurisdiction. Use the pattern as a starting structure; refine to your context.
When a pattern conflicts with explicit guidance from your notified body or accredited assessor, **the assessor wins**. The pattern documentation is best-effort; the assessor is the conformance authority.
## Next steps
ISO 10218-1:2025 end-to-end.
ISO/TS 15066 contact-force pattern.
ISO 3691-4 detection-zone pattern.
Self-propelled machinery technical-file workflow.