Secure elements

eCAD Hardware Products

Hardware / PCB CAD design collection for the EmbeddedOS (EoS) ecosystem. The repository organizes hardware product designs by application domain. Each domain holds one or more product lines, and each product line typically carries a product datasheet, a bill of materials (bom.csv), power-budget simulation scripts, and placeholder directories for PCB and mechanical CAD artifacts. Several product lines also include KiCad schematics (*.kicad_sch).

Status varies by design. Directories are at different maturity levels (many "Design" / "Pre-production"); PCB and CAD folders often contain .gitkeep placeholders rather than finished layouts. Check each design's own README.md and docs/ for its current state.

Domains

The repository contains 16 domain design collections:

Plus:

• future_designs/ — early/prospective concepts (e.g. eBCI-Lite)
• docs/ — repository-level documentation

Typical design layout

Most domains follow a common structure, for example:

eAerospace_CAD_Design/
  README.md
  docs/                      business_plan.md, regulatory_path.md
  ebuild_simulation/         eBuild simulation notes
  <product_line>/
    product_datasheet.md
    bom.csv
    simulation/power_budget_sim.py
    hardware/
      pcb/  cad/  antenna/   (artifact folders; often .gitkeep placeholders)

Artifact formats present in the repo include Markdown datasheets, CSV BOMs, Python simulation scripts, and KiCad schematics (*.kicad_sch). Some product lines also include TypeScript/Dart companion app sources and 3D-model notes.

Simulations

Power-budget simulations are plain Python scripts, runnable per product line:

cd eAerospace_CAD_Design/<product_line>/simulation/
python3 power_budget_sim.py

Design docs reference the EoSim digital-twin platform for hardware-in-the-loop testing. Running one script alone does not establish that a product is validated.

Evidence-backed product validation

The committed tools/catalog/product_inventory.json is the complete product execution set. The v1 contract schemas and policy requirements are documented in docs/hardware-validation-contract-v1.md.

Discover inventory drift and inspect local tool capabilities:

python3 tools/validate_products.py discover
python3 tools/validate_products.py capabilities

Execute V0-V4 for every inventoried product and write hash-bound receipts:

python3 tools/validate_products.py validate \
  --all \
  --output /tmp/ecad-validation \
  --mode evidence
python3 tools/validate_products.py verify-bundle \
  /tmp/ecad-validation/bundle.json

--mode evidence succeeds when the selected inventory was executed and valid receipts were written. Individual products may still be honestly FAIL, BLOCKED, INCONCLUSIVE, or NOT_RUN. Use --mode gate for a release check; it succeeds only when every selected product has real PASS evidence for V0, V1, V2, V3, and V4. Historical baseline entries never waive a failed or missing requirement.

CAD dataset and engineering model

datasets/cad/ holds CAD dataset items for the multi-domain validation work in issue #27. Each item is a STEP design, the design intent the CAD cannot carry, and machine-readable requirements; the pipeline extracts it with the OpenCASCADE kernel, builds an engineering model in which every value states its source and status, and runs V0-V4 with domain simulators. UNKNOWN values are never filled in: a requirement that depends on one is BLOCKED.

python3 -m pip install -r tools/requirements.txt -r tools/requirements-cad.txt
python3 tools/cad_dataset.py check    datasets/cad/robotic_joint_001
python3 tools/cad_dataset.py validate datasets/cad/robotic_joint_001 --output /tmp/joint-run

See datasets/cad/README.md and docs/cad-dataset-engineering-model-v1.md.

License

MIT — see LICENSE.

One exception: the EmbeddedOS original boards in boards/eos, their design files and the footprint library drawn for them are Copyright (c) 2026 Kartikeydheer Srivastava, all rights reserved, and are not under the MIT licence. The exact files are listed in boards/eos/README.md.