Research
The door we locked before the CE mark — Companion safety, in plain language
Why we do not show CE today, how the gate checks conditions, and what gets better for users — written for first-time readers.
Hello — Sena here. Plain language today.
One line: A CE mark is not a pretty stamp. It is a door that opens only when product, documents, and date all match. We keep that door locked for now.
Why we built this
Europe’s Cyber Resilience Act (CRA) raises the bar for digital product security.
Some products show CE-looking artwork before the homework is done.
XENLOOK chose the opposite:
- so users are not misled
- so journalists can re-check public links
- so we never sound “certified” before the gate allows it
Companion Desktop publishes readiness (cra_readiness) and does not serve a CE image until every condition passes.
How we built it
Think of five locks. All must pass on server UTC time:
- Application date (2027-12-11) has arrived
- Manufacturer approval remains active
- Public release blockers are zero
- Installer file hash matches the fixed record
- Declaration-of-conformity PDF hash matches
If any lock fails, status stays in readiness and no CE image URL is returned.
Changing a browser clock or guessing a URL will not open it.
What gets better
| Who | Benefit |
|---|---|
| Users | No fake CE · clear status on download |
| Press / partners | Same numbers on public page + API |
| Company | Lower overclaim risk · honest timeline |
Links: Download · AI certification · Companion compliance
Limits (honest)
This is not “CE certified” or “EU approved.”
Code-signing helps trust; it does not replace CRA Notified Body assessment when required.