​

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.

​

How to choose a pattern

Pick the pattern that matches your product class and your conformance target: 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.

​

Patterns that cross-cut

Two patterns apply to every project regardless of the primary certification scenario:

​

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