Skip to main content

max / everycycle

Drop link into now-private cross-project style doc The Rhai style guide / brand / hardware-operation notes moved to the private _private/docs/meta tree (git=public / Syncthing=private reorg). Reword to reference the convention without a path into private storage; the public _meta/scripts/lint-rhai.sh link is kept where present.
Co-Authored-By
Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Author: Max Johnson <me@maxj.phd> · 2026-06-05 01:28 UTC
Signed with PGP, not checked
Commit: 32e9819a135a926d36c4632541763f2387a67745
Parent: e582881
2 files changed, +2 insertions, -2 deletions
M CONTRIBUTING.md +1 -1
@@ -12,7 +12,7 @@
12 12
13 13 ## Documentation
14 14
15 - - Per-project doc files follow Make Creative's [markdown standards](../../../code/_meta/docs/markdown_standards.md) (private link; the convention summary is below).
15 + - Per-project doc files follow Make Creative's markdown standards (internal; the convention summary is below).
16 16 - Architecture lives in `docs/architecture.md`.
17 17 - A `CHANGELOG.md` will appear once there are user-visible changes worth recording. Until then, the git log is the record.
18 18
M docs/roadmap.md +1 -1
@@ -95,7 +95,7 @@
95 95 | **H3** | Entry-level edge | Hobbyists, classrooms, residencies (~$2K) | Mini-ITX or SFF, single GPU, quiet, low-power. |
96 96 | **H4** | Rack appliance | Datacenter and colo deployments (~$15K+) | 2U or 4U, 4-8 GPU bays, redundant PSU, dual NIC, OpenBMC. |
97 97
98 - Each milestone produces: published BOM, chassis CAD, thermal model, BMC firmware bundle, EveryCycle config tuned for the platform, assembly guide. See `_meta/docs/hardware_operation.md` for the broader operation framing (chassis, residency, supplier relationships).
98 + Each milestone produces: published BOM, chassis CAD, thermal model, BMC firmware bundle, EveryCycle config tuned for the platform, assembly guide. See the internal hardware-operation notes for the broader operation framing (chassis, residency, supplier relationships).
99 99
100 100 ### Thread I — Client API and adoption
101 101