docs: the UX charter names only this fork's product

The doctrine is shared but the document is not: each fork's copy now speaks
about its own product only, so it reads as that project's own charter rather
than as a note about a sibling repository. This is a deliberate divergence —
the two copies must NOT be reconciled by a parity sweep. The CAD sources stay
byte-identical; only this doc branches.

snaporca-2is.
This commit is contained in:
Tommaso Bianchi
2026-07-30 21:11:50 +02:00
parent 8cc08845a8
commit 76690f66e9
+2 -3
View File
@@ -1,8 +1,7 @@
# Orca-CAD — UX guidelines and design charter
Status: proposed, v1. Owner: design working group. Applies to the Design tab in
both forks (Orca-CAD on OrcaSlicer, SnapOrca-CAD on Snapmaker Orca) — the CAD
sources are byte-identical across them, so the UX doctrine is one doctrine.
Status: proposed, v1. Owner: design working group. Applies to the Design tab
the parametric CAD environment inside OrcaSlicer.
This document is a **review instrument**, not an essay. Sections 39 are written
so that a reviewer can hold a pull request against them and get a yes or a no.