§
Sovereign.Software
↓ .MD

← The Sovereign Software Index

Engineering & CAD

KiCad

Electronic schematic capture and PCB design suite where every net, footprint, and trace is stored in human-readable S-expressions with zero cloud licensing.

1. Overview

Electronic schematic capture and PCB design suite where every net, footprint, and trace is stored in human-readable S-expressions with zero cloud licensing.

Category: Engineering & CAD.

2. Version and scope assessed

Version assessed: Source commit ba5ed30c1bee8bcfa7db6dc423f1d20224c4e3a5; PCB S-expression connectivity and project-archive inclusion limits.

3. Overall determination

Computing determination

4. Principle profile

Principle findings for KiCad
OrderPrincipleFinding
ISovereigntyNot assessed
IILongevityNot assessed
IIILocality✓ Meets
IVTransparency and ControlNot assessed

5. Fundamental requirements

Fundamental requirements for KiCad
RequirementStatus
E1 Independent access to essential information✓ Pass
E2 Practicable exit and migration? Not Verified
E3 Independent interpretation and recovery? Not Verified
E4 Continuing authority and custody over already-created work✓ Pass
E5 Governability of consequential actions? Not Verified

6. Evidence and verification

7. Migration and recovery

Native storage format: Plain-Text S-Expressions (.kicad_sch/.kicad_pcb).

Synchronization or runtime model: Git / Local Vendor Libraries.

Example export or inspection command (not verified against any particular version or data set): kicad-cli pcb export gerbers board.kicad_pcb

8. Architectural strengths

Established strengths and their scope are recorded in the evidence and assessment findings on this page.

9. Architectural limitations

10. Assessment findings and remaining work

Verification scenario: Open the project across machines; compare schematic, PCB, symbols, footprints, 3D models, netlists, and Gerbers.

What may invalidate an overconfident claim: Manufacturing Gerbers do not preserve editable circuit meaning or BOM and library dependencies.

Documentation starting point: https://docs.kicad.org/

Evidence update: 23 October 2026

Assessment follow-up: These findings now appear in the application’s evidence and limitations. At the user’s request, existing eligibility and principle ratings are unchanged; E3/E5, principle consistency and blank-status fixes will be reconciled in the next pass. Reproduction details and retained inputs are in evidence/third-pass/batch-5/.

Human-readable criteria: Can an independent party preserve the source model, units, dependencies, and editable structure, reproduce the result, and exchange it without losing important design meaning?

Rating reconciliation: 24 October 2026

E3 and E5 remain Not Verified for the existing declared scope. Longevity and Transparency and Control are Not assessed pending their required minimums. Sovereignty is also Not assessed because the required access/exit/custody minimums are not all established. This is a targeted evidence decision, not a finding that the product fails. Existing E1, E4 and Locality findings were not re-certified.

Remaining: Hierarchical schematic/custom-library reconstruction, complete archive/move including external models, manufacturing and editable export comparison, old/new-version saves, .history recovery and schematic-to-PCB update effects. E5 needs inspectable schematic-to-PCB updates, destructive edit/output overwrite controls and available correction; accuracy claims are separate.

Next without installing locally: Inspect a complete synthetic schematic/PCB/library/model packet and expected connectivity/units manifest, with independent output comparisons. Obtain primary-source or external update/undo/overwrite evidence.

The individual decision and provenance are retained in evidence/rating-reconciliation/batch-6/. Overall: Insufficient evidence.

Contribute verification evidence for KiCad

Have you tested clean-machine restoration, format migration, or failure rollback for KiCad? We welcome reproducible laboratory logs, synthetic test fixtures, and independent assessments to resolve open findings.

Read the evaluation protocol · Submit verification records on GitHub

Individually reconciled in rating batch 6 on 24 October 2026. E3/E5 remain Not Verified for explicit missing coverage; dependent unsupported findings corrected. Previously resolved questions are retained, not counted again. E1/E4/Locality were not re-certified by this targeted review. The assessment procedure is described in the methodology.