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

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.

​

The standards model

Three concepts. Master these and the rest of the section makes sense. The pricing implication: first standards subscription is included on Team; each additional is $99 / standard / month (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.

​

How a standard moves through Roboticks

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.

​

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 for the practical difference.

​

Pricing

Standards are an itemised upsell. 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