Living paper v0.1-dev: evidence, author input, and linked practice

README.md

@@ -59,6 +59,7 @@ A recursive process rather than a fixed path.
 ## 📂 Repository Map
 
 - `/site/` — reader-facing Public Seed website source; not a replacement for research or the Wiki
+- `/research/` — versioned synthesis papers; source treatments retain their existing canonical homes
 - `/core/` — foundational texts and framework documents
 - `/systems/` — models and methods for understanding how systems behave under stress and failure  
 - `/concepts/` — glossary and key definitions  
@@ -80,6 +81,7 @@ The internal repository map is also described in [`root_map.md`](root_map.md). T
 Suggested entry points:
 
 - [Public Seed website source](site/README.md) — reader-facing introduction and five Atlas guides; hosting remains separate
+- [Coherence Is a Systems Property](research/papers/coherent-systems/README.md) — living-paper scaffold, v0.1-dev; author review pending
 - [Ecosystem Map](ECOSYSTEM.md) — understand the wider project family  
 - [Root Sequence Wiki](https://github.com/Root-Sequence/wiki) — browse terms, phrases, projects, provenance, and conceptual archaeology  
 - [Idea Trails](IDEA_TRAILS.md) — understand the recurring questions and how each project transforms them  

THOUGHT_ROUTING.md

@@ -45,6 +45,16 @@ Check, as relevant:
 
 Search for the mechanism and question, not only the exact phrase. Similar wording may hide different ideas; different wording may describe the same one.
 
+#### Build on existing work; name the actual gap
+
+**Clarified by the author, 2026-09-16:** Interest in an idea or outside guidance is not a request to create another framework. Look for relevant established work as well as existing project documents. Reuse what already addresses the need, connect missing references, and extend only what remains insufficiently covered. A useful synthesis need not claim novelty.
+
+Before proposing a new framework, taxonomy, repository, or tracking layer, state what the existing options cannot do and ask whether a new structure is wanted. Do not make new terminology the default response to enthusiasm. A passage in an existing home may be enough.
+
+During a routing detour, preserve the active project's next unresolved question in its existing record. After the update, return a short recap of what we were doing and that question, rather than another expanding plan. Keep proposed interpretations separate from author decisions. A request to save insights does not answer a previously open conceptual question.
+
+Apply the [participation and review-burden lesson](core/legible-systems.md#participation-sensemaking-and-review-burden): reduce reconstruction work, do not count document production as comprehension, and check unresolved dependencies before consequential commitments. Exploratory ideas may remain separate or be dropped; the map does not have to make every connection fit.
+
 ### 3. Classify on separate axes
 
 Do not collapse these into one vague status.

core/legible-systems.md

@@ -3,6 +3,8 @@
 **Status:** Working foundation / cross-domain design principle  
 **First formalized here:** 2026-09-06
 
+**Recent addition:** [Participation, sensemaking, and review burden](#participation-sensemaking-and-review-burden) connects the existing principle to checked W3C guidance and records the living-paper conversation's practical lessons.
+
 ## Core idea
 
 A **legible system** can be used simply without requiring its workings to remain mysterious.
@@ -339,4 +341,48 @@ More generally:
 
 > **A humane system should help the people inside it understand the system, participate in it, question it, modify it, and eventually need its designers less.**
 
-That is the direction of travel, not a claim that every system can or should become equally simple.
+That is the direction of travel, not a claim that every system can or should become equally simple.
+
+---
+
+## Participation, sensemaking, and review burden
+
+**Added:** 2026-09-16, from the living-paper conversation. **Status:** working design interpretation; no usability or efficacy result. This extends the existing treatment, not a new framework. Earlier material above is preserved.
+
+> **Understanding can develop through supported participation; it needn't arrive fully formed before participation begins.**
+
+This is a project formulation, not a quotation from W3C or a claim of scholarly novelty. Invite questions, examples, corrections, and uncertainty before demanding a finished explanation. Keep relevant evidence available. Support for exploration does not authorize consequential action without adequate understanding, consent, or safeguards.
+
+### Sensemaking without forced agreement
+
+Weick, Sutcliffe, and Obstfeld's *Organizing and the Process of Sensemaking* (2005) connects explicit interpretations of circumstances with action. The publisher's abstract and bibliographic details were checked; this is not a full-text review.[^sensemaking2005]
+
+Our application distinguishes understanding what someone says, understanding why a choice seemed reasonable, and concluding that an account fits the evidence. One does not establish the others. Assistance should help make an interpretation inspectable and revisable, not manufacture agreement or mistake fluency for truth. "Supported sensemaking" is descriptive language here, not a named replacement for existing research.
+
+### Do not transfer the burden and call it assistance
+
+A proposed failure pattern in AI-assisted work is: more documents produced, more apparent progress, more unacknowledged reading and verification work for the person. This is a workflow hypothesis, not a measured result from this project. Review effort, comprehension, unresolved decisions, and the ability to resume deserve attention alongside output volume.
+
+Keep the current passage, source locator, decision status, and next question together. Provide reminders with actionable alternatives or a route to someone able to change the constraint. A warning alone cannot create time, resources, or decision authority. Explanations must remain challengeable, and neither refusal nor uncertainty should count as failure to understand.
+
+### Existing guidance to use before adding new rules
+
+The following sources were checked on 2026-09-16 at the stated scope. Their roles differ; none certifies Root Sequence, a whole framework, or an implementation. Extending web guidance into institutional or collaborative settings is our proposed application, not demonstrated universal transfer.
+
+| Source and exact edition | Material inspected and possible use | Boundary |
+|---|---|---|
+| [Making Content Usable for People with Cognitive and Learning Disabilities](https://www.w3.org/TR/2021/NOTE-coga-usable-20210429/), Working Group Note, 29 April 2021 | Abstract/status, easy-language summary, objective/pattern headings, and focus/recovery passages: familiar steps, less reliance on memory, summaries, error recovery, help, and involving affected users. | Supplemental guidance, not additional WCAG conformance requirements. No pattern-by-pattern audit or user testing performed here. |
+| [Web Platform Design Principles](https://www.w3.org/TR/2026/NOTE-design-principles-20260914/), Group Note, 14 September 2026 | Abstract/status and section 1.1: prioritize user needs while acknowledging implementation dependencies and finite resources. | API-design guidance, not proof of a universal priority rule or endorsement of our project. |
+| [Privacy Principles](https://www.w3.org/TR/2025/STMT-privacy-principles-20250515/), W3C Statement, 15 May 2025 | Status and section 1.1.2: privacy labor concerns offloading protective work onto the people affected by data processing. | A grounded comparison for responsibility transfer; not a reason to remove meaningful choice or consent. |
+| [Ethical Web Principles](https://www.w3.org/TR/2024/STMT-ethical-web-principles-20241212/), W3C Statement, 12 December 2024 | Sections 2.7–2.11: verifiable information, individual control, reduced centralization, environmental effects, inspectability, and interoperable alternatives. | Normative design principles, not evidence that actual web systems already deliver them. |
+| [Web Sustainability Guidelines](https://www.w3.org/TR/2026/DNOTE-web-sustainability-guidelines-20260820/), Group Note Draft, 20 August 2026 | Abstract/status and section headings: impacts on people and the environment, infrastructure, product management, maintenance, and resource budgets. | Initial orientation only; not a completed standard, impact calculation, or full guideline review. |
+
+W3C's cognitive guidance explicitly goes beyond WCAG's requirements. The practical lesson for this project is to examine unmet needs even when formal requirements have been met; it is not permission to disregard those requirements.
+
+### Learning while building
+
+Exploration can branch before every question is resolved. Before a consequential commitment, identify what it depends on, which assumptions remain unsettled, and who bears failure. Retain reversible trials and revision paths where possible. Do not force every idea into a final harmonious account: some connections may fail, remain unresolved, or be better kept separate.
+
+Use the existing [thought-routing convention](../THOUGHT_ROUTING.md) to record these distinctions without another tracking system. The [paper's drafting instructions](../research/papers/coherent-systems/AGENTS.md) apply them to passage-level author review. These links describe saved process guidance, not an implemented or validated interface.
+
+[^sensemaking2005]: Karl E. Weick, Kathleen M. Sutcliffe, and David Obstfeld (2005), *Organizing and the Process of Sensemaking*, Organization Science 16(4), 409–421. DOI: 10.1287/orsc.1050.0133. [Publisher abstract and citation](https://pubsonline.informs.org/doi/10.1287/orsc.1050.0133). No claim that an intelligible interpretation is therefore correct.

core/universal_coherence_framework.md

@@ -1,5 +1,11 @@
 # Universal Coherence Framework
 
+**Scope notice added 2026-09-16:** The earlier Root Sequence summary below is retained, not promoted to the canonical UCF specification. UCF is an optional analytical framework; its proposed revision lives in the [dedicated repository](https://github.com/Root-Sequence/universal-coherence-framework/blob/c4d7b236828a59139c0d5204b1faaed13154682a/models/ucf-model-v1.1-draft.md). See the [living-paper reconciliation](../research/papers/coherent-systems/notes/ucf-reconciliation.md) for definitions and provenance. Both remain drafts awaiting author review.
+
+The six headings below are a local explanatory sequence, not UCF's four analytical layers or four optional state labels. Statements about natural drift are working hypotheses, not demonstrated laws. Functional fit does not by itself establish wider benefit or legitimate authority.
+
+---
+
 The Universal Coherence Framework (UCF) describes how systems align—or fail to align—with reality over time.
 
 It is not a fixed model. It is a way of observing whether a system holds together internally, interacts accurately with the world, and sustains itself without generating hidden instability.

research/README.md

@@ -0,0 +1,15 @@
+# Research syntheses
+
+This directory holds versioned papers that synthesize Root Sequence's existing research. It does not replace the canonical treatments in `concepts/`, `systems/`, `analysis/`, or `futures/`.
+
+## Living papers
+
+- [Coherence Is a Systems Property](papers/coherent-systems/README.md) — **v0.1-dev; AI-assisted working draft; author review pending**. Charter, annotated argument, claims ledger, source map, and research questions. Not a reviewed release or a validated theory.
+
+A paper proposes a synthesis; the underlying research can contradict and revise it. Do not move material into this directory merely to make the paper appear comprehensive.
+
+## Publication boundary
+
+Public branches and pull requests in this repository are public. They are not private review spaces. Only public-safe synthesis belongs here; private notes and unpublished fiction retain their existing homes and permissions. Website presentation is separate and requires an explicit publication pass.
+
+[Repository map](../root_map.md) · [Contribution guidance](../contributing.md)

research/papers/coherent-systems/AGENTS.md

@@ -0,0 +1,33 @@
+# Drafting and author review
+
+**Requested workflow, recorded 2026-09-16.** Applies to the paper and its supporting notes. This process does not approve any manuscript claim or authorize publication.
+
+## Work through questions
+
+Retrieve relevant existing project material before asking the author to repeat it. Draft one manageable passage or decision at a time. When an ambiguity changes meaning, scope, claims, values, attribution, or publication, ask before making that decision on the author's behalf.
+
+Default to one substantive question at a time. Supply the short passage, example, or source locator needed to answer. Two or three concrete alternatives can help, but leave room for a mixture, neither, uncertainty, or different wording. Avoid leading questions that make one answer sound like the only reasonable choice. Routine formatting and other reversible editorial maintenance do not need repeated permission.
+
+Accept fragments, examples, corrections, and reactions as input. Label your proposed synthesis as interpretation; check consequential changes rather than treating your formulation as the author's own words. Show what changed and why after an answer. Do not postpone all author input until a large finished draft exists.
+
+## Support review without replacing judgment
+
+Keep the relevant text and source material available during review. Do not require an unaided explanation from memory or an improvised defense as proof of participation. Help develop a written explanation that the author can inspect, correct, qualify, or reject. Pause or restate a question when needed.
+
+Source checks and independent evaluation remain necessary where the claim requires them. Do not confuse conceptual agreement with source verification, approval of wording, or approval to publish. A request to continue, silence, or approval of one passage does not approve the entire manuscript. No personal health disclosure is required to use this workflow.
+
+## Keep the record usable
+
+Maintain a brief decision note in the existing claim, source, or change record: author-stated intent, assistant interpretation, affected passage, unresolved question, and review status. Record only decisions actually made. Do not create a new tracking system or ask the author to maintain duplicate logs.
+
+Keep earlier meanings, counterarguments, and source visibility intact. Do not invent earlier contributions, quotations, personal experience, or approvals. Do not publish private conversation excerpts or personal details merely because they explain the process.
+
+Use [AI-ASSISTANCE.md](AI-ASSISTANCE.md) for disclosure and review distinctions and [README.md](README.md) for paper scope. These repository instructions are not a claim that every future tool or conversation automatically loads them.
+
+## Extend what exists and return to the active question
+
+**Author clarification, 2026-09-16:** The aim is to address gaps in existing work, not generate new frameworks by default. Check established literature and existing project treatments, identify the specific missing piece, and add only that piece. Preserve the option that the useful contribution is a synthesis or application, not a novel method. An enthusiastic response to a term is not authorization to create a taxonomy or new project.
+
+Apply [the existing Legible Systems treatment](../../../core/legible-systems.md#participation-sensemaking-and-review-burden) to this collaboration: more prose can transfer more review work to the author. Keep enough context for the next decision, avoid expanding unreviewed dependent claims, and provide a short re-entry recap after a research or routing detour. Do not put the burden of restoring context back on the author.
+
+Use [THOUGHT_ROUTING.md](../../../THOUGHT_ROUTING.md) for cross-project routing. Keep open questions in the existing claim record. Neither helpful guidance nor a readable explanation replaces evidence, independent review where needed, or consent to consequential actions.