From d391993463e7d15935d5ef8d5df3e1db9900f205 Mon Sep 17 00:00:00 2001 From: "Jonathan D.A. Jewell" <6759885+hyperpolymath@users.noreply.github.com> Date: Mon, 14 Sep 2026 20:57:32 +0100 Subject: [PATCH 1/2] docs: state "elegance by default" as the fourth principle, in the owner's register MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Companion to hyperpolymath/standards#783. The standards copy of RSR-PHILOSOPHY.adoc says the manifesto states the same doctrine in the owner's own voice and that "where wording must be reconciled, the manifesto prevails" — so this is the wording that governs, and the standards PR should be reconciled to it rather than the reverse. Two changes: * "Three principles carry most of that weight" -> "Four". Left alone it would have been a silent miscount the moment the section below landed. * New `== Elegance by default`, written in this file's register rather than the standards one: plain prose, no bold lead line, and tied back to a manifesto pillar the way its three siblings are. The tie is to "The wager: value made legible" in README.adoc, which already argues that judgments of value "are usually smuggled in implicitly and backed by authority: trust me, the spec says so, the model said so", and that "a value that is explicit and inspectable can be contested by the people it bears on; a value backed only by authority cannot". An unlabelled list of options is that smuggling in its plainest form — whichever option is listed first or described most fluently becomes the recommendation whether anyone intended it or not. Labelling the elegant arm structures the judgment instead of asserting it, which is what makes it contestable: the owner can then take the other arm deliberately, which is a decision, rather than by default, which is a drift. The owner's instruction included "I will not always pick that, I'm sure", so the section closes by stating that the default is a starting point and not a prediction. Naming the arm is the obligation; taking the other one with full information is legitimate. This file's existing NOTE — "Status: proposed for owner ratification … not yet canon" — is unchanged and still applies to the new section. Co-Authored-By: Claude Opus 5 Claude-Session: https://claude.ai/code/session_014QN8x5x4kNKY8EYCFsCmWB --- docs/RSR-PHILOSOPHY.adoc | 36 +++++++++++++++++++++++++++++++++++- 1 file changed, 35 insertions(+), 1 deletion(-) diff --git a/docs/RSR-PHILOSOPHY.adoc b/docs/RSR-PHILOSOPHY.adoc index ca2ab5e..a4cb171 100644 --- a/docs/RSR-PHILOSOPHY.adoc +++ b/docs/RSR-PHILOSOPHY.adoc @@ -15,7 +15,7 @@ manifesto would state the same doctrine in the owner's register. The manifesto's three pillars — machine-readable governance, neurosymbolic verification, post-disciplinary praxis — describe *what the estate is for*. The -operating doctrine describes *how work is actually undertaken* within it. Three +operating doctrine describes *how work is actually undertaken* within it. Four principles carry most of that weight, because each names a trap that fluent, plausible work falls into. @@ -57,6 +57,40 @@ broken precondition is a forged result — the exact category error the second pillar rejects, fluency mistaken for proof. Prefer a build that breaks to a build that lies. +== Elegance by default + +Treat the most elegant and correct long-term solution as the default choice — and say +which option that is, every time a choice is put to the owner. This is not a preference +for tidiness. It is a refusal to let the judgment be made silently. + +It is the wager applied to the offer itself. A set of options presented as merely +_different_ has already smuggled a judgment of value in implicitly: whichever option is +listed first, or described most fluently, becomes the recommendation whether anyone +intended it or not — and the one doing the smuggling is usually whoever found it +quickest to write. That is a value backed by authority in its plainest form, _these are +your options, trust me_. Naming the elegant and correct arm structures the judgment +instead of asserting it, and structure is what makes it contestable: the owner can then +take the other arm deliberately, which is a decision, rather than by default, which is +a drift. + +So the principle carries three obligations: + +* *Label it* — exactly one option is marked as the most elegant and correct in the long + run, judged on long-run grounds alone: correctness, absence of deferred breakage, no + special cases, a fix at the generator rather than at the instance. Never on effort, + speed, or convenience. Where two options genuinely tie, say so — silence is not a tie. +* *Justify any departure* — a recommendation that is not the elegant arm names both arms + and states, in the offer itself, why the departure is made on this occasion. An + unexplained departure is a defect in the question, not a matter of style. The labels + are never merged to avoid having to write the explanation. +* *It binds unasked decisions too* — this is a methodology, not a formatting rule for + questions. Where the non-elegant arm is taken without asking, that is reported, not + absorbed. + +The default is a starting point, not a prediction. The other arm may be taken with full +information, and often should be; what may not happen is an expedient choice made in +ignorance that it was the expedient one. + == Relation to the canon * `hyperpolymath/standards` — `RSR-PHILOSOPHY.adoc`, the canonical prose source. From 547bc3247876067e3af991a24174c9dd0ad6d714 Mon Sep 17 00:00:00 2001 From: "coderabbitai[bot]" <136622811+coderabbitai[bot]@users.noreply.github.com> Date: Mon, 14 Sep 2026 22:35:00 +0000 Subject: [PATCH 2/2] Fix CodeRabbit issues in PR #86 --- docs/RSR-PHILOSOPHY.adoc | 14 +++++++++----- 1 file changed, 9 insertions(+), 5 deletions(-) diff --git a/docs/RSR-PHILOSOPHY.adoc b/docs/RSR-PHILOSOPHY.adoc index a4cb171..bb5a443 100644 --- a/docs/RSR-PHILOSOPHY.adoc +++ b/docs/RSR-PHILOSOPHY.adoc @@ -75,14 +75,18 @@ a drift. So the principle carries three obligations: -* *Label it* — exactly one option is marked as the most elegant and correct in the long - run, judged on long-run grounds alone: correctness, absence of deferred breakage, no - special cases, a fix at the generator rather than at the instance. Never on effort, - speed, or convenience. Where two options genuinely tie, say so — silence is not a tie. +* *Label it* — normally, exactly one option is marked as the most elegant and correct in + the long run, judged on long-run grounds alone: correctness, absence of deferred + breakage, no special cases, a fix at the generator rather than at the instance. Never + on effort, speed, or convenience. Where two or more options genuinely tie on those + grounds, label every tied option as equally most elegant and correct — silence is not a + tie. * *Justify any departure* — a recommendation that is not the elegant arm names both arms and states, in the offer itself, why the departure is made on this occasion. An unexplained departure is a defect in the question, not a matter of style. The labels - are never merged to avoid having to write the explanation. + are never merged to avoid having to write the explanation. Where options tie, the + singular "`elegant arm`" means the set of equally labelled elegant options: only a + recommendation outside that set is a departure. * *It binds unasked decisions too* — this is a methodology, not a formatting rule for questions. Where the non-elegant arm is taken without asking, that is reported, not absorbed.