From 77181f1ab0fd3cad29006ba004cd8bcfa55fbd65 Mon Sep 17 00:00:00 2001 From: Rae Lovejoy Date: Fri, 25 Sep 2026 09:49:10 -0700 Subject: [PATCH 1/5] Refresh website for Root Sequence router role --- site/index.html | 169 ++++++++++++++++++++++++------------------------ 1 file changed, 83 insertions(+), 86 deletions(-) diff --git a/site/index.html b/site/index.html index 27bef95..d829ff8 100644 --- a/site/index.html +++ b/site/index.html @@ -9,17 +9,17 @@ Root Sequence · Research for a more coherent world - + - + - + @@ -284,8 +284,8 @@

English / source edition

Research for a more coherent world

-

Root Sequence is an open research project about the connections between people, technology, institutions, and the systems we build.

-

We examine problems that don’t fit neatly within one field. What looks like a technical limitation might also be a question of ownership, coordination, access, or whose knowledge counts. The work follows those connections into practical projects and imagined futures, developing ideas that others can examine, question, and build on.

+

Root Sequence is an open transdisciplinary research and design project for questions that cross fields, connecting ideas without flattening their differences.

+

We start with messy questions that don’t fit neatly within one field. We trace the connections, find the disciplines and methods that already study each part, then reconnect what they reveal without pretending the parts are the same. Some of that work becomes experiments, tools, designs, or imagined futures.

Root Sequence is an independent project started by Rae Lovejoy. Begin with the everyday example, read the current research, or explore selected related projects.

@@ -304,9 +304,9 @@

About Root Sequence

About this project.

-

Root Sequence studies how intelligence, technology, and social systems shape the conditions people live in.

-

Intelligence here includes human reasoning, machine intelligence, and the ways groups and institutions gather information, learn, and make decisions.

-

A service can meet its targets and still be difficult to use. A useful technology can depend on rules that make it hard to repair. Looking at either in isolation leaves part of the problem unexplained.

+

Root Sequence is a place for questions that cross fields, and for figuring out what kind of question you are actually asking.

+

Topics include human and machine intelligence, institutions, infrastructure, embodiment, community, power, and the conditions that make some actions possible while closing off others.

+

A service can meet its targets and still be unusable. A repairable device can still be impossible to repair. A person can have a formal option that is not a real one. Problems like these often belong to several fields at once.

Why “Root Sequence”?

A root is an underlying condition or relationship from which an outcome grows. A sequence is what happens as conditions interact through time, feedback, choice, and consequence.

@@ -315,10 +315,10 @@

Why “Root Sequence”?

Read why the project is called Root Sequence Opens in a new tab -

What the project investigates

-

The research follows connections between technical choices and social conditions: what a tool assumes about its users, who can change it, whose needs are missed, and what happens when it fails. It also revisits alternatives that were tried, abandoned, or never developed.

-

From questions to projects

-

The work includes research notes, essays, design proposals, and experiments. Sources, assumptions, and unresolved questions stay with the work so people can examine how a conclusion was reached and where it might fail.

+

How the research works

+

Root Sequence starts by tracing the whole problem, then breaks it apart again. A technical failure might need reliability engineering; a question about real opportunity might need capability or accessibility research; a boundary or power question might need critical systems methods. The point is not to replace those fields with one theory, but to route each mechanism to strong native methods and reconnect what they show.

+

From research to projects

+

The work keeps sources, assumptions, disagreements, and null results visible so ideas can be narrowed or retired when the evidence pushes back. Some connections become research notes; others become tests, simulations, tools, or design requirements.

Some questions lead to community tools or computing designs; others inform Coherent World and @@ -361,9 +361,9 @@

A repairable devi

A repairable design is not necessarily a repairable system.

-

Here, coherence means looking beyond the object itself. Parts, instructions, software, ownership, cost, and the right to make changes all affect whether repair is actually possible.

- -Read the coherence notes +

The hardware, software, instructions, ownership, cost, access, and decision rights are different parts of the same repair problem. Root Sequence would route each part to the fields that can study it properly, then reconnect the findings to understand the whole system.

+ +See the method and concept router Opens in a new tab
@@ -381,7 +381,7 @@

A repairable devi Selected research and writing

A few places to begin.

-

These are selected entry points, not the complete collection. They lead to longer source documents on GitHub, where the wider body of research notes, analysis, systems work, and essays lives.

+

These are selected entry points into both what Root Sequence studies and how the work is done. They lead to the longer source documents on GitHub.

Browse the wider research repository @@ -390,60 +390,57 @@

  • -

    Working paper

    -

    -Coherence Is a Systems Property -

    -

    A developing argument about examining intelligent systems alongside the institutions, infrastructure, and conditions they depend on.

    -

    AI-assisted draft. Author review pending; not peer reviewed.

    -     -Read the working paper +

    Research method

    +

    How Root Sequence researches

    +

    A repeatable process for preserving an intuition, finding the fields that already study its parts, comparing methods, testing the synthesis, and narrowing or retiring ideas when they don’t add value.

    +     +Read the research method Opens in a new tab
  • -

    Conceptual framework

    -

    Intelligence Ecology

    -

    How training, markets, institutions, permissions, and material conditions reward some forms of intelligent behavior over others.

    -

    Developing framework. Claims about a particular system require their own evidence.

    - -Read Intelligence Ecology +

    Working paper

    +

    Coherence Is a Systems Property

    +

    A developing argument about examining intelligent systems alongside the institutions, infrastructure, and conditions they depend on.

    +

    AI-assisted draft. Author review pending; not peer reviewed.

    +     +Read the working paper Opens in a new tab
  • -

    Design principle

    -

    Making systems understandable

    -

    When a tool or service goes wrong, what do people need to know, and what should they be able to do next?

    - -Read the notes on understandable systems +

    Working framework

    +

    Adaptive continuity and dynamic coherence

    +

    How history can change not only a system’s current state but what it can do next, with explicit limits on cross-domain analogy and no universal coherence score.

    +     +Read the adaptive-continuity framework Opens in a new tab
  • -

    Systems method

    -

    Events, patterns, and scale

    -

    A method for moving between individual events and wider patterns without losing evidence, causality, or accountability.

    - -Read the systems note +

    Knowledge design

    +

    Epistemic discoverability and knowledge routing

    +

    How people can move from the questions and vocabulary they already have toward fields, concepts, sources, and methods they do not yet know how to name.

    +     +Read the knowledge-routing concept Opens in a new tab
  • -

    Systems note

    -

    Resilience and graceful degradation

    -

    How to preserve essential capabilities when dependencies fail, including diverse fallbacks, maintenance, local capacity, and humane limits.

    - -Read the resilience notes +

    Design principle

    +

    Legible Systems

    +

    How a system can remain approachable without hiding the information people need to understand, question, repair, modify, or leave it.

    +     +Read Legible Systems Opens in a new tab
  • -

    Historical analysis

    -

    Revisiting ideas that were left behind

    -

    How to investigate an old possibility without assuming it would have worked, or that people would choose it now.

    - -Read the notes on past possibilities +

    Research resource

    +

    Reading Trails

    +

    Curated routes into the archives, societies, courses, papers, and intellectual neighborhoods that surface during research, kept separate from claim-level evidence.

    +     +Explore the Reading Trails Opens in a new tab
    • @@ -649,7 +646,7 @@

    Suggest a correction

    1. The repairable phone is a hypothetical example for discussion, not an assessment of a particular product. It applies questions developed in the coherence research collection.

      - + Coherence research collection Opens in a new tab @@ -764,7 +761,7 @@

      { "en": { "ui.title": "Root Sequence · Research for a more coherent world", - "ui.description": "Root Sequence is an open research project about the connections between people, technology, institutions, and the systems we build.", + "ui.description": "Root Sequence is an open transdisciplinary research and design project for questions that cross fields, connecting ideas without flattening their differences.", "ui.skip": "Skip to the introduction", "ui.sections": "Sections", "ui.display": "Reading", @@ -799,8 +796,8 @@

      "nav.contact": "Take part", "intro.title1": "Research for a", "intro.title2": "more coherent world", - "intro.lede": "Root Sequence is an open research project about the connections between people, technology, institutions, and the systems we build.", - "intro.p1": "We examine problems that don’t fit neatly within one field. What looks like a technical limitation might also be a question of ownership, coordination, access, or whose knowledge counts. The work follows those connections into practical projects and imagined futures, developing ideas that others can examine, question, and build on.", + "intro.lede": "Root Sequence is an open transdisciplinary research and design project for questions that cross fields, connecting ideas without flattening their differences.", + "intro.p1": "We start with messy questions that don’t fit neatly within one field. We trace the connections, find the disciplines and methods that already study each part, then reconnect what they reveal without pretending the parts are the same. Some of that work becomes experiments, tools, designs, or imagined futures.", "intro.bylineLead": "Root Sequence is an independent project started by", "intro.bylineTail": "Begin with the everyday example, read the current research, or explore selected related projects.", "intro.research": "Explore the research", @@ -815,36 +812,36 @@

      "example.row3": "For the owner", "example.cell3": "A possible repair can still be out of reach.", "example.pull": "A repairable design is not necessarily a repairable system.", - "example.p3": "Here, coherence means looking beyond the object itself. Parts, instructions, software, ownership, cost, and the right to make changes all affect whether repair is actually possible.", - "example.source": "Read the coherence notes", + "example.p3": "The hardware, software, instructions, ownership, cost, access, and decision rights are different parts of the same repair problem. Root Sequence would route each part to the fields that can study it properly, then reconnect the findings to understand the whole system.", + "example.source": "See the method and concept router", "example.next": "Continue to the research", "research.title": "A few places to begin.", - "research.intro": "These are selected entry points, not the complete collection. They lead to longer source documents on GitHub, where the wider body of research notes, analysis, systems work, and essays lives.", - "research.type1": "Working paper", - "research.typeFramework": "Conceptual framework", - "research.typePrinciple": "Design principle", - "research.typeMethod": "Systems method", - "research.typeSystems": "Systems note", - "research.typeAnalysis": "Historical analysis", + "research.intro": "These are selected entry points into both what Root Sequence studies and how the work is done. They lead to the longer source documents on GitHub.", + "research.typeMethod": "Research method", + "research.methodTitle": "How Root Sequence researches", + "research.methodDescription": "A repeatable process for preserving an intuition, finding the fields that already study its parts, comparing methods, testing the synthesis, and narrowing or retiring ideas when they don’t add value.", + "research.methodLink": "Read the research method", + "research.typePaper": "Working paper", + "research.paperTitle": "Coherence Is a Systems Property", "research.paperDescription": "A developing argument about examining intelligent systems alongside the institutions, infrastructure, and conditions they depend on.", "research.paperStatus": "AI-assisted draft. Author review pending; not peer reviewed.", "research.paperLink": "Read the working paper", - "research.ecologyTitle": "Intelligence Ecology", - "research.ecologyDescription": "How training, markets, institutions, permissions, and material conditions reward some forms of intelligent behavior over others.", - "research.ecologyStatus": "Developing framework. Claims about a particular system require their own evidence.", - "research.ecologyLink": "Read Intelligence Ecology", - "research.legibleTitle": "Making systems understandable", - "research.legibleDescription": "When a tool or service goes wrong, what do people need to know, and what should they be able to do next?", - "research.legibleLink": "Read the notes on understandable systems", - "research.scaleTitle": "Events, patterns, and scale", - "research.scaleDescription": "A method for moving between individual events and wider patterns without losing evidence, causality, or accountability.", - "research.scaleLink": "Read the systems note", - "research.resilienceTitle": "Resilience and graceful degradation", - "research.resilienceDescription": "How to preserve essential capabilities when dependencies fail, including diverse fallbacks, maintenance, local capacity, and humane limits.", - "research.resilienceLink": "Read the resilience notes", - "research.historyTitle": "Revisiting ideas that were left behind", - "research.historyDescription": "How to investigate an old possibility without assuming it would have worked, or that people would choose it now.", - "research.historyLink": "Read the notes on past possibilities", + "research.typeFramework": "Working framework", + "research.dynamicTitle": "Adaptive continuity and dynamic coherence", + "research.dynamicDescription": "How history can change not only a system’s current state but what it can do next, with explicit limits on cross-domain analogy and no universal coherence score.", + "research.dynamicLink": "Read the adaptive-continuity framework", + "research.typeConcept": "Knowledge design", + "research.epistemicTitle": "Epistemic discoverability and knowledge routing", + "research.epistemicDescription": "How people can move from the questions and vocabulary they already have toward fields, concepts, sources, and methods they do not yet know how to name.", + "research.epistemicLink": "Read the knowledge-routing concept", + "research.typePrinciple": "Design principle", + "research.legibleTitle": "Legible Systems", + "research.legibleDescription": "How a system can remain approachable without hiding the information people need to understand, question, repair, modify, or leave it.", + "research.legibleLink": "Read Legible Systems", + "research.typeResource": "Research resource", + "research.trailsTitle": "Reading Trails", + "research.trailsDescription": "Curated routes into the archives, societies, courses, papers, and intellectual neighborhoods that surface during research, kept separate from claim-level evidence.", + "research.trailsLink": "Explore the Reading Trails", "research.allLink": "Browse the wider research repository", "research.next": "Where imagination fits", "possibilities.title": "What could be different?", @@ -880,9 +877,9 @@

      "projects.map": "Read the full project map", "projects.next": "Ways to take part", "about.title": "About this project.", - "about.lede": "Root Sequence studies how intelligence, technology, and social systems shape the conditions people live in.", - "about.intelligence": "Intelligence here includes human reasoning, machine intelligence, and the ways groups and institutions gather information, learn, and make decisions.", - "about.p1": "A service can meet its targets and still be difficult to use. A useful technology can depend on rules that make it hard to repair. Looking at either in isolation leaves part of the problem unexplained.", + "about.lede": "Root Sequence is a place for questions that cross fields, and for figuring out what kind of question you are actually asking.", + "about.intelligence": "Topics include human and machine intelligence, institutions, infrastructure, embodiment, community, power, and the conditions that make some actions possible while closing off others.", + "about.p1": "A service can meet its targets and still be unusable. A repairable device can still be impossible to repair. A person can have a formal option that is not a real one. Problems like these often belong to several fields at once.", "about.nameTitle": "Why “Root Sequence”?", "about.nameMeaning": "A root is an underlying condition or relationship from which an outcome grows. A sequence is what happens as conditions interact through time, feedback, choice, and consequence.", "about.nameQuestion": "Together, the name asks: What conditions made this possible, and what does it make possible next? What happens next can become part of the starting conditions for whatever follows.", @@ -931,10 +928,10 @@

      "details.siteLicense": "CC0 license", "details.fontCredit": "The embedded Cascadia Mono wordmark font is provided by Microsoft under the SIL Open Font License 1.1.", "details.fontLicense": "Cascadia Mono license", - "about.scopeTitle": "What the project investigates", - "about.scope": "The research follows connections between technical choices and social conditions: what a tool assumes about its users, who can change it, whose needs are missed, and what happens when it fails. It also revisits alternatives that were tried, abandoned, or never developed.", - "about.workTitle": "From questions to projects", - "about.work1": "The work includes research notes, essays, design proposals, and experiments. Sources, assumptions, and unresolved questions stay with the work so people can examine how a conclusion was reached and where it might fail.", + "about.scopeTitle": "How the research works", + "about.scope": "Root Sequence starts by tracing the whole problem, then breaks it apart again. A technical failure might need reliability engineering; a question about real opportunity might need capability or accessibility research; a boundary or power question might need critical systems methods. The point is not to replace those fields with one theory, but to route each mechanism to strong native methods and reconnect what they show.", + "about.workTitle": "From research to projects", + "about.work1": "The work keeps sources, assumptions, disagreements, and null results visible so ideas can be narrowed or retired when the evidence pushes back. Some connections become research notes; others become tests, simulations, tools, or design requirements.", "about.work2": "Some questions lead to community tools or computing designs; others inform Coherent World and No One Noticed. Findings and problems from those projects can feed back into the research. An imagined result in a story is kept separate from evidence that something works.", "intro.about": "About Root Sequence", "overlay.close": "Close", From 209c99782d2170bf0fa222aaf3063357458d9c15 Mon Sep 17 00:00:00 2001 From: Rae Lovejoy Date: Fri, 25 Sep 2026 09:50:09 -0700 Subject: [PATCH 2/5] Update website tests for router-role review candidate --- site/test_site.py | 21 ++++++++++++--------- 1 file changed, 12 insertions(+), 9 deletions(-) diff --git a/site/test_site.py b/site/test_site.py index bbe6320..9b9ecf9 100644 --- a/site/test_site.py +++ b/site/test_site.py @@ -16,7 +16,7 @@ HERE = Path(__file__).resolve().parent -APPROVED_PREVIEW_SHA256 = "08a1ce67f37f3db55e235cb3703bcdb552deead2ffd4aafd6cd732f69b384356" +LAST_APPROVED_PREVIEW_SHA256 = "08a1ce67f37f3db55e235cb3703bcdb552deead2ffd4aafd6cd732f69b384356" spec = importlib.util.spec_from_file_location("site_builder", HERE / "build.py") builder = importlib.util.module_from_spec(spec) spec.loader.exec_module(builder) @@ -87,11 +87,11 @@ def parse(self, path): parser.feed(path.read_text(encoding="utf-8")) return parser - def test_canonical_source_is_the_approved_preview(self): + def test_review_candidate_differs_from_last_approved_preview(self): actual = hashlib.sha256((HERE / "index.html").read_bytes()).hexdigest() - self.assertEqual(actual, APPROVED_PREVIEW_SHA256) + self.assertNotEqual(actual, LAST_APPROVED_PREVIEW_SHA256) - def test_preview_build_preserves_the_approved_html_exactly(self): + def test_preview_build_preserves_the_review_html_exactly(self): output, manifest = self.build() self.assertEqual((output / "index.html").read_bytes(), (self.root / "index.html").read_bytes()) self.assertEqual(manifest["build_mode"], "preview") @@ -169,17 +169,20 @@ def test_required_approved_copy_and_controls_are_present(self): for phrase in ( "Research for a", "more coherent world", - "Root Sequence is an open research project", - "Intelligence here includes human reasoning, machine intelligence", + "Root Sequence is an open transdisciplinary research and design project", + "Root Sequence is a place for questions that cross fields", "Root Sequence is an independent project started by", "https://github.com/raelovejoy", "Why “Root Sequence”?", "What conditions made this possible, and what does it make possible next?", "https://github.com/Root-Sequence/root-sequence/blob/main/concepts/root-sequence.md", "Selected research and writing", - "Intelligence Ecology", - "Events, patterns, and scale", - "Resilience and graceful degradation", + "How Root Sequence researches", + "Adaptive continuity and dynamic coherence", + "Epistemic discoverability and knowledge routing", + "Legible Systems", + "Reading Trails", + "https://github.com/Root-Sequence/root-sequence/blob/main/research/method-router.md", "Being Human(e): An Incomplete Guide", 'id="project-humane"', "Its public website has not been built yet", From 919e3acc45759041ee61055316b77f5c88f2737a Mon Sep 17 00:00:00 2001 From: Rae Lovejoy Date: Fri, 25 Sep 2026 09:50:41 -0700 Subject: [PATCH 3/5] Mark website source as unapproved router-role candidate --- site/README.md | 14 +++++++++----- 1 file changed, 9 insertions(+), 5 deletions(-) diff --git a/site/README.md b/site/README.md index a7e9e51..4c7741b 100644 --- a/site/README.md +++ b/site/README.md @@ -2,11 +2,15 @@ This directory is the canonical source for `rootsequence.systems`. -The current [`index.html`](index.html) is the single-page public seed approved -by Rae Lovejoy on 2026-09-18. It includes a short explanation of the name Root -Sequence, a link to the canonical concept page, and the six-item Selected -Research section. It is tied to the exact digest recorded in -[`approval.json`](approval.json). +The current [`index.html`](index.html) on this branch is a **review candidate** +updated on 2026-09-25 to reflect Root Sequence's router-and-synthesis role, +canonical research method, adaptive-continuity work, epistemic discoverability, +Legible Systems, and Reading Trails. It is **not yet publication-approved**. + +The last approved public seed remains the 2026-09-18 edition recorded in +[`approval.json`](approval.json). That approval intentionally does not match +this candidate, so `build.py --release` remains blocked until Rae Lovejoy +reviews and explicitly approves the new source. The page is one self-contained file with its styles, scripts, favicon, and Cascadia Mono wordmark font embedded. It makes no runtime requests for fonts, From f207ef1df20c8938fc85afe669cfcf8e39802f81 Mon Sep 17 00:00:00 2001 From: Rae Lovejoy Date: Fri, 25 Sep 2026 09:50:43 -0700 Subject: [PATCH 4/5] Record router-role website copy candidate --- site/COPY-REVIEW.md | 50 +++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 50 insertions(+) diff --git a/site/COPY-REVIEW.md b/site/COPY-REVIEW.md index 5eb8389..52f7fca 100644 --- a/site/COPY-REVIEW.md +++ b/site/COPY-REVIEW.md @@ -1,5 +1,55 @@ # Website copy review: September 16, 2026 +## Review candidate: Root Sequence router role — September 25, 2026 + +**Status: awaiting Rae Lovejoy's editorial approval. Not approved for release.** + +This candidate updates the public explanation after the merged +adaptive-continuity / research-method work changed Root Sequence's current +self-description. + +The one-page structure, headline **"Research for a more coherent world,"** +reading controls, selected-project section, participation routes, visual +design, embedded assets, and publication architecture remain unchanged. + +### Copy changes + +- The introduction now describes Root Sequence as an **open transdisciplinary + research and design project for questions that cross fields**. +- The About section explains the current workflow in plain language: + trace the whole problem, identify the different kinds of question inside it, + route mechanisms to the fields and methods that study them, then reconnect + the findings without pretending the mechanisms are identical. +- The repair example no longer presents "coherence" as the catch-all answer. + It shows the device, software, access, ownership, cost, and decision-right + questions as different parts of one problem and routes readers to the + Method & Concept Router. +- The six Selected Research entries now foreground: + 1. Root Sequence Research Method; + 2. *Coherence Is a Systems Property*; + 3. Adaptive continuity and dynamic coherence; + 4. Epistemic discoverability and knowledge routing; + 5. Legible Systems; + 6. Reading Trails. +- The social/metadata description now reflects the transdisciplinary + research-and-design role. + +### What this candidate does not claim + +The site does not say Root Sequence invented the native theories it routes to. +It does not present Dynamic Coherence as a universal analysis method or score. +It does not claim the editorial router pilots validated the method. + +The research repository remains the canonical source for the details and +evidence boundaries. + +### Approval boundary + +`approval.json` is intentionally unchanged from the 2026-09-18 approved +edition. The release builder must continue to reject this candidate until a +new exact-source approval is recorded. + + ## Approval update: name explanation — September 18, 2026 The current candidate adds a short **Why “Root Sequence”?** passage to the From 6cbc79d21c629776847703efe8ba785baefacd10 Mon Sep 17 00:00:00 2001 From: Rae Lovejoy Date: Fri, 25 Sep 2026 09:51:45 -0700 Subject: [PATCH 5/5] Record router-role website candidate validation --- site/VALIDATION.md | 38 ++++++++++++++++++++++++++++++++++++++ 1 file changed, 38 insertions(+) diff --git a/site/VALIDATION.md b/site/VALIDATION.md index 3405b00..b2609ad 100644 --- a/site/VALIDATION.md +++ b/site/VALIDATION.md @@ -1,5 +1,43 @@ # Local validation — 2026-09-16 +## Router-role copy candidate — September 25, 2026 + +**Status: review candidate only; not approved or released.** + +Connector-level structural checks on the branch found: + +- one `h1`; +- 60 unique HTML IDs with no duplicates; +- 27 internal fragment links with no missing targets; +- English translation JSON parses and covers all 171 referenced i18n/aria keys; +- two executable inline scripts remain present and the CSP still declares two + SHA-256 script hashes; the copy edit changed only HTML text, links, and the + non-executable translation JSON; +- all new canonical GitHub destinations exist on current `main`: + - `research/method.md`; + - `research/method-router.md`; + - `research/papers/coherent-systems/paper.md`; + - `concepts/dynamic-coherence.md`; + - `concepts/epistemic-discoverability.md`; + - `concepts/legible-systems.md`; + - `research/reading-trails/README.md`; +- the old selected-research labels (Intelligence Ecology, Events/patterns/scale, + Resilience/graceful-degradation, historical-contingency entry) are no longer + present in the selected-reading copy; +- required router-role copy is present in both visible HTML and the English + translation table. + +`test_site.py` was updated so this branch is treated as an **unapproved review +candidate** rather than falsely expected to match the September 18 approved +preview. The release approval record remains unchanged, so the actual +`build.py --release` gate is intentionally expected to reject this candidate +until Rae Lovejoy approves the exact current source. + +The complete Python site test suite and browser-layout/render checks were **not +executed in this connector-only pass**. They remain required before publication. +No live-domain or deployment check is claimed. + + ## Approved Root Sequence name explanation — 2026-09-18 - The About section includes a compact explanation of “root,” “sequence,” and