# Crado

> Compliance, inside the engineering loop.

Crado is the evidence layer for regulated hardware. It keeps every test result, design change and regulation tied to the product revision it belongs to.

The evidence layer for regulated hardware: one record between your engineering team and the regulations your product must meet.

## How it works
- Your engineers: Set priorities, confirm facts, make every decision.
- Crado agents: Read reports, organise the evidence, propose likely causes with their evidence.
- Crado rules engine: Checks measurements against the regulation, with the citation and rule version recorded. Same input, same result.
- Your product record: Revisions, test reports, changes and regulations, in one place.
- Reads lab reports today (PDF, TXT, Markdown). Email, team chat and change tickets: ROADMAP.

Every change should arrive with its evidence. Engineers should design, test and decide. Finding out what a change did to the evidence should not take a week of searching.

A record that follows the revision. Every report, confirmed fact, likely cause and change is filed with the product revision it belongs to, so the next one starts from what the last one learned.

Agents investigate. Engineers decide. In a regulated product, a confident wrong answer costs more than no answer. Agents propose and cite, a deterministic engine does the arithmetic, and nothing is marked known until a person confirms it.

## Agents
- EMC investigator (LIVE): Ranks likely causes of a failed radiated-emissions test, each with its evidence, and suggests the next test.
- Change reviewer (ROADMAP): Shows which evidence and certifications a design change touches.
- Retest planner (ROADMAP): Proposes the smallest set of checks that settles an open question.
- Lab liaison (ROADMAP): Keeps test plans, samples and lab threads in step with each revision.
- Compliance writer (ROADMAP): Drafts review packages for engineers to check and approve.
- Evidence auditor (ROADMAP): Finds evidence that went stale after a change, before an auditor does.

## Coverage
- 47 CFR 15.109(a), Class B, 3 m, Radiated emissions, quasi-peak: LIVE
- 47 CFR 15.109(b), Class A, 10 m, Radiated emissions, quasi-peak: ROADMAP
- EU EMC and Radio Equipment Directives, Radiated and conducted emissions, Per harmonised standard: ROADMAP
- EU Machinery Regulation 2023/1230, Substantial modification, Change assessment: ROADMAP
- RTCA DO-160, Qualification by similarity, Environmental test evidence: ROADMAP

## Status
- EMC investigator (radiated-emissions investigation under 47 CFR 15.109(a)): LIVE
- Product memory (reports, facts and likely causes filed with each product): LIVE
- Change and retest comparison: LIVE
- Evidence state per revision: LIVE
- Change reviewer agent: ROADMAP
- Retest planner agent: ROADMAP
- Lab liaison agent: ROADMAP
- Compliance writer agent: ROADMAP
- Evidence auditor agent: ROADMAP
- Reading email, team chat and change tickets: ROADMAP
- 47 CFR 15.109(b), Class A at 10 m: ROADMAP
- EU EMC and Radio Equipment Directives: ROADMAP
- EU Machinery Regulation 2023/1230: ROADMAP
- RTCA DO-160: ROADMAP

## FAQ
- Will Crado tell me if my product will pass? No. Crado reports the margin to the limit and ranks likely causes. The decision stays with your engineers and your lab.
- Does Crado replace my EMC engineer or test lab? No. Crado organises the evidence they work from and does the arithmetic against the rules. Measurement, judgement and certification stay with people and accredited labs.
- Why isn't a general AI assistant enough? Compliance needs numbers that come from a cited, versioned rule, evidence tied to the exact product revision, and a clear line between what was measured and what was inferred. A chat window keeps none of that.
- What does Crado do on its own? It reads reports, extracts values, files evidence to the right revision and proposes likely causes. Nothing is confirmed, decided or sent outside your workspace without a person.
- Where does my data go? Into your workspace. Crado does not use your data for other customers. Contributing to a shared benchmark would need your explicit opt-in, and it is off by default.
- Which parts are live today? Radiated-emissions investigation under 47 CFR 15.109(a), product memory, change and retest comparison and evidence state per revision. Everything else on this page is marked Roadmap.

## Pages
- [Home](https://www.crado.io/): Crado is the evidence layer for regulated hardware. It keeps every test result, design change and regulation tied to the product revision it belongs to.

## Docs
- [Introduction](https://www.crado.io/docs): what Crado does and how it reaches a result
- [Concepts](https://www.crado.io/docs/concepts): revisions, requirements, evidence, evidence states, agents, rules and review
- [Evaluation](https://www.crado.io/docs/evaluation): report confirmation, rule evaluation, measurement comparisons, blocked checks
- [Reference](https://www.crado.io/docs/reference): regulatory coverage and glossary
- [Trust](https://www.crado.io/docs/trust): workspace access, data handling and security status
- [Changelog](https://www.crado.io/docs/changelog)

Contact: hello@crado.io