The vocabulary of a Crosspad migration report.
A report is only useful if every word in it has one meaning. This page lists each evidence category, verdict, completion state and defined term you will meet in a report or in the workspace, quotes the definition from the document that owns it, and adds one plain-English line. It defines nothing of its own.
The six categories a report uses, per domain.
Quoted from Section 5 of the Commercial Beta Terms and Scope. The report states, per validated domain, which category applies.
| CATEGORY | MEANING (QUOTED) | IN PLAIN ENGLISH |
|---|---|---|
VERIFIED | Source and target were independently observed and match within the validation's tolerance. | Both sides were read and they agree. |
TRANSLATED_EQUIVALENTLY | The target expresses the same intent with a different KiCad construct; the mapping is stated. | KiCad says it differently; the report tells you how. |
REPAIRED_AND_REVALIDATED | A discrepancy was detected, a repair applied, and the affected domains revalidated after the repair. | Something was off, it was fixed, and the fix was checked. |
ACTION_REQUIRED | You must provide an input (asset, confirmation) for this item to be completed. | We need something from you before this item can be finished. |
ENGINEERING_DECISION_REQUIRED | The item needs an engineering judgment we cannot make for you; options are described. | Only you can make this call; the report lays out the options. |
UNSUPPORTED | Outside the Supported Scope; disclosed, not migrated or not verified. | Out of scope; named in the report, not migrated or not verified. |
A Conforming Deliverable is one where every domain in Section 4 is VERIFIED, TRANSLATED_EQUIVALENTLY or REPAIRED_AND_REVALIDATED, with any remaining items disclosed in one of the other three categories.
We do not publish numeric "confidence scores" for a migration. We publish categories, counts, and the evidence behind them.
Words the policies use, and what you see instead.
Before any payment, the policies say the analysis returns one of three verdicts. Those three names never appear on your screen — this is what each one looks like when you meet it.
| POLICY WORD | WHAT YOU SEE | WHAT IT MEANS |
|---|---|---|
Ready | You will not see this word — a file you can order simply runs. | The file is a Supported Input: it can be ordered as it is. |
Decisions required | The REVIEW REQUIRED badge. | Still a Supported Input — it can be ordered, but the migration will ask you for Guided Decisions along the way. |
Blocked | The UNSUPPORTED badge — never charged. | Outside the Supported Scope. A Blocked project cannot be ordered and nothing is charged. |
Analysis and migration are free. A credit is spent only when you unlock a finished migration. A failed, blocked or unsupported migration never costs a credit.
Quoted from the Refund and Remediation Policy, “In plain words”, v1.0.
How a finished job is labelled in your workspace.
A migration job ends in one completion state. The workspace shows it as a badge, and the credit rule follows from it: a credit is spent only when you unlock the delivery of a completed job that carries a deliverable verdict. Failed and unsupported jobs never cost anything.
| STATE | BADGE | MEANING |
|---|---|---|
COMPLETED_AUTOMATICALLY | VERIFIED | The migration completed without repairs. |
COMPLETED_AFTER_AUTO_REPAIR | VERIFIED | The migration completed after repairs that were validated afterwards. |
ACTION_REQUIRED | REVIEW REQUIRED | An input from you is needed to finish an item. |
ENGINEERING_DECISION_REQUIRED | REVIEW REQUIRED | An engineering judgment is needed; options are described. |
UNSUPPORTED | UNSUPPORTED | The file or a construct is outside the Supported Scope. Never charged. |
FAILED | FAILED | No deliverable was produced. Never charged; Remediation-First applies to a paid Order. |
What decides whether you can unlock
A migration whose badge is VERIFIED or REVIEW REQUIRED can be unlocked. UNSUPPORTED and FAILED cannot, and never cost anything.
Behind those badges the engine returns SAFE, COMPLETED or REVIEW_REQUIRED on a job whose status is COMPLETED; the workspace maps each one to the badge above. You never have to read them.
The uppercase token beside each finding.
Open the findings list in a report and each line reads: a plain-English title, a small uppercase code, and a detail line. The code is the identifier, not the explanation.
- The title is the meaning
Every finding is written out in words first. If the sentence beside a code does not tell you what happened, that is a bug in the report — tell us.
- The code is a stable handle
It names the check that fired, in a domain_what form such as COMP_MISSING or CONN_PIN_LOST_NET. It stays the same across runs, so the same issue on two boards carries the same code.
- It is not a closed list
The codes come from the migration engine's rule set and grow with it, so this page does not publish a table that would go stale. Quote the code when you write to us and it points straight at the check.
- A code is not a verdict
The evidence category on the domain — the six above — is what says whether an item is verified, translated, repaired, disclosed or out of scope. A finding code only says which check produced it.
Terms the Refund and Remediation Policy defines.
Quoted from Sections 2 and 3 of the Refund and Remediation Policy. The version you accepted at checkout, identified by version number and hash on your receipt, applies to your Order.
| TERM | DEFINITION (QUOTED) | IN PLAIN ENGLISH |
|---|---|---|
| Unlock | As defined in the Terms: one Credit unlocks one completed Migration; the Credit Price is the Pack price divided by its number of Credits; Unlock is the moment the Credit is spent. | The moment you spend a credit and the download opens. |
| Supported Input | A Source File within the Supported Scope of the Commercial Beta Terms that received a Ready or Decisions required verdict at Analysis. | A file the analysis said can be ordered. |
| Deliverable | The sealed, hash-identified Delivery Bundle: converted KiCad files, migration report, decision receipts, warnings and validation manifest. | What you download when a migration is delivered. |
| Conforming Deliverable | A Deliverable whose validation manifest reports every domain within the Supported Scope as VERIFIED, TRANSLATED_EQUIVALENTLY or REPAIRED_AND_REVALIDATED, with any remaining items disclosed as ACTION_REQUIRED, ENGINEERING_DECISION_REQUIRED or UNSUPPORTED. Items that are disclosed do not make a Deliverable non-conforming. | A delivery where every in-scope domain is verified, translated or repaired, and everything else is disclosed. |
| Initial Failure | A Migration that does not reach a deliverable verdict and therefore cannot be unlocked. It spends no Credit. | The first paid attempt did not reach a Conforming Deliverable. |
| Material Defect | A difference between the Deliverable and the Source File that (a) is within the Supported Scope, (b) is not disclosed in the report, and (c) affects connectivity, geometry, layer mapping, design rules or component data in a way a qualified engineer would consider significant. Cosmetic differences, KiCad rendering differences and disclosed items are not Material Defects. | An undisclosed, in-scope difference that matters to an engineer. |
| Remediation | The work we perform after an Initial Failure or an accepted Defect Report: alternate migration strategies, repairs, reconstruction, guided Decisions, revalidation and re-Delivery. | The fix-it work after a failure or an accepted defect report. |
| Remediation Cycle | One re-processing, revalidation and re-Delivery. | One more full attempt. |
| Remediation Period | 30 calendar days from our Initial Failure notice or our acceptance of a Defect Report, covering up to 3 Remediation Cycles. We may extend it once by 15 days with notice. It pauses while a Customer Request is open. | The window in which remediation runs. |
| Customer Request | Our request to you for information, an asset (for example a missing library or model), or a Decision that we need to continue. | Something we need from you to keep going. |
| Customer Acceptance | Your explicit acceptance in the workspace; or 30 days after Delivery without a Defect Report; or your written acceptance. | When a delivery counts as accepted. |
| Commercially Reasonable Efforts | The efforts a competent provider of automated migration services would make within the Remediation Period, without being required to build new features for Unsupported constructs or to perform manual engineering redesign of your board. | Serious effort within the period — not new features or a redesign. |
The eight things an Order commits us to.
Quoted from Section 2 of the Commercial Beta Terms and Scope — the commitments that govern your Order.
| INCLUDED | DESCRIPTION (QUOTED) |
|---|---|
| Free Analysis | Compatibility verdict and preliminary report, before payment. |
| Automated migration | Conversion of the Source File to the target KiCad format, with repairs applied only where they can be validated. |
| Guided Decisions | Options and consequences for constructs without an exact KiCad equivalent; applied only on your confirmation. |
| Independent validation | Comparison of the result with the Source File across the domains in Section 4, producing the evidence categories in Section 5. |
| Delivery Bundle | KiCad project files for the target version, migration report, decision receipts, warnings, validation manifest with SHA-256 hashes, and a README-FIRST file with the engineering-review warning. |
| Download Period | 90 days of download access, extendable on request. |
| Remediation Service | As defined in the Refund and Remediation Policy. |
| Support | As described in the Support and Remediation Commitments. |
What the bundle contains today
You download one file, crosspad-migration.zip. It carries your board as a .kicad_pcb, the component and net inventories, the DRC and import reports, and the full migration report.
Frequently asked questions.
What does REVIEW REQUIRED mean on my migration?
The job completed, but at least one item is ACTION_REQUIRED (we need an input from you) or ENGINEERING_DECISION_REQUIRED (a judgment only you can make). The report lists each item with its options. A job in this state carries a deliverable verdict, so its delivery can be unlocked.
Does an UNSUPPORTED item make my deliverable non-conforming?
No. A Conforming Deliverable is one where every domain in the Supported Scope is VERIFIED, TRANSLATED_EQUIVALENTLY or REPAIRED_AND_REVALIDATED, with any remaining items disclosed as ACTION_REQUIRED, ENGINEERING_DECISION_REQUIRED or UNSUPPORTED. Items that are disclosed do not make a Deliverable non-conforming.
Does Crosspad publish a confidence score?
No. We do not publish numeric "confidence scores" for a migration. We publish categories, counts, and the evidence behind them.
Which outcome costs a credit?
Only unlocking the delivery of a completed job whose badge is VERIFIED or REVIEW REQUIRED. The analysis is free, and FAILED or UNSUPPORTED outcomes never cost anything.
Every word above, on your own board.
Run the free analysis and read the categories against your project instead of a glossary.
The analysis is free.
Last updated 2026-09-05. Quoted definitions come from the Commercial Beta Terms and Scope and the Refund and Remediation Policy, v1.0; the documents themselves govern. Completion states and badges reflect the current workspace.