## Source

- "Add open-source licence to `hardware` repo + styled README"
- "Make a `hardware` repository as public one"
- "Setup public GitHub org (logo, domain verification, etc.)"

## Current state

- The `shellbuild/hardware` repository already exists but is **private**, has **no licence**, and has a README, `DESIGN.md`, `core/`, `tools/` and `.opencode/`.
- The `shellbuild` organisation exists, but its description is empty and `is_verified` is false.

## Acceptance

- [ ] Present licence options and a recommendation for the hardware files and any code. Do not add a licence until the owner chooses.
- [ ] Audit the repository history and working tree for secrets or private material before making it public.
- [ ] Replace the README with a styled one covering the hardware overview, BOM, assembly, CAD/build instructions, compatibility and contribution rules.
- [ ] Prepare the repository for public release, but make it public only after the licence, history audit and draft-spec review are complete. Hardware is currently spec/design only (#92).
- [ ] Finish the organisation profile: logo, description, website and verified `shell.build` domain.
- [ ] Add CI that runs the CAD build/validation commands the repository depends on.
- [ ] Remove or document `.opencode/` and any other agent-only files.
- [ ] Cross-link the hardware repository from `shell.build/hardware` and this repository.

The GitHub OAuth app move and logo remain in #69; this issue owns the organisation profile and hardware repository.


<sub>Generated on _MrBeast_ using _opencode/deepseek-v4.1-flash_ in _ses_e8326e581ffeJviTmSkomwnKES_</sub>