> ## 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.
# Standards Coverage
> Pin the standards you certify against. Roboticks tracks publication feeds, surfaces the requirements impacted by every amendment, and ingests new editions on the day they publish.
# Standards Coverage
Roboticks is built around the standards your machinery is certified against. You pin them; we track them; the platform surfaces what changes when an edition or amendment lands.
**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.
## The standards model
Three concepts. Master these and the rest of the section makes sense.
| Concept | What it does |
| -------------------- | -------------------------------------------------------------------------------------------------------------------------------------------- |
| **Pinning** | Bind a project (or organisation) to a specific edition of a standard. See [Pinning](/standards/pinning). |
| **Publication feed** | Roboticks polls EU OJ, ISO/IEC catalogs, BSI Knowledge, and Perinorm; alerts you when a pinned standard amends. See [Feed](/standards/feed). |
| **Derivation** | A requirement records the clause(s) it derives from. When a clause changes, the platform surfaces every requirement downstream. |
The pricing implication: **first standards subscription is included on Team; each additional is \$99 / standard / month** ([pricing](/pricing)).
## Standards Roboticks ships with
Customers most commonly pin one or more of these. Each has a dedicated page with scope, what Roboticks supports, what we explicitly do not do, an example requirement structure, and suggested test patterns.
The EU Machinery Regulation. Applies January 20, 2027. Replaces 2006/42/EC.
Industrial robot safety. The 2025 editions replaced the 2011 ones.
Collaborative robots (cobots). Contact-force limits.
Safety-related parts of machinery control systems. PL a–e.
Functional safety of E/E/PE systems. SIL 1–4.
Machinery functional safety, derived from IEC 61508.
Machinery general principles, risk assessment.
Electro-sensitive protective equipment (light curtains, scanners).
Driverless industrial trucks / AMRs.
Autonomous mobile robots — US analogue to ISO 3691-4.
Regulation 2024/1689. AI-component robotics, high-risk classification.
Business continuity for service-robotics OEMs.
## How a standard moves through Roboticks
```mermaid theme={null}
%%{init: {"theme": "neutral", "themeVariables": {"primaryColor": "#4040ff"}} }%%
flowchart LR
Pub["Publication source
(EU OJ / ISO / IEC / BSI)"] --> Feed["Roboticks feed poller"]
Feed --> Alert["Pinned-standard alert"]
Alert --> Diff["Amendment diff view"]
Diff --> Impact["Impacted requirements"]
Impact --> Reverify["Targeted re-verification"]
Reverify --> Pack["Updated evidence pack"]
```
1. You pin **ISO 10218-1:2025** at the project level.
2. ISO publishes an amendment. The feed poller detects it within 24 hours.
3. A dashboard alert lands; Slack and PagerDuty fire if configured.
4. The diff view shows clause-level changes. Each clause is annotated with the Roboticks requirements that derive from it.
5. You triage: re-derive the requirements that need updating, mark the rest unchanged, regenerate the affected releases' evidence packs.
The full workflow is detailed in [Re-conformity on amendment](/compliance/re-conformity-on-amendment).
## What "we support a standard" means
Two registers — **derive** vs **conform**:
* **Derive from**: Roboticks ingests the standard text (PDF, structured XML if the publisher provides one, manual entry), surfaces clauses as referenceable anchors, and lets you author requirements that link back to specific clauses. The standard's edition and amendment level are tracked on every snapshot.
* **Conform to**: The decision that your product meets the standard's clauses. This is a regulatory determination — made by you, your QA team, your notified body, your certification body — not by Roboticks. The platform provides the evidence; the conformance determination is human.
See [Pinning](/standards/pinning) for the practical difference.
## Pricing
Standards are an itemised upsell.
| Tier | Standards included | Additional |
| ---------- | -------------------------------- | -------------------- |
| Free | Catalog browse only (no pinning) | — |
| Team | 1 standard subscription | \$99 / standard / mo |
| Enterprise | Bundled per contract | — |
| Sponsored | All bundled | — |
The Free-tier catalog lets you explore the metadata of every standard Roboticks tracks, see derived requirement templates, and evaluate whether pinning is worth the cost. You cannot author a requirement that derives from an unpinned standard.
## What is out of scope today
* **Notified-body services.** Roboticks does not act as a notified body or certification body for any standard.
* **Tool qualification.** Neither the platform nor any first-party connector is qualified under DO-178C TQL, ISO 26262-8 TCL, or any equivalent. Where your conformity claim requires a qualified verification tool, qualify it independently.
* **Conformance attestation.** Roboticks does not issue conformance letters, conformity declarations, or any analogue. The evidence pack records facts; the conformance claim is yours.
## Next steps
Org-wide vs project-scoped; bulk pinning from templates.
Sources, cadence, amendment alerts.
The canonical audit-readiness disclaimer.
End-to-end workflows by certification scenario.