Status: scaffolded Publication state: public scaffold Release state: not released
embedded-hardware-lab is a public scaffold for synthetic embedded hardware and PCB pattern studies. It documents KiCad public-safe rules, Pico/RP-series and generic MCU patterns, firmware boundaries, sensor/actuator integration notes, breadboard-to-PCB workflow, test harness templates, diagrams, and validation notes.
This repo is not a production hardware repository, manufacturing package, released firmware source, customer hardware record, certified design package, or deployment source. It does not contain production board source, routing, BOMs, Gerbers, exact pin maps, private firmware, customer hardware, customer wiring, manufacturing details, credentials, endpoints, or sealed source.
| Field | Value |
|---|---|
| Build state | scaffolded |
| Public GitHub repo | published scaffold |
| Publication state | public scaffold |
| Release state | not released |
| Published artifact | scaffolded |
| Released artifact | not released |
| Profile routing | planned |
| Proof-stack routing | planned |
The repo covers documentation patterns for:
- public-safe board study rules;
- generic MCU role patterns;
- Pico/RP-series context without exact assignments;
- firmware boundary policy;
- sensor/actuator integration notes;
- breadboard-to-PCB workflow review;
- public-safe test harnesses;
- validation templates.
Board pattern content must remain synthetic, simplified, and reviewed. KiCad examples may document public-safe study rules and schematic-symbol boundaries, but must not include production board source, routing, BOMs, Gerbers, or manufacturing-ready files.
MCU patterns may describe generic role categories, interface boundaries, and validation prompts. They must not include exact private pin maps, product-specific assignments, private firmware, or customer hardware.
Firmware examples, if added later, must be synthetic and non-production. They must not include private firmware, credentials, endpoints, live-device execution logic, customer integrations, or deployment claims.
Integration notes may describe generic sensor roles, actuator roles, harness review prompts, and public-safe test assumptions. They must not include customer parts, customer wiring, or production harness drawings.
Workflow notes may document review stages from synthetic breadboard concept to public-safe PCB study. They must not include manufacturing-ready design packages or supplier-specific production records.
Pin content must remain role-based and generic. Exact pin maps and product-specific assignments are excluded.
Test harness notes may use mock data and synthetic validation prompts. They must not include private logs, live hardware telemetry, or customer test records.
KiCad content is allowed only as public-safe rules, synthetic schematic-symbol notes, or reviewed non-production examples. Manufacturing files are excluded.
Run:
bash scripts/validate-public-boundary.sh
rg -n "planned|scaffolded|published|released|private/not-public|production board source|routing|BOMs|Gerbers|exact pin maps|private firmware|manufacturing details|customer hardware|customer wiring|certified-design|validation|review" .
git diff --check
git status --short
git remote -vThis repository contains public-safe embedded hardware, PCB, firmware-boundary, and validation studies only. It does not contain production board source, routing, BOMs, Gerbers, exact pin maps, private firmware, manufacturing details, customer hardware, customer wiring, private test logs, certified-design claims, credentials, endpoints, or sealed source. KiCad examples, MCU patterns, firmware snippets, breadboard notes, and test harnesses are synthetic unless explicitly marked as reviewed public material.
Franzabner profile routing and franzabner-proof-stack routing remain planned. Any routing update must be handled as a separate reviewed change with release state not released and proof state scaffolded.
The first planned artifact is:
mcu-patterns/public-safe-mcu-management-bus-pattern.md
The earlier mcu-patterns/pico-rp-series-pattern.md file remains supporting scaffold material. The first artifact remains scaffolded until human review approves any later public creation or routing work.