CRA Conformity Dossier

The CRA conformity-dossier export composes the CRA technical-file bundle with a selected conformity-assessment overlay. This page is for product teams assembling a CRA dossier for Stella Ops itself or for a customer’s released product; it sits under the CRA Assurance Packs index.

Claim boundary: manufacturer-customer-support for customer products and manufacturer-self when the product is Stella Ops itself.

Source Docs

Supported Routes

CRA-Q5 records Module A as the default route for Stella itself unless counsel or a future SKU classification changes that decision. B+C and H remain available for customer products or future Stella SKUs that require stricter overlays.

Boundary

The dossier is an evidence export. It does not make Stella the notified body, does not auto-file with an authority, and does not remove the manufacturer’s obligation to select the correct assessment route.

The generic ExportCenter Assurance profile id is cra.conformity-dossier, backed by adapter id cra:conformity-dossier and the compatibility command stella export conformity-dossier. Readiness shares the CRA technical-documentation signed-export checks and reports live-publication preflight separately.

Change Log

Date (UTC)Update
2026-06-16Reconciled to verified code: the cra.conformity-dossier profile (adapter cra:conformity-dossier) is registered and ConformityDossierAdapter.cs composes the tech-file bundle with Module A / B+C / H overlays (src/ExportCenter/StellaOps.ExportCenter.Adapters.Cra/). Boundary unchanged — the dossier is an evidence export, not a notified-body act and not an auto-filing. Carried-through residuals (DoC stub, no HTTP run-trigger) are tracked as G3/G5 in cra-gap-closure-plan.md.