From 76690f66e92e4244ed9e47738dfa6daf928fb57b Mon Sep 17 00:00:00 2001 From: Tommaso Bianchi Date: Thu, 30 Jul 2026 21:11:50 +0200 Subject: [PATCH] docs: the UX charter names only this fork's product MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit 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. --- docs/cad_ux_guidelines.md | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/docs/cad_ux_guidelines.md b/docs/cad_ux_guidelines.md index 72545c9054..92da2b4c57 100644 --- a/docs/cad_ux_guidelines.md +++ b/docs/cad_ux_guidelines.md @@ -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 3–9 are written so that a reviewer can hold a pull request against them and get a yes or a no.