This document is under active development and has not been finalised.
Skip to content

9.2 Publication Strategy ​

9.2.1 Dual Publication Concept ​

PRINCIPLE

Single Source of Truth = the product's Git repository Public Presentation = central compliance website

Compliance data is maintained in exactly one place — the respective product's repository. From there, it is automatically published to a central compliance website.

text
┌────────────────────┐                ┌──────────────────────────┐
│  Product Repo      │     CI/CD      │  Generated Artefacts     │
│                    │                │                          │
│  .compliance/      │  Validation    │  ┌── Compliance Portal   │
│    cra-statement.  │──────────────→│  │   (HTML/PDF)           │
│    json            │  + Generation  │  ├── CE Marking          │
│                    │                │  │   (About, README)      │
│  (single source)   │                │  ├── Container Labels    │
│                    │                │  │   (OCI annotations)    │
│                    │                │  ├── Simplified DoC       │
│                    │                │  └── API Endpoint         │
└────────────────────┘                └──────────────────────────┘
        ↑                                       ↑
   Developers maintain                 Customers, authorities,
   only the JSON                       public

9.2.2 Benefits ​

AspectBenefit
VersioningStatement is versioned alongside the product code
ReviewChanges go through the same review process as code
AutomationPublication happens automatically on release
ConsistencyJSON schema enforces a uniform format across all products
Audit trailGit history documents every change

9.2.3 Repository Structure ​

Each product repository contains a .compliance/ directory:

text
product-repo/
├── .compliance/
│   ├── cra-statement.json          # Machine-readable CRA statement
│   └── README.md                   # Brief note on compliance structure
├── SECURITY.md                     # Vulnerability Disclosure Policy
├── docs/
│   └── compliance/
│       ├── eu-declaration.pdf      # EU Declaration of Conformity (Annex V)
│       └── user-info.md            # User information (Annex II)
└── ...

Files in Detail ​

FileRequiredDescription
.compliance/cra-statement.json✅ YesMachine-readable CRA Compliance Statement (→ 9.3)
.compliance/README.mdRecommendedExplains the compliance structure to developers
SECURITY.md✅ YesVulnerability Disclosure Policy (→ 4.2)
docs/compliance/eu-declaration.pdf✅ YesLegally binding EU Declaration of Conformity
docs/compliance/user-info.md✅ YesUser information per Annex II

9.2.4 Website URL Scheme ​

The central compliance portal follows a uniform URL structure:

text
https://cra.app.bauer-group.com/
├── /products/                      # Product directory
│   ├── /products/{name}/           # Product compliance page
│   │   ├── /cra                    # CRA Compliance Statement
│   │   ├── /doc                    # EU Declaration of Conformity
│   │   └── /sbom                   # SBOM download
│   └── ...
└── /api/                           # (Optional) API access for authorities
    └── /api/products/{name}.json   # Machine-readable access

9.2.5 Accessibility ​

InformationPublicInternalCRA Reference
CRA Compliance Statement✅✅Art. 13
EU Declaration of Conformity✅✅Art. 28
Simplified DoC✅✅Annex VI
User information (Annex II)✅✅Art. 13
SBOMOn request✅Annex I, Part II
Technical documentation (Annex VII)❌✅Art. 31
Conformity assessment records❌✅Art. 28

NOTE

The complete technical documentation (Annex VII) is not required to be made public, but must be presented to market surveillance authorities within 10 days upon request (Art. 31 CRA).

9.2.6 CI/CD Integration ​

Publication is integrated into the existing CI/CD pipeline:

text
Release tag created
    │
    ├── 1. JSON schema validation (.compliance/cra-statement.json)
    │       → Failure = release blocked
    │
    ├── 2. Completeness check
    │       → Are all required fields populated?
    │       → Do referenced documents (DoC, SBOM) exist?
    │
    ├── 3. Publication to compliance portal
    │       → Generate HTML
    │       → Generate PDF (optional)
    │
    └── 4. Notification
            → Slack/Teams: "Compliance statement for {product} v{version} published"

9.2.7 Cross-References ​

TopicLink
JSON schema definition9.3 Machine-Readable Format
Update process9.4 Maintenance & Updates
SBOM archival2.3 Archival & Retention
Fillable templateA.9 CRA Compliance Statement

Documentation licensed under CC BY-NC 4.0 · Code licensed under MIT