OSE Systems Automation: Difference between revisions
(Add working example of automation in OSHW documentation and modeling) |
|||
| Line 22: | Line 22: | ||
If hardware is specified as a schema, and schemas compile deterministically into CAD, BOMs, and build instructions, then hardware becomes replicable the same way software is replicable. | If hardware is specified as a schema, and schemas compile deterministically into CAD, BOMs, and build instructions, then hardware becomes replicable the same way software is replicable. | ||
=D3D Pro Documentation as a prototype= | |||
The [[D3D Pro v23.12]]'s documentation is an example of a plain text, YAML-based, schema defined open-source hardware documentation that is directly rendered into a complete build document and static webpage. The documentation software used is being developed here: [https://github.com/dof-initiative DOF Initiative on Github]. In future updates of the DOF (Distributed Open Source Hardware Framework) software, the schemas will define all of the build steps, CAD and CAM files, the ready-to-publish documentation layouts, and other forms and documents needed for certifications. With integrations into tools like CadQuery, or the FreeCAD API, DOF will be able to make models with any level of detail while saving time doing so. The schema data is stored in plain text files that can be tracked by git, so it can be forked, branched, merged, etc enabling distributed OSHW development at scale akin to FOSS today. | |||
Latest revision as of 00:00, 21 January 2026
Canonical Frame (Non-Negotiable)
The civilization bottleneck OSE is attacking is not labor. It is translation.
Specifically:
Translating design intent into executable production without relying on human memory or hero expertise.
Compiler
Precise Statement (Canonical)
The compiler consumes a schema and deterministically generates a FreeCAD model (and all other downstream artifacts).
Or more formally:
Schema → Compiler → CAD / BOM / Build / QC / Certification Artifacts
Clean Version
https://chatgpt.com/share/696f7727-7704-8010-9b20-a10908e73564
If hardware is specified as a schema, and schemas compile deterministically into CAD, BOMs, and build instructions, then hardware becomes replicable the same way software is replicable.
D3D Pro Documentation as a prototype
The D3D Pro v23.12's documentation is an example of a plain text, YAML-based, schema defined open-source hardware documentation that is directly rendered into a complete build document and static webpage. The documentation software used is being developed here: DOF Initiative on Github. In future updates of the DOF (Distributed Open Source Hardware Framework) software, the schemas will define all of the build steps, CAD and CAM files, the ready-to-publish documentation layouts, and other forms and documents needed for certifications. With integrations into tools like CadQuery, or the FreeCAD API, DOF will be able to make models with any level of detail while saving time doing so. The schema data is stored in plain text files that can be tracked by git, so it can be forked, branched, merged, etc enabling distributed OSHW development at scale akin to FOSS today.