Getting started
Follow this workflow: export from your CAD tool, upload the CGES file(s) into a private account-scoped workspace, and review deterministic analysis outputs in the web visualizer. This is the baseline flow planned for launch while revision comparison and deeper API automation roll out with pilot users.
Future proof your schematics
Checklist
- Add required core part attributes such as
roleandfunction. Add optional analysis source attributes only when your exporter guide says how they will map into CGES. - Run exporter to generate
*_CGES.jsonand optional*_CGES.md. - Submit exports to Circuit Genome and review analysis/report outputs.
How the Published Files Fit Together
| Directory | Purpose | Use it when |
|---|---|---|
/standard |
Normative CGES specification text. | You need the contract, conformance language, or artifact requirements. |
/schemas |
Structural validation for core and extension payloads. | You are validating JSON shape or binding tooling to a schema. |
/conformance |
Semantic validation rules and canonical vector bundles. | You need to check counts, referential integrity, or expected pass/fail cases. |
/docs/exporter-guides |
Informative per-tool exporter guidance. | You are implementing EAGLE or Altium extraction and mapping behavior. |
/docs/implementer-workflow.html/docs/consumer-workflow.html |
Informative onboarding paths for producers and consumers. | You need the shortest route through the standard, schema, rules, vectors, and guides. |
/docs/reference |
Shared reference material kept out of the core standard body. | You need tier criteria, part-type classification, panelization reference data, or human-readable extension semantics. |
Documentation Map
{
"schema_version": "1.0",
"components": [
{
"refdes": "R1",
"role": "bias",
"function": "pull_up"
}
]
}