Corpus / Design rules
Every documented diagram, checked
`verifyNetlist` runs over every `schemd` fence in the documentation. The rules are the compiler's own, so what passes here is what passes in your build.
- Diagrams
- 40
- Clean
- 39
- Errors
- 0
- Warnings
- 0
- Notes
- 1
- Demonstrations
- 11
Which rules fired
Deliberate demonstrations
Pages that teach a rule must break it. These diagrams declare the diagnostics they expect, so they never masquerade as defects.
Variant family specimen component-reference
- expected unconnected-component Component RV7 takes part in no connection.
- expected unconnected-component Component CT7 takes part in no connection.
- expected unconnected-component Component LC7 takes part in no connection.
- expected unconnected-component Component DZ7 takes part in no connection.
- expected unconnected-component Component QM7 takes part in no connection.
- expected disconnected-subcircuit The diagram contains 5 independent connected groups.
Five-wire reversal bus grammar
- expected disconnected-subcircuit The diagram contains 5 independent connected groups.
Bounded orthogonal corridor limits
- expected unconnected-component Component CAGE takes part in no connection.
- expected disconnected-subcircuit The diagram contains 2 independent connected groups.
Two nets, one canvas limits
- expected disconnected-subcircuit The diagram contains 2 independent connected groups.
Small source, real routing work limits
- expected disconnected-subcircuit The diagram contains 2 independent connected groups.
Rotated components with upright math math-labels
- expected unconnected-component Component V3 takes part in no connection.
- expected unconnected-component Component L3 takes part in no connection.
- expected unconnected-component Component Q3 takes part in no connection.
- expected unconnected-component Component O3 takes part in no connection.
- expected disconnected-subcircuit The diagram contains 4 independent connected groups.
A shorted rail netlist
- expected shorted-supply Net rail ties supply rails V8, GRT together.
Two outputs, one node netlist
- expected multiple-drivers Net $1 is driven by U.out, V.out.
Repeated passives output-modes
- expected unconnected-component Component RA takes part in no connection.
- expected unconnected-component Component RB takes part in no connection.
- expected unconnected-component Component RC takes part in no connection.
- expected disconnected-subcircuit The diagram contains 3 independent connected groups.
Bounded rotated route performance
- expected unconnected-component Component SHLD takes part in no connection.
- expected disconnected-subcircuit The diagram contains 2 independent connected groups.
Cross-domain 0.7 specimen roadmap
- expected unconnected-component Component AC7 takes part in no connection.
- expected unconnected-component Component CD7 takes part in no connection.
- expected unconnected-component Component FA7 takes part in no connection.
- expected unconnected-component Component QZ7 takes part in no connection.
- expected unconnected-component Component RIG7 takes part in no connection.
- expected disconnected-subcircuit The diagram contains 5 independent connected groups.
Check your own diagrams
The same rules run as a service, so a project can gate its own build without installing the compiler. Nothing is stored and no source leaves the request.
curl -X POST https://schemd.johnowolabiidogun.dev/api/verify \
-H 'content-type: application/json' \
-d '{"source": "source:V1 \"AC\" at (100,150) #blue [type=voltage-ac]\n..."}'
{"ok": false, "counts": {"errors": 1, "warnings": 0, "notes": 0},
"diagnostics": [{"code": "shorted-supply", "severity": "error", "line": 4, ...}]} ok answers the only question a build asks. The badge below reports this corpus:
Flagged diagrams
Two nets, one crossing overview
- info disconnected-subcircuit The diagram contains 2 independent connected groups.