gunnchOS

Devices · STAGING_WORKER

Hardware industrial design

First-party hardware design status for the gunnchOS hardware work, including the Hardware Quartet design record.

Explore device

Explore device

Records copied from this repository

Overview

Overview

# gunnchos-hardware-industrial-design Industrial and electrical design source of truth for the **gunnchOS3k** first-party device family (Student 14.5, Handheld Hybrid, DS-XL Coder, Edge I/O Rings, First-party Dock). > **Current release/state:** `PHYSICAL_PENDING` — design/BOM/RFQ *packets* exist; no fab, no certification, no RFQ send from Cursor. > **Hardware v1.0 mainline (this campaign):** see [`hardware_v1/`](hard

What is this?

CAD, BOM, device-class specs, firmware/OS compatibility handoff packages, and manufacturer-facing design artifacts for first-party hardware.

Why does it exist?

So OS, Lab, manufacturing, and education work share one honest hardware truth before physical EVT.

Methods

# Reproducibility — gunnchos Hardware Industrial Design ## Clone / setup / run ```bash git clone https://github.com/gunnchOS3k/{name}.git cd gunnchos-hardware-industrial-design # See README.md for repo-specific setup python3 scripts/check_required_files.py # Expected: CI smoke pass; tests pass or documented skip ``` ## Expected outputs - Required documentation files present (`python3 scripts/check_required_files.py`) - Tests pass **or** documented smoke-only path for docs-only repos - No claim of field deployment from synthetic outputs alone ## Tool versions | Tool | Version guidance | |------|------------------| | Python | 3.10+ where `requirements.txt` exists | | Node | 18+ LTS where `pac

Native research runtimes stay on a local checkout. This page shows repository records only.

Artifacts

Source

Source repository

Pinned source af5af66a28e36351b3929ef15756b6df6381ff6a

Limitations

About / Build status / Evidence

What is this?

First-party hardware design status for the gunnchOS hardware work, including the Hardware Quartet design record.

The research code is not executing here. This is a research surface.

Why does it exist?

It gives this repository a public web surface inside the gunnchOS ecosystem without pretending the original runtime runs on Cloudflare Workers.

What can I actually do with it today?

Use the primary action to inspect repository records, then open the source for the local toolchain.

What is not finished?

STAGING_WORKER

Runtime mode on this page: PRECOMPUTED. No remote model call is made.