Skip to main content

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.

Audit-Readiness Disclaimer

This page is the canonical reference for what Roboticks is, what it is not, and where the boundaries between platform output and human regulatory judgement sit. Every standards and compliance page in this documentation links here. If you are about to put a Roboticks evidence pack in front of a notified body, read this page first.
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.

What Roboticks does

In one sentence: Roboticks pins every safety, functional, and performance requirement to a passing test, on every PR, every release, every regulation update, and produces a tamper-evident evidence pack the certified toolchain ingests. Concretely:
  • Ingests requirements (ReqIF, PDF, structured YAML, connector pulls).
  • Snapshots requirements per release, immutably.
  • Runs your test suite on hosted or self-hosted runners.
  • Captures JUnit XML, logs, MCAP bag files, coverage, SARIF static-analysis findings, SBOM.
  • Tracks the standards your project is pinned to and surfaces amendment impacts.
  • Builds traceability matrices linking requirements to tests, tests to results, results to evidence.
  • Assembles evidence packs (PDF, ZIP, ReqIF) signed with a tamper-evident hash chain.
  • Retains evidence for the 10-year EU Product Liability tail.

What Roboticks does not do

We are not a notified body

Notified bodies are designated by EU Member States to assess product conformity under specific regulations. They are listed in NANDO (ec.europa.eu/growth/tools-databases/nando). Roboticks is not a notified body for any regulation. We do not perform:
  • EU-type examination certificates under EU MR 2023/1230.
  • Full quality assurance assessment under Annex X of EU MR 2023/1230.
  • Quality management system audits.
  • Conformity assessment for AI Act Annex I or Annex III high-risk systems.
  • Any analogue under non-EU regimes (TÜV-style assessments, UL listing, CSA marking, KCs).
The conformity decision is made by your notified body, certification body, or accredited assessor — not by Roboticks.

We are not a certified or qualified toolchain

Tool qualification is a process the safety standards define for verification tools used in a safety-related lifecycle. Specifics:
StandardConcept
DO-178CTQL (Tool Qualification Level) 1–5
ISO 26262 (automotive)TCL (Tool Confidence Level) 1–3 + TD (Tool Development) for TCL 2/3
IEC 61508-3 §7.4.4.7T1 / T2 / T3 classification
EN 50128 (rail)T1 / T2 / T3 classification
Roboticks is not qualified under any of these regimes today. Where your conformity claim requires a qualified verification tool, the verification tools you bring (compilers, test frameworks, static analysers) must satisfy that requirement independently. Roboticks’s aggregation function — pulling JUnit XML, SARIF, coverage reports your qualified tools produced — does not transform the safety-relevant artefacts in a way that would itself require T3 qualification. We recommend treating Roboticks as a T1 / T2 verification-evidence aggregator alongside your qualified verification tools, and documenting that posture in your tool-classification justification.

We do not issue conformity assessments

Roboticks does not produce:
  • Declarations of Conformity (DoCs).
  • Certificates of conformity.
  • Letters of attestation that a product meets a standard.
  • Any document that an authority would treat as a third-party conformity claim.
What the platform produces is verification evidence. The conformity claim is made by your organisation (or the notified body you contract with) on the basis of that evidence.

We do not interpret standards for you

Roboticks tracks standards, surfaces clauses, and lets you derive requirements from clauses. The interpretation of what a clause requires of your specific product is a human regulatory judgement. The example derived requirements throughout this documentation are illustrative; they reflect Roboticks’s reading of the clauses and should not be relied upon as legally accurate for your conformity claim. Verify every interpretation against the standard text and your accredited assessor.

We do not perform dataset cards, bias evaluations, or model cards (AI Act)

Article 10 of the EU AI Act expects structured dataset documentation, training data bias examination, and (in practice) model cards. Roboticks does not currently author these. The functionality is on the Year 2 roadmap. For AI Act conformity today, fill the gap with adjacent tooling.

What a notified body still requires

A Roboticks evidence pack is one input — typically the verification-evidence input — to the technical file the notified body assesses. The full technical file under EU MR 2023/1230 Annex IV includes elements Roboticks does not produce:
  • Risk assessment narrative — the safety-engineering write-up that derives the hazards and risk-reduction strategy. (Roboticks can attach this; it does not author it.)
  • Design drawings and engineering documentation — mechanical, electrical, hydraulic schematics. (Off-platform.)
  • Instructions for use, maintenance, and decommissioning — user-facing documentation. (Off-platform.)
  • Declaration of Conformity — issued by you. (Off-platform.)
  • Quality management system documentation — ISO 9001 / ISO 13485 style. (Off-platform.)
  • Component supplier certifications — for safety-rated components (drives, controllers, sensors). (Supplier-provided; Roboticks can reference them.)
The pack is necessary but not sufficient. Plan the broader technical-file assembly around it.

Year 2 roadmap

These are honestly on the roadmap, are not available today, and should not be relied upon for present conformity claims:
CapabilityTarget
Tool qualification (T2/T3 under IEC 61508-3)Year 2; will be communicated explicitly when achieved
Tool qualification (TCL 2/3 under ISO 26262-8)Year 2+
Dataset cards (AI Act Article 10)Year 2
Bias evaluation connector integrationsYear 2
Model cards authoringYear 2
Notified-body service partnerships (we expect to partner, not become)Year 1.5
Sector-specific extensions (medical via IEC 62304, automotive via ISO 26262)Year 2+
The roadmap is not a commitment; it is the current direction. Where any of these gaps are blocking, the recommended posture is to fill with adjacent tooling and use Roboticks for the substantial subset it does cover today. The information on this page and throughout the Roboticks documentation is provided “as is” without warranty. Roboticks Inc. makes no representation that conformity to any standard or regulation will be achieved through use of the platform. Conformity is determined by the responsible authority (notified body, certification body, regulator) on the basis of evidence the product manufacturer provides; Roboticks is one tool that may contribute to that evidence. Use of the platform does not transfer any conformity obligation from the customer to Roboticks. For commercial terms, see the Master Services Agreement. For privacy and data handling, see the Data Processing Addendum at roboticks.io/legal.

Standards Overview

The standards Roboticks ships with deep coverage of.

Compliance Patterns

End-to-end workflows by certification scenario.

Evidence Pack Overview

What the pack does and does not contain.

Customer Handoff

The recommended cover letter, repeating this disclaimer.