Product source
OpenDrone
Editable hardware designs and firmware for OpenDrone.
.cpp
Firmware.cppSourceReviewOutputsEvidence
Connected source
The workspace
03 / Connected ownership
Workspace explorerHardware in context
Reusable automation
Shared tooling
Shared checks, exporters and templates reduce repeated engineering work.
.py
Design checks.py.py
Manufacturing export.py.yml
Repository templates.ymlSourceReviewOutputsEvidence
Controlled handoff
Production
Design revisions connect to manufacturing packs and build instructions.
.json
Source identity.json.zip
Manufacturing pack.zip.pdf
Build instructions.pdfSourceReviewOutputsEvidence
Procedures, recorded captures and reports keep physical evidence together.
.md
Procedure.md.csv
Capture.csv.pdf
Report.pdfSourceReviewOutputsEvidence
Materials & origin
Sourcing & stock
Specifications connect supplier evidence and material lots to their use.
.pdf
Specification.pdf.json
Supplier evidence.json.json
Lot → build.jsonSourceReviewOutputsEvidence
Evidence assembly
Compliance
Requirements and source manifests organise evidence and expose gaps.
.yaml
Requirements.yaml.json
Source manifest.json.json
Evidence gaps.jsonSourceReviewOutputsEvidence
Company foundation
Operations
Company records connect purchases, receipt reviews and their evidence.
.json
Purchase records.json.json
Receipt review.json.pdf
Linked evidence.pdfSourceReviewOutputsEvidence
Shared knowledge
Education
Reusable project and media tools help explain how the hardware works.
.py
Project template.py.mp4
Demonstration.mp4.vtt
Transcript.vttSourceReviewOutputsEvidence
OpenDrone / engineering examples
Design · Evidence · HistoryFiles. With a family tree.
Open in 3D ↗ SchematicConnected components ↗ PCBEvery copper layer ↗ Bench exampleSeparate ESC capture ↗ ReleaseSource → outputs ↗ Design source→Manufacturing pack→Physical build→Evidence
Independent source · Controlled handoffsPublic repositories ↗