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 Publication Feed

Standards change. New editions publish, amendments land, harmonised lists shift, and your conformance posture shifts with them. The Roboticks feed exists to surface those changes against the standards you have pinned — within a day of publication, with the impacted requirements highlighted.

​

What we poll

You do not need a BSI, Perinorm, ANSI, or JIS subscription on your side. The Roboticks subscription consolidates them; the per-standard $99/month fee covers our share of the per-standard licensing burden.

​

What the feed catches

• New editions — e.g., ISO 10218-1 transitioned from the 2011 edition to the 2025 edition; the feed surfaced the publication and the harmonisation-list update.
• Amendments — A1, A2, technical corrigenda. The feed captures the clause-level diff where the publisher provides one.
• Withdrawals — an edition retired by the issuing body. Important for legacy projects still pinned to the retired edition.
• Harmonisation changes — when a standard is added to or removed from the EU OJ harmonised list for a specific regulation (e.g., the harmonised-standards list under EU MR 2023/1230).
• Citations under new regulations — a standard previously not cited becomes the prescribed means of compliance under a new regulation.

​

Update cadence

The poller runs every 6 hours. EU OJ updates show within hours; ISO/IEC catalog updates show within a day; Perinorm and BSI updates within 24–48 hours of publisher availability. We over-poll deliberately — a pinned-standard amendment is high-signal news and the bandwidth cost is trivial. Once a change is detected, the dashboard updates, and configured alert channels fire within minutes.

​

How a change surfaces

The alert payload includes:

• The standard identifier, edition, and amendment number.
• Number of requirements pinned to this standard.
• Number of requirements derived from clauses changed by the amendment (when clause-level diffs are available).
• A link to the diff view in the dashboard.
• A link to the publisher’s official errata or amendment text.

​

Diff view

When the publisher provides a clause-level diff (most ISO and IEC publications do for A-amendments; corrigenda are usually unstructured prose), Roboticks renders it side-by-side with the impacted derived requirements. The view highlights:

• Clauses added — likely need new derived requirements.
• Clauses removed — derived requirements may now be orphaned.
• Clauses changed — derived requirements should be reviewed for continued accuracy.
• Renumbering — derivation links auto-remap, but flagged for confirmation.

The diff is read-only; it surfaces what changed. Acting on it — re-deriving requirements, re-verifying releases — is the re-conformity workflow.

​

Alerts

Configure alert delivery per pinned standard or per organisation: Severity tiers — info (publication metadata change), notice (new edition), warning (amendment with impacted requirements), critical (withdrawal of a pinned edition).

​

Subscription billing

Standards subscriptions are billed as part of the pricing model:

• Team: first standard included, $99 / standard / month for each additional.
• Enterprise: bundled per contract.
• Free: catalog browse only — no feed, no alerts.

Subscriptions are pro-rated within a billing cycle. Pinning a new standard mid-month bills a pro-rated fee for the remainder of the cycle, then the full $99 on the next cycle.

​

What the feed does not do

• It does not interpret the amendment. What an amendment means for your specific product is a human regulatory judgement. The feed surfaces the change; the diff view structures it; your engineers and compliance staff decide what to do.
• It does not auto-derive new requirements. Derived-requirement authoring is human-initiated. The LLM can suggest; you ratify.
• It does not re-run conformance. Conformance claims are off-platform. The feed signals that a re-conformance assessment may be needed; the assessment is your process.

​

Catalog completeness

Roboticks aims for full coverage of the standards most commonly cited under EU MR 2023/1230 and adjacent regimes. The 12 standards with dedicated documentation pages (see Overview) all have full feed coverage including clause-level derivation where the publisher supports it. Standards we track at metadata-only resolution (publication, withdrawal, edition) but without clause-level derivation are listed in the catalog with a “metadata-only” badge. Request full coverage for an additional standard via hello@roboticks.io; we add coverage based on customer demand.

​

Next steps