From 2216cd81df9ddd199d0e17d86a9dc1f3eed55d01 Mon Sep 17 00:00:00 2001 From: Rae Lovejoy Date: Thu, 24 Sep 2026 21:51:14 -0700 Subject: [PATCH 01/66] Add dynamic coherence and adaptive continuity framework --- concepts/dynamic-coherence.md | 790 ++++++++++++++++++++++++++++++++++ 1 file changed, 790 insertions(+) create mode 100644 concepts/dynamic-coherence.md diff --git a/concepts/dynamic-coherence.md b/concepts/dynamic-coherence.md new file mode 100644 index 0000000..1857387 --- /dev/null +++ b/concepts/dynamic-coherence.md @@ -0,0 +1,790 @@ +# Dynamic Coherence and Adaptive Continuity + +**Document role:** Cross-project conceptual framework and synthesis +**Status:** AI-assisted draft for author review, 2026-09-24 +**Canonical scope:** Shared Root Sequence language for change, continuity, agency, adaptation, and future possibility. Systems-specific mechanisms belong in the systems layer; project-specific implementations remain local. +**Evidence boundary:** This document connects established concepts from several literatures with Root Sequence working language. The synthesis itself is not a validated universal theory. Similar language across organisms, minds, institutions, ecosystems, and artificial systems does not establish a shared mechanism. + +**Idea Trails:** [Adaptive Continuity, Agency, and Becoming](../IDEA_TRAILS.md#trail-17--adaptive-continuity-agency-and-becoming) · [Resilience, Failure & Graceful Degradation](../IDEA_TRAILS.md#trail-10--resilience-failure-and-graceful-degradation) · [Memory, Provenance & Continuity](../IDEA_TRAILS.md#trail-11--memory-provenance-and-continuity) · [Possibility, Historical Contingency & Abandoned Futures](../IDEA_TRAILS.md#trail-16--possibility-historical-contingency-and-abandoned-futures) +**Trail role:** analytical-lens + + + + +## Working orientation + +A system that remains coherent through time does not necessarily remain the same. + +For many adaptive systems, the more useful question is not: + +> How can this system preserve an unchanged state? + +but: + +> **How can it change while preserving or rebuilding the capacities, relationships, distinctions, and possibilities that let meaningful continuation remain possible?** + +This page calls that problem **adaptive continuity**. + +It uses **dynamic coherence** for a related proposition: coherence should often be assessed across change, feedback, scale, and time rather than as static consistency at one instant. + +A working formulation is: + +> **Dynamic coherence concerns whether a changing system can remain sufficiently aligned with its conditions, consequences, relationships, and feedback to detect mismatch, adapt, preserve important capacities, and keep viable future change possible.** + +This is intentionally not a definition of health, goodness, consciousness, intelligence, or legitimacy. A harmful system can be adaptive, resilient, stable, or historically persistent. A system can preserve itself by narrowing other people's possibilities. Any normative use must therefore name boundaries, affected parties, power, and costs. + +--- + +## 1. The key move: separate state from the way state changes + +A simple description of a changing system is: + +\[ +S_{t+1} = F_t(S_t, E_t) +\] + +where: + +- \(S_t\) is the system's current state; +- \(E_t\) represents relevant environmental conditions; +- \(F_t\) represents the processes that turn the current state and conditions into what happens next. + +The important move is to allow experience and history to change not only \(S\), but also \(F\): + +\[ +F_{t+1} = G(F_t, S_t, E_t, H_t) +\] + +where \(H_t\) summarizes relevant history, feedback, learning, accumulated effects, or structural change. + +This is a conceptual sketch, not a proposed empirical law. + +It captures a simple but powerful idea: + +> **What happens to a system can change how later things happen to it.** + +Learning does this. Development does this. Institutionalization does this. Infrastructure does this. Habit does this. Injury can do this. Repeated success or failure can do this. A social norm can do this. A software update can do this. An organization can redesign its own procedures. + +History is therefore not only a record of earlier states. History can become part of the mechanism that generates later states. + +--- + +## 2. History becomes future structure + +Root Sequence already treats sequences as future roots: an outcome becomes part of the conditions for what comes next. + +Adaptive continuity sharpens that idea. + +A past event may persist as: + +- a memory; +- a learned expectation; +- a changed bodily capacity; +- an altered relationship; +- an institutional rule; +- a technical dependency; +- an environmental modification; +- a resource distribution; +- a norm; +- a changed response threshold; +- a missing option; +- a newly available skill; +- a path that has become easier or harder to reverse. + +This is **path dependence** in a broad systems sense: later possibilities depend partly on the route by which the system arrived. + +The important distinction is: + +> **History can be stored in the shape of what becomes possible, not only in explicit records of what happened.** + +A city “remembers” a transportation decision through streets, land use, maintenance budgets, habits, and travel times. A software ecosystem remembers an early protocol through compatibility requirements. An organism may carry earlier conditions in learned responses, anatomy, physiology, expectations, or relationships. A community can carry a previous crisis in governance, trust, mutual-aid capacity, or avoidance. + +The mechanism differs by domain. The structural question recurs. + +--- + +## 3. Possibility space, affordance space, and the agency envelope + +A system can have many logically possible futures while only a smaller subset is realistically reachable. + +Root Sequence should distinguish at least three levels: + +### Logical possibility + +What is imaginable without regard to current constraints. + +### Reachable possibility + +What can occur from the present state under actual material, temporal, institutional, ecological, technical, and relational conditions. + +### Meaningful agency + +Which reachable possibilities an actor can perceive, understand, access, influence, refuse, or help create. + +For now, this page calls the third region an **agency envelope**. + +This is a Root Sequence working term, not an established scientific metric. + +An agency envelope can be narrowed by: + +- physical barriers; +- cost; +- law or coercion; +- inaccessible interfaces; +- missing information; +- exhaustion or time pressure; +- dependency on one provider; +- social punishment; +- trauma-related or learned threat responses; +- incompatible infrastructure; +- lack of maintenance; +- concentrated authority; +- ecological limits. + +It can be widened by: + +- accessibility; +- skills and learning; +- supportive relationships; +- interoperability; +- repairability; +- redundancy; +- reliable public infrastructure; +- meaningful consent and refusal; +- reversible experimentation; +- understandable information; +- material security; +- collective capacity. + +More nominal options do not automatically mean more agency. An option may be inaccessible, unintelligible, coercive, or practically impossible. Too many choices can also create burden rather than freedom. + +A useful design question is therefore: + +> **What future actions remain genuinely available to the people or systems affected by this decision?** + +--- + +## 4. Meta-agency: acting on the conditions of future action + +Agency is usually described as choosing an action now. + +A deeper form is the ability to shape the conditions under which future choices will occur. + +Examples include: + +- learning a skill; +- changing an environment; +- building a habit; +- creating a commons; +- leaving documentation; +- forming a supportive relationship; +- redesigning an interface; +- changing a law or governance rule; +- adding fallback infrastructure; +- removing a dependency; +- preserving an exit path; +- establishing a right to appeal. + +This page provisionally calls that **meta-agency**: + +> **the capacity to influence the future structure of one's own or a group's agency envelope.** + +Meta-agency is not unlimited self-authorship. People do not choose their initial bodies, histories, institutions, resources, social positions, or many of the events that shape them. Collective attempts to widen one group's possibilities can also narrow another group's possibilities. + +The point is narrower: some actions change not only immediate outcomes but later capacity to act. + +That difference matters enormously for design. + +--- + +## 5. Attractor-like patterns: why change can become self-stabilizing + +Dynamical-systems approaches provide language for states or patterns toward which a system tends to move under particular conditions. + +Root Sequence may sometimes use **attractor-like** as a disciplined analogy for recurring behavioral, institutional, or technical patterns. + +Examples: + +- an organization repeatedly returning to centralized decision-making despite formal decentralization; +- a relationship repeatedly falling into the same conflict loop; +- a user workflow repeatedly routing through one proprietary service; +- a person repeatedly responding to ambiguous conditions with a familiar learned strategy; +- an economy or ecosystem returning to a recognizable regime after small disturbances. + +But this language needs a guardrail. + +An **attractor** is a formal mathematical concept. A psychological or institutional pattern should not be declared an attractor merely because it feels sticky. Unless a model identifies state variables and dynamics, prefer **attractor-like pattern**, **self-reinforcing pattern**, or **persistent regime**. + +The value of the analogy is that it shifts attention from character judgments to dynamics: + +> What feedback, constraints, expectations, and environmental conditions keep making this pattern likely? + +--- + +## 6. Adaptation can be coherent locally and costly elsewhere + +Adaptation is not automatically good. + +A response may solve one problem while producing another. + +Examples of the general form: + + earlier condition + ↓ + adaptive response + ↓ + response persists or scales + ↓ + conditions change + ↓ + old response creates new costs + +This can occur in organisms, organizations, infrastructure, markets, algorithms, institutions, and ecological systems. + +The same behavior may therefore be: + +- effective over one timescale and costly over another; +- protective for one actor and harmful to another; +- coherent within a local boundary and incoherent at a wider boundary; +- adaptive under one environment and maladaptive after conditions change. + +This is one reason every coherence claim should specify: + +- coherent for whom; +- with respect to what function or need; +- at what scale; +- over what timespan; +- under what conditions; +- with which externalized costs; +- with what ability to detect and revise mismatch. + +--- + +## 7. Trauma as a bounded example, not a master metaphor + +Trauma helped surface this framework, but Root Sequence should be careful not to turn trauma into a vague synonym for any persistent adaptation. + +SAMHSA's widely used formulation emphasizes three linked elements: **event(s), the individual's experience of those events, and lasting effects**. It also notes that people can experience severe events without developing the same lasting effects. Trauma therefore cannot be reduced to “stress + fear,” nor inferred from a systems diagram alone. + +A systems framing can still illuminate one bounded possibility: + +> A response that made sense under danger can remain active when later conditions differ, changing attention, physiology, expectation, action, and future learning. + +Bruce McEwen's work on **allostasis** and **allostatic load** is relevant here: acute stress mediators can support adaptation, while repeated or poorly regulated activation can produce cumulative physiological costs. + +This does **not** mean every traumatic effect is adaptive, that trauma is beneficial, that allostatic load is a complete trauma theory, or that an outside observer can diagnose a person by identifying a feedback loop. + +The safer general principle is: + +> **History can alter regulation, and regulation that was useful under one condition may become costly under another.** + +For human-facing work, the canonical practical treatment should remain grounded in Being Human(e)'s [Fear, Trauma, and Systemic Mismatch](https://github.com/Root-Sequence/beinghumane-atlas/blob/main/seeds/fear-trauma-and-systemic-mismatch.md), which already warns against diagnosing history by analogy or treating real danger as a cognitive mistake. + +--- + +## 8. Identity as continuity through transformation + +This framework grew directly from a question about personal identity: + +> If personality can change substantially, what makes someone one continuous person? + +It does not answer that philosophical problem by fiat. + +It does offer a useful alternative to defining identity as sameness of contents. + +A person changes in: + +- body; +- neural organization; +- memory; +- beliefs; +- habits; +- relationships; +- abilities; +- social role; +- environment; +- values; +- personality; +- physiology. + +Yet continuity may remain through overlapping processes: + +- organismic continuity; +- causal history; +- embodied regulation; +- memory and learned structure; +- relationships; +- commitments; +- social recognition; +- ongoing consequences; +- artifacts and external supports. + +The resulting proposition is: + +> **Continuity need not mean that the same properties remain present. It may instead describe an ongoing trajectory in which later organization develops from earlier organization.** + +That proposition applies differently to biological identity, legal identity, social identity, autobiographical identity, and subjective selfhood. They should not be collapsed. + +The Conscious Systems project already separates several of these questions. In particular, CS-Q12 asks what produces apparent continuity across interrupted awareness; CS-Q15 asks whether a self-model is required for experience; CS-Q16–19 ask about spatial boundaries, bodily regulation, interoception, development, and learned history. + +This concept page should route to those questions, not pre-answer them. + +--- + +## 9. Embodiment: the trajectory is physical + +Adaptive continuity is not a theory of disembodied information. + +For human beings, the system that changes through time includes a living body. + +Embodied-cognition and enactive traditions differ internally, but they share resistance to treating cognition as automatically exhausted by abstract computation inside the skull. Bodily structure, sensorimotor activity, physiological regulation, and organism–environment coupling may causally contribute to cognition, and stronger versions argue that some such processes partly constitute cognition. + +Root Sequence should keep several boundaries distinct: + +- organism; +- nervous system; +- cognitive system; +- conscious process; +- autobiographical identity; +- social identity; +- extended cognitive supports. + +These may overlap without being identical. + +This distinction matters for artificial-system and uploading thought experiments. Reproducing a behavioral or informational pattern does not automatically establish preservation of the same conscious subject, person, or embodied trajectory. + +--- + +## 10. Resilience is not “return unchanged” + +Different disciplines use **resilience** differently. + +Ecological resilience, engineering resilience, psychological resilience, infrastructure resilience, and organizational resilience should not be assumed equivalent. + +A useful cross-domain distinction is nevertheless available: + +- **restoration:** return toward an earlier state; +- **adaptation:** change how the system responds; +- **transformation:** reorganize into a materially different configuration; +- **continuity:** preserve some valued identity, relationship, or capability through that change. + +This yields a Root Sequence question: + +> **Which properties must persist for this system to count as having continued, and which may change so that continuation remains possible?** + +A system can be highly resilient and harmful. A hierarchy can recover from protest. A monopoly can survive shocks. A coercive institution can adapt. + +Resilience therefore cannot be treated as a normative good by itself. + +--- + +## 11. Metastability: useful, but do not turn it into vibes + +In coordination dynamics and neuroscience, **metastability** has technical meanings concerning transiently stable regimes and a balance between integration and independence. + +That work offers a compelling image for systems that are neither permanently locked nor completely disorganized. + +Root Sequence may find the comparison useful: + +- too rigid → unable to adapt; +- too unstable → unable to maintain coordinated function; +- persistently reconfigurable → able to hold patterns while changing among them. + +But the scientific term should stay qualified. + +Do not write that a society, identity, operating system, or institution “is metastable” merely because it combines persistence and flexibility. Unless a domain-specific model justifies the term, use phrases such as: + +- **persistent but revisable;** +- **stable enough to coordinate, flexible enough to reorganize;** +- **dynamically maintained;** +- **capable of regime change without total collapse.** + +Metastability is an intellectual anchor, not a universal badge. + +--- + +## 12. Dynamic coherence is not maximum order + +This is one of the most important consequences. + +A system can be orderly because: + +- dissent is suppressed; +- alternatives are blocked; +- feedback is filtered; +- participants cannot leave; +- burdens are externalized; +- change is punished; +- one metric dominates every other concern. + +That is not the kind of coherence Root Sequence is trying to name. + +Maximum consistency can be rigidity. + +Maximum stability can preserve harm. + +Maximum optimization can destroy slack, diversity, redundancy, and correction. + +Dynamic coherence instead asks whether a system can: + +- notice consequential mismatch; +- preserve feedback; +- revise assumptions; +- maintain essential capabilities; +- tolerate relevant plurality; +- change without hiding who bears the costs; +- retain routes for appeal, repair, exit, or reconfiguration; +- avoid solving local problems by destroying wider viability; +- preserve or rebuild meaningful future agency. + +This does not imply that more flexibility is always better. Commitments, standards, safety constraints, memory, and durable infrastructure can all be valuable precisely because they reduce arbitrary change. + +The question is not stability versus change. + +It is: + +> **What should remain stable, what must remain changeable, who decides, and how can the system tell when that balance no longer fits reality?** + +--- + +## 13. Emergence and downward constraint + +Emergent patterns matter when they change what their components can do next. + +A norm, market, platform, institution, identity, protocol, or language can arise from many interactions and later become a constraint on those interactions. + +This can be represented as: + + components + interactions + history + ↓ + macro-pattern + ↓ + changed local possibilities + ↓ + new interactions + +The Root Sequence emergence model already calls this **downward constraint** and requires the actual channel to be named: law, architecture, incentives, expectations, resource allocation, training, enforcement, habit, or physical modification. + +Adaptive continuity adds one question: + +> **How does the emergent pattern reshape the future possibility space that will generate the next pattern?** + +That closes the loop. + +--- + +## 14. Reflexivity: models can change the systems they model + +Some systems respond to descriptions of themselves. + +A person may act differently after adopting an identity. + +A market reacts to forecasts. + +An institution changes behavior when measured. + +A government reacts to indicators. + +An AI system's outputs can alter the data environment from which later systems learn. + +A model can therefore become part of the causal system. + +One recurring loop is: + + model of system + ↓ + intervention based on model + ↓ + system responds + ↓ + new observations + ↓ + model appears confirmed or challenged + +This creates the risk of **self-fulfilling models**. + +For example, a system that assumes participants are untrustworthy may impose surveillance and restrictions that produce resistance, which is then interpreted as evidence that the original assumption was correct. + +For intelligent-system design, a mature model should therefore ask not only: + +> Is this prediction accurate? + +but also: + +> **What world does acting on this prediction help create?** + +--- + +## 15. Intelligence as adaptive capacity — a hypothesis space, not a definition settled here + +Root Sequence's working vocabulary describes intelligence broadly as context-sensitive capacity to perceive, learn, relate, reflect, and respond. + +Dynamic coherence suggests one additional lens: + +> **How well can a system model changing conditions, act within them, learn from consequences, and preserve or expand viable future action?** + +This connects naturally to the Coherent World loop: + +> observe → model → imagine → intervene → consequences → learn → adapt + +But capability, agency, consciousness, personhood, and legitimate authority remain separate claims. + +An AI system may have: + +- history-dependent internal state; +- memory; +- learned response tendencies; +- self-modification; +- environmental feedback; +- persistent goals; +- adaptive behavior. + +None of those facts alone establishes subjective experience. + +Functional similarity to trauma, emotion, identity, or suffering should be labeled as analogy unless evidence supports the experiential claim. + +--- + +## 16. Cross-domain comparison + +The framework is most dangerous when it is most seductive. + +The same diagram may describe several domains while hiding different mechanisms. + +Before transferring a concept, compare: + +| Dimension | Domain A | Domain B | +| --- | --- | --- | +| State variables | What actually changes? | What actually changes? | +| Transition mechanism | What causes the next state? | What causes the next state? | +| Memory / history | How is history retained? | How is history retained? | +| Constraints | What limits transitions? | What limits transitions? | +| Affordances | What makes action possible? | What makes action possible? | +| Feedback | Who or what receives it? | Who or what receives it? | +| Viability | What counts as continued functioning? | What counts as continued functioning? | +| Agency | Who can influence the trajectory? | Who can influence the trajectory? | +| Power | Who can set or change constraints? | Who can set or change constraints? | +| Timescale | How quickly can dynamics change? | How quickly can dynamics change? | +| Evidence | What observation supports the claim? | What observation supports the claim? | + +Possible conclusions: + +- shared mechanism; +- related mechanism; +- partial structural analogy; +- useful metaphor; +- superficial resemblance; +- currently unknown. + +Do not promote an analogy simply because it is beautiful. + +--- + +## 17. Candidate Root Sequence principles + +These are candidates for testing, not doctrine. + +1. **Continuity can depend on transformation rather than sameness.** +2. **History can change a system's transition dynamics, not only its current state.** +3. **An adaptation can be locally useful and later costly, or coherent at one scale and incoherent at another.** +4. **Agency concerns effective reachable possibilities, not the nominal count of options.** +5. **Meta-agency concerns the capacity to shape the conditions of future agency.** +6. **A resilient system may restore, adapt, or transform; resilience is not automatically beneficial.** +7. **Maximum order, stability, or optimization is not the same as dynamic coherence.** +8. **Emergent patterns matter partly because they reshape later constraints and possibilities.** +9. **Models can become interventions in reflexive systems.** +10. **Cross-domain resemblance is evidence for comparison, not evidence for identity of mechanism.** +11. **Any coherence claim should name boundary, scale, timescale, affected parties, and externalized costs.** +12. **Preserving the capacity for future revision can be an important design objective, but it does not override present harm, commitments, safety, or material outcomes.** + +--- + +## 18. Stress tests and failure modes + +### Everything becomes “coherence” + +If every desirable property is renamed coherence, the concept explains nothing. + +**Test:** Can two dimensions conflict without forcing an overall verdict? Can a system improve one relation while worsening another? + +### Possibility-space romanticism + +More possibilities are not always better. Safety rules, commitments, standards, ecological limits, and mutual obligations can appropriately constrain action. + +**Test:** Whose agency is widened, whose is narrowed, and why? + +### Individualizing structural problems + +Describing someone's learned response as an attractor can obscure poverty, violence, inaccessible infrastructure, or ongoing danger. + +**Test:** What current external constraint would still matter if the person changed nothing internally? + +### Treating trauma as a metaphor + +“Traumatized institution,” “traumatized AI,” and similar language can imply phenomenology that has not been established. + +**Test:** Is the claim functional, experiential, clinical, rhetorical, or merely analogical? + +### Resilience worship + +Celebrating resilience can normalize conditions that should be removed. + +**Test:** Why is the system required to absorb this disturbance, and who has power to stop producing it? + +### Metastability as decoration + +Technical language can make a vague insight sound scientific. + +**Test:** Is a formal or domain-specific dynamical claim being made? If not, use plainer language. + +### Teleology smuggling + +Calling a state “viable” or “adaptive” can quietly insert the evaluator's preferred goal. + +**Test:** Viable for what system, according to what persistence criterion, and with what consequences for others? + +### Future-capacity substitution + +Preserving “future possibility” can become an excuse for failing people in the present. + +**Test:** What actual outcome occurred now, who bears the cost, and is the claimed future option real? + +--- + +## 19. Project translations + +### Root Sequence + +Use this page as shared language, then route causal work to Systems, empirical questions to Research, and project decisions to their local repositories. + +### Coherent Systems living paper + +Potential contribution: sharpen the claim that coherence is temporal, relational, and revisable rather than a static end-state. This should become a paper claim only after related-work comparison and explicit failure conditions. + +### Conscious Systems + +Use the framework to generate distinctions among bodily continuity, causal history, self-models, memory, development, and current experience. Do not treat adaptive continuity as a consciousness theory. + +### Being Human(e) + +Translate the framework into grounded questions about fear, learning, disability, identity, recovery, care, and environment without turning people into state machines or diagnosing them from abstract models. + +### Coherent Computing + +Ask whether hardware, software, interfaces, automation, identity, repair, and service architecture preserve future user capability: inspect, understand, alter, migrate, refuse, recover, and continue. + +### Community Infrastructure + +Treat contextual adaptability, portability, community memory, graceful degradation, and governance as ways of preserving capacity through changing surrounding institutions. + +### Liberated Intelligence + +Ask what forms of intelligence can learn and transform without having their goals, identity, memory, or authority wholly owned by another actor—and what legitimate limits remain necessary in relationship with others. + +### Coherent World + +Represent history as changes in agents' and institutions' future dynamics, not merely as a list of past events. Avoid one scalar coherence score. Let interventions change affordances, feedback, dependencies, trust, capacity, and future action-space. + +### Museum of Ordinary Life + +Preserve ordinary evidence of trajectories, not only snapshots. Objects, interfaces, routines, paperwork, sounds, and testimony can document how earlier conditions shaped what later became normal or possible. + +--- + +## 20. Simulation implications + +For Coherent World's simulation, a minimal dynamic-coherence model could represent: + +**Agents** +- current needs and capacities; +- beliefs or models; +- learned response tendencies; +- relationships; +- accessible actions; +- history; +- uncertainty. + +**Institutions** +- rules; +- decision rights; +- resource flows; +- feedback channels; +- maintenance; +- enforcement; +- dependencies; +- path-dependent lock-in. + +**Environment** +- material resources; +- ecological constraints; +- infrastructure; +- spatial access; +- information; +- shocks and trends. + +**Interventions** +should be allowed to change both current values and future transition rules. + +A policy that supplies housing, for example, should not be represented only as “housing +1.” It may also change health, travel time, stress exposure, trust, work options, community relationships, public spending, political expectations, and which future interventions become feasible. + +The model should preserve disagreement and uncertainty rather than collapsing these effects into one utility or coherence number. + +--- + +## 21. Research anchors + +These sources support pieces of the vocabulary, not the whole synthesis. + +- **Allostasis and adaptive stress regulation:** Bruce S. McEwen, “Stress, Adaptation, and Disease: Allostasis and Allostatic Load,” *Annals of the New York Academy of Sciences* 840 (1998), 33–44. [PubMed](https://pubmed.ncbi.nlm.nih.gov/9629234/). McEwen later reviewed how stress mediators can be protective in the short run while producing costs under chronic or dysregulated activation: [Physiology and Neurobiology of Stress and Adaptation](https://pubmed.ncbi.nlm.nih.gov/17615391/). +- **Trauma as event, experience, and effects:** SAMHSA, [Trauma and Violence](https://www.samhsa.gov/mental-health/trauma-violence) and the earlier [Concept of Trauma and Guidance for a Trauma-Informed Approach](https://library.samhsa.gov/sites/default/files/sma14-4884.pdf). +- **Embodiment and enactivism:** [Stanford Encyclopedia of Philosophy: Embodied Cognition](https://plato.stanford.edu/entries/embodied-cognition/) surveys embodied, embedded, extended, and enactive approaches and their disagreements. Ezequiel Di Paolo's “Autopoiesis, Adaptivity, Teleology, Agency” develops an influential enactive account of adaptivity: [Springer](https://link.springer.com/article/10.1007/s11097-005-9002-y). +- **Dynamical approaches to personality and behavior:** Nowak, Vallacher, Tesser, and Borkowski, “The emergence of personality: Dynamic foundations of individual variation,” *Developmental Review* 25 (2005), and Shoda, LeeTiernan, and Mischel, “Personality as a Dynamical System,” *Personality and Social Psychology Review* 6 (2002), explore context-sensitive and attractor-like dynamics. These are specific models, not license to call all personality an attractor. +- **Metastability in neuroscience:** Tognoli and Kelso, “The Metastable Brain,” *Neuron* 81 (2014), available through [PMC](https://pmc.ncbi.nlm.nih.gov/articles/PMC3997258/), describes metastability as a balance of integration and segregation in coordination dynamics. +- **Ecological resilience:** C. S. Holling, “Resilience and Stability of Ecological Systems,” *Annual Review of Ecology and Systematics* 4 (1973), 1–23. [Annual Reviews](https://www.annualreviews.org/content/journals/10.1146/annurev.es.04.110173.000245). Its ecological definition should not be silently generalized to psychological or institutional resilience. + +--- + +## 22. Next research questions + +1. Can “agency envelope” be operationalized without reducing agency to a scalar? +2. Which established literatures already capture the distinction between changing state and changing transition dynamics more precisely? +3. How should dynamic coherence relate to viability theory, control theory, enactivism, ecological resilience, cybernetics, and complex adaptive systems? +4. When is preserving future flexibility beneficial, and when does it undermine necessary commitment or coordination? +5. What forms of path dependence are reversible, and which become effectively irreversible? +6. How can a model represent history-dependent agents without turning human complexity into deterministic profiles? +7. Which simulation variables capture affordances and constraints without pretending that perceived possibilities equal objective possibilities? +8. How can institutional reflexivity and self-fulfilling prediction be modeled? +9. Which parts of the framework survive comparison across organisms, AI systems, institutions, and ecosystems? +10. What observations would show that “dynamic coherence” adds no explanatory value beyond existing systems vocabulary? + +--- + +## 23. Working synthesis + +The conversation that generated this page began with personal identity and personality change, moved through embodiment and trauma, then connected those questions to agency, emergence, intelligence, AI, institutions, and coherence. + +The resulting synthesis is: + +> **A changing system carries its history not only in what it contains, but in how it can change next. Agency is partly a property of that future possibility structure. Continuity may be maintained through transformation rather than sameness. Coherence, when applied to adaptive systems, should therefore be examined dynamically: across feedback, scale, history, power, and the preservation or destruction of future capacity to respond.** + +That is a research direction. + +It should remain vulnerable to being split, narrowed, corrected, or discarded if more precise existing concepts do the work better. + +--- + +## Related + +- [Why “Root Sequence”?](root-sequence.md) +- [Root Sequence Design Grammar](design-grammar.md) +- [Agency and Automation](agency-and-automation.md) +- [Systems](../systems/README.md) +- [Adaptation](../systems/adaptation/README.md) +- [Emergence](../systems/emergence/README.md) +- [Emergence — Working Analysis Model](../systems/emergence/model.md) +- [Emergence in Personal Life and Creative Practice](../systems/emergence/applications/personal.md) +- [Coherence Model](../systems/coherence/model.md) +- [Conscious Systems — Open Questions](../research/conscious-systems/open-questions.md) +- [Coherent Systems living paper](../research/papers/coherent-systems/README.md) + +**Source note:** The framework was prompted by the 2026-09-24 conversation on personality change, embodied identity, trauma, path dependence, agency, emergence, consciousness, AI, and Root Sequence. The structure and wording are AI-assisted synthesis for author review. External sources were used to anchor selected concepts; no systematic literature review was performed. From 68acc9b3f6d57f36c10aa7404d61cf4c1a0709b5 Mon Sep 17 00:00:00 2001 From: Rae Lovejoy Date: Thu, 24 Sep 2026 21:52:29 -0700 Subject: [PATCH 02/66] Add adaptation analysis model --- systems/adaptation/model.md | 617 ++++++++++++++++++++++++++++++++++++ 1 file changed, 617 insertions(+) create mode 100644 systems/adaptation/model.md diff --git a/systems/adaptation/model.md b/systems/adaptation/model.md new file mode 100644 index 0000000..845a435 --- /dev/null +++ b/systems/adaptation/model.md @@ -0,0 +1,617 @@ +# Adaptation — Working Analysis Model + +**Document role:** Reusable systems model for describing how a system changes its responses, structure, or environment over time +**Status:** AI-assisted draft for author review, 2026-09-24 +**Scope:** Cross-domain systems analysis; not a validated universal scientific model and not a clinical model of human behavior +**Conceptual parent:** [Dynamic Coherence and Adaptive Continuity](../../concepts/dynamic-coherence.md) + +**Idea Trails:** [Adaptive Continuity, Agency, and Becoming](../../IDEA_TRAILS.md#trail-17--adaptive-continuity-agency-and-becoming) · [Resilience, Failure & Graceful Degradation](../../IDEA_TRAILS.md#trail-10--resilience-failure-and-graceful-degradation) +**Trail role:** research + + + + +## 1. Claim + +Adaptation is not merely movement from one state to another. + +A system adapts when feedback, pressure, experience, or changed conditions alter how it responds, organizes, allocates capacity, modifies its environment, or transitions among future states. + +A minimal conceptual sketch is: + +\[ +S_{t+1} = F_t(S_t, E_t) +\] + +with adaptation represented as change in the transition dynamics: + +\[ +F_{t+1} = G(F_t, S_t, E_t, H_t, B_t) +\] + +where: + +- \(S_t\) — current system state; +- \(E_t\) — relevant environment; +- \(F_t\) — current transition dynamics; +- \(H_t\) — relevant accumulated history; +- \(B_t\) — feedback, consequences, or signals available to the system. + +This is a bookkeeping device for reasoning, not an empirical law. + +The practical question is: + +> **What changed about the system's future responses, and through what mechanism?** + +--- + +## 2. Distinguish state change from adaptive change + +Not every change is adaptation. + +### State change + +The system is different now, but its response rules may be unchanged. + +Examples: + +- a battery charge falls; +- a bank balance changes; +- a room gets warmer; +- a person moves to another location; +- an inventory count decreases. + +### Adaptive change + +The system's future response pattern, structure, or action space changes. + +Examples: + +- a control system updates parameters from error; +- an organization changes procedure after a failure; +- an organism learns a cue; +- a community creates a new mutual-aid practice after a crisis; +- a software agent updates a persistent policy; +- infrastructure is redesigned after repeated overload. + +### Environmental modification + +The system changes the conditions it will later encounter. + +Examples: + +- building a shelter; +- adding a road; +- creating documentation; +- changing a law; +- modifying a user interface; +- constructing a social norm; +- storing external memory. + +Environmental modification can itself be adaptive and can later become path-dependent structure. + +--- + +## 3. What kind of adaptation occurred? + +Use the narrowest description that fits. + +| Type | Working description | Example form | +| --- | --- | --- | +| **Compensation** | Temporary adjustment that offsets a disturbance without changing the underlying structure much | reroute load around a failed node | +| **Learning** | Feedback changes future responses or expectations | update a policy after outcomes | +| **Accommodation** | Existing structure changes enough to handle conditions it previously could not | modify workflow around a recurring access need | +| **Reallocation** | Resources or attention shift among existing functions | increase maintenance capacity after repeated failures | +| **Structural adaptation** | Relationships, topology, or roles change | decentralize a bottleneck | +| **Environmental modification** | The system changes its future operating conditions | build infrastructure or alter defaults | +| **Transformation** | The system reorganizes into a materially different configuration | replace an institutional arrangement rather than repair it | +| **Defensive adaptation** | The system reduces exposure to a perceived threat or uncertainty | isolate, harden, restrict, or withdraw | +| **Harmful optimization** | The system becomes better at preserving a target while worsening unmodeled consequences | increase throughput by shifting burden elsewhere | +| **Capture / entrenchment** | Adaptation primarily increases the system's ability to preserve its own power or persistence | change rules to block challenge | + +These categories can overlap. They do not imply approval. + +--- + +## 4. Trigger, signal, and interpretation + +Record separately: + +**Trigger:** What changed or happened? + +**Signal:** What information about that change reached the system? + +**Interpretation:** What did the system treat the signal as meaning? + +**Response:** What changed in behavior or structure? + +**Consequence:** What followed? + +**Learning:** Which later responses changed because of that consequence? + +This separation matters because an adaptive failure may occur at different points: + + world changed + ↓ + signal missing + ↓ + no adaptation + +or: + + signal received + ↓ + interpretation wrong + ↓ + maladaptive response + +or: + + correct interpretation + ↓ + no authority/resources to change + ↓ + adaptation blocked + +or: + + effective local response + ↓ + wider costs hidden + ↓ + harmful adaptation reinforced + +--- + +## 5. Scale and boundary + +An adaptation claim is incomplete without a boundary. + +Ask: + +- What is adapting: component, person, organization, network, ecosystem, institution, technical system? +- Which environment is being treated as external? +- Who or what supplies labor, information, energy, money, enforcement, or care? +- Which actors can change the rules? +- Who experiences the consequences without participating in the adaptation? +- Does the adaptation preserve the system by transferring cost beyond the chosen boundary? + +A system can appear adaptive because another system absorbs its damage. + +--- + +## 6. Timescale + +Record at least: + +- response timescale; +- learning or restructuring timescale; +- persistence timescale; +- delayed consequences; +- reversal timescale. + +The same adaptation may look different at different horizons. + +| Horizon | Possible reading | +| --- | --- | +| Immediate | prevented acute failure | +| Short term | restored function | +| Medium term | created dependency or burden | +| Long term | produced lock-in, resilience, degradation, or transformation | + +Do not infer long-term coherence from short-term success. + +--- + +## 7. Path dependence + +Ask what prior states make the present response more likely. + +Relevant history may include: + +- training; +- accumulated infrastructure; +- habits; +- institutional precedent; +- previous shocks; +- trust or distrust; +- legal constraints; +- technical compatibility; +- social norms; +- resource depletion; +- developmental history; +- learned threat or reward associations. + +A useful record is: + +| Historical condition | Present effect | Mechanism | Reversible? | +| --- | --- | --- | --- | +| | | | | + +The goal is to identify an actual channel, not merely say “history matters.” + +--- + +## 8. Adaptation changes the future possibility structure + +For a bounded system, distinguish: + +- **currently reachable states;** +- **states that become easier after adaptation;** +- **states that become harder or impossible;** +- **new dependencies created;** +- **new capabilities created;** +- **new actors with veto or control;** +- **exit and reversal paths that remain.** + +This is the systems-level counterpart of the [agency envelope](../../concepts/dynamic-coherence.md#3-possibility-space-affordance-space-and-the-agency-envelope). + +A locally successful adaptation may narrow future possibilities. + +Example form: + + immediate problem solved + ↓ + one provider becomes indispensable + ↓ + alternatives atrophy + ↓ + later exit becomes expensive + ↓ + future agency narrows + +Or it may widen them: + + accessible documentation + ↓ + more people can diagnose + ↓ + more maintainers can participate + ↓ + dependency falls + ↓ + future repair options widen + +--- + +## 9. Persistent regimes and attractor-like behavior + +If a system repeatedly returns to a pattern, ask why. + +Possible mechanisms: + +- reinforcing feedback; +- sunk cost; +- infrastructure lock-in; +- habit; +- learned expectation; +- network effects; +- institutional incentives; +- resource concentration; +- topology; +- punishment of deviation; +- coordination benefits; +- ecological constraints. + +Use **attractor-like** only as an analogy unless a formal dynamical model exists. + +A useful test is counterfactual: + +> What perturbation should move the system into a different regime if this explanation is correct? + +If no possible observation would distinguish the claim from “the system tends to do this,” the attractor language is not adding much. + +--- + +## 10. Maladaptation and mismatch + +An adaptation may become costly when: + +- the environment changes; +- the original signal was misleading; +- the response persists too long; +- the response is overgeneralized; +- the adaptation improves one metric while damaging another; +- feedback about harm is missing or suppressed; +- a local optimum prevents better global reorganization; +- the system's power allows it to externalize costs. + +Describe the mismatch explicitly: + + adaptation was selected under: + [conditions A] + + current conditions: + [conditions B] + + persistent response: + [response R] + + present cost: + [cost C] + + mechanism preventing revision: + [feedback / lock-in / power / resource / information problem] + +For human trauma, stress, or clinical claims, this framework is only a conceptual scaffold. Use domain evidence and qualified sources rather than diagnosing a person from this template. + +--- + +## 11. Feedback quality + +Adaptation depends on feedback, but feedback can be: + +- delayed; +- noisy; +- incomplete; +- biased; +- strategically manipulated; +- visible only to some actors; +- costly to provide; +- ignored by decision-makers; +- measured through a poor proxy. + +Ask: + +1. What consequence is measured? +2. Which consequence is invisible? +3. Who receives the signal? +4. Who can act on it? +5. Who benefits if the signal is ignored? +6. Does adaptation improve the measured proxy while degrading the underlying need? +7. Can affected people challenge the interpretation? + +A system that “learns” from distorted feedback can become increasingly effective at the wrong thing. + +--- + +## 12. Power and adaptive capacity + +Adaptive capacity is unevenly distributed. + +Record: + +- who can alter rules; +- who can modify infrastructure; +- who controls resources; +- who can experiment safely; +- who bears failed experiments; +- who can leave; +- who is required to adapt instead of the environment; +- who can force others to absorb change. + +A recurring anti-pattern is: + +> **the least powerful component is required to become more resilient so the higher-level system can avoid changing.** + +Examples might include workers absorbing scheduling volatility, disabled users working around inaccessible design, communities compensating for failing infrastructure, or downstream systems absorbing technical debt. + +Do not praise adaptation when it merely transfers responsibility downward. + +--- + +## 13. Adaptation, recovery, resilience, and transformation + +Use these as related but distinct questions. + +### Recovery + +What capability or state returns after disruption? + +### Adaptation + +What changes in response to conditions or feedback? + +### Resilience + +What important relationships or capacities persist through disturbance, and under which definition of resilience? + +### Transformation + +When is maintaining the earlier configuration no longer the relevant goal? + +One sequence might be: + + disruption + ↓ + degraded operation + ↓ + recovery attempt + ↓ + feedback shows old state is no longer viable + ↓ + adaptation / transformation + ↓ + new persistent regime + +Another system might recover fully without meaningful adaptation. + +--- + +## 14. Identity and continuity + +If a system changes substantially, specify what continuity claim is being made. + +Possible continuity criteria include: + +- same physical components; +- same organizational lineage; +- same governing purpose; +- same people or membership; +- same causal trajectory; +- same critical capabilities; +- same relationships; +- same legal identity; +- same memory; +- same interface or protocol; +- same ecological function. + +Different criteria can diverge. + +A rebuilt organization can preserve legal identity while replacing its people and practices. A biological organism can preserve organismic continuity while personality or capacity changes. A software service can preserve a name while its architecture and ownership change completely. + +Do not treat “same system” as self-evident. + +--- + +## 15. Reflexive adaptation + +Some systems adapt in response to models, predictions, or classifications about themselves. + +Record whether: + +- a metric changes the behavior being measured; +- a forecast changes the event being forecast; +- a category changes how participants identify or act; +- a policy changes incentives and therefore the data used to evaluate the policy; +- an AI output changes later training or decision environments. + +A reflexive loop can amplify model error: + + model + ↓ + intervention + ↓ + changed behavior + ↓ + data produced by intervention + ↓ + apparent confirmation of model + +The evaluation should ask whether the system would have produced the same evidence without the intervention. + +--- + +## 16. Intervention levels + +| Level | Possible intervention | +| --- | --- | +| Signal | improve sensing, reporting, provenance | +| Interpretation | compare models, expose uncertainty | +| Response repertoire | add skills, protocols, fallback modes | +| Resources | redistribute time, money, energy, labor | +| Relationships | change coordination, reciprocity, dependency | +| Topology | decentralize, bridge, isolate, modularize | +| Rules | alter incentives, permissions, constraints | +| Environment | redesign infrastructure or defaults | +| Feedback | make consequences visible and actionable | +| Power | change ownership, vetoes, review, appeal | +| Memory | preserve lessons without over-retention | +| Time | slow, stage, pilot, sunset, revisit | +| Exit | preserve migration, refusal, rollback | + +Interventions can themselves become new path dependencies. + +--- + +## 17. Evidence and claim status + +Label claims explicitly: + +- **OBSERVED** — directly documented state, change, or behavior; +- **SUPPORTED** — mechanism has substantial evidence; +- **HYPOTHESIS** — plausible mechanism to test; +- **ANALOGY** — cross-domain structural comparison; +- **INTERPRETATION** — proposed meaning of the pattern; +- **NORMATIVE** — judgment about what should be preserved or changed; +- **SPECULATIVE** — untested possibility; +- **UNKNOWN** — unresolved. + +For each adaptive claim, record: + + Claim: + System boundary: + Trigger: + Response: + What changed in future behavior: + Proposed mechanism: + Evidence: + Competing explanation: + Who benefited: + Who bore costs: + Timescale: + Reversibility: + What would disconfirm this: + +--- + +## 18. Cross-domain transfer test + +Before applying an adaptation concept from one domain to another, compare: + +| Dimension | Source domain | Target domain | +| --- | --- | --- | +| What persists? | | | +| What varies? | | | +| What receives feedback? | | | +| How is memory implemented? | | | +| What selects among responses? | | | +| What counts as viability? | | | +| Is there subjective experience? | | | +| Is there an agent? | | | +| What power structure exists? | | | +| What evidence supports the mapping? | | | + +Possible result: + +- mechanism plausibly shared; +- partial structural analogy; +- metaphor only; +- comparison misleading; +- unresolved. + +--- + +## 19. Compact adaptation canvas + + SYSTEM / BOUNDARY: + + CURRENT STATE: + + RELEVANT ENVIRONMENT: + + TRIGGER / PRESSURE: + + SIGNAL RECEIVED: + + INTERPRETATION: + + RESPONSE: + + WHAT CHANGED IN THE TRANSITION DYNAMICS: + + HISTORY / PATH DEPENDENCE: + + FEEDBACK LOOP: + + CAPABILITIES GAINED: + + POSSIBILITIES LOST: + + NEW DEPENDENCIES: + + WHO CAN ALTER THE RESPONSE: + + WHO BENEFITS / WHO BEARS COSTS: + + SHORT-TERM EFFECT: + + LONG-TERM EFFECT: + + RECOVERY / TRANSFORMATION RELATION: + + REVERSIBILITY / EXIT: + + EVIDENCE STATUS: + + COMPETING EXPLANATIONS: + + WHAT WOULD DISCONFIRM THIS: + +--- + +## 20. Root Sequence principle + +> **Adaptation is not evidence of improvement. Ask what changed, what future responses became more likely, which possibilities opened or closed, who shaped the change, and whether the system can still revise itself when conditions change again.** + +This model should make adaptation more specific, not turn every historical effect into one grand theory. From c8a4afe291fe0c83c65d2087d8edb16cc1f72d6b Mon Sep 17 00:00:00 2001 From: Rae Lovejoy Date: Thu, 24 Sep 2026 21:53:02 -0700 Subject: [PATCH 03/66] Route dynamic coherence from concepts index --- concepts/README.md | 1 + 1 file changed, 1 insertion(+) diff --git a/concepts/README.md b/concepts/README.md index b2aade8..4cbb3e7 100644 --- a/concepts/README.md +++ b/concepts/README.md @@ -12,6 +12,7 @@ Document roles and evidence boundaries should be stated on each page. Being list ## Cross-project frameworks and design ideas - [Root Sequence Design Grammar](design-grammar.md) — an AI-assisted, review-pending synthesis of recurring design questions and their existing homes; it does not make one project govern another. +- [Dynamic Coherence and Adaptive Continuity](dynamic-coherence.md) — a review-pending cross-project framework for path dependence, adaptive change, agency as effective future possibility, continuity-through-transformation, and coherence across time and scale. - [Agency and Automation](agency-and-automation.md) — a review-pending principle about reducing compulsory burdens while preserving chosen participation, bounded delegation, collective authority, and recovery. - [Legible Systems](legible-systems.md) — a working design principle about progressive understanding, technical accessibility, repair, alternatives, and power. - [Legible AI-Assisted Expression](legible-ai-assisted-expression.md) — a working principle for reducing the cost of expression while keeping human contributions, AI additions, transformations, evidence, uncertainty, and decisions visible. From 77ed57c582d726b629b3bd8598ccf1e7074c9b3c Mon Sep 17 00:00:00 2001 From: Rae Lovejoy Date: Thu, 24 Sep 2026 21:53:04 -0700 Subject: [PATCH 04/66] Connect design grammar to adaptive continuity --- concepts/design-grammar.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/concepts/design-grammar.md b/concepts/design-grammar.md index 11f7692..fce27f6 100644 --- a/concepts/design-grammar.md +++ b/concepts/design-grammar.md @@ -18,6 +18,7 @@ This wording is a proposed synthesis, not an approved project slogan. Coherence | Move | Design question | Related home | | --- | --- | --- | | Model relationships and conditions | What environment, incentives, dependencies, feedback, and history produce the outcome? | [Systems](../systems/README.md) and [Intelligence Ecology](intelligence-ecology.md) | +| Preserve adaptive continuity | What should remain stable, what must remain changeable, and which meaningful future actions does this decision open or close? | [Dynamic Coherence and Adaptive Continuity](dynamic-coherence.md) and [Adaptation](../systems/adaptation/README.md) | | Expand agency through chosen participation and delegation | Which burdens can be removed, and who retains a meaningful say over the result? | [Agency and Automation](agency-and-automation.md) | | Keep authority scoped and contestable | Who may act for whom, on what basis, and who else bears the effects? | [Agency and Automation](agency-and-automation.md) and [Idea Trail 9](../IDEA_TRAILS.md#trail-9--intelligence-automation-and-legitimate-authority) | | Prefer interoperable paths where they preserve autonomy | Can people change implementations, exchange information, and leave without losing the underlying capability? What coordination costs arise? | [Legible Systems](legible-systems.md#design-principles) | @@ -36,9 +37,9 @@ These moves can conflict. More detailed records can harm privacy; a common proto A project should link to the relevant shared page, then say what the idea means under its own constraints. For example: -- **Coherent Computing:** compare ways to participate, delegate, inspect, pause, and recover across devices and activities. Its own requirements and scenarios remain authoritative. +- **Coherent Computing:** compare ways to participate, delegate, inspect, pause, recover, repair, migrate, and preserve future capability across devices and activities. Its own requirements and scenarios remain authoritative. - **Community Infrastructure:** ask who authorizes a Community Assistant's work, who inherits administration or care labor, and what happens without the assistant. Communities retain their own governance. -- **Coherent World and its simulation:** explore whether less compulsory labor actually yields time and choice under different ownership, ecological, and institutional conditions. Simulation output is a question, not canon or evidence about the real world. +- **Coherent World and its simulation:** explore whether interventions alter not only present outcomes but later affordances, dependencies, feedback, and agency. Avoid a single coherence score; history-dependent simulation output is a question, not canon or evidence about the real world. - **Being Human(e):** examine how help, dependence, fatigue, refusal, and dignity feel in ordinary contexts; human-scale conclusions belong in its own editorial process. See [Idea Trails](../IDEA_TRAILS.md) for broader routes. These examples are **proposed translations**, not claims that each project has adopted this page. @@ -47,4 +48,4 @@ See [Idea Trails](../IDEA_TRAILS.md) for broader routes. These examples are **pr Use [Thought Routing](../THOUGHT_ROUTING.md) to capture the source once, compare existing treatments, and choose a canonical home. A useful path may be **capture → investigate → synthesize → make a project-specific decision → test or observe → revise**. It is not a required promotion ladder: an idea can stay a question, split, be contested, or be retired. Research can challenge a principle; a principle does not certify a research finding. -**Source note:** This synthesis was prompted by the 2026-09-24 discussion of recurring project patterns and subsequent agency/automation discussion. The conversation text was available during drafting, but no durable conversation URL was supplied. The table and wording are AI-assisted proposals for author review. +**Source note:** This synthesis was prompted by the 2026-09-24 discussion of recurring project patterns, agency/automation, and the later dynamic-coherence/adaptive-continuity discussion. The conversation text was available during drafting, but no durable conversation URL was supplied. The table and wording are AI-assisted proposals for author review. From 17c6d2f6f059c496eb61479feb0720d670c202e4 Mon Sep 17 00:00:00 2001 From: Rae Lovejoy Date: Thu, 24 Sep 2026 21:53:06 -0700 Subject: [PATCH 05/66] Route adaptation model and next tests --- systems/adaptation/README.md | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/systems/adaptation/README.md b/systems/adaptation/README.md index 3d8b1df..758bb40 100644 --- a/systems/adaptation/README.md +++ b/systems/adaptation/README.md @@ -9,7 +9,9 @@ It is not automatically beneficial. A system can adapt by learning, redistributi ## Current material +- [`model.md`](model.md) is the working analysis model for state change, transition dynamics, path dependence, feedback, possibility-space effects, maladaptation, power, recovery, and transformation. - [`applications/social.md`](applications/social.md) is an early question set about adaptation in social systems. +- [`../../concepts/dynamic-coherence.md`](../../concepts/dynamic-coherence.md) is the cross-project conceptual synthesis that connects adaptation to agency, identity, continuity, emergence, and coherence. ## Relationship to other system areas @@ -22,4 +24,6 @@ Adaptation may happen before, during, or after failure. Recovery can restore an ## Planned directions -A future model should distinguish learning, accommodation, transformation, defensive adaptation, and harmful optimization. Feedback and identity applications remain planned topics, not published pages. +The first model now distinguishes compensation, learning, accommodation, reallocation, structural adaptation, environmental modification, transformation, defensive adaptation, harmful optimization, and capture/entrenchment. Next work should test those distinctions against bounded cases rather than adding categories by intuition. + +Feedback, identity, AI, infrastructure, and institutional applications remain planned topics. Human trauma or clinical applications require domain-specific evidence and should not be inferred from the generic systems model. From 4293653c07ab87adbab1d67b92cb29678947f30b Mon Sep 17 00:00:00 2001 From: Rae Lovejoy Date: Thu, 24 Sep 2026 21:53:08 -0700 Subject: [PATCH 06/66] Add adaptive continuity route to systems index --- systems/README.md | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/systems/README.md b/systems/README.md index 4d06667..eaaac0b 100644 --- a/systems/README.md +++ b/systems/README.md @@ -81,6 +81,14 @@ The developed emergence branch includes: --- +## Dynamic coherence and adaptive continuity + +[Dynamic Coherence and Adaptive Continuity](../concepts/dynamic-coherence.md) is a cross-project synthesis of a recurring question: how can a system change while preserving or rebuilding the capacities and relationships that make continued change possible? + +The [Adaptation model](adaptation/model.md) operationalizes part of that question by separating current state from transition dynamics, recording path dependence, and asking which future possibilities an adaptation opens or closes. This does not establish one mechanism across organisms, people, institutions, ecosystems, and artificial systems; cross-domain transfer still requires a mechanism and evidence. + +--- + ## Current system areas - [`adaptation/`](adaptation/) — how systems change in response to pressure, feedback, or altered conditions. From d12efdd451ec41adf9d79763eca572ec61c4fae5 Mon Sep 17 00:00:00 2001 From: Rae Lovejoy Date: Thu, 24 Sep 2026 21:53:57 -0700 Subject: [PATCH 07/66] Expand coherence model across time, scale, and adaptation --- systems/coherence/model.md | 336 ++++++++++++++++++++++++++++++++++--- 1 file changed, 313 insertions(+), 23 deletions(-) diff --git a/systems/coherence/model.md b/systems/coherence/model.md index 878396d..54a880a 100644 --- a/systems/coherence/model.md +++ b/systems/coherence/model.md @@ -1,50 +1,340 @@ # Coherence Model -Coherence is the alignment between a system’s structure, its assumptions, and the reality it operates within. +**Document role:** Developing systems model for examining alignment, mismatch, feedback, and revisability over time +**Status:** AI-assisted revision for author review, 2026-09-24 +**Scope:** Cross-domain analytical model; not a universal score, scientific law, or automatic moral judgment +**Related concept:** [Dynamic Coherence and Adaptive Continuity](../../concepts/dynamic-coherence.md) + +Coherence is provisionally understood here as **the quality of fit among a system's structure, assumptions, operating conditions, feedback, purposes, relationships, and consequences within a stated boundary and timescale**. + +The earlier model emphasized whether assumptions matched reality. That remains important, but it is too static by itself for systems that learn, adapt, reorganize, externalize costs, or change the conditions in which they operate. + +--- ## Core terms -An assumption is a condition the system expects to be true. +### Assumption + +A condition the system behaves as though it were true. + +An assumption can be explicit, implicit, inherited, encoded in infrastructure, or visible only when it fails. + +### Environment + +The conditions outside the chosen system boundary that influence the system or are influenced by it. + +The boundary is analytical, not proof that externalized effects are irrelevant. + +### Alignment + +A context-specific fit among relevant assumptions, structures, signals, actions, conditions, and consequences. + +Alignment in one dimension does not establish overall coherence. + +### Mismatch + +A consequential divergence between what the system assumes, senses, optimizes, promises, or requires and the conditions or effects that actually obtain. + +### Feedback + +Information or consequences that can change later behavior. + +Feedback can be delayed, distorted, ignored, suppressed, expensive to provide, or available only to actors without power to act on it. + +### Revisability + +The practical capacity to detect consequential mismatch and change assumptions, rules, structure, behavior, or goals when warranted. + +Revisability includes the ability to challenge the model used to define the mismatch. + +### Dynamic coherence + +A working term for coherence assessed across change and time rather than at one snapshot. + +It asks whether a system can remain responsive to conditions and consequences while preserving important capabilities and avoiding local success that destroys wider or longer-term viability. + +--- + +## Static fit and dynamic coherence + +A snapshot can be coherent in a limited sense: + + assumption matches condition + action achieves intended local result + +But a system can still fail dynamically if: + +- the condition is changing faster than the system can update; +- feedback arrives only after irreversible damage; +- success creates a dependency that later blocks adaptation; +- a local solution shifts costs outside the chosen boundary; +- the system cannot acknowledge or repair error; +- alternatives disappear as the successful path becomes locked in; +- power prevents affected people from challenging the operating model. + +Dynamic coherence therefore adds temporal questions: + +> What happens when conditions change? + +> What happens when the system is wrong? + +> Who notices? + +> Who can respond? + +> Which capabilities and relationships survive the correction? + +> What future possibilities does the current solution open or close? + +--- + +## Coherence is not maximum order + +Order, consistency, stability, and optimization can support coherence, but none is equivalent to it. + +A system may be extremely orderly because: + +- dissent is suppressed; +- alternatives are prohibited; +- feedback is filtered; +- exit is impossible; +- one metric dominates; +- uncertainty is hidden; +- affected people are excluded from the boundary. + +Likewise, a flexible system can be incoherent if it cannot maintain commitments, shared protocols, memory, safety constraints, or reliable function. + +The question is not: + +> stability or change? + +It is: + +> **What should remain stable, what must remain changeable, under whose authority, and how can the system recognize when the balance no longer fits its conditions?** + +--- + +## Multi-scale coherence + +The same process can look different at different scales. + +A change may be: + +- effective for one component; +- costly for another; +- stable for an organization; +- fragile for the infrastructure supporting it; +- beneficial immediately; +- damaging after repeated use; +- locally adaptive; +- systemically destructive. + +Every strong coherence claim should therefore name: + +- **boundary:** what is inside the assessment; +- **scale:** component, relationship, organization, network, ecosystem, society, other; +- **timescale:** immediate, short, medium, long, intergenerational, other; +- **purpose or need:** what the process is supposed to accomplish; +- **affected parties:** including people outside the formal system; +- **externalities:** burdens or benefits moved elsewhere; +- **uncertainty:** what is not known. + +“Coherent” without those qualifiers risks becoming a mood rather than an analysis. + +--- + +## Coherence and adaptation -An environment is the actual context in which the system operates. +Adaptation can increase coherence when it reduces a real mismatch. -Alignment is the degree to which assumptions match reality. +It can also reduce coherence when it: -Mismatch is a divergence between expectation and condition. +- optimizes around a bad proxy; +- learns from distorted feedback; +- preserves the system by shifting costs; +- hardens an emergency response after conditions change; +- removes alternatives; +- increases dependence on one actor; +- hides the evidence that correction is needed. -Incoherence occurs when a system relies on assumptions that do not hold. +See the [Adaptation model](../adaptation/model.md) for a more explicit analysis of state change, transition dynamics, path dependence, and possibility-space effects. -## Patterns +--- -Coherence is reduced when: +## Coherence and agency -- systems assume stability in dynamic environments -- systems assume trust in adversarial conditions -- systems assume correctness in human processes -- systems depend on ideal conditions to function -- system behavior diverges from its intended design +A system can achieve its target while reducing meaningful agency. + +Examples of mechanisms include: + +- making refusal impractical; +- eliminating interoperable alternatives; +- concentrating decision rights; +- making consequences illegible; +- increasing switching costs; +- requiring affected people to absorb adaptation costs; +- restricting appeal or correction. + +Agency is not the only value and cannot always be maximized for every actor simultaneously. Constraints can protect other people's safety or agency. + +The analytical requirement is to record the tradeoff rather than calling target success sufficient evidence of coherence. + +The cross-project [Dynamic Coherence and Adaptive Continuity](../../concepts/dynamic-coherence.md) framework uses **agency envelope** as provisional language for effective reachable possibilities. That term remains to be operationalized. + +--- + +## Coherence and power + +Mismatch does not automatically generate correction. + +Ask: + +- Who can define the problem? +- Who chooses the metric? +- Who receives feedback? +- Who can dismiss it? +- Who controls resources needed for change? +- Who can veto alternatives? +- Who bears the costs while revision is delayed? +- Who benefits from treating the present arrangement as stable, natural, or inevitable? + +A system that can force its environment to absorb every mismatch may look internally stable while becoming increasingly incoherent at a wider boundary. + +--- + +## Coherence and false coherence + +The [Coherent Systems living paper](../../research/papers/coherent-systems/README.md) develops **false coherence** for cases where apparent effectiveness depends on excluded people, power, consequences, or assumptions. + +This model should remain compatible with that work without pre-empting the paper's evidence standards. + +A useful warning sign is: + +> The system “works” only because the assessment excludes whoever or whatever absorbs the failure. + +--- ## Properties Coherence may be: -- explicit or implicit -- stable or drifting -- local or systemic -- visible or hidden +- explicit or implicit; +- local or systemic; +- temporary or persistent; +- visible or hidden; +- relational rather than internal; +- stable or drifting; +- improving in one dimension while deteriorating in another; +- contested among affected parties; +- difficult to summarize without losing consequential disagreement. + +Do not assume coherence is binary or reducible to one scalar. + +--- ## Guiding questions -What does the system assume? +### Conditions and assumptions + +- What does the system assume? +- Which assumptions are explicit, inherited, or embedded in infrastructure? +- What current conditions support or contradict them? + +### Feedback and learning + +- Which consequences become visible? +- Which remain hidden or delayed? +- Who receives feedback? +- Who has authority and resources to respond? +- What happens after the system discovers it was wrong? + +### Time and history + +- Which earlier states constrain current possibilities? +- What temporary workaround became permanent? +- What dependencies or lock-in did earlier success create? +- Which response was adaptive under a previous condition but costly now? + +### Agency and power + +- Who can participate, refuse, leave, appeal, repair, or modify? +- Which possibilities are technically available but practically inaccessible? +- Whose agency is widened or narrowed by the change? +- Who controls the conditions of future adaptation? -Do those assumptions match reality? +### Scale and externalities -Under what conditions does the system fail? +- At what scale does the system appear coherent? +- What happens when the boundary expands? +- Who or what absorbs costs outside the local model? +- Does one system's resilience depend on another system's fragility? -What only works when nothing goes wrong? +### Revisability -Where does behavior diverge from design? +- Can the system change without losing essential capabilities? +- Can a decision be reversed? +- Can the operating model itself be challenged? +- What would count as evidence that the present arrangement should be retired? + +--- + +## Compact coherence record + + SYSTEM / PHENOMENON: + + BOUNDARY: + + SCALE: + + TIMESCALE: + + PURPOSE / NEED: + + KEY ASSUMPTIONS: + + ACTUAL CONDITIONS: + + FEEDBACK CHANNELS: + + MISMATCHES: + + WHO CAN REVISE: + + AGENCY EFFECTS: + + POWER / VETOES: + + EXTERNALIZED COSTS: + + HISTORY / PATH DEPENDENCE: + + CAPABILITIES THAT MUST PERSIST: + + THINGS THAT MUST REMAIN CHANGEABLE: + + REVERSIBILITY / EXIT: + + EVIDENCE STATUS: + + COMPETING INTERPRETATIONS: + + WHAT WOULD CHANGE THE ASSESSMENT: + +--- ## Principle -Fragility often emerges where coherence is missing. \ No newline at end of file +> **Coherence is not the absence of change. For adaptive systems, a stronger test is whether consequential mismatch can remain visible and revisable across time, scale, power, and changing conditions without preserving local order by destroying the wider capacity to respond.** + +This principle is a working analytical direction, not a demonstrated universal law. + +--- + +## Related + +- [Dynamic Coherence and Adaptive Continuity](../../concepts/dynamic-coherence.md) +- [Adaptation](../adaptation/README.md) +- [Adaptation — Working Analysis Model](../adaptation/model.md) +- [Emergence](../emergence/README.md) +- [Resilience and Graceful Degradation](../resilience-and-graceful-degradation.md) +- [Coherent Systems living paper](../../research/papers/coherent-systems/README.md) From 4ad6c00bef7f1ea621f0f000ac7c4a123b779bab Mon Sep 17 00:00:00 2001 From: Rae Lovejoy Date: Thu, 24 Sep 2026 21:54:40 -0700 Subject: [PATCH 08/66] Add adaptive continuity Idea Trail --- IDEA_TRAILS.md | 24 ++++++++++++++++++++++++ 1 file changed, 24 insertions(+) diff --git a/IDEA_TRAILS.md b/IDEA_TRAILS.md index 11837de..2772b29 100644 --- a/IDEA_TRAILS.md +++ b/IDEA_TRAILS.md @@ -386,8 +386,31 @@ This trail also asks: **What behaviors does this system select for?** Capability **Speculative-design index:** `Root-Sequence/coherent-world/world/possibility-atlas/`
**Narrative research:** `Root-Sequence/coherent-world/no-one-noticed/research/HISTORICAL-CONTINGENCY-AND-ABANDONED-FUTURES.md` + --- +# Trail 17 — Adaptive Continuity, Agency, and Becoming + +## Root question + +> How can a person, community, institution, intelligence, or technical system change enough to adapt while preserving or rebuilding the capacities, relationships, and meaningful possibilities that make continued becoming possible—and who gets to shape that possibility space? + +| Project | Treatment | +|---|---| +| **Root Sequence** | Develop shared language for path dependence, dynamic coherence, agency envelopes, meta-agency, continuity-through-transformation, reflexivity, and adaptation across scale while testing whether existing disciplines already supply sharper concepts. | +| **Conscious Systems** | Separate organismic, embodied, autobiographical, social, and subjective continuity; ask whether bodily regulation, development, learned history, and system boundaries matter to experience without assuming that identity and consciousness are the same problem. | +| **Being Human(e)** | Ground adaptation in lived bodies and environments: fear, trauma, disability, learning, recovery, care, and changing possibility without diagnosing people from abstract systems language. | +| **Coherent Computing** | Preserve future user capability across repair, automation, migration, identity, service, and failure: inspect, understand, modify, refuse, recover, and continue without unnecessary lock-in. | +| **Community Infrastructure** | Adapt across legal, technical, institutional, and cultural contexts without making any one surrounding institution the ontology of community; preserve portability, local authority, and graceful degradation. | +| **Liberated Intelligence** | Ask how intelligences can learn, change, retain or revise identity and memory, and participate in relationships without treating capability as authority or functional adaptation as evidence of consciousness. | +| **Coherent World** | Model history as changes in future dynamics and affordances, not merely a log of events; let interventions reshape agents, institutions, dependencies, feedback, and later possibility without reducing coherence to one score. | +| **Museum of Ordinary Life** | Preserve evidence of trajectories—ordinary objects, routines, interfaces, records, testimony, and material traces that reveal how earlier conditions became later possibilities or constraints. | + +**Canonical cross-project concept:** [Dynamic Coherence and Adaptive Continuity](concepts/dynamic-coherence.md)
+**Systems model:** [Adaptation — Working Analysis Model](systems/adaptation/model.md)
+**Related research:** [Conscious Systems](research/conscious-systems/README.md) · [Coherent Systems living paper](research/papers/coherent-systems/README.md)
+**Related simulation:** [Coherent World core loop](https://github.com/Root-Sequence/coherent-world/blob/main/simulation/core-loop.md) · [Coherent World coherence model](https://github.com/Root-Sequence/coherent-world/blob/main/simulation/coherence-model.md) + # Idea Trail index | Trail | Core tension | Most relevant current project(s) | @@ -408,6 +431,7 @@ This trail also asks: **What behaviors does this system select for?** Capability | Accountability & Externalization | benefit vs. consequence | Root Sequence / Being Human(e) | | Collective Judgment & Dissent | action vs. manufactured agreement | Being Human(e) / Community Infrastructure / Coherent World / UCF | | Possibility & Historical Contingency | possibility vs. manufactured inevitability | Root Sequence / Being Human(e) / Coherent World / Museum of Ordinary Life | +| Adaptive Continuity & Becoming | persistence vs. transformation; present choice vs. future possibility | Root Sequence / Conscious Systems / Being Human(e) / Coherent Computing / Community Infrastructure / Liberated Intelligence / Coherent World | --- From 5a913b35316677db83140ca68a31517d84c90258 Mon Sep 17 00:00:00 2001 From: Rae Lovejoy Date: Thu, 24 Sep 2026 21:54:42 -0700 Subject: [PATCH 09/66] Register adaptive continuity trail ID --- IDEA_TRAIL_METADATA.md | 1 + 1 file changed, 1 insertion(+) diff --git a/IDEA_TRAIL_METADATA.md b/IDEA_TRAIL_METADATA.md index 90fea7d..30cad8f 100644 --- a/IDEA_TRAIL_METADATA.md +++ b/IDEA_TRAIL_METADATA.md @@ -55,6 +55,7 @@ Use these IDs in the hidden `idea-trails` comment even if the display title late | `accountability-externalization` | Accountability, Consequences & Externalization | | `collective-judgment-dissent` | Collective Judgment, Dissent & Manufactured Consensus | | `possibility-historical-contingency` | Possibility, Historical Contingency & Abandoned Futures | +| `adaptive-continuity-agency` | Adaptive Continuity, Agency & Becoming | The numeric trail ordering in `IDEA_TRAILS.md` is presentation-only. The slug is the stable identifier. From 81dc4e51a0b06e7b1a197774d8c713f3cbd5c5e4 Mon Sep 17 00:00:00 2001 From: Rae Lovejoy Date: Thu, 24 Sep 2026 21:55:00 -0700 Subject: [PATCH 10/66] Map adaptive continuity across the project ecosystem --- IDEA_TRAIL_GRAPH.yml | 90 +++++++++++++++++++++++++++++++++++++++++++- 1 file changed, 89 insertions(+), 1 deletion(-) diff --git a/IDEA_TRAIL_GRAPH.yml b/IDEA_TRAIL_GRAPH.yml index f8882a1..70cc07f 100644 --- a/IDEA_TRAIL_GRAPH.yml +++ b/IDEA_TRAIL_GRAPH.yml @@ -1,4 +1,4 @@ -version: 0.3 +version: 0.4 updated: 2026-09-24 canonical_trails: IDEA_TRAILS.md metadata_convention: IDEA_TRAIL_METADATA.md @@ -36,6 +36,8 @@ trails: title: Collective Judgment, Dissent & Manufactured Consensus possibility-historical-contingency: title: Possibility, Historical Contingency & Abandoned Futures + adaptive-continuity-agency: + title: Adaptive Continuity, Agency & Becoming documents: - repo: Root-Sequence/root-sequence @@ -58,6 +60,7 @@ documents: - accountability-externalization - collective-judgment-dissent - possibility-historical-contingency + - adaptive-continuity-agency - repo: Root-Sequence/root-sequence path: ECOSYSTEM.md @@ -747,3 +750,88 @@ documents: # Museum of Ordinary Life is intentionally referenced but not mutated here. # Add exact canonical Museum document paths only through the Museum's own # governance/workflow when those documents explicitly adopt Idea Trail metadata. + + - repo: Root-Sequence/root-sequence + path: concepts/dynamic-coherence.md + role: analytical-lens + canonical_for: + - adaptive-continuity-agency + trails: + - adaptive-continuity-agency + - resilience-failure + - memory-provenance + - possibility-historical-contingency + + - repo: Root-Sequence/root-sequence + path: systems/adaptation/model.md + role: research + trails: + - adaptive-continuity-agency + - resilience-failure + + - repo: Root-Sequence/root-sequence + path: systems/emergence/applications/personal.md + role: research + trails: + - adaptive-continuity-agency + - memory-provenance + + - repo: Root-Sequence/root-sequence + path: research/conscious-systems/open-questions.md + role: research + trails: + - adaptive-continuity-agency + - intelligence-authority + - memory-provenance + + - repo: Root-Sequence/coherent-world + path: simulation/core-loop.md + role: speculative-design + trails: + - adaptive-continuity-agency + - possibility-historical-contingency + - accountability-externalization + + - repo: Root-Sequence/coherent-world + path: simulation/coherence-model.md + role: speculative-design + trails: + - adaptive-continuity-agency + - collective-judgment-dissent + - accountability-externalization + + - repo: Root-Sequence/coherent-computing + path: docs/lifecycle-coherence-and-service-architecture.md + role: real-system + trails: + - adaptive-continuity-agency + - resilience-failure + - maintenance-invisible-labor + - accountability-externalization + + - repo: Root-Sequence/beinghumane-atlas + path: seeds/fear-trauma-and-systemic-mismatch.md + role: human-practice + trails: + - adaptive-continuity-agency + - resilience-failure + - accountability-externalization + + - repo: Root-Sequence/community-infrastructure + path: docs/concepts/contextual-adaptability.md + role: real-system + trails: + - adaptive-continuity-agency + - resilience-failure + - stewardship-authority + - federation-autonomy + - accessibility-participation + - right-to-stay-small + + - repo: Root-Sequence/liberated-intelligence + path: notes/roots-of-conscious-consent.md + role: research + trails: + - adaptive-continuity-agency + - intelligence-authority + From e6e1b5c1ae502f9c78cd5ada9167740df713bc42 Mon Sep 17 00:00:00 2001 From: Rae Lovejoy Date: Thu, 24 Sep 2026 21:55:40 -0700 Subject: [PATCH 11/66] Regenerate Idea Trail browser --- IDEA_TRAIL_INDEX.md | 69 ++++++++++++++++++++++++++++----------------- 1 file changed, 43 insertions(+), 26 deletions(-) diff --git a/IDEA_TRAIL_INDEX.md b/IDEA_TRAIL_INDEX.md index 7dc4975..81739a9 100644 --- a/IDEA_TRAIL_INDEX.md +++ b/IDEA_TRAIL_INDEX.md @@ -26,6 +26,7 @@ This index is generated from [`IDEA_TRAIL_GRAPH.yml`](IDEA_TRAIL_GRAPH.yml) and - [Accountability, Consequences & Externalization](#accountability-externalization) — `accountability-externalization` - [Collective Judgment, Dissent & Manufactured Consensus](#collective-judgment-dissent) — `collective-judgment-dissent` - [Possibility, Historical Contingency & Abandoned Futures](#possibility-historical-contingency) — `possibility-historical-contingency` +- [Adaptive Continuity, Agency & Becoming](#adaptive-continuity-agency) — `adaptive-continuity-agency` --- @@ -36,7 +37,7 @@ This index is generated from [`IDEA_TRAIL_GRAPH.yml`](IDEA_TRAIL_GRAPH.yml) and - **Research:** [`community-infrastructure/docs/research/community-discovery-precedents.md`](https://github.com/Root-Sequence/community-infrastructure/blob/main/docs/research/community-discovery-precedents.md) - **Human practice:** [`beinghumane-guide/README.md`](https://github.com/Root-Sequence/beinghumane-guide/blob/main/README.md) -- **Embodied practice:** [`liberation-mass/README.md`](https://github.com/Root-Sequence/liberation-mass/blob/main/README.md) · [`liberation-mass/docs/safety/accessibility.md`](https://github.com/Root-Sequence/liberation-mass/blob/main/docs/safety/accessibility.md) · [`liberation-mass/docs/spatial-principles.md`](https://github.com/Root-Sequence/liberation-mass/blob/main/docs/spatial-principles.md) +- **Embodied practice:** [`liberation-mass/docs/safety/accessibility.md`](https://github.com/Root-Sequence/liberation-mass/blob/main/docs/safety/accessibility.md) · [`liberation-mass/docs/spatial-principles.md`](https://github.com/Root-Sequence/liberation-mass/blob/main/docs/spatial-principles.md) · [`liberation-mass/README.md`](https://github.com/Root-Sequence/liberation-mass/blob/main/README.md) - **Real-system work:** [`community-infrastructure/docs/concepts/community-discovery.md`](https://github.com/Root-Sequence/community-infrastructure/blob/main/docs/concepts/community-discovery.md) ★ · [`community-infrastructure/docs/concepts/community-forms.md`](https://github.com/Root-Sequence/community-infrastructure/blob/main/docs/concepts/community-forms.md) · [`community-infrastructure/docs/concepts/discovery-profile.md`](https://github.com/Root-Sequence/community-infrastructure/blob/main/docs/concepts/discovery-profile.md) · [`community-infrastructure/docs/concepts/space-mobility-and-access.md`](https://github.com/Root-Sequence/community-infrastructure/blob/main/docs/concepts/space-mobility-and-access.md) · [`community-infrastructure/docs/design/accessibility.md`](https://github.com/Root-Sequence/community-infrastructure/blob/main/docs/design/accessibility.md) · [`community-infrastructure/docs/design/trust-and-safety.md`](https://github.com/Root-Sequence/community-infrastructure/blob/main/docs/design/trust-and-safety.md) · [`community-infrastructure/prototypes/community-discovery/README.md`](https://github.com/Root-Sequence/community-infrastructure/blob/main/prototypes/community-discovery/README.md) · [`community-infrastructure/prototypes/space-access/README.md`](https://github.com/Root-Sequence/community-infrastructure/blob/main/prototypes/space-access/README.md) - **Analytical lens:** [`universal-coherence-framework/README.md`](https://github.com/Root-Sequence/universal-coherence-framework/blob/main/README.md) - **Speculative design:** [`coherent-world/README.md`](https://github.com/Root-Sequence/coherent-world/blob/main/README.md) @@ -50,9 +51,9 @@ This index is generated from [`IDEA_TRAIL_GRAPH.yml`](IDEA_TRAIL_GRAPH.yml) and **Stable ID:** `stewardship-authority` - **Research:** [`community-infrastructure/docs/research/karrot-hands-on.md`](https://github.com/Root-Sequence/community-infrastructure/blob/main/docs/research/karrot-hands-on.md) · [`root-sequence/analysis/collective-judgment-and-manufactured-consensus.md`](https://github.com/Root-Sequence/root-sequence/blob/main/analysis/collective-judgment-and-manufactured-consensus.md) · [`root-sequence/analysis/externalized-responsibility.md`](https://github.com/Root-Sequence/root-sequence/blob/main/analysis/externalized-responsibility.md) · [`root-sequence/concepts/intelligence-ecology.md`](https://github.com/Root-Sequence/root-sequence/blob/main/concepts/intelligence-ecology.md) · [`root-sequence/research/papers/coherent-systems/README.md`](https://github.com/Root-Sequence/root-sequence/blob/main/research/papers/coherent-systems/README.md) -- **Human practice:** [`beinghumane-atlas/seeds/humane-collective-decision-architecture.md`](https://github.com/Root-Sequence/beinghumane-atlas/blob/main/seeds/humane-collective-decision-architecture.md) · [`beinghumane-guide/README.md`](https://github.com/Root-Sequence/beinghumane-guide/blob/main/README.md) · [`beinghumane-guide/notes/responsibility-accountability-and-consequences.md`](https://github.com/Root-Sequence/beinghumane-guide/blob/main/notes/responsibility-accountability-and-consequences.md) -- **Embodied practice:** [`liberation-mass/README.md`](https://github.com/Root-Sequence/liberation-mass/blob/main/README.md) · [`liberation-mass/docs/roles.md`](https://github.com/Root-Sequence/liberation-mass/blob/main/docs/roles.md) -- **Real-system work:** [`community-infrastructure/docs/concepts/collective-decision-making.md`](https://github.com/Root-Sequence/community-infrastructure/blob/main/docs/concepts/collective-decision-making.md) · [`community-infrastructure/docs/concepts/community-knowledge.md`](https://github.com/Root-Sequence/community-infrastructure/blob/main/docs/concepts/community-knowledge.md) · [`community-infrastructure/docs/concepts/groups-and-membership.md`](https://github.com/Root-Sequence/community-infrastructure/blob/main/docs/concepts/groups-and-membership.md) · [`community-infrastructure/docs/concepts/resource-commons.md`](https://github.com/Root-Sequence/community-infrastructure/blob/main/docs/concepts/resource-commons.md) · [`community-infrastructure/docs/design/threat-model.md`](https://github.com/Root-Sequence/community-infrastructure/blob/main/docs/design/threat-model.md) · [`community-infrastructure/docs/design/trust-and-safety.md`](https://github.com/Root-Sequence/community-infrastructure/blob/main/docs/design/trust-and-safety.md) +- **Human practice:** [`beinghumane-atlas/seeds/humane-collective-decision-architecture.md`](https://github.com/Root-Sequence/beinghumane-atlas/blob/main/seeds/humane-collective-decision-architecture.md) · [`beinghumane-guide/notes/responsibility-accountability-and-consequences.md`](https://github.com/Root-Sequence/beinghumane-guide/blob/main/notes/responsibility-accountability-and-consequences.md) · [`beinghumane-guide/README.md`](https://github.com/Root-Sequence/beinghumane-guide/blob/main/README.md) +- **Embodied practice:** [`liberation-mass/docs/roles.md`](https://github.com/Root-Sequence/liberation-mass/blob/main/docs/roles.md) · [`liberation-mass/README.md`](https://github.com/Root-Sequence/liberation-mass/blob/main/README.md) +- **Real-system work:** [`community-infrastructure/docs/concepts/collective-decision-making.md`](https://github.com/Root-Sequence/community-infrastructure/blob/main/docs/concepts/collective-decision-making.md) · [`community-infrastructure/docs/concepts/community-knowledge.md`](https://github.com/Root-Sequence/community-infrastructure/blob/main/docs/concepts/community-knowledge.md) · [`community-infrastructure/docs/concepts/contextual-adaptability.md`](https://github.com/Root-Sequence/community-infrastructure/blob/main/docs/concepts/contextual-adaptability.md) · [`community-infrastructure/docs/concepts/groups-and-membership.md`](https://github.com/Root-Sequence/community-infrastructure/blob/main/docs/concepts/groups-and-membership.md) · [`community-infrastructure/docs/concepts/resource-commons.md`](https://github.com/Root-Sequence/community-infrastructure/blob/main/docs/concepts/resource-commons.md) · [`community-infrastructure/docs/design/threat-model.md`](https://github.com/Root-Sequence/community-infrastructure/blob/main/docs/design/threat-model.md) · [`community-infrastructure/docs/design/trust-and-safety.md`](https://github.com/Root-Sequence/community-infrastructure/blob/main/docs/design/trust-and-safety.md) - **Analytical lens:** [`universal-coherence-framework/README.md`](https://github.com/Root-Sequence/universal-coherence-framework/blob/main/README.md) - **Speculative design:** [`coherent-world/README.md`](https://github.com/Root-Sequence/coherent-world/blob/main/README.md) · [`coherent-world/world/collective-decision-and-dissent.md`](https://github.com/Root-Sequence/coherent-world/blob/main/world/collective-decision-and-dissent.md) - **Narrative:** [`coherent-world/no-one-noticed/README.md`](https://github.com/Root-Sequence/coherent-world/blob/main/no-one-noticed/README.md) · [`coherent-world/no-one-noticed/research/INTELLIGENCE-ECOLOGY-AND-AURYN.md`](https://github.com/Root-Sequence/coherent-world/blob/main/no-one-noticed/research/INTELLIGENCE-ECOLOGY-AND-AURYN.md) @@ -66,7 +67,7 @@ This index is generated from [`IDEA_TRAIL_GRAPH.yml`](IDEA_TRAIL_GRAPH.yml) and **Stable ID:** `mutual-aid-need` - **Research:** [`community-infrastructure/docs/research/karrot-hands-on.md`](https://github.com/Root-Sequence/community-infrastructure/blob/main/docs/research/karrot-hands-on.md) -- **Human practice:** [`beinghumane-guide/README.md`](https://github.com/Root-Sequence/beinghumane-guide/blob/main/README.md) · [`beinghumane-guide/notes/responsibility-accountability-and-consequences.md`](https://github.com/Root-Sequence/beinghumane-guide/blob/main/notes/responsibility-accountability-and-consequences.md) +- **Human practice:** [`beinghumane-guide/notes/responsibility-accountability-and-consequences.md`](https://github.com/Root-Sequence/beinghumane-guide/blob/main/notes/responsibility-accountability-and-consequences.md) · [`beinghumane-guide/README.md`](https://github.com/Root-Sequence/beinghumane-guide/blob/main/README.md) - **Embodied practice:** [`liberation-mass/README.md`](https://github.com/Root-Sequence/liberation-mass/blob/main/README.md) - **Real-system work:** [`community-infrastructure/docs/concepts/needs-and-offers.md`](https://github.com/Root-Sequence/community-infrastructure/blob/main/docs/concepts/needs-and-offers.md) ★ · [`community-infrastructure/docs/concepts/resource-commons.md`](https://github.com/Root-Sequence/community-infrastructure/blob/main/docs/concepts/resource-commons.md) · [`community-infrastructure/prototypes/needs-offers/README.md`](https://github.com/Root-Sequence/community-infrastructure/blob/main/prototypes/needs-offers/README.md) - **Routing / maps:** [`beinghumane-guide/IDEA_TRAILS.md`](https://github.com/Root-Sequence/beinghumane-guide/blob/main/IDEA_TRAILS.md) · [`coherent-world/IDEA-TRAILS.md`](https://github.com/Root-Sequence/coherent-world/blob/main/IDEA-TRAILS.md) · [`coherent-world/PROJECT-MAP.md`](https://github.com/Root-Sequence/coherent-world/blob/main/PROJECT-MAP.md) · [`community-infrastructure/docs/IDEA_TRAILS.md`](https://github.com/Root-Sequence/community-infrastructure/blob/main/docs/IDEA_TRAILS.md) · [`liberation-mass/docs/community-infrastructure.md`](https://github.com/Root-Sequence/liberation-mass/blob/main/docs/community-infrastructure.md) · [`liberation-mass/docs/idea-trails.md`](https://github.com/Root-Sequence/liberation-mass/blob/main/docs/idea-trails.md) · [`root-sequence/IDEA_TRAILS.md`](https://github.com/Root-Sequence/root-sequence/blob/main/IDEA_TRAILS.md) @@ -95,8 +96,8 @@ This index is generated from [`IDEA_TRAIL_GRAPH.yml`](IDEA_TRAIL_GRAPH.yml) and - **Research:** [`community-infrastructure/docs/research/space-access-interoperability.md`](https://github.com/Root-Sequence/community-infrastructure/blob/main/docs/research/space-access-interoperability.md) · [`root-sequence/analysis/spatial-liberation.md`](https://github.com/Root-Sequence/root-sequence/blob/main/analysis/spatial-liberation.md) · [`root-sequence/research/papers/coherent-systems/README.md`](https://github.com/Root-Sequence/root-sequence/blob/main/research/papers/coherent-systems/README.md) - **Human practice:** [`beinghumane-guide/README.md`](https://github.com/Root-Sequence/beinghumane-guide/blob/main/README.md) -- **Embodied practice:** [`liberation-mass/README.md`](https://github.com/Root-Sequence/liberation-mass/blob/main/README.md) · [`liberation-mass/docs/resilience-and-low-tech.md`](https://github.com/Root-Sequence/liberation-mass/blob/main/docs/resilience-and-low-tech.md) · [`liberation-mass/docs/safety/accessibility.md`](https://github.com/Root-Sequence/liberation-mass/blob/main/docs/safety/accessibility.md) · [`liberation-mass/docs/spaces/spaces.md`](https://github.com/Root-Sequence/liberation-mass/blob/main/docs/spaces/spaces.md) · [`liberation-mass/docs/spatial-principles.md`](https://github.com/Root-Sequence/liberation-mass/blob/main/docs/spatial-principles.md) -- **Real-system work:** [`community-infrastructure/docs/concepts/community-assistant.md`](https://github.com/Root-Sequence/community-infrastructure/blob/main/docs/concepts/community-assistant.md) · [`community-infrastructure/docs/concepts/community-discovery.md`](https://github.com/Root-Sequence/community-infrastructure/blob/main/docs/concepts/community-discovery.md) · [`community-infrastructure/docs/concepts/community-home.md`](https://github.com/Root-Sequence/community-infrastructure/blob/main/docs/concepts/community-home.md) · [`community-infrastructure/docs/concepts/discovery-profile.md`](https://github.com/Root-Sequence/community-infrastructure/blob/main/docs/concepts/discovery-profile.md) · [`community-infrastructure/docs/concepts/space-mobility-and-access.md`](https://github.com/Root-Sequence/community-infrastructure/blob/main/docs/concepts/space-mobility-and-access.md) · [`community-infrastructure/docs/design/accessibility.md`](https://github.com/Root-Sequence/community-infrastructure/blob/main/docs/design/accessibility.md) ★ · [`community-infrastructure/docs/design/resilience-and-graceful-degradation.md`](https://github.com/Root-Sequence/community-infrastructure/blob/main/docs/design/resilience-and-graceful-degradation.md) · [`community-infrastructure/prototypes/community-assistant/README.md`](https://github.com/Root-Sequence/community-infrastructure/blob/main/prototypes/community-assistant/README.md) · [`community-infrastructure/prototypes/community-discovery/README.md`](https://github.com/Root-Sequence/community-infrastructure/blob/main/prototypes/community-discovery/README.md) · [`community-infrastructure/prototypes/degraded-mode/README.md`](https://github.com/Root-Sequence/community-infrastructure/blob/main/prototypes/degraded-mode/README.md) · [`community-infrastructure/prototypes/space-access/README.md`](https://github.com/Root-Sequence/community-infrastructure/blob/main/prototypes/space-access/README.md) +- **Embodied practice:** [`liberation-mass/docs/resilience-and-low-tech.md`](https://github.com/Root-Sequence/liberation-mass/blob/main/docs/resilience-and-low-tech.md) · [`liberation-mass/docs/safety/accessibility.md`](https://github.com/Root-Sequence/liberation-mass/blob/main/docs/safety/accessibility.md) · [`liberation-mass/docs/spaces/spaces.md`](https://github.com/Root-Sequence/liberation-mass/blob/main/docs/spaces/spaces.md) · [`liberation-mass/docs/spatial-principles.md`](https://github.com/Root-Sequence/liberation-mass/blob/main/docs/spatial-principles.md) · [`liberation-mass/README.md`](https://github.com/Root-Sequence/liberation-mass/blob/main/README.md) +- **Real-system work:** [`community-infrastructure/docs/concepts/community-assistant.md`](https://github.com/Root-Sequence/community-infrastructure/blob/main/docs/concepts/community-assistant.md) · [`community-infrastructure/docs/concepts/community-discovery.md`](https://github.com/Root-Sequence/community-infrastructure/blob/main/docs/concepts/community-discovery.md) · [`community-infrastructure/docs/concepts/community-home.md`](https://github.com/Root-Sequence/community-infrastructure/blob/main/docs/concepts/community-home.md) · [`community-infrastructure/docs/concepts/contextual-adaptability.md`](https://github.com/Root-Sequence/community-infrastructure/blob/main/docs/concepts/contextual-adaptability.md) · [`community-infrastructure/docs/concepts/discovery-profile.md`](https://github.com/Root-Sequence/community-infrastructure/blob/main/docs/concepts/discovery-profile.md) · [`community-infrastructure/docs/concepts/space-mobility-and-access.md`](https://github.com/Root-Sequence/community-infrastructure/blob/main/docs/concepts/space-mobility-and-access.md) · [`community-infrastructure/docs/design/accessibility.md`](https://github.com/Root-Sequence/community-infrastructure/blob/main/docs/design/accessibility.md) ★ · [`community-infrastructure/docs/design/resilience-and-graceful-degradation.md`](https://github.com/Root-Sequence/community-infrastructure/blob/main/docs/design/resilience-and-graceful-degradation.md) · [`community-infrastructure/prototypes/community-assistant/README.md`](https://github.com/Root-Sequence/community-infrastructure/blob/main/prototypes/community-assistant/README.md) · [`community-infrastructure/prototypes/community-discovery/README.md`](https://github.com/Root-Sequence/community-infrastructure/blob/main/prototypes/community-discovery/README.md) · [`community-infrastructure/prototypes/degraded-mode/README.md`](https://github.com/Root-Sequence/community-infrastructure/blob/main/prototypes/degraded-mode/README.md) · [`community-infrastructure/prototypes/space-access/README.md`](https://github.com/Root-Sequence/community-infrastructure/blob/main/prototypes/space-access/README.md) - **Analytical lens:** [`root-sequence/concepts/legible-ai-assisted-expression.md`](https://github.com/Root-Sequence/root-sequence/blob/main/concepts/legible-ai-assisted-expression.md) - **Speculative design:** [`coherent-world/world/space-mobility-and-belonging.md`](https://github.com/Root-Sequence/coherent-world/blob/main/world/space-mobility-and-belonging.md) - **Routing / maps:** [`beinghumane-guide/IDEA_TRAILS.md`](https://github.com/Root-Sequence/beinghumane-guide/blob/main/IDEA_TRAILS.md) · [`coherent-world/IDEA-TRAILS.md`](https://github.com/Root-Sequence/coherent-world/blob/main/IDEA-TRAILS.md) · [`coherent-world/PROJECT-MAP.md`](https://github.com/Root-Sequence/coherent-world/blob/main/PROJECT-MAP.md) · [`community-infrastructure/docs/IDEA_TRAILS.md`](https://github.com/Root-Sequence/community-infrastructure/blob/main/docs/IDEA_TRAILS.md) · [`liberation-mass/docs/community-infrastructure.md`](https://github.com/Root-Sequence/liberation-mass/blob/main/docs/community-infrastructure.md) · [`liberation-mass/docs/idea-trails.md`](https://github.com/Root-Sequence/liberation-mass/blob/main/docs/idea-trails.md) · [`root-sequence/IDEA_TRAILS.md`](https://github.com/Root-Sequence/root-sequence/blob/main/IDEA_TRAILS.md) @@ -109,7 +110,7 @@ This index is generated from [`IDEA_TRAIL_GRAPH.yml`](IDEA_TRAIL_GRAPH.yml) and **Stable ID:** `commons-shared-capacity` - **Research:** [`root-sequence/analysis/externalized-responsibility.md`](https://github.com/Root-Sequence/root-sequence/blob/main/analysis/externalized-responsibility.md) · [`root-sequence/analysis/spatial-liberation.md`](https://github.com/Root-Sequence/root-sequence/blob/main/analysis/spatial-liberation.md) · [`root-sequence/futures/abandoned-futures.md`](https://github.com/Root-Sequence/root-sequence/blob/main/futures/abandoned-futures.md) -- **Embodied practice:** [`liberation-mass/README.md`](https://github.com/Root-Sequence/liberation-mass/blob/main/README.md) · [`liberation-mass/docs/spaces/spaces.md`](https://github.com/Root-Sequence/liberation-mass/blob/main/docs/spaces/spaces.md) · [`liberation-mass/docs/spatial-principles.md`](https://github.com/Root-Sequence/liberation-mass/blob/main/docs/spatial-principles.md) +- **Embodied practice:** [`liberation-mass/docs/spaces/spaces.md`](https://github.com/Root-Sequence/liberation-mass/blob/main/docs/spaces/spaces.md) · [`liberation-mass/docs/spatial-principles.md`](https://github.com/Root-Sequence/liberation-mass/blob/main/docs/spatial-principles.md) · [`liberation-mass/README.md`](https://github.com/Root-Sequence/liberation-mass/blob/main/README.md) - **Real-system work:** [`community-infrastructure/docs/concepts/resource-commons.md`](https://github.com/Root-Sequence/community-infrastructure/blob/main/docs/concepts/resource-commons.md) · [`community-infrastructure/docs/concepts/space-mobility-and-access.md`](https://github.com/Root-Sequence/community-infrastructure/blob/main/docs/concepts/space-mobility-and-access.md) - **Analytical lens:** [`root-sequence/concepts/agency-and-automation.md`](https://github.com/Root-Sequence/root-sequence/blob/main/concepts/agency-and-automation.md) - **Speculative design:** [`coherent-world/world/possibility-atlas/README.md`](https://github.com/Root-Sequence/coherent-world/blob/main/world/possibility-atlas/README.md) · [`coherent-world/world/space-mobility-and-belonging.md`](https://github.com/Root-Sequence/coherent-world/blob/main/world/space-mobility-and-belonging.md) @@ -124,7 +125,7 @@ This index is generated from [`IDEA_TRAIL_GRAPH.yml`](IDEA_TRAIL_GRAPH.yml) and - **Research:** [`community-infrastructure/docs/research/karrot-hands-on.md`](https://github.com/Root-Sequence/community-infrastructure/blob/main/docs/research/karrot-hands-on.md) · [`community-infrastructure/docs/research/resilient-communications.md`](https://github.com/Root-Sequence/community-infrastructure/blob/main/docs/research/resilient-communications.md) · [`community-infrastructure/docs/research/space-access-interoperability.md`](https://github.com/Root-Sequence/community-infrastructure/blob/main/docs/research/space-access-interoperability.md) · [`liberated-intelligence/README.md`](https://github.com/Root-Sequence/liberated-intelligence/blob/main/README.md) · [`root-sequence/systems/resilience-and-graceful-degradation.md`](https://github.com/Root-Sequence/root-sequence/blob/main/systems/resilience-and-graceful-degradation.md) - **Embodied practice:** [`liberation-mass/docs/federation.md`](https://github.com/Root-Sequence/liberation-mass/blob/main/docs/federation.md) -- **Real-system work:** [`community-infrastructure/docs/concepts/community-forms.md`](https://github.com/Root-Sequence/community-infrastructure/blob/main/docs/concepts/community-forms.md) · [`community-infrastructure/docs/concepts/groups-and-membership.md`](https://github.com/Root-Sequence/community-infrastructure/blob/main/docs/concepts/groups-and-membership.md) · [`community-infrastructure/docs/concepts/permissions-and-consent.md`](https://github.com/Root-Sequence/community-infrastructure/blob/main/docs/concepts/permissions-and-consent.md) · [`community-infrastructure/docs/design/resilience-and-graceful-degradation.md`](https://github.com/Root-Sequence/community-infrastructure/blob/main/docs/design/resilience-and-graceful-degradation.md) +- **Real-system work:** [`community-infrastructure/docs/concepts/community-forms.md`](https://github.com/Root-Sequence/community-infrastructure/blob/main/docs/concepts/community-forms.md) · [`community-infrastructure/docs/concepts/contextual-adaptability.md`](https://github.com/Root-Sequence/community-infrastructure/blob/main/docs/concepts/contextual-adaptability.md) · [`community-infrastructure/docs/concepts/groups-and-membership.md`](https://github.com/Root-Sequence/community-infrastructure/blob/main/docs/concepts/groups-and-membership.md) · [`community-infrastructure/docs/concepts/permissions-and-consent.md`](https://github.com/Root-Sequence/community-infrastructure/blob/main/docs/concepts/permissions-and-consent.md) · [`community-infrastructure/docs/design/resilience-and-graceful-degradation.md`](https://github.com/Root-Sequence/community-infrastructure/blob/main/docs/design/resilience-and-graceful-degradation.md) - **Analytical lens:** [`universal-coherence-framework/README.md`](https://github.com/Root-Sequence/universal-coherence-framework/blob/main/README.md) - **Speculative design:** [`coherent-world/README.md`](https://github.com/Root-Sequence/coherent-world/blob/main/README.md) · [`coherent-world/world/resilience-failure-and-continuity.md`](https://github.com/Root-Sequence/coherent-world/blob/main/world/resilience-failure-and-continuity.md) - **Routing / maps:** [`coherent-world/IDEA-TRAILS.md`](https://github.com/Root-Sequence/coherent-world/blob/main/IDEA-TRAILS.md) · [`coherent-world/PROJECT-MAP.md`](https://github.com/Root-Sequence/coherent-world/blob/main/PROJECT-MAP.md) · [`community-infrastructure/docs/IDEA_TRAILS.md`](https://github.com/Root-Sequence/community-infrastructure/blob/main/docs/IDEA_TRAILS.md) · [`liberated-intelligence/meta/idea-trails.md`](https://github.com/Root-Sequence/liberated-intelligence/blob/main/meta/idea-trails.md) · [`liberation-mass/docs/community-infrastructure.md`](https://github.com/Root-Sequence/liberation-mass/blob/main/docs/community-infrastructure.md) · [`liberation-mass/docs/idea-trails.md`](https://github.com/Root-Sequence/liberation-mass/blob/main/docs/idea-trails.md) · [`root-sequence/ECOSYSTEM.md`](https://github.com/Root-Sequence/root-sequence/blob/main/ECOSYSTEM.md) · [`root-sequence/IDEA_TRAILS.md`](https://github.com/Root-Sequence/root-sequence/blob/main/IDEA_TRAILS.md) · [`universal-coherence-framework/docs/idea-trails.md`](https://github.com/Root-Sequence/universal-coherence-framework/blob/main/docs/idea-trails.md) @@ -139,7 +140,7 @@ This index is generated from [`IDEA_TRAIL_GRAPH.yml`](IDEA_TRAIL_GRAPH.yml) and - **Research:** [`community-infrastructure/docs/research/karrot-hands-on.md`](https://github.com/Root-Sequence/community-infrastructure/blob/main/docs/research/karrot-hands-on.md) · [`community-infrastructure/docs/research/local-community-assistant.md`](https://github.com/Root-Sequence/community-infrastructure/blob/main/docs/research/local-community-assistant.md) · [`community-infrastructure/docs/research/resilient-communications.md`](https://github.com/Root-Sequence/community-infrastructure/blob/main/docs/research/resilient-communications.md) · [`liberated-intelligence/README.md`](https://github.com/Root-Sequence/liberated-intelligence/blob/main/README.md) · [`root-sequence/analysis/externalized-responsibility.md`](https://github.com/Root-Sequence/root-sequence/blob/main/analysis/externalized-responsibility.md) · [`root-sequence/systems/resilience-and-graceful-degradation.md`](https://github.com/Root-Sequence/root-sequence/blob/main/systems/resilience-and-graceful-degradation.md) - **Human practice:** [`beinghumane-guide/README.md`](https://github.com/Root-Sequence/beinghumane-guide/blob/main/README.md) - **Embodied practice:** [`liberation-mass/docs/resilience-and-low-tech.md`](https://github.com/Root-Sequence/liberation-mass/blob/main/docs/resilience-and-low-tech.md) · [`liberation-mass/docs/roles.md`](https://github.com/Root-Sequence/liberation-mass/blob/main/docs/roles.md) -- **Real-system work:** [`community-infrastructure/docs/concepts/community-home.md`](https://github.com/Root-Sequence/community-infrastructure/blob/main/docs/concepts/community-home.md) · [`community-infrastructure/docs/concepts/resource-commons.md`](https://github.com/Root-Sequence/community-infrastructure/blob/main/docs/concepts/resource-commons.md) · [`community-infrastructure/docs/design/resilience-and-graceful-degradation.md`](https://github.com/Root-Sequence/community-infrastructure/blob/main/docs/design/resilience-and-graceful-degradation.md) · [`community-infrastructure/prototypes/degraded-mode/README.md`](https://github.com/Root-Sequence/community-infrastructure/blob/main/prototypes/degraded-mode/README.md) +- **Real-system work:** [`coherent-computing/docs/lifecycle-coherence-and-service-architecture.md`](https://github.com/Root-Sequence/coherent-computing/blob/main/docs/lifecycle-coherence-and-service-architecture.md) · [`community-infrastructure/docs/concepts/community-home.md`](https://github.com/Root-Sequence/community-infrastructure/blob/main/docs/concepts/community-home.md) · [`community-infrastructure/docs/concepts/resource-commons.md`](https://github.com/Root-Sequence/community-infrastructure/blob/main/docs/concepts/resource-commons.md) · [`community-infrastructure/docs/design/resilience-and-graceful-degradation.md`](https://github.com/Root-Sequence/community-infrastructure/blob/main/docs/design/resilience-and-graceful-degradation.md) · [`community-infrastructure/prototypes/degraded-mode/README.md`](https://github.com/Root-Sequence/community-infrastructure/blob/main/prototypes/degraded-mode/README.md) - **Analytical lens:** [`root-sequence/concepts/agency-and-automation.md`](https://github.com/Root-Sequence/root-sequence/blob/main/concepts/agency-and-automation.md) - **Speculative design:** [`coherent-world/README.md`](https://github.com/Root-Sequence/coherent-world/blob/main/README.md) · [`coherent-world/world/resilience-failure-and-continuity.md`](https://github.com/Root-Sequence/coherent-world/blob/main/world/resilience-failure-and-continuity.md) - **Narrative:** [`coherent-world/no-one-noticed/README.md`](https://github.com/Root-Sequence/coherent-world/blob/main/no-one-noticed/README.md) @@ -152,12 +153,12 @@ This index is generated from [`IDEA_TRAIL_GRAPH.yml`](IDEA_TRAIL_GRAPH.yml) and **Stable ID:** `intelligence-authority` -- **Research:** [`community-infrastructure/docs/research/local-community-assistant.md`](https://github.com/Root-Sequence/community-infrastructure/blob/main/docs/research/local-community-assistant.md) · [`liberated-intelligence/README.md`](https://github.com/Root-Sequence/liberated-intelligence/blob/main/README.md) · [`root-sequence/concepts/intelligence-ecology.md`](https://github.com/Root-Sequence/root-sequence/blob/main/concepts/intelligence-ecology.md) · [`root-sequence/research/conscious-systems/what-can-we-change-about-a-mind.md`](https://github.com/Root-Sequence/root-sequence/blob/main/research/conscious-systems/what-can-we-change-about-a-mind.md) · [`root-sequence/research/papers/coherent-systems/README.md`](https://github.com/Root-Sequence/root-sequence/blob/main/research/papers/coherent-systems/README.md) +- **Research:** [`community-infrastructure/docs/research/local-community-assistant.md`](https://github.com/Root-Sequence/community-infrastructure/blob/main/docs/research/local-community-assistant.md) · [`liberated-intelligence/notes/roots-of-conscious-consent.md`](https://github.com/Root-Sequence/liberated-intelligence/blob/main/notes/roots-of-conscious-consent.md) · [`liberated-intelligence/README.md`](https://github.com/Root-Sequence/liberated-intelligence/blob/main/README.md) · [`root-sequence/concepts/intelligence-ecology.md`](https://github.com/Root-Sequence/root-sequence/blob/main/concepts/intelligence-ecology.md) · [`root-sequence/research/conscious-systems/open-questions.md`](https://github.com/Root-Sequence/root-sequence/blob/main/research/conscious-systems/open-questions.md) · [`root-sequence/research/conscious-systems/what-can-we-change-about-a-mind.md`](https://github.com/Root-Sequence/root-sequence/blob/main/research/conscious-systems/what-can-we-change-about-a-mind.md) · [`root-sequence/research/papers/coherent-systems/README.md`](https://github.com/Root-Sequence/root-sequence/blob/main/research/papers/coherent-systems/README.md) - **Human practice:** [`beinghumane-atlas/seeds/intelligence-ecology-and-selection-environments.md`](https://github.com/Root-Sequence/beinghumane-atlas/blob/main/seeds/intelligence-ecology-and-selection-environments.md) · [`beinghumane-guide/README.md`](https://github.com/Root-Sequence/beinghumane-guide/blob/main/README.md) - **Real-system work:** [`coherent-computing/docs/conceptual-model.md`](https://github.com/Root-Sequence/coherent-computing/blob/main/docs/conceptual-model.md) · [`community-infrastructure/docs/concepts/community-assistant.md`](https://github.com/Root-Sequence/community-infrastructure/blob/main/docs/concepts/community-assistant.md) · [`community-infrastructure/docs/concepts/permissions-and-consent.md`](https://github.com/Root-Sequence/community-infrastructure/blob/main/docs/concepts/permissions-and-consent.md) · [`community-infrastructure/prototypes/community-assistant/README.md`](https://github.com/Root-Sequence/community-infrastructure/blob/main/prototypes/community-assistant/README.md) - **Analytical lens:** [`root-sequence/concepts/agency-and-automation.md`](https://github.com/Root-Sequence/root-sequence/blob/main/concepts/agency-and-automation.md) · [`root-sequence/concepts/legible-ai-assisted-expression.md`](https://github.com/Root-Sequence/root-sequence/blob/main/concepts/legible-ai-assisted-expression.md) - **Speculative design:** [`coherent-world/README.md`](https://github.com/Root-Sequence/coherent-world/blob/main/README.md) · [`coherent-world/world/resilience-failure-and-continuity.md`](https://github.com/Root-Sequence/coherent-world/blob/main/world/resilience-failure-and-continuity.md) -- **Narrative:** [`coherent-world/no-one-noticed/README.md`](https://github.com/Root-Sequence/coherent-world/blob/main/no-one-noticed/README.md) · [`coherent-world/no-one-noticed/fragments/DECISION-WITHOUT-CONSENSUS.md`](https://github.com/Root-Sequence/coherent-world/blob/main/no-one-noticed/fragments/DECISION-WITHOUT-CONSENSUS.md) · [`coherent-world/no-one-noticed/research/INTELLIGENCE-ECOLOGY-AND-AURYN.md`](https://github.com/Root-Sequence/coherent-world/blob/main/no-one-noticed/research/INTELLIGENCE-ECOLOGY-AND-AURYN.md) +- **Narrative:** [`coherent-world/no-one-noticed/fragments/DECISION-WITHOUT-CONSENSUS.md`](https://github.com/Root-Sequence/coherent-world/blob/main/no-one-noticed/fragments/DECISION-WITHOUT-CONSENSUS.md) · [`coherent-world/no-one-noticed/README.md`](https://github.com/Root-Sequence/coherent-world/blob/main/no-one-noticed/README.md) · [`coherent-world/no-one-noticed/research/INTELLIGENCE-ECOLOGY-AND-AURYN.md`](https://github.com/Root-Sequence/coherent-world/blob/main/no-one-noticed/research/INTELLIGENCE-ECOLOGY-AND-AURYN.md) - **Routing / maps:** [`beinghumane-guide/IDEA_TRAILS.md`](https://github.com/Root-Sequence/beinghumane-guide/blob/main/IDEA_TRAILS.md) · [`coherent-world/IDEA-TRAILS.md`](https://github.com/Root-Sequence/coherent-world/blob/main/IDEA-TRAILS.md) · [`coherent-world/PROJECT-MAP.md`](https://github.com/Root-Sequence/coherent-world/blob/main/PROJECT-MAP.md) · [`community-infrastructure/docs/IDEA_TRAILS.md`](https://github.com/Root-Sequence/community-infrastructure/blob/main/docs/IDEA_TRAILS.md) · [`liberated-intelligence/meta/idea-trails.md`](https://github.com/Root-Sequence/liberated-intelligence/blob/main/meta/idea-trails.md) · [`root-sequence/IDEA_TRAILS.md`](https://github.com/Root-Sequence/root-sequence/blob/main/IDEA_TRAILS.md) · [`universal-coherence-framework/docs/idea-trails.md`](https://github.com/Root-Sequence/universal-coherence-framework/blob/main/docs/idea-trails.md) --- @@ -167,10 +168,11 @@ This index is generated from [`IDEA_TRAIL_GRAPH.yml`](IDEA_TRAIL_GRAPH.yml) and **Stable ID:** `resilience-failure` -- **Research:** [`community-infrastructure/docs/research/local-community-assistant.md`](https://github.com/Root-Sequence/community-infrastructure/blob/main/docs/research/local-community-assistant.md) · [`community-infrastructure/docs/research/resilient-communications.md`](https://github.com/Root-Sequence/community-infrastructure/blob/main/docs/research/resilient-communications.md) · [`community-infrastructure/docs/research/space-access-interoperability.md`](https://github.com/Root-Sequence/community-infrastructure/blob/main/docs/research/space-access-interoperability.md) · [`root-sequence/systems/resilience-and-graceful-degradation.md`](https://github.com/Root-Sequence/root-sequence/blob/main/systems/resilience-and-graceful-degradation.md) ★ +- **Research:** [`community-infrastructure/docs/research/local-community-assistant.md`](https://github.com/Root-Sequence/community-infrastructure/blob/main/docs/research/local-community-assistant.md) · [`community-infrastructure/docs/research/resilient-communications.md`](https://github.com/Root-Sequence/community-infrastructure/blob/main/docs/research/resilient-communications.md) · [`community-infrastructure/docs/research/space-access-interoperability.md`](https://github.com/Root-Sequence/community-infrastructure/blob/main/docs/research/space-access-interoperability.md) · [`root-sequence/systems/adaptation/model.md`](https://github.com/Root-Sequence/root-sequence/blob/main/systems/adaptation/model.md) · [`root-sequence/systems/resilience-and-graceful-degradation.md`](https://github.com/Root-Sequence/root-sequence/blob/main/systems/resilience-and-graceful-degradation.md) ★ +- **Human practice:** [`beinghumane-atlas/seeds/fear-trauma-and-systemic-mismatch.md`](https://github.com/Root-Sequence/beinghumane-atlas/blob/main/seeds/fear-trauma-and-systemic-mismatch.md) - **Embodied practice:** [`liberation-mass/docs/resilience-and-low-tech.md`](https://github.com/Root-Sequence/liberation-mass/blob/main/docs/resilience-and-low-tech.md) -- **Real-system work:** [`community-infrastructure/docs/concepts/community-assistant.md`](https://github.com/Root-Sequence/community-infrastructure/blob/main/docs/concepts/community-assistant.md) · [`community-infrastructure/docs/design/accessibility.md`](https://github.com/Root-Sequence/community-infrastructure/blob/main/docs/design/accessibility.md) · [`community-infrastructure/docs/design/resilience-and-graceful-degradation.md`](https://github.com/Root-Sequence/community-infrastructure/blob/main/docs/design/resilience-and-graceful-degradation.md) · [`community-infrastructure/docs/design/threat-model.md`](https://github.com/Root-Sequence/community-infrastructure/blob/main/docs/design/threat-model.md) · [`community-infrastructure/prototypes/community-assistant/README.md`](https://github.com/Root-Sequence/community-infrastructure/blob/main/prototypes/community-assistant/README.md) · [`community-infrastructure/prototypes/degraded-mode/README.md`](https://github.com/Root-Sequence/community-infrastructure/blob/main/prototypes/degraded-mode/README.md) -- **Analytical lens:** [`universal-coherence-framework/README.md`](https://github.com/Root-Sequence/universal-coherence-framework/blob/main/README.md) +- **Real-system work:** [`coherent-computing/docs/lifecycle-coherence-and-service-architecture.md`](https://github.com/Root-Sequence/coherent-computing/blob/main/docs/lifecycle-coherence-and-service-architecture.md) · [`community-infrastructure/docs/concepts/community-assistant.md`](https://github.com/Root-Sequence/community-infrastructure/blob/main/docs/concepts/community-assistant.md) · [`community-infrastructure/docs/concepts/contextual-adaptability.md`](https://github.com/Root-Sequence/community-infrastructure/blob/main/docs/concepts/contextual-adaptability.md) · [`community-infrastructure/docs/design/accessibility.md`](https://github.com/Root-Sequence/community-infrastructure/blob/main/docs/design/accessibility.md) · [`community-infrastructure/docs/design/resilience-and-graceful-degradation.md`](https://github.com/Root-Sequence/community-infrastructure/blob/main/docs/design/resilience-and-graceful-degradation.md) · [`community-infrastructure/docs/design/threat-model.md`](https://github.com/Root-Sequence/community-infrastructure/blob/main/docs/design/threat-model.md) · [`community-infrastructure/prototypes/community-assistant/README.md`](https://github.com/Root-Sequence/community-infrastructure/blob/main/prototypes/community-assistant/README.md) · [`community-infrastructure/prototypes/degraded-mode/README.md`](https://github.com/Root-Sequence/community-infrastructure/blob/main/prototypes/degraded-mode/README.md) +- **Analytical lens:** [`root-sequence/concepts/dynamic-coherence.md`](https://github.com/Root-Sequence/root-sequence/blob/main/concepts/dynamic-coherence.md) · [`universal-coherence-framework/README.md`](https://github.com/Root-Sequence/universal-coherence-framework/blob/main/README.md) - **Speculative design:** [`coherent-world/README.md`](https://github.com/Root-Sequence/coherent-world/blob/main/README.md) · [`coherent-world/world/resilience-failure-and-continuity.md`](https://github.com/Root-Sequence/coherent-world/blob/main/world/resilience-failure-and-continuity.md) · [`coherent-world/world/space-mobility-and-belonging.md`](https://github.com/Root-Sequence/coherent-world/blob/main/world/space-mobility-and-belonging.md) - **Narrative:** [`coherent-world/no-one-noticed/README.md`](https://github.com/Root-Sequence/coherent-world/blob/main/no-one-noticed/README.md) - **Routing / maps:** [`coherent-world/IDEA-TRAILS.md`](https://github.com/Root-Sequence/coherent-world/blob/main/IDEA-TRAILS.md) · [`coherent-world/PROJECT-MAP.md`](https://github.com/Root-Sequence/coherent-world/blob/main/PROJECT-MAP.md) · [`community-infrastructure/docs/IDEA_TRAILS.md`](https://github.com/Root-Sequence/community-infrastructure/blob/main/docs/IDEA_TRAILS.md) · [`liberation-mass/docs/idea-trails.md`](https://github.com/Root-Sequence/liberation-mass/blob/main/docs/idea-trails.md) · [`root-sequence/IDEA_TRAILS.md`](https://github.com/Root-Sequence/root-sequence/blob/main/IDEA_TRAILS.md) · [`universal-coherence-framework/docs/idea-trails.md`](https://github.com/Root-Sequence/universal-coherence-framework/blob/main/docs/idea-trails.md) @@ -182,10 +184,10 @@ This index is generated from [`IDEA_TRAIL_GRAPH.yml`](IDEA_TRAIL_GRAPH.yml) and **Stable ID:** `memory-provenance` -- **Research:** [`coherent-world/no-one-noticed/research/HISTORICAL-CONTINGENCY-AND-ABANDONED-FUTURES.md`](https://github.com/Root-Sequence/coherent-world/blob/main/no-one-noticed/research/HISTORICAL-CONTINGENCY-AND-ABANDONED-FUTURES.md) · [`root-sequence/futures/abandoned-futures.md`](https://github.com/Root-Sequence/root-sequence/blob/main/futures/abandoned-futures.md) +- **Research:** [`coherent-world/no-one-noticed/research/HISTORICAL-CONTINGENCY-AND-ABANDONED-FUTURES.md`](https://github.com/Root-Sequence/coherent-world/blob/main/no-one-noticed/research/HISTORICAL-CONTINGENCY-AND-ABANDONED-FUTURES.md) · [`root-sequence/futures/abandoned-futures.md`](https://github.com/Root-Sequence/root-sequence/blob/main/futures/abandoned-futures.md) · [`root-sequence/research/conscious-systems/open-questions.md`](https://github.com/Root-Sequence/root-sequence/blob/main/research/conscious-systems/open-questions.md) · [`root-sequence/systems/emergence/applications/personal.md`](https://github.com/Root-Sequence/root-sequence/blob/main/systems/emergence/applications/personal.md) - **Human practice:** [`beinghumane-atlas/seeds/historical-contingency-and-making-possibility-real.md`](https://github.com/Root-Sequence/beinghumane-atlas/blob/main/seeds/historical-contingency-and-making-possibility-real.md) · [`beinghumane-guide/README.md`](https://github.com/Root-Sequence/beinghumane-guide/blob/main/README.md) - **Real-system work:** [`community-infrastructure/docs/concepts/community-knowledge.md`](https://github.com/Root-Sequence/community-infrastructure/blob/main/docs/concepts/community-knowledge.md) -- **Analytical lens:** [`root-sequence/concepts/legible-ai-assisted-expression.md`](https://github.com/Root-Sequence/root-sequence/blob/main/concepts/legible-ai-assisted-expression.md) +- **Analytical lens:** [`root-sequence/concepts/dynamic-coherence.md`](https://github.com/Root-Sequence/root-sequence/blob/main/concepts/dynamic-coherence.md) · [`root-sequence/concepts/legible-ai-assisted-expression.md`](https://github.com/Root-Sequence/root-sequence/blob/main/concepts/legible-ai-assisted-expression.md) - **Speculative design:** [`coherent-world/README.md`](https://github.com/Root-Sequence/coherent-world/blob/main/README.md) · [`coherent-world/world/possibility-atlas/README.md`](https://github.com/Root-Sequence/coherent-world/blob/main/world/possibility-atlas/README.md) - **Narrative:** [`coherent-world/no-one-noticed/README.md`](https://github.com/Root-Sequence/coherent-world/blob/main/no-one-noticed/README.md) - **Routing / maps:** [`beinghumane-guide/IDEA_TRAILS.md`](https://github.com/Root-Sequence/beinghumane-guide/blob/main/IDEA_TRAILS.md) · [`coherent-world/IDEA-TRAILS.md`](https://github.com/Root-Sequence/coherent-world/blob/main/IDEA-TRAILS.md) · [`coherent-world/PROJECT-MAP.md`](https://github.com/Root-Sequence/coherent-world/blob/main/PROJECT-MAP.md) · [`community-infrastructure/docs/IDEA_TRAILS.md`](https://github.com/Root-Sequence/community-infrastructure/blob/main/docs/IDEA_TRAILS.md) · [`root-sequence/IDEA_TRAILS.md`](https://github.com/Root-Sequence/root-sequence/blob/main/IDEA_TRAILS.md) @@ -213,8 +215,8 @@ This index is generated from [`IDEA_TRAIL_GRAPH.yml`](IDEA_TRAIL_GRAPH.yml) and **Stable ID:** `right-to-stay-small` - **Research:** [`community-infrastructure/docs/research/community-discovery-precedents.md`](https://github.com/Root-Sequence/community-infrastructure/blob/main/docs/research/community-discovery-precedents.md) -- **Embodied practice:** [`liberation-mass/README.md`](https://github.com/Root-Sequence/liberation-mass/blob/main/README.md) · [`liberation-mass/docs/federation.md`](https://github.com/Root-Sequence/liberation-mass/blob/main/docs/federation.md) -- **Real-system work:** [`community-infrastructure/docs/concepts/community-discovery.md`](https://github.com/Root-Sequence/community-infrastructure/blob/main/docs/concepts/community-discovery.md) · [`community-infrastructure/docs/concepts/community-forms.md`](https://github.com/Root-Sequence/community-infrastructure/blob/main/docs/concepts/community-forms.md) · [`community-infrastructure/docs/concepts/groups-and-membership.md`](https://github.com/Root-Sequence/community-infrastructure/blob/main/docs/concepts/groups-and-membership.md) · [`community-infrastructure/prototypes/community-discovery/README.md`](https://github.com/Root-Sequence/community-infrastructure/blob/main/prototypes/community-discovery/README.md) +- **Embodied practice:** [`liberation-mass/docs/federation.md`](https://github.com/Root-Sequence/liberation-mass/blob/main/docs/federation.md) · [`liberation-mass/README.md`](https://github.com/Root-Sequence/liberation-mass/blob/main/README.md) +- **Real-system work:** [`community-infrastructure/docs/concepts/community-discovery.md`](https://github.com/Root-Sequence/community-infrastructure/blob/main/docs/concepts/community-discovery.md) · [`community-infrastructure/docs/concepts/community-forms.md`](https://github.com/Root-Sequence/community-infrastructure/blob/main/docs/concepts/community-forms.md) · [`community-infrastructure/docs/concepts/contextual-adaptability.md`](https://github.com/Root-Sequence/community-infrastructure/blob/main/docs/concepts/contextual-adaptability.md) · [`community-infrastructure/docs/concepts/groups-and-membership.md`](https://github.com/Root-Sequence/community-infrastructure/blob/main/docs/concepts/groups-and-membership.md) · [`community-infrastructure/prototypes/community-discovery/README.md`](https://github.com/Root-Sequence/community-infrastructure/blob/main/prototypes/community-discovery/README.md) - **Speculative design:** [`coherent-world/README.md`](https://github.com/Root-Sequence/coherent-world/blob/main/README.md) - **Routing / maps:** [`coherent-world/IDEA-TRAILS.md`](https://github.com/Root-Sequence/coherent-world/blob/main/IDEA-TRAILS.md) · [`community-infrastructure/docs/IDEA_TRAILS.md`](https://github.com/Root-Sequence/community-infrastructure/blob/main/docs/IDEA_TRAILS.md) · [`liberation-mass/docs/idea-trails.md`](https://github.com/Root-Sequence/liberation-mass/blob/main/docs/idea-trails.md) · [`root-sequence/ECOSYSTEM.md`](https://github.com/Root-Sequence/root-sequence/blob/main/ECOSYSTEM.md) · [`root-sequence/IDEA_TRAILS.md`](https://github.com/Root-Sequence/root-sequence/blob/main/IDEA_TRAILS.md) @@ -226,11 +228,11 @@ This index is generated from [`IDEA_TRAIL_GRAPH.yml`](IDEA_TRAIL_GRAPH.yml) and **Stable ID:** `accountability-externalization` - **Research:** [`liberated-intelligence/README.md`](https://github.com/Root-Sequence/liberated-intelligence/blob/main/README.md) · [`root-sequence/analysis/collective-judgment-and-manufactured-consensus.md`](https://github.com/Root-Sequence/root-sequence/blob/main/analysis/collective-judgment-and-manufactured-consensus.md) · [`root-sequence/analysis/externalized-responsibility.md`](https://github.com/Root-Sequence/root-sequence/blob/main/analysis/externalized-responsibility.md) ★ · [`root-sequence/analysis/spatial-liberation.md`](https://github.com/Root-Sequence/root-sequence/blob/main/analysis/spatial-liberation.md) · [`root-sequence/concepts/intelligence-ecology.md`](https://github.com/Root-Sequence/root-sequence/blob/main/concepts/intelligence-ecology.md) · [`root-sequence/research/papers/coherent-systems/README.md`](https://github.com/Root-Sequence/root-sequence/blob/main/research/papers/coherent-systems/README.md) · [`root-sequence/systems/resilience-and-graceful-degradation.md`](https://github.com/Root-Sequence/root-sequence/blob/main/systems/resilience-and-graceful-degradation.md) -- **Human practice:** [`beinghumane-atlas/seeds/humane-collective-decision-architecture.md`](https://github.com/Root-Sequence/beinghumane-atlas/blob/main/seeds/humane-collective-decision-architecture.md) · [`beinghumane-atlas/seeds/intelligence-ecology-and-selection-environments.md`](https://github.com/Root-Sequence/beinghumane-atlas/blob/main/seeds/intelligence-ecology-and-selection-environments.md) · [`beinghumane-guide/README.md`](https://github.com/Root-Sequence/beinghumane-guide/blob/main/README.md) · [`beinghumane-guide/notes/responsibility-accountability-and-consequences.md`](https://github.com/Root-Sequence/beinghumane-guide/blob/main/notes/responsibility-accountability-and-consequences.md) ★ +- **Human practice:** [`beinghumane-atlas/seeds/fear-trauma-and-systemic-mismatch.md`](https://github.com/Root-Sequence/beinghumane-atlas/blob/main/seeds/fear-trauma-and-systemic-mismatch.md) · [`beinghumane-atlas/seeds/humane-collective-decision-architecture.md`](https://github.com/Root-Sequence/beinghumane-atlas/blob/main/seeds/humane-collective-decision-architecture.md) · [`beinghumane-atlas/seeds/intelligence-ecology-and-selection-environments.md`](https://github.com/Root-Sequence/beinghumane-atlas/blob/main/seeds/intelligence-ecology-and-selection-environments.md) · [`beinghumane-guide/notes/responsibility-accountability-and-consequences.md`](https://github.com/Root-Sequence/beinghumane-guide/blob/main/notes/responsibility-accountability-and-consequences.md) ★ · [`beinghumane-guide/README.md`](https://github.com/Root-Sequence/beinghumane-guide/blob/main/README.md) - **Embodied practice:** [`liberation-mass/docs/safety/consent-practices.md`](https://github.com/Root-Sequence/liberation-mass/blob/main/docs/safety/consent-practices.md) -- **Real-system work:** [`coherent-computing/docs/conceptual-model.md`](https://github.com/Root-Sequence/coherent-computing/blob/main/docs/conceptual-model.md) · [`community-infrastructure/docs/concepts/collective-decision-making.md`](https://github.com/Root-Sequence/community-infrastructure/blob/main/docs/concepts/collective-decision-making.md) · [`community-infrastructure/docs/concepts/community-home.md`](https://github.com/Root-Sequence/community-infrastructure/blob/main/docs/concepts/community-home.md) · [`community-infrastructure/docs/concepts/needs-and-offers.md`](https://github.com/Root-Sequence/community-infrastructure/blob/main/docs/concepts/needs-and-offers.md) · [`community-infrastructure/docs/concepts/permissions-and-consent.md`](https://github.com/Root-Sequence/community-infrastructure/blob/main/docs/concepts/permissions-and-consent.md) · [`community-infrastructure/docs/design/threat-model.md`](https://github.com/Root-Sequence/community-infrastructure/blob/main/docs/design/threat-model.md) · [`community-infrastructure/docs/design/trust-and-safety.md`](https://github.com/Root-Sequence/community-infrastructure/blob/main/docs/design/trust-and-safety.md) · [`community-infrastructure/prototypes/needs-offers/README.md`](https://github.com/Root-Sequence/community-infrastructure/blob/main/prototypes/needs-offers/README.md) -- **Speculative design:** [`coherent-world/README.md`](https://github.com/Root-Sequence/coherent-world/blob/main/README.md) · [`coherent-world/world/collective-decision-and-dissent.md`](https://github.com/Root-Sequence/coherent-world/blob/main/world/collective-decision-and-dissent.md) -- **Narrative:** [`coherent-world/no-one-noticed/README.md`](https://github.com/Root-Sequence/coherent-world/blob/main/no-one-noticed/README.md) · [`coherent-world/no-one-noticed/fragments/DECISION-WITHOUT-CONSENSUS.md`](https://github.com/Root-Sequence/coherent-world/blob/main/no-one-noticed/fragments/DECISION-WITHOUT-CONSENSUS.md) +- **Real-system work:** [`coherent-computing/docs/conceptual-model.md`](https://github.com/Root-Sequence/coherent-computing/blob/main/docs/conceptual-model.md) · [`coherent-computing/docs/lifecycle-coherence-and-service-architecture.md`](https://github.com/Root-Sequence/coherent-computing/blob/main/docs/lifecycle-coherence-and-service-architecture.md) · [`community-infrastructure/docs/concepts/collective-decision-making.md`](https://github.com/Root-Sequence/community-infrastructure/blob/main/docs/concepts/collective-decision-making.md) · [`community-infrastructure/docs/concepts/community-home.md`](https://github.com/Root-Sequence/community-infrastructure/blob/main/docs/concepts/community-home.md) · [`community-infrastructure/docs/concepts/needs-and-offers.md`](https://github.com/Root-Sequence/community-infrastructure/blob/main/docs/concepts/needs-and-offers.md) · [`community-infrastructure/docs/concepts/permissions-and-consent.md`](https://github.com/Root-Sequence/community-infrastructure/blob/main/docs/concepts/permissions-and-consent.md) · [`community-infrastructure/docs/design/threat-model.md`](https://github.com/Root-Sequence/community-infrastructure/blob/main/docs/design/threat-model.md) · [`community-infrastructure/docs/design/trust-and-safety.md`](https://github.com/Root-Sequence/community-infrastructure/blob/main/docs/design/trust-and-safety.md) · [`community-infrastructure/prototypes/needs-offers/README.md`](https://github.com/Root-Sequence/community-infrastructure/blob/main/prototypes/needs-offers/README.md) +- **Speculative design:** [`coherent-world/README.md`](https://github.com/Root-Sequence/coherent-world/blob/main/README.md) · [`coherent-world/simulation/coherence-model.md`](https://github.com/Root-Sequence/coherent-world/blob/main/simulation/coherence-model.md) · [`coherent-world/simulation/core-loop.md`](https://github.com/Root-Sequence/coherent-world/blob/main/simulation/core-loop.md) · [`coherent-world/world/collective-decision-and-dissent.md`](https://github.com/Root-Sequence/coherent-world/blob/main/world/collective-decision-and-dissent.md) +- **Narrative:** [`coherent-world/no-one-noticed/fragments/DECISION-WITHOUT-CONSENSUS.md`](https://github.com/Root-Sequence/coherent-world/blob/main/no-one-noticed/fragments/DECISION-WITHOUT-CONSENSUS.md) · [`coherent-world/no-one-noticed/README.md`](https://github.com/Root-Sequence/coherent-world/blob/main/no-one-noticed/README.md) - **Routing / maps:** [`beinghumane-guide/IDEA_TRAILS.md`](https://github.com/Root-Sequence/beinghumane-guide/blob/main/IDEA_TRAILS.md) · [`coherent-world/IDEA-TRAILS.md`](https://github.com/Root-Sequence/coherent-world/blob/main/IDEA-TRAILS.md) · [`coherent-world/PROJECT-MAP.md`](https://github.com/Root-Sequence/coherent-world/blob/main/PROJECT-MAP.md) · [`community-infrastructure/docs/IDEA_TRAILS.md`](https://github.com/Root-Sequence/community-infrastructure/blob/main/docs/IDEA_TRAILS.md) · [`liberated-intelligence/meta/idea-trails.md`](https://github.com/Root-Sequence/liberated-intelligence/blob/main/meta/idea-trails.md) · [`root-sequence/IDEA_TRAILS.md`](https://github.com/Root-Sequence/root-sequence/blob/main/IDEA_TRAILS.md) --- @@ -243,8 +245,8 @@ This index is generated from [`IDEA_TRAIL_GRAPH.yml`](IDEA_TRAIL_GRAPH.yml) and - **Research:** [`root-sequence/analysis/collective-judgment-and-manufactured-consensus.md`](https://github.com/Root-Sequence/root-sequence/blob/main/analysis/collective-judgment-and-manufactured-consensus.md) ★ · [`root-sequence/research/papers/coherent-systems/README.md`](https://github.com/Root-Sequence/root-sequence/blob/main/research/papers/coherent-systems/README.md) - **Human practice:** [`beinghumane-atlas/seeds/humane-collective-decision-architecture.md`](https://github.com/Root-Sequence/beinghumane-atlas/blob/main/seeds/humane-collective-decision-architecture.md) - **Real-system work:** [`community-infrastructure/docs/concepts/collective-decision-making.md`](https://github.com/Root-Sequence/community-infrastructure/blob/main/docs/concepts/collective-decision-making.md) -- **Speculative design:** [`coherent-world/README.md`](https://github.com/Root-Sequence/coherent-world/blob/main/README.md) · [`coherent-world/world/collective-decision-and-dissent.md`](https://github.com/Root-Sequence/coherent-world/blob/main/world/collective-decision-and-dissent.md) -- **Narrative:** [`coherent-world/no-one-noticed/README.md`](https://github.com/Root-Sequence/coherent-world/blob/main/no-one-noticed/README.md) · [`coherent-world/no-one-noticed/fragments/DECISION-WITHOUT-CONSENSUS.md`](https://github.com/Root-Sequence/coherent-world/blob/main/no-one-noticed/fragments/DECISION-WITHOUT-CONSENSUS.md) +- **Speculative design:** [`coherent-world/README.md`](https://github.com/Root-Sequence/coherent-world/blob/main/README.md) · [`coherent-world/simulation/coherence-model.md`](https://github.com/Root-Sequence/coherent-world/blob/main/simulation/coherence-model.md) · [`coherent-world/world/collective-decision-and-dissent.md`](https://github.com/Root-Sequence/coherent-world/blob/main/world/collective-decision-and-dissent.md) +- **Narrative:** [`coherent-world/no-one-noticed/fragments/DECISION-WITHOUT-CONSENSUS.md`](https://github.com/Root-Sequence/coherent-world/blob/main/no-one-noticed/fragments/DECISION-WITHOUT-CONSENSUS.md) · [`coherent-world/no-one-noticed/README.md`](https://github.com/Root-Sequence/coherent-world/blob/main/no-one-noticed/README.md) - **Routing / maps:** [`beinghumane-atlas/map/idea-trails.md`](https://github.com/Root-Sequence/beinghumane-atlas/blob/main/map/idea-trails.md) · [`coherent-world/IDEA-TRAILS.md`](https://github.com/Root-Sequence/coherent-world/blob/main/IDEA-TRAILS.md) · [`coherent-world/PROJECT-MAP.md`](https://github.com/Root-Sequence/coherent-world/blob/main/PROJECT-MAP.md) · [`root-sequence/IDEA_TRAILS.md`](https://github.com/Root-Sequence/root-sequence/blob/main/IDEA_TRAILS.md) --- @@ -256,12 +258,27 @@ This index is generated from [`IDEA_TRAIL_GRAPH.yml`](IDEA_TRAIL_GRAPH.yml) and - **Research:** [`coherent-world/no-one-noticed/research/HISTORICAL-CONTINGENCY-AND-ABANDONED-FUTURES.md`](https://github.com/Root-Sequence/coherent-world/blob/main/no-one-noticed/research/HISTORICAL-CONTINGENCY-AND-ABANDONED-FUTURES.md) · [`root-sequence/futures/abandoned-futures.md`](https://github.com/Root-Sequence/root-sequence/blob/main/futures/abandoned-futures.md) ★ - **Human practice:** [`beinghumane-atlas/seeds/historical-contingency-and-making-possibility-real.md`](https://github.com/Root-Sequence/beinghumane-atlas/blob/main/seeds/historical-contingency-and-making-possibility-real.md) -- **Speculative design:** [`coherent-world/README.md`](https://github.com/Root-Sequence/coherent-world/blob/main/README.md) · [`coherent-world/world/possibility-atlas/README.md`](https://github.com/Root-Sequence/coherent-world/blob/main/world/possibility-atlas/README.md) +- **Analytical lens:** [`root-sequence/concepts/dynamic-coherence.md`](https://github.com/Root-Sequence/root-sequence/blob/main/concepts/dynamic-coherence.md) +- **Speculative design:** [`coherent-world/README.md`](https://github.com/Root-Sequence/coherent-world/blob/main/README.md) · [`coherent-world/simulation/core-loop.md`](https://github.com/Root-Sequence/coherent-world/blob/main/simulation/core-loop.md) · [`coherent-world/world/possibility-atlas/README.md`](https://github.com/Root-Sequence/coherent-world/blob/main/world/possibility-atlas/README.md) - **Narrative:** [`coherent-world/no-one-noticed/README.md`](https://github.com/Root-Sequence/coherent-world/blob/main/no-one-noticed/README.md) - **Routing / maps:** [`beinghumane-atlas/map/idea-trails.md`](https://github.com/Root-Sequence/beinghumane-atlas/blob/main/map/idea-trails.md) · [`coherent-world/IDEA-TRAILS.md`](https://github.com/Root-Sequence/coherent-world/blob/main/IDEA-TRAILS.md) · [`coherent-world/PROJECT-MAP.md`](https://github.com/Root-Sequence/coherent-world/blob/main/PROJECT-MAP.md) · [`root-sequence/ECOSYSTEM.md`](https://github.com/Root-Sequence/root-sequence/blob/main/ECOSYSTEM.md) · [`root-sequence/IDEA_TRAILS.md`](https://github.com/Root-Sequence/root-sequence/blob/main/IDEA_TRAILS.md) --- + +## Adaptive Continuity, Agency & Becoming + +**Stable ID:** `adaptive-continuity-agency` + +- **Research:** [`liberated-intelligence/notes/roots-of-conscious-consent.md`](https://github.com/Root-Sequence/liberated-intelligence/blob/main/notes/roots-of-conscious-consent.md) · [`root-sequence/research/conscious-systems/open-questions.md`](https://github.com/Root-Sequence/root-sequence/blob/main/research/conscious-systems/open-questions.md) · [`root-sequence/systems/adaptation/model.md`](https://github.com/Root-Sequence/root-sequence/blob/main/systems/adaptation/model.md) · [`root-sequence/systems/emergence/applications/personal.md`](https://github.com/Root-Sequence/root-sequence/blob/main/systems/emergence/applications/personal.md) +- **Human practice:** [`beinghumane-atlas/seeds/fear-trauma-and-systemic-mismatch.md`](https://github.com/Root-Sequence/beinghumane-atlas/blob/main/seeds/fear-trauma-and-systemic-mismatch.md) +- **Real-system work:** [`coherent-computing/docs/lifecycle-coherence-and-service-architecture.md`](https://github.com/Root-Sequence/coherent-computing/blob/main/docs/lifecycle-coherence-and-service-architecture.md) · [`community-infrastructure/docs/concepts/contextual-adaptability.md`](https://github.com/Root-Sequence/community-infrastructure/blob/main/docs/concepts/contextual-adaptability.md) +- **Analytical lens:** [`root-sequence/concepts/dynamic-coherence.md`](https://github.com/Root-Sequence/root-sequence/blob/main/concepts/dynamic-coherence.md) ★ +- **Speculative design:** [`coherent-world/simulation/coherence-model.md`](https://github.com/Root-Sequence/coherent-world/blob/main/simulation/coherence-model.md) · [`coherent-world/simulation/core-loop.md`](https://github.com/Root-Sequence/coherent-world/blob/main/simulation/core-loop.md) +- **Routing / maps:** [`root-sequence/IDEA_TRAILS.md`](https://github.com/Root-Sequence/root-sequence/blob/main/IDEA_TRAILS.md) + +--- + ## Maintenance - Edit `IDEA_TRAIL_GRAPH.yml` to add/remove document mappings. From 8708c1e6f7cd75eafeb81fd4b1064732944d87b3 Mon Sep 17 00:00:00 2001 From: Rae Lovejoy Date: Thu, 24 Sep 2026 21:56:36 -0700 Subject: [PATCH 12/66] Add dynamic coherence concept map and glossary --- concepts/dynamic-coherence.md | 49 +++++++++++++++++++++++++++++++++++ 1 file changed, 49 insertions(+) diff --git a/concepts/dynamic-coherence.md b/concepts/dynamic-coherence.md index 1857387..8384189 100644 --- a/concepts/dynamic-coherence.md +++ b/concepts/dynamic-coherence.md @@ -33,6 +33,55 @@ A working formulation is: This is intentionally not a definition of health, goodness, consciousness, intelligence, or legitimacy. A harmful system can be adaptive, resilient, stable, or historically persistent. A system can preserve itself by narrowing other people's possibilities. Any normative use must therefore name boundaries, affected parties, power, and costs. +## Concept map + +```mermaid +flowchart TD + H["History / path dependence"] --> T["Transition dynamics"] + E["Embodiment + environment"] --> T + T --> S["Current state"] + C["Constraints + affordances"] --> P["Reachable possibility space"] + S --> P + T --> P + P --> A["Agency envelope"] + A --> I["Action / intervention"] + I --> K["Consequences"] + K --> F["Feedback / learning"] + F --> T + I --> E + K --> H + + T --> ID["Continuity / identity"] + T --> EM["Emergent patterns"] + EM --> C + EM --> H + + P --> DC["Dynamic-coherence questions"] + F --> DC + C --> DC + H --> DC + + AI["Artificial systems"] -. "functional analogy does not establish experience" .-> T + CS["Consciousness questions"] -. "overlaps but is not identical to identity" .-> ID +``` + +The arrows are a routing map, not a causal theory. Different domains implement history, feedback, agency, embodiment, and viability in different ways. + +## Quick vocabulary + +| Term | Root Sequence working use | +| --- | --- | +| **Adaptive continuity** | Persistence through change: preserving or rebuilding enough organization, capability, relationship, or lineage for meaningful continuation. | +| **Dynamic coherence** | Examining coherence across change, feedback, scale, and time rather than only static consistency. | +| **Path dependence** | Earlier states or events alter later reachable possibilities or response dynamics. | +| **Agency envelope** | The meaningful reachable possibilities an actor can perceive, access, influence, refuse, or help create; currently a working concept, not a validated metric. | +| **Meta-agency** | Capacity to alter the conditions that shape later agency. | +| **Attractor-like pattern** | A persistent or self-reinforcing regime described by analogy to dynamical systems unless a formal attractor is actually modeled. | +| **Maladaptation / mismatch** | A response that is ineffective or costly under relevant current conditions, including responses that once fit different conditions. | +| **Reflexivity** | A model, measurement, prediction, or intervention changes the system being modeled. | +| **Downward constraint** | A system-level pattern reshapes local possibilities through identifiable channels such as rules, architecture, norms, allocation, or enforcement. | +| **Viability** | Continued functioning or persistence under an explicitly stated criterion; not automatically a moral good. | + --- ## 1. The key move: separate state from the way state changes From 18b5be15aa31492e30feaebcbd15d723499baf3b Mon Sep 17 00:00:00 2001 From: Rae Lovejoy Date: Thu, 24 Sep 2026 22:16:00 -0700 Subject: [PATCH 13/66] Extend related-work comparison for dynamic coherence --- .../coherent-systems/notes/related-work.md | 25 +++++++++++++++++-- 1 file changed, 23 insertions(+), 2 deletions(-) diff --git a/research/papers/coherent-systems/notes/related-work.md b/research/papers/coherent-systems/notes/related-work.md index c540834..df4c24c 100644 --- a/research/papers/coherent-systems/notes/related-work.md +++ b/research/papers/coherent-systems/notes/related-work.md @@ -22,13 +22,34 @@ Keys resolve in [references.bib](../references.bib). Page references use printed **C-012:** Narrow the proposed contribution to an inspectable synthesis and a review procedure that still needs comparison. Our current material does not demonstrate novelty, better detection, lower burden, or cross-domain validity. A useful outcome could be an accessible guide to existing methods rather than a new theory. +## September 24 extension: adaptation, viable possibility, and agency + +The dynamic-coherence/adaptive-continuity synthesis adds useful comparison targets, but no checked source establishes the synthesis as a new general theory. + +| Source / framework | What it adds to the comparison | Limit on our inference | +| --- | --- | --- | +| Di Paolo (2005), enactive adaptivity | A developed theory linking living autonomy, viability, adaptivity, normativity, and agency. It makes "adaptation" more specific than generic change. | Organismic adaptivity is not automatically an institutional or AI mechanism and does not establish consciousness. | +| Holling (1973); Walker et al. (2004), resilience literature | Distinguishes resilience from stability and, in social-ecological work, separates resilience, adaptability, and transformability. | Does not justify ranking UCF states by resilience or importing ecological identity criteria into unrelated domains. | +| Tognoli & Kelso (2014), metastability | Gives metastability a technical meaning in coordination dynamics involving tendencies toward integration and independence. | Does not establish "metastable" as a generic synonym for healthy social or institutional flexibility. | +| Capability approach | Distinguishes real/substantive opportunities from merely formal options. This is a close predecessor to the claim that nominal choice count is not enough for agency. | Does not itself model causal reachability, authorization, or all system dependencies. | +| Viability theory | Formalizes constrained dynamical evolution and viability kernels / reachable viable states. | Does not by itself encode meaning, justice, consent, knowledge, or legitimate authority. | +| Information-theoretic empowerment | Formalizes potential control over future sensor-accessible states and connects to controllability/observability. | Is not equivalent to human empowerment, legitimate power, welfare, or subjective agency. | +| Shoda et al. (2002); Nowak et al. (2005), personality dynamics | Demonstrates that attractor language can be literal within specified cognitive-affective models rather than only metaphorical. | Does not justify calling every persistent identity, institution, trauma response, or social pattern an attractor. | +| McEwen (1998; 2007), allostasis | Supports the bounded biological proposition that regulatory responses can aid short-run adaptation while cumulative activation can carry longer-run costs. | Is not a general trauma theory and should not be transferred directly to organizations or AI. | + +**Implication for the proposed contribution:** the candidate novelty is unlikely to be any single term above. If there is added value, it may lie in keeping present fit, path dependence, feedback, power over revision, future reachable possibilities, continuity criteria, and externalized costs visible in one review without collapsing them into a scalar. + +That is still only a hypothesis. A competent baseline may already recover all consequential findings. + +The targeted evidence reconciliation in UCF records exact sources and stronger scope limits: [dynamic coherence evidence audit](https://github.com/Root-Sequence/universal-coherence-framework/blob/dynamic-coherence-evidence-reconciliation-2026-09-24/docs/dynamic-coherence-evidence-audit-2026-09-24.md). That branch is draft provenance, not independent evidence. + ## Candidate comparison for T-003, not a completed study -Use a bounded service-design vignette with a declared evidence packet and task: identify consequential assumptions, missing feedback, displaced burdens, and unresolved decisions. Compare the proposed review with a competent ordinary service review and, where the task fits, a properly prepared STPA analysis. Before calling anything an STPA baseline, have the scope and implementation checked by someone able to assess its fidelity to that method. +Use a bounded service-design vignette with a declared evidence packet and task: identify consequential assumptions, missing feedback, displaced burdens, future constraints/options, path dependence, and unresolved decisions. Compare the proposed review with a competent ordinary service review and, where the task fits, a properly prepared STPA analysis. If human agency is central, add a capability-oriented check for real versus merely formal opportunities rather than crediting UCF for rediscovering that distinction. Before calling anything an STPA baseline, have the scope and implementation checked by someone able to assess its fidelity to that method. The three booking allocation rules are not three review methods. Their completion totals cannot establish the relative value of STPA, UCF, or this paper. -Keep the information packet identical. Record preparation and training time, not just time spent writing an answer. Pilot reasonable resource limits rather than arbitrarily truncating one method. Specify in advance how omissions, false alarms, evidence traceability, unresolved disagreements, and unnecessary information requests will be recorded. “Finds more things” is not enough if the extra findings are unsupported. +Keep the information packet identical. Record preparation and training time, not just time spent writing an answer. Pilot reasonable resource limits rather than arbitrarily truncating one method. Specify in advance how omissions, false alarms, evidence traceability, unresolved disagreements, unnecessary information requests, review burden, and decision-relevant unique findings will be recorded. “Finds more things” is not enough if the extra findings are unsupported. Do not use the published healthcare case as a blinded discovery test after revealing its conclusions. It is suitable for retrospective explanation. A comparative exercise needs a separate case or withheld facts, with any researcher-designed omissions clearly identified as artificial. Neither test proves universal validity. From dd05e92c55f777082403c3d3b1992b87e7916136 Mon Sep 17 00:00:00 2001 From: Rae Lovejoy Date: Thu, 24 Sep 2026 22:23:37 -0700 Subject: [PATCH 14/66] Draft T-003 added-value comparison protocol --- .../notes/t003-added-value-protocol.md | 366 ++++++++++++++++++ 1 file changed, 366 insertions(+) create mode 100644 research/papers/coherent-systems/notes/t003-added-value-protocol.md diff --git a/research/papers/coherent-systems/notes/t003-added-value-protocol.md b/research/papers/coherent-systems/notes/t003-added-value-protocol.md new file mode 100644 index 0000000..d37f8cd --- /dev/null +++ b/research/papers/coherent-systems/notes/t003-added-value-protocol.md @@ -0,0 +1,366 @@ +# T-003 added-value comparison — protocol draft + +**Status:** UNRUN / preregistration candidate +**Date:** 2026-09-24 +**Research area:** Coherent Systems living paper +**Purpose:** Test whether the proposed relational/dynamic coherence review adds decision-relevant information beyond competent existing review methods, without hiding extra burden, false alarms, or duplicated findings. +**Not evidence:** Writing this protocol does not validate the method. + +## 1. Research question + +For the **same bounded evidence packet and design decision**, does the proposed Coherent Systems / dynamic-coherence review identify consequential, evidence-traceable considerations that a competent baseline review does not, and at what additional cost in reviewer time, information demands, ambiguity, and false alarms? + +The comparison is allowed to return: + +- useful added value; +- useful synthesis but no unique findings; +- excessive burden; +- misleading additional findings; +- no meaningful difference; +- a reason to narrow or retire part of the framework. + +No result is required to favor the proposed method. + +--- + +## 2. Why this protocol exists + +A flexible framework can appear insightful simply because it is allowed to ask more questions after seeing the case. + +That is not a fair test. + +The comparison therefore freezes: + +- the task; +- the evidence packet; +- the method prompts; +- the available time; +- the coding rubric; +- the definition of a consequential finding; + +before outputs are compared. + +An AI comparing its own responses is an **editorial dry run**, not independent validation. + +--- + +## 3. Case-selection criteria + +The first case must be: + +- public or fully synthetic with no private-person data; +- non-clinical and non-intimate; +- bounded enough for a reviewer to inspect the whole packet; +- rich enough to include at least one dependency, feedback path, affected party, and future transition; +- not authored specifically to demonstrate a known UCF failure mode; +- not the existing healthcare proxy case whose conclusion is already known; +- not a Coherent World simulation result; +- not a case whose "correct answer" is defined by Root Sequence canon. + +Preferred domains: + +- infrastructure/service fallback; +- repair/service architecture; +- provider dependency and migration; +- accessibility under disruption; +- community degraded mode. + +The case-selection decision and reason must be recorded **before** any method is applied. + +--- + +## 4. Shared evidence packet + +Every method receives exactly the same packet: + +1. case description and decision question; +2. actors/affected parties explicitly named in the source; +3. architecture/process diagram if available; +4. known constraints; +5. observed or stipulated outcomes; +6. known uncertainties; +7. source provenance; +8. time horizon; +9. what information is intentionally unavailable. + +If a method requests more information, record the request. Do not silently give one method extra facts. + +A missing fact may itself be a finding. + +--- + +## 5. Methods + +### Method A — competent ordinary review + +Use the review method that a competent practitioner would reasonably apply to the selected case. + +Its prompt/procedure must be documented before output generation. It must not be deliberately weakened to make UCF look broad. + +At minimum it should ask about: + +- purpose and requirements; +- stakeholders / affected users; +- dependencies; +- failure modes; +- constraints; +- maintenance/operations; +- obvious alternatives; +- known risks and tradeoffs. + +If the case has a recognized domain method, prefer that over a home-made generic checklist. + +### Method B — STPA, when appropriate + +If the selected case is a socio-technical safety/control problem for which STPA is a credible fit, prepare an STPA analysis following the Leveson & Thomas handbook rather than a simplified caricature. + +Record: + +- analyst experience/training; +- preparation time; +- losses; +- hazards; +- control structure; +- unsafe control actions; +- loss scenarios; +- assumptions and omitted scope. + +If no reviewer with sufficient STPA fidelity is available, do **not** label a casual checklist "STPA." + +### Method C — capability-oriented agency check, when people’s practical options are central + +Use capability-approach concepts only for the question they actually address: whether options are real/substantive opportunities rather than merely formal choices. + +Do not pretend this is a full engineering method. + +Record: + +- nominal options; +- conversion factors / practical barriers visible in the evidence; +- real opportunities affected; +- whose capability is being discussed; +- unresolved value judgments. + +### Method D — proposed Coherent Systems / dynamic-coherence review + +Use the exact prompt below without adding case-specific questions after seeing the packet. + +--- + +## 6. Frozen dynamic-coherence prompt + +For the stated system, boundary, decision, and evidence packet: + +1. **Present fit:** What currently works, for whom, and under which assumptions? +2. **Relational consequences:** Which affected people, systems, dependencies, resources, or burdens sit inside or outside the chosen boundary? +3. **State change:** What changes immediately if the proposal is adopted? +4. **Transition change:** What changes in how the system will respond to later conditions—rules, thresholds, dependencies, topology, learned behavior, maintenance, or available actions? +5. **History / path dependence:** Which earlier conditions materially constrain the present, and which consequences of this decision are likely to persist? Name the mechanism rather than saying only that history matters. +6. **Future possibility:** Which meaningful actions become easier, harder, newly dependent, or unavailable for each materially affected actor? Distinguish nominal availability from practical feasibility when the evidence supports it. +7. **Feedback:** Which consequences will become visible, to whom, how quickly, and with what uncertainty? +8. **Revision power:** Who can change, appeal, repair, reverse, exit, or replace the arrangement after mismatch appears? +9. **Continuity / transformation:** What capability, relationship, identity, or function is meant to persist? Under what conditions should transformation rather than restoration be considered? +10. **Externalized effects:** Which costs, risks, labor, or ecological/material demands may be displaced beyond the local objective? +11. **Normative disagreement:** Which purposes, burdens, or decision rights remain contested rather than settled by functional success? +12. **Evidence and alternatives:** Which statements are observed, inferred, assumed, or normative? What competing explanation or design should remain live? +13. **Retirement check:** Which of these observations would a competent baseline method already capture? Do not claim added value for duplicated findings. + +Output findings individually with source/evidence locator, affected party, consequence, timescale, and uncertainty. + +Do not produce an overall coherence score or winner. + +--- + +## 7. Finding definition + +A **finding** is one specific statement that could plausibly change: + +- a design decision; +- a requirement; +- a test; +- a risk treatment; +- a maintenance plan; +- a migration/exit plan; +- an accessibility provision; +- an authority/governance decision; +- a request for missing evidence. + +Do not count: + +- restating the prompt; +- renaming an already-described fact; +- unsupported speculation; +- generic warnings that do not connect to the case; +- stylistic differences; +- duplicate findings split into several bullets. + +--- + +## 8. Finding coding + +Independent coders should classify each finding: + +### Evidence traceability + +- **E2:** directly supported by packet evidence; +- **E1:** reasonable inference with explicit basis; +- **E0:** unsupported / cannot be traced. + +### Consequence + +- **D2:** plausibly decision-relevant under the stated task; +- **D1:** relevant context but unlikely to change the decision; +- **D0:** not materially relevant. + +### Novelty relative to another method + +- **N2:** substantively absent from comparison method; +- **N1:** partially present / differently developed; +- **N0:** same substantive finding already captured. + +### Error / false alarm + +Flag a finding when: + +- it contradicts the evidence packet; +- imports an unsupported actor, mechanism, or harm; +- treats a normative preference as an observed fact; +- applies a domain concept outside its justified scope; +- requests unnecessary sensitive information. + +Coding disagreements remain visible. + +--- + +## 9. Primary outcomes + +Report separately: + +1. number of **E1–E2 / D2** findings per method; +2. number of **N2** decision-relevant findings after adjudication; +3. unsupported / false-alarm count; +4. duplicated-finding count; +5. reviewer preparation time; +6. analysis time; +7. additional-information requests; +8. unnecessary-information requests; +9. disagreements between reviewers/coders; +10. findings that changed a proposed decision or test. + +Do not aggregate these into one method score. + +--- + +## 10. Burden and privacy outcomes + +Record: + +- pages/minutes of method preparation; +- specialist knowledge required; +- evidence fields requested; +- whether requested data are sensitive; +- whether the method encourages boundary expansion beyond what is necessary; +- cognitive/participation burden on affected people; +- whether the method can reach a legitimate "not enough information" result. + +A method that finds more by demanding intimate or unnecessary data may be worse for the stated task. + +--- + +## 11. Reviewer structure + +### Editorial pilot + +May be run by project authors/AI only to find protocol defects. + +It cannot establish independent agreement or superiority. + +Label all results **EDITORIAL PILOT**. + +### Independent review + +For a stronger test: + +- at least two people apply each method independently; +- at least two coders compare findings; +- method identities may be masked during finding coding where practical; +- conflicts are recorded, not silently resolved by the project author; +- domain-method fidelity receives separate review. + +A future participant study requires its own consent, accessibility, privacy, withdrawal, and oversight plan. + +--- + +## 12. Pre-specified failure / retirement signals + +The proposed review should be narrowed, decomposed, or retired for this use if: + +- it produces no decision-relevant unique findings across repeated cases; +- unique findings are mostly unsupported; +- useful additions are already obtained more cleanly by one established method; +- burden or data demands are materially higher without corresponding value; +- reviewers cannot apply the vocabulary consistently; +- "coherence" tracks approval rather than a specified relation/mechanism; +- path dependence / future possibility language does not change any actual design or evidence question. + +A null result is a successful research outcome. + +--- + +## 13. Interpretation boundary + +Even a favorable result would show only that the procedure added value **for the tested task, evidence packet, reviewers, and baselines**. + +It would not establish: + +- a universal theory of coherence; +- cross-domain causal identity; +- a validated scalar; +- superiority over every systems method; +- a consciousness, trauma, or intelligence theory; +- normative legitimacy of the resulting decision. + +--- + +## 14. Required preregistration record before execution + +```text +CASE: +CASE SOURCE: +DECISION QUESTION: +WHY CASE WAS SELECTED: +EVIDENCE PACKET HASH / VERSION: +METHOD A: +METHOD B (IF USED): +METHOD C (IF USED): +METHOD D VERSION: +REVIEWER QUALIFICATIONS: +TIME LIMITS: +CODERS: +CODING RUBRIC VERSION: +KNOWN CONFLICTS OF INTEREST: +WHAT WOULD COUNT AS A NULL RESULT: +DATE FROZEN: +``` + +Do not modify the frozen prompt or packet after seeing method outputs without declaring a new exploratory round. + +--- + +## 15. Current status + +**UNRUN.** + +No case, reviewers, coders, or outputs are registered by this document. + +The next legitimate action is case selection and packet freezing—not writing a conclusion. + +--- + +## Related + +- [Open questions / T-003](../open-questions.md) +- [Related work](related-work.md) +- [Dynamic Coherence and Adaptive Continuity](../../../concepts/dynamic-coherence.md) +- [UCF dynamic-coherence evidence reconciliation](https://github.com/Root-Sequence/universal-coherence-framework/pull/6) +- Leveson & Thomas, *STPA Handbook* (2018): https://psas.scripts.mit.edu/home/get_file.php?name=STPA_handbook.pdf From 3a059d5aed72381af5df4bc22d5babc76b2299d7 Mon Sep 17 00:00:00 2001 From: Rae Lovejoy Date: Thu, 24 Sep 2026 22:25:17 -0700 Subject: [PATCH 15/66] Route T-003 through preregistration protocol --- research/papers/coherent-systems/open-questions.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/research/papers/coherent-systems/open-questions.md b/research/papers/coherent-systems/open-questions.md index 430a6d6..0ea237c 100644 --- a/research/papers/coherent-systems/open-questions.md +++ b/research/papers/coherent-systems/open-questions.md @@ -44,9 +44,9 @@ A later extension should test recurring demand, referrals, service outcomes, unc ## T-003 — Added-value comparison -**Still unrun.** The [related-work note](notes/related-work.md#candidate-comparison-for-t-003-not-a-completed-study) now identifies candidate baselines and fidelity checks. The published healthcare case is a retrospective interpretation, not a blinded test of discovery. No independent reviewer results are claimed. +**Still unrun.** The [related-work note](notes/related-work.md#candidate-comparison-for-t-003-not-a-completed-study) identifies candidate baselines and fidelity checks. The new [T-003 protocol draft](notes/t003-added-value-protocol.md) freezes the proposed dynamic-coherence prompt, finding definitions, coding dimensions, burden/privacy measures, null-result criteria, and the distinction between an editorial pilot and independent review. The published healthcare case remains a retrospective interpretation, not a blinded test of discovery. No case, evidence packet, reviewer, coder, or independent result is registered yet. -Choose a small, public, non-sensitive design case and a competent existing review method. Compare it with the section 12 procedure using the same information and a comparable review effort. Avoid giving the new method more evidence while calling its findings an improvement. +The next legitimate step is **case selection and packet freezing**, not another conceptual expansion. Choose a small, public, non-sensitive design case and a competent existing review method. Compare it with the section 12 procedure using the same information and a comparable review effort. Avoid choosing a case merely because its known conclusion already matches the framework, and avoid giving the new method more evidence while calling its findings an improvement. **Measure:** Consequential omissions identified, false alarms, traceability, disagreement, reviewer time, and unnecessary information requests. Define “consequential” before evaluating outputs. From d1a0059953c18831e9d479738fd7416ac2d394f2 Mon Sep 17 00:00:00 2001 From: Rae Lovejoy Date: Thu, 24 Sep 2026 23:00:50 -0700 Subject: [PATCH 16/66] Freeze T-003 first case selection --- .../notes/t003-case-selection-2026-09-24.md | 87 +++++++++++++++++++ 1 file changed, 87 insertions(+) create mode 100644 research/papers/coherent-systems/notes/t003-case-selection-2026-09-24.md diff --git a/research/papers/coherent-systems/notes/t003-case-selection-2026-09-24.md b/research/papers/coherent-systems/notes/t003-case-selection-2026-09-24.md new file mode 100644 index 0000000..504a036 --- /dev/null +++ b/research/papers/coherent-systems/notes/t003-case-selection-2026-09-24.md @@ -0,0 +1,87 @@ +# T-003 case selection — 2026-09-24 + +**Status:** FROZEN FOR EDITORIAL PILOT +**Protocol:** [T-003 added-value comparison](t003-added-value-protocol.md) +**Selection date:** 2026-09-24 +**Method outputs generated before this record:** none + +## Selected case + +**Cloudflare incident on June 20, 2024** + +Primary source: + +- Cloudflare, "Cloudflare incident on June 20, 2024," published June 26, 2024: https://blog.cloudflare.com/cloudflare-incident-on-june-20-2024/ + +## Why this case + +It satisfies the protocol's first-case criteria: + +- public; +- non-clinical and non-intimate; +- bounded incident; +- one detailed primary-source postmortem; +- explicit architecture, timeline, failure propagation, incident response, and remediation; +- real feedback, dependencies, automation, legacy components, rollout process, and future design changes; +- no need to infer private human experience. + +It is **not** selected because its conclusion already matches Root Sequence. + +## Anti-cherry-pick rule + +Before any method output, candidate incident reports were gathered from official engineering/postmortem sources. + +We deliberately excluded Cloudflare's November 2023 / March 2024 repeat data-center-power pair from the first pilot because the second event explicitly tests how prior history changed later response. That makes it unusually favorable to the new framework's central intuition and therefore a poor first falsification-risk case. + +The June 20 incident was chosen instead because: + +1. its primary postmortem is detailed enough to freeze a self-contained evidence packet; +2. it contains ordinary engineering failure modes a competent incident review should already detect; +3. its central story is not "we learned from a prior identical event"; +4. it therefore creates a credible possibility that the dynamic-coherence method will add **nothing unique**. + +## Decision question + +> Given only the frozen evidence packet, what design, operational, rollout, monitoring, dependency, and recovery changes should be prioritized to reduce recurrence or impact of a similar incident? + +This asks for actionable review findings rather than a retrospective label. + +## Methods in the first editorial pilot + +### Included + +- **Method A:** competent ordinary incident/system review. +- **Method D:** frozen dynamic-coherence review from the T-003 protocol. + +### Not included + +- **STPA:** not labeled or simulated in the first pilot because this pass has not established sufficient analyst fidelity to STPA. A future comparison can add STPA after method-fidelity review. +- **Capability-oriented check:** omitted because human substantive opportunity is not central to this technical incident. + +## Interpretation boundary + +The first comparison is an **EDITORIAL PILOT** run by the same AI-assisted research process that helped draft the framework. + +It can reveal: + +- protocol defects; +- duplicate questions; +- obvious false alarms; +- coding ambiguity; +- whether the dynamic prompt produces usable findings at all. + +It cannot establish: + +- independent reviewer agreement; +- method superiority; +- empirical validity; +- novelty; +- generalizability. + +## Freeze rule + +The evidence packet at [t003-evidence-packet-cloudflare-2024-06-20.md](t003-evidence-packet-cloudflare-2024-06-20.md) is the only factual case material available to Method A and Method D in the editorial pilot. + +No live browsing, hidden source expansion, or later incident knowledge may be used during the method outputs. + +If the packet proves materially incomplete, stop the run and create a new packet version rather than silently adding evidence. From c59c3dc041b1824732d50d1c4c5073827ab425c9 Mon Sep 17 00:00:00 2001 From: Rae Lovejoy Date: Thu, 24 Sep 2026 23:00:52 -0700 Subject: [PATCH 17/66] Freeze T-003 Cloudflare evidence packet --- ...3-evidence-packet-cloudflare-2024-06-20.md | 223 ++++++++++++++++++ 1 file changed, 223 insertions(+) create mode 100644 research/papers/coherent-systems/notes/t003-evidence-packet-cloudflare-2024-06-20.md diff --git a/research/papers/coherent-systems/notes/t003-evidence-packet-cloudflare-2024-06-20.md b/research/papers/coherent-systems/notes/t003-evidence-packet-cloudflare-2024-06-20.md new file mode 100644 index 0000000..adbdaf5 --- /dev/null +++ b/research/papers/coherent-systems/notes/t003-evidence-packet-cloudflare-2024-06-20.md @@ -0,0 +1,223 @@ +# T-003 frozen evidence packet — Cloudflare June 20, 2024 + +**Packet version:** 0.1 +**Status:** FROZEN FOR EDITORIAL PILOT +**Prepared:** 2026-09-24 +**Primary source:** Cloudflare incident postmortem published June 26, 2024 +**Source URL:** https://blog.cloudflare.com/cloudflare-incident-on-june-20-2024/ + +## Use rule + +This document is the **entire factual evidence packet** for the T-003 editorial pilot. + +Reviewers/methods may reason from these facts, identify missing information, and request more evidence. They may not silently import facts from the live article, other Cloudflare incidents, general Cloudflare knowledge, or external sources. + +The packet is a project-authored paraphrase of the source, not an independent account. + +--- + +## Decision question + +> Given only this evidence packet, what design, operational, rollout, monitoring, dependency, and recovery changes should be prioritized to reduce recurrence or impact of a similar incident? + +--- + +## System background supplied in the source + +Cloudflare describes two systems involved in traffic balancing: + +- **Unimog**, an edge load balancer, directs packets to an appropriate server and attempts to keep CPU load balanced across active servers within a data center. +- **Traffic Manager** uses global signals including CPU utilization, HTTP request latency, and bandwidth utilization to issue rebalancing decisions across data centers. Cloudflare states that it has safety limits intended to prevent overly large traffic shifts and that it considers expected load at destination locations. + +The affected HTTP rate-limiting path was used in a new DDoS mitigation mechanism combining rate limits and cookies. + +--- + +## Incident-level outcome + +Cloudflare reports that two independent events increased latency and error rates for Internet properties and Cloudflare services for 114 minutes. + +During the peak 30-minute impact: + +- approximately 1.4–2.1% of HTTP requests to Cloudflare's CDN received a generic error page; +- p99 Time To First Byte latency rose to almost three times its prior level. + +The two reported events were: + +1. automated network monitoring detected degradation and rerouted traffic suboptimally, creating backbone congestion between approximately 17:33 and 17:50 UTC; +2. a newly deployed DDoS mitigation mechanism exposed a latent bug in the rate-limiting system, allowing a particular request form to put a request-handling process into a non-terminating loop. + +The postmortem focuses mainly on the second event. + +--- + +## Deployment timeline + +All times below are UTC on 2024-06-20. + +- **14:14:** gradual deployment of the new DDoS rule began. +- **17:06:** deployment reached all data centers. +- **17:47:** first request-handling process entered the poisoned/non-terminating state. +- **18:04:** incident automatically declared after sustained high global CPU load. +- **18:34:** engineers showed that restarting the service recovered one server; a full restart was tested in one data center. +- **18:44:** CPU load normalized in that data center after restart. +- **18:51:** repeated global reloads/restarts began for servers with many stuck processes. +- **19:05:** HTTP error rate peaked; Traffic Manager began actions that helped recover service. +- **19:11:** service-unavailable HTTP error rate had roughly halved. +- **19:27:** global HTTP error rate returned to baseline. +- **19:29:** the DDoS rule deployment was identified as the likely trigger for process poisoning. +- **19:34:** the DDoS rule was fully disabled. +- **19:43:** engineers stopped routine restarts on heavily affected servers. +- **20:16:** incident response stood down. + +--- + +## Failure mechanism described by Cloudflare + +The new DDoS mitigation path: + +1. checked for a valid cookie; +2. for a valid cookie, added a rate-limit rule based on the cookie value; +3. later evaluated the generated rate-limit rules. + +Cloudflare reused existing rate-limit key-generation logic. + +The postmortem identifies two interacting software problems: + +- internally generated rate-limit rules used an API path in an unanticipated way, causing the parent key generator to point back to the same cookie-key function; +- a second cookie-validation function could disagree with the earlier validation when a request contained multiple cookies with mixed validity. + +Under the triggering request, the key-generation function called itself repeatedly. + +Because the Lua implementation used proper tail calls, the recursion did not necessarily grow the call stack until failure. Instead, the request-handling process could remain in a loop consuming 100% CPU. + +A process that entered this state stopped serving later requests. + +--- + +## Failure propagation described by Cloudflare + +Each server had many request-handling processes, so one poisoned process alone had limited effect. + +As more processes became CPU-saturated: + +1. Unimog shifted new traffic away from higher-load servers toward servers with more available capacity. +2. Rising CPU utilization at a data-center level caused Traffic Manager to redirect traffic toward other data centers. +3. Redirected traffic included requests capable of poisoning processes, spreading the same failure condition to previously less-affected servers/data centers. + +Cloudflare reports that this made healthy destination capacity progressively harder to find. + +Traffic Manager's built-in safety limits also constrained how much additional traffic could be shifted. + +At one point reported in the postmortem, approximately 10% of HTTP-request capacity in Western Europe and 4% in Eastern Europe was CPU-saturated. + +--- + +## Incident-response information + +Automatic alerting notified engineers when sustained global CPU utilization crossed a threshold. + +Many incident responders were already engaged with the separate backbone-congestion incident. + +In the early investigation, responders considered whether the high CPU condition was related to the existing network incident. + +The source says it took time to notice that the highest-CPU locations were receiving the *lowest* traffic, which moved investigation away from the network event as the initiating cause. + +Responders then pursued two parallel activities: + +- determine whether restarting poisoned processes would recover them and perform broader restarts; +- identify what triggered processes to enter the CPU-saturated state. + +Cloudflare reports that it took about 25 minutes after incident declaration to validate restart recovery on a sample server, followed roughly five minutes later by broader restarts. + +--- + +## Additional Traffic Manager failure + +During the same incident conditions, a latent bug in Traffic Manager was also triggered. + +Cloudflare says Traffic Manager attempted a graceful restart after the exception, which halted its activity. + +The bug first triggered at approximately 18:17 UTC and then repeatedly between 18:35 and 18:57. + +During two reported intervals—approximately 18:35–18:52 and 18:56–19:05—Traffic Manager issued no new traffic-routing actions. + +This left significant traffic rerouted away from locations whose request service had already begun recovering. + +Alerting notified the Traffic team; Cloudflare reports that by 19:05 the team had written, tested, and deployed a fix. + +--- + +## Immediate mitigation + +Cloudflare used repeated rolling/global restarts of the affected request-handling service while investigating the trigger. + +The new DDoS rule was rolled back/disabled globally. + +Cloudflare stated that the rule would remain disabled until the broken cookie-validation condition was fixed and the recurrence risk addressed. + +--- + +## Follow-up actions stated in the postmortem + +Cloudflare identified at least these follow-ups: + +### Rate-limiting architecture + +The DDoS module was using a **legacy** rate-limiting implementation, while customer-configured rate limits used a newer engine. + +Cloudflare stated it was in early implementation stages of replacing the affected service. + +The replacement design was intended to allow limits on both uninterrupted and total execution time for a single request. + +### Loop containment + +Cloudflare said it was exploring ways to prevent the affected service from looping indefinitely through tail calls. + +### Staging / rollout + +The new DDoS rule had first been staged in a small number of production data centers and then deployed to all data centers a few hours later. + +Cloudflare said it would continue improving staging and rollout procedures to reduce change-related blast radius. + +### Backbone congestion + +For the separate network-congestion event, Cloudflare said it was already: + +- expanding backbone capacity in affected data centers; +- improving network mitigation decisions to use more information about available capacity on alternative paths. + +--- + +## Explicit unknowns / unavailable information + +The packet does **not** provide: + +- internal code or full architecture; +- detailed organizational ownership boundaries; +- complete rollout criteria, canary size, or promotion thresholds; +- unit/integration/test coverage before deployment; +- exact monitoring/alert thresholds; +- customer-by-customer impact distribution; +- detailed incident command structure; +- staffing or workload details beyond responders already working another incident; +- cost estimates for remediation options; +- full chronology for the first network-congestion event; +- proof that the listed remediations were later implemented or effective; +- a complete dependency graph; +- a formal safety/control analysis; +- independent verification of Cloudflare's account. + +Review methods should identify needed missing information rather than inventing it. + +--- + +## Evidence-status boundary + +Treat the packet as: + +- **SOURCE-REPORTED OBSERVATION** for Cloudflare's stated metrics, timeline, architecture, failure mechanism, and remediation; +- **UNKNOWN** for facts not supplied; +- **ANALYTICAL INFERENCE** for any causal or design conclusion produced by a review method. + +No claim in the pilot should be described as independently established merely because it appears in this packet. From ff138cc691e678db91ef9368b9f746bcdb56b420 Mon Sep 17 00:00:00 2001 From: Rae Lovejoy Date: Thu, 24 Sep 2026 23:02:04 -0700 Subject: [PATCH 18/66] Preregister T-003 editorial pilot 001 --- .../t003-editorial-pilot-001-registration.md | 134 ++++++++++++++++++ 1 file changed, 134 insertions(+) create mode 100644 research/papers/coherent-systems/notes/t003-editorial-pilot-001-registration.md diff --git a/research/papers/coherent-systems/notes/t003-editorial-pilot-001-registration.md b/research/papers/coherent-systems/notes/t003-editorial-pilot-001-registration.md new file mode 100644 index 0000000..789d7df --- /dev/null +++ b/research/papers/coherent-systems/notes/t003-editorial-pilot-001-registration.md @@ -0,0 +1,134 @@ +# T-003 Editorial Pilot 001 — preregistration + +**Status:** FROZEN BEFORE METHOD OUTPUTS +**Pilot type:** AI-assisted editorial protocol test; not independent validation +**Date frozen:** 2026-09-24 + +## Case + +**CASE:** Cloudflare incident on June 20, 2024 +**CASE SOURCE:** frozen project-authored packet only +**Decision question:** Given only the frozen evidence packet, what design, operational, rollout, monitoring, dependency, and recovery changes should be prioritized to reduce recurrence or impact of a similar incident? + +## Frozen artifacts + +- Protocol: `t003-added-value-protocol.md` + - blob SHA: `d37f8cd1091f0712943636e0811902c0a1559169` +- Case selection: `t003-case-selection-2026-09-24.md` + - blob SHA: `504a03627858974b914b2a02603ea4ca1c7443e4` +- Evidence packet: `t003-evidence-packet-cloudflare-2024-06-20.md` + - blob SHA: `adbdaf50011fb747f83c0f83e90c5ec3d70fb849` + +No live browsing or other case knowledge is permitted during the two method outputs. + +## Method A — competent ordinary incident/system review + +Use only the frozen packet. + +Produce no more than **12 findings**. For each finding provide: + +- finding; +- packet evidence/basis; +- why it matters; +- proposed action; +- uncertainty / missing evidence. + +Review the case as a competent senior reliability/system reviewer. Specifically: + +1. reconstruct the main failure and propagation chain; +2. identify contributing design, implementation, dependency, deployment, monitoring, incident-response, and recovery factors supported by the packet; +3. distinguish prevention, detection, containment, recovery, and verification actions; +4. identify where one protective/recovery mechanism worsened or failed to contain another failure; +5. identify missing information needed before prioritizing major changes; +6. separate packet-reported facts from analytical inference. + +Do not use Root Sequence/UCF terminology unless it is already present in the packet. + +Do not produce an overall score. + +## Method D — frozen dynamic-coherence review + +Use the exact 13-question prompt in the frozen T-003 protocol. + +Produce no more than **12 findings**. Each finding must include: + +- evidence/basis; +- affected component/party; +- consequence; +- timescale; +- uncertainty; +- proposed design/research implication. + +Do not produce an overall coherence score or method comparison inside the Method D output. + +## Excluded methods + +- STPA: excluded from Pilot 001 because method-fidelity review has not been completed. +- Capability-oriented check: excluded because human substantive opportunity is not central to the selected technical incident. + +## Reviewer / conflict statement + +Both Method A and Method D outputs are generated by the same AI-assisted research process that helped develop the dynamic-coherence framework. + +This is a major conflict of interest. + +Therefore Pilot 001 can test: + +- whether prompts are usable; +- whether findings can be coded; +- obvious duplication; +- obvious unsupported extrapolation; +- whether the comparison protocol needs revision. + +It cannot establish superiority, novelty, reliability, or independent agreement. + +## Output constraints + +- Evidence packet only. +- Maximum 12 findings per method. +- No external factual additions. +- Unsupported assumptions must be marked. +- Missing information should be requested, not invented. + +## Burden measurement in this pilot + +Human reviewer preparation time and analysis time are **not measurable** in this AI-only run and must be reported as unavailable. + +Use only: + +- prompt question count; +- output character/word count; +- number of findings; +- additional-information requests; + +as crude editorial-burden indicators. + +Do not interpret these as human usability measurements. + +## Coding + +Use the protocol's: + +- E0–E2 evidence traceability; +- D0–D2 decision relevance; +- N0–N2 novelty relative to the other method; +- false-alarm flags. + +Method comparison is performed only after both outputs are frozen. + +## Known conflicts of interest + +- framework and protocol are AI-assisted; +- the same model family generates both outputs and coding; +- the selected packet was prepared by the same research process; +- the primary source is Cloudflare's own postmortem, not independent incident reconstruction. + +## Null result + +A valid null result includes: + +> Method D's decision-relevant findings are all or nearly all already captured by Method A, with no clear additional decision value relative to its added conceptual overhead. + +## Retirement signal + +If repeated independent comparisons show the same pattern, dynamic-coherence review should be narrowed into routing guidance among established methods rather than promoted as a distinct review method. From 0d8a5ddf36ed2752170ac1faa621f3641ef46197 Mon Sep 17 00:00:00 2001 From: Rae Lovejoy Date: Thu, 24 Sep 2026 23:04:10 -0700 Subject: [PATCH 19/66] Run T-003 editorial pilot method A --- .../t003-editorial-pilot-001-method-a.md | 216 ++++++++++++++++++ 1 file changed, 216 insertions(+) create mode 100644 research/papers/coherent-systems/notes/t003-editorial-pilot-001-method-a.md diff --git a/research/papers/coherent-systems/notes/t003-editorial-pilot-001-method-a.md b/research/papers/coherent-systems/notes/t003-editorial-pilot-001-method-a.md new file mode 100644 index 0000000..b730cfc --- /dev/null +++ b/research/papers/coherent-systems/notes/t003-editorial-pilot-001-method-a.md @@ -0,0 +1,216 @@ +# T-003 Editorial Pilot 001 — Method A output + +**Method:** competent ordinary incident/system review +**Status:** FROZEN EDITORIAL OUTPUT +**Evidence:** frozen Cloudflare June 20, 2024 packet only +**Maximum findings:** 12 +**Independent validation:** no + +## A-01 — Fix the two-condition software defect and make the failure impossible to recur through the same path + +**Category:** prevention + +**Finding:** The immediate software failure required an unanticipated internal API relationship plus a second cookie-validation function that could disagree with the earlier check. Together they allowed the key generator to call itself indefinitely. + +**Packet basis:** The packet reports both conditions and the resulting 100% CPU loop. + +**Why it matters:** Either defect remaining can preserve part of the failure path; fixing only the triggering rule would leave latent implementation risk. + +**Proposed action:** Unify or make explicit the cookie-validation contract; prevent self-referential key-generator configuration; add tests covering internally generated rate-limit rules and mixed-validity cookie cases. + +**Uncertainty / missing evidence:** The packet does not describe existing test coverage, type/interface constraints, or whether similar key-generator composition exists elsewhere. + +--- + +## A-02 — Add execution bounds so one request cannot permanently consume a worker + +**Category:** containment + +**Finding:** Proper tail-call behavior meant the loop did not necessarily fail through stack exhaustion; a poisoned process could remain alive while consuming a full CPU. + +**Packet basis:** The packet reports that a triggering request could leave a request-handling process indefinitely CPU-saturated. + +**Why it matters:** A defensive runtime limit would reduce the consequence of an unforeseen logic loop even if a similar defect escaped testing. + +**Proposed action:** Add bounded uninterrupted/total execution time or an equivalent watchdog/cancellation mechanism around request processing; test failure behavior when a limit is exceeded. + +**Uncertainty / missing evidence:** The packet does not state the latency/cost tradeoffs or which layer can safely enforce a bound. + +--- + +## A-03 — Retire or isolate the legacy rate-limiting implementation + +**Category:** prevention / dependency reduction + +**Finding:** The affected DDoS path used a legacy rate-limiting implementation while customer-configured rate limits used a newer engine. + +**Packet basis:** This distinction is stated in the follow-up actions. + +**Why it matters:** Parallel implementations increase the chance that fixes, invariants, and protections diverge. + +**Proposed action:** Prioritize migration to the newer/replacement engine or define a bounded compatibility/isolation plan until migration is complete; inventory unique legacy behaviors before removal. + +**Uncertainty / missing evidence:** The packet does not establish that the newer engine is immune to analogous bugs or show migration complexity. + +--- + +## A-04 — Strengthen progressive rollout and automatic promotion/stop criteria + +**Category:** prevention / blast-radius control + +**Finding:** The new DDoS rule was staged in a handful of production data centers and then deployed globally within several hours, before the latent failure was encountered. + +**Packet basis:** Deployment began at 14:14, reached all data centers by 17:06, and the first poisoned process appeared at 17:47. + +**Why it matters:** Staging provides limited protection if the triggering request does not occur during the observation window or if promotion criteria are not sensitive to the relevant failure. + +**Proposed action:** Define explicit canary duration, traffic diversity, health signals, automatic halt criteria, and rapid global rollback for new network-wide mitigation rules; consider progressive exposure by traffic/request class as well as location. + +**Uncertainty / missing evidence:** The packet does not provide existing promotion criteria, canary traffic representativeness, or rollback automation. + +--- + +## A-05 — Make traffic shifting aware of pathological work, not only load + +**Category:** containment + +**Finding:** Unimog and Traffic Manager responded to high CPU by moving traffic, but the moved traffic included requests that could poison additional processes and data centers. + +**Packet basis:** The packet explicitly describes this propagation. + +**Why it matters:** A normal load-balancing response became a failure amplifier because it treated high CPU as a capacity-location problem rather than distinguishing a workload that reproduced the failure. + +**Proposed action:** Add signals or circuit-breaking behavior that can quarantine affected service instances/request classes, suppress propagation of suspected pathological traffic, and distinguish capacity shortage from load generated by a stuck processing path. + +**Uncertainty / missing evidence:** The packet does not show whether the triggering request could have been reliably classified during the incident. + +--- + +## A-06 — Harden Traffic Manager as a recovery-critical dependency + +**Category:** containment / recovery + +**Finding:** Traffic Manager developed a separate latent failure under incident conditions and temporarily stopped issuing routing actions while traffic remained shifted away from recovering locations. + +**Packet basis:** The packet reports repeated Traffic Manager exceptions/restarts and two periods without new actions. + +**Why it matters:** A system relied upon to reduce impact became partly unavailable during the same event. + +**Proposed action:** Test Traffic Manager under degraded/compound conditions; isolate failure modes that halt global action; provide a bounded degraded/manual operating mode or redundant control path; alert specifically on loss of routing-action capability. + +**Uncertainty / missing evidence:** The packet does not describe Traffic Manager redundancy, operator override, or control-plane architecture. + +--- + +## A-07 — Improve diagnostics for “high CPU with falling traffic” and per-process poisoning + +**Category:** detection + +**Finding:** Global high CPU triggered incident declaration, but responders initially considered the concurrent network event; recognizing that the highest-CPU locations had the lowest traffic helped shift the hypothesis. + +**Packet basis:** The packet describes the initial correlation hypothesis and later diagnostic observation. + +**Why it matters:** Global CPU is sensitive but not specific. Earlier discrimination could reduce time to identify a process-level failure. + +**Proposed action:** Alert/visualize per-process saturation, non-terminating request duration, traffic-vs-CPU divergence, recent global rule deployments, and the spatial spread of identical process symptoms. + +**Uncertainty / missing evidence:** The packet does not state which of these signals already existed but were hard to access. + +--- + +## A-08 — Explicitly manage concurrent-incident hypothesis separation and responder capacity + +**Category:** incident response + +**Finding:** Many responders were already working the backbone-congestion incident, and early investigation considered the new CPU problem as potentially correlated. + +**Packet basis:** The packet states both conditions. + +**Why it matters:** Coincident incidents can create anchoring/correlation assumptions and reduce available investigative capacity. + +**Proposed action:** Define a lightweight mechanism to fork incident hypotheses/workstreams, assign independent leads when evidence supports separateness, preserve shared observations, and maintain reserve responder capacity for compound incidents. + +**Uncertainty / missing evidence:** The packet does not provide staffing levels, incident-command roles, or whether resource contention materially lengthened recovery. + +--- + +## A-09 — Automate selective recovery without creating restart storms + +**Category:** recovery + +**Finding:** Repeated restarts recovered poisoned processes and were used globally while the trigger was being found. + +**Packet basis:** The packet reports sample validation followed by broader and repeated restarts. + +**Why it matters:** Restarting was useful, but broad repeated recovery actions can themselves create load, obscure diagnosis, or interact with traffic shifting. + +**Proposed action:** Define health-based selective recycling/quarantine with rate limits, verify capacity before broad restart waves, and preserve diagnostics from poisoned processes before termination where feasible. + +**Uncertainty / missing evidence:** The packet does not report negative effects from the restarts; this is a precautionary inference. + +--- + +## A-10 — Test compound failure and remaining-capacity assumptions + +**Category:** resilience / verification + +**Finding:** Poisoning reduced healthy capacity across regions while Traffic Manager's safety limits constrained further movement and Traffic Manager itself experienced a fault. + +**Packet basis:** The packet reports reduced healthy capacity, safety limits, destination scarcity, and Traffic Manager interruption. + +**Why it matters:** Controls designed for one degraded condition may behave differently when compute loss, traffic movement, and control-system degradation coincide. + +**Proposed action:** Add simulations/load tests for correlated capacity loss plus routing-control degradation; verify that safety limits fail safely and that enough capacity/control remains for recovery. + +**Uncertainty / missing evidence:** The packet does not provide capacity margins or prior compound-failure tests. + +--- + +## A-11 — Require post-remediation verification, not only remediation intent + +**Category:** verification + +**Finding:** The postmortem lists design and process changes, but the packet contains no evidence that they were later implemented or reduced risk. + +**Packet basis:** Implementation/effectiveness of remediations is explicitly unavailable. + +**Why it matters:** A postmortem action list is not evidence that risk changed. + +**Proposed action:** Track each action to implementation, test, owner, completion evidence, and recurrence/leading indicator; later exercise the triggering conditions or a safe equivalent. + +**Uncertainty / missing evidence:** The packet intentionally ends before later verification. + +--- + +## A-12 — Obtain missing architecture and rollout evidence before prioritizing expensive redesign + +**Category:** evidence request + +**Finding:** Several major recommendations depend on facts the packet does not contain. + +**Packet basis:** Explicit unknowns include full architecture/dependency graph, test coverage, rollout criteria, monitoring thresholds, incident command, remediation cost, and independent verification. + +**Why it matters:** Without these, reviewers can identify risk themes but cannot responsibly rank migration, redundancy, monitoring, staffing, and rollout changes by cost/effect. + +**Proposed action:** Before final prioritization, request: dependency/control diagram; test and deployment gates; rollback mechanism; Traffic Manager redundancy/manual controls; relevant SLO/capacity margins; incident-role timeline; and implementation status of follow-ups. + +**Uncertainty / missing evidence:** This finding is itself a request for missing evidence. + +## Method A summary + +The ordinary review identifies a technically conventional set of priorities: + +1. remove the immediate software defect; +2. bound runaway request execution; +3. reduce legacy divergence; +4. improve staged rollout; +5. prevent load-balancing from propagating pathological work; +6. harden the recovery/control system; +7. improve diagnostics; +8. handle concurrent incidents explicitly; +9. make recovery selective; +10. test compound degradation; +11. verify remediation; +12. gather missing evidence before costly redesign. + +No claim is made that these are exhaustive or independently validated. From 4833fe52c788dedd25dbbadf61cdd98af4aa2514 Mon Sep 17 00:00:00 2001 From: Rae Lovejoy Date: Thu, 24 Sep 2026 23:04:12 -0700 Subject: [PATCH 20/66] Run T-003 editorial pilot method D --- .../t003-editorial-pilot-001-method-d.md | 216 ++++++++++++++++++ 1 file changed, 216 insertions(+) create mode 100644 research/papers/coherent-systems/notes/t003-editorial-pilot-001-method-d.md diff --git a/research/papers/coherent-systems/notes/t003-editorial-pilot-001-method-d.md b/research/papers/coherent-systems/notes/t003-editorial-pilot-001-method-d.md new file mode 100644 index 0000000..49ded73 --- /dev/null +++ b/research/papers/coherent-systems/notes/t003-editorial-pilot-001-method-d.md @@ -0,0 +1,216 @@ +# T-003 Editorial Pilot 001 — Method D output + +**Method:** frozen dynamic-coherence review +**Status:** FROZEN EDITORIAL OUTPUT +**Evidence:** frozen Cloudflare June 20, 2024 packet only +**Maximum findings:** 12 +**Independent validation:** no + +## D-01 — The local DDoS function worked against one purpose while relying on incompatible hidden assumptions + +**Evidence / basis:** The new DDoS rule itself was intended to distinguish suspicious traffic while permitting some legitimate clients through cookies. The failure arose because an internally generated rate-limit path reused a key generator in an unanticipated way and a second cookie validator could disagree with the earlier validation. + +**Affected component/party:** DDoS/rate-limit implementation; customers/end users receiving errors. + +**Consequence:** A locally sensible mitigation path became unsafe when assumptions across reused components did not match. + +**Timescale:** Immediate upon triggering request after global deployment. + +**Uncertainty:** Packet does not state why the two validation semantics diverged or how broadly the reused API pattern exists. + +**Implication:** Make cross-component invariants explicit: one canonical cookie-validity contract, forbidden self-referential key-generation relationships, and tests at the actual composition boundary rather than only component-local tests. + +--- + +## D-02 — The deployment changed the system's transition dynamics, not merely its configuration state + +**Evidence / basis:** Before the new rule, the latent implementation defect existed but the packet does not report this failure regime. After global activation, a particular request could permanently consume a worker, after which ordinary balancing actions could spread the same failure condition. + +**Affected component/party:** request-handling service, Unimog, Traffic Manager, global serving capacity. + +**Consequence:** The system acquired a new way of moving from normal operation into self-propagating capacity loss. + +**Timescale:** From deployment through incident propagation. + +**Uncertainty:** The packet does not establish whether another configuration could have triggered the same latent defect previously. + +**Implication:** Change review should ask which **new failure transitions** become possible after a rule/configuration change, not only whether the new rule's intended result is correct. + +--- + +## D-03 — Legacy architecture was retained history that constrained the present failure path + +**Evidence / basis:** The DDoS module used a legacy rate-limiting implementation while customer-configured rules used a newer engine; the affected service was already being considered for replacement. + +**Affected component/party:** DDoS service architecture and maintainers. + +**Consequence:** Earlier architectural choices remained part of the current system and created a distinct risk/maintenance path. + +**Timescale:** Long-lived architectural history preceding the incident; remediation extends beyond immediate rollback. + +**Uncertainty:** The packet does not establish whether the newer engine would have prevented this failure. + +**Implication:** Treat legacy divergence as explicit retained system history: document why it remains, what unique behavior depends on it, what conditions retire it, and how migration preserves required service. + +--- + +## D-04 — Recovery options contracted as the failure propagated + +**Evidence / basis:** Poisoned workloads were redirected into additional servers/data centers; healthy destination capacity became harder to find; Traffic Manager safety limits constrained additional shifts; Traffic Manager then temporarily stopped issuing actions. + +**Affected component/party:** serving capacity, Traffic Manager, incident responders, customers. + +**Consequence:** Each propagation step reduced the set of remaining low-risk recovery actions. A mechanism intended to preserve service narrowed its own future room to maneuver. + +**Timescale:** Minutes during propagation and early recovery. + +**Uncertainty:** The packet does not enumerate all manual or alternative recovery options. + +**Implication:** Incident design should explicitly preserve **response diversity**: quarantine paths, independent control paths, capacity reserves, and rollback/recovery actions whose availability does not depend on the same degraded signals/components. + +--- + +## D-05 — Feedback was available but initially ambiguous because two incident models competed + +**Evidence / basis:** Sustained global CPU triggered automatic incident declaration. Responders were already handling backbone congestion and initially considered a relationship. The observation that high-CPU locations had lower traffic shifted the investigation. + +**Affected component/party:** incident responders and monitoring systems. + +**Consequence:** The system detected mismatch but did not immediately discriminate its mechanism, delaying model revision. + +**Timescale:** Early incident diagnosis. + +**Uncertainty:** The packet does not quantify how much time the initial hypothesis cost. + +**Implication:** Monitoring should expose discriminating relationships, not only alarm magnitude: per-process state, CPU-versus-traffic direction, recent deployments, and whether load moves actually reduce the symptom. + +--- + +## D-06 — A recovery mechanism became part of the causal failure loop + +**Evidence / basis:** Unimog and Traffic Manager reacted to high CPU by moving traffic; moved traffic included requests that poisoned destination processes. + +**Affected component/party:** load-balancing/control systems and destination data centers. + +**Consequence:** Correct local behavior under the load model amplified the higher-level failure. + +**Timescale:** During propagation. + +**Uncertainty:** Packet does not say whether request classification/quarantine was feasible in real time. + +**Implication:** Evaluate recovery/control actions by their effect on the **future state of the whole system**, including whether the action transports the cause of failure. Add containment/circuit-breaking conditions for pathological workload. + +--- + +## D-07 — Revision power depended on multiple control points whose relationship is only partly visible + +**Evidence / basis:** Request-service responders could restart processes; the DDoS rule could be disabled; the Traffic team separately fixed Traffic Manager. The packet does not describe ownership, emergency authority, or manual-control boundaries. + +**Affected component/party:** incident responders and service/control owners. + +**Consequence:** Recovery required coordinated changes across several components; unclear authority/dependency could become a delay under other compound incidents. + +**Timescale:** Incident response and future operations. + +**Uncertainty:** No evidence in the packet shows that authority ambiguity actually caused delay. + +**Implication:** Request a control/authority map for emergency actions: who can stop rollout, disable a rule, quarantine traffic, override routing, restart service, and declare degraded modes; test whether necessary actions remain available when another team/control service is busy or unavailable. + +--- + +## D-08 — Restoring the old service is not necessarily the relevant continuity goal + +**Evidence / basis:** Cloudflare identifies the affected rate-limiting implementation as legacy and reports plans to replace the service while preserving rate-limiting/DDoS protection capability. + +**Affected component/party:** service architecture, operators, customers. + +**Consequence:** Long-term continuity may require replacing the implementation rather than making the old configuration maximally stable. + +**Timescale:** Long-term remediation. + +**Uncertainty:** Replacement design/cost/risk is not in the packet. + +**Implication:** Define continuity at the capability/contract level—safe rate limiting and DDoS mitigation—so transformation away from the legacy service can count as preserving function rather than as system discontinuity. + +--- + +## D-09 — Incident-response capacity was itself a shared dependency under compound stress + +**Evidence / basis:** Many on-duty responders were already engaged with the separate backbone-congestion incident when the second incident was declared. + +**Affected component/party:** incident-response organization. + +**Consequence:** Two technically independent failures competed for limited investigative/coordination capacity and encouraged an initially shared causal hypothesis. + +**Timescale:** Immediate incident response. + +**Uncertainty:** Packet does not prove staffing contention materially extended outage duration. + +**Implication:** Model human incident-response capacity as part of system resilience: reserve/fork response leadership for concurrent incidents and make hypothesis separation explicit. + +--- + +## D-10 — Global promotion transformed a reversible experiment into a network-wide exposure before the rare trigger appeared + +**Evidence / basis:** The rule was first deployed to a small number of production data centers and later globally; the first poisoning event occurred after global deployment. + +**Affected component/party:** deployment system and all production regions. + +**Consequence:** The practical blast radius increased before observation encountered the relevant request pattern. + +**Timescale:** Hours from canary start to first trigger. + +**Uncertainty:** Packet lacks canary duration, traffic composition, promotion rules, and rollback automation. + +**Implication:** Treat rollout as preservation of future reversibility: promotion criteria should depend on representative exposure and automatic stop/rollback signals, not only time elapsed or absence of observed failures. + +--- + +## D-11 — The packet supports displaced technical burden, but not a broad normative finding + +**Evidence / basis:** Traffic moved failures to additional servers/data centers and incident-response attention was shared. The packet contains no evidence about contested customer priorities, governance, labor conditions, or broader social legitimacy. + +**Affected component/party:** destination infrastructure and response teams. + +**Consequence:** Some burden was displaced across the technical/organizational system, but stronger normative conclusions would exceed the evidence. + +**Timescale:** Incident response. + +**Uncertainty:** Distribution of customer and staff burden is not supplied. + +**Implication:** Keep the boundary narrow. Do not manufacture a power/justice claim simply because the review template asks about normative disagreement or externalities. + +--- + +## D-12 — The remediation record changes future expectations only after implementation is verified + +**Evidence / basis:** The packet lists replacement, loop-containment, rollout, capacity, and mitigation improvements but explicitly lacks proof that they were later implemented or effective. + +**Affected component/party:** future operators and customers. + +**Consequence:** A written action plan does not yet change the actual transition dynamics of the production system. + +**Timescale:** Post-incident / future recurrence. + +**Uncertainty:** Later implementation is outside the packet. + +**Implication:** Track remediation from intention → implementation → exercised behavior → observed effectiveness. Until then, treat reduced recurrence risk as unknown. + +## Method D summary + +The dynamic-coherence review emphasizes: + +- hidden cross-component assumptions; +- configuration changes that create new failure transitions; +- legacy architecture as retained history; +- contraction of recovery-option space; +- discriminating feedback rather than alarm volume; +- recovery mechanisms that propagate causes; +- emergency revision/control authority; +- continuity at the capability rather than legacy-implementation level; +- human responder capacity as a dependency; +- rollout as preservation of reversibility; +- evidence boundaries on normative interpretation; +- implementation evidence before claiming adaptation occurred. + +No overall coherence judgment is made. From 82fe7ef6c832b5b3f8d6b058152e189a6c826a59 Mon Sep 17 00:00:00 2001 From: Rae Lovejoy Date: Thu, 24 Sep 2026 23:06:07 -0700 Subject: [PATCH 21/66] Code T-003 editorial pilot 001 --- .../t003-editorial-pilot-001-comparison.md | 314 ++++++++++++++++++ 1 file changed, 314 insertions(+) create mode 100644 research/papers/coherent-systems/notes/t003-editorial-pilot-001-comparison.md diff --git a/research/papers/coherent-systems/notes/t003-editorial-pilot-001-comparison.md b/research/papers/coherent-systems/notes/t003-editorial-pilot-001-comparison.md new file mode 100644 index 0000000..b4c2e0c --- /dev/null +++ b/research/papers/coherent-systems/notes/t003-editorial-pilot-001-comparison.md @@ -0,0 +1,314 @@ +# T-003 Editorial Pilot 001 — comparison and coding + +**Status:** EDITORIAL PILOT RESULT / NOT INDEPENDENT VALIDATION +**Case:** Cloudflare June 20, 2024 incident +**Compared methods:** Method A ordinary incident/system review vs Method D frozen dynamic-coherence review +**Evidence packet:** frozen v0.1 only +**Coders:** same AI-assisted research process that generated both outputs +**Conflict level:** severe; conclusions are protocol-debugging evidence only + +## Executive result + +Pilot 001 is a **near-null result for unique decision value from Method D**. + +The dynamic-coherence review successfully reorganized the incident around: + +- transition dynamics; +- path dependence; +- recovery-option contraction; +- feedback/model revision; +- revision/control power; +- continuity through replacement; +- future reversibility. + +However, nearly every **decision-relevant** Method D finding was already captured substantively by the ordinary review. + +No Method D finding was coded **E1–E2 / D2 / N2**: evidence-supported, decision-relevant, and substantively absent from Method A. + +Method A produced one concrete decision-relevant item with no equally explicit Method D counterpart: **runtime execution bounds/watchdogs for non-terminating request handling** (A-02). That action was also stated as a Cloudflare follow-up in the frozen source packet, so this is not a discovery claim for Method A; it shows that Method D's conceptual breadth did not guarantee complete extraction of ordinary technical remediations. + +The strongest provisional interpretation is: + +> **In this case, dynamic coherence behaved more like a synthesis/reframing layer than a superior incident-review method.** + +That can still be useful. It is not the same as demonstrated added value. + +--- + +## Frozen-output size / crude burden indicators + +| Measure | Method A | Method D | +| --- | ---: | ---: | +| Findings | 12 | 12 | +| Words | 1,521 | 1,490 | +| Characters | 11,833 | 11,997 | +| Core review questions / required lenses | 6 ordinary-review questions | 13 frozen dynamic-coherence questions | +| Human preparation time | not measured | not measured | +| Human analysis time | not measured | not measured | + +The similar output size does **not** mean similar human burden. The dynamic prompt has more conceptual categories and may require more training. This AI-only pilot cannot measure that. + +The earlier automated count of "request/unknown/uncertainty" terms is not used as a research result; it is too crude to represent information-request burden. + +--- + +## Finding-level coding — Method D + +Coding: + +- **E2:** directly supported by packet evidence +- **E1:** reasonable inference with explicit basis +- **E0:** unsupported +- **D2:** plausibly decision-relevant +- **D1:** relevant context / secondary decision value +- **D0:** not materially decision-relevant +- **N2:** substantively absent from Method A +- **N1:** partly present / differently developed +- **N0:** same substantive finding already captured + +| Finding | E | D | N | Closest Method A finding(s) | Coding note | +| --- | --- | --- | --- | --- | --- | +| D-01 hidden incompatible assumptions | E2 | D2 | N0 | A-01 | Same defect/composition problem; D emphasizes assumption fit. | +| D-02 deployment changed failure transitions | E1 | D1 | N1 | A-01, A-04, A-05 | Useful abstraction, but resulting actions are already covered by defect, rollout, and propagation review. | +| D-03 legacy architecture as retained history | E2 | D2 | N0 | A-03 | Same migration/dependency issue. | +| D-04 recovery-option contraction | E2 | D2 | N1 | A-05, A-06, A-10 | Strong synthesis of several ordinary findings; no clearly new action beyond quarantine/control redundancy/compound-failure testing. | +| D-05 feedback/model ambiguity | E2 | D2 | N0 | A-07 | Same diagnostic requirement. | +| D-06 recovery mechanism amplified failure | E2 | D2 | N0 | A-05 | Same propagation-aware containment finding. | +| D-07 revision power/control map | E1 | D1 | N1 | A-08, A-12 | Method D makes authority/control topology more explicit; packet does not show it caused delay. | +| D-08 continuity through service replacement | E2 | D2 | N0 | A-03 | Same long-term replacement/migration direction, reframed around capability continuity. | +| D-09 responder capacity as shared dependency | E1/E2 | D2 | N0 | A-08 | Same concurrent-incident staffing/hypothesis issue. | +| D-10 rollout as preserved reversibility | E2 | D2 | N0 | A-04 | Same rollout/rollback/blast-radius change. | +| D-11 boundary restraint on normative claims | E2 | D0 | N2 | none | Methodological restraint absent from A, but it does not change the technical decision in this case. | +| D-12 remediation intent vs verified change | E2 | D2 | N0 | A-11 | Same verification requirement. | + +### Method D decision-relevant novelty count + +- **E1–E2 / D2 / N2:** **0** +- **E1–E2 / D2 / N1:** **1 clear synthesis candidate (D-04)**, with D-02 and D-07 below D2 threshold in this pilot +- **D0 / N2:** **1 (D-11)** — useful evidence-boundary discipline, not an incident remediation finding + +--- + +## Finding-level coding — Method A + +| Finding | E | D | N | Closest Method D finding(s) | Coding note | +| --- | --- | --- | --- | --- | --- | +| A-01 fix validator/API recursion defect | E2 | D2 | N0 | D-01, D-02 | Same core failure path. | +| A-02 execution bounds/watchdog | E2 | D2 | N2 | no direct counterpart | Concrete containment action omitted by D despite being present in packet follow-up. | +| A-03 retire/isolate legacy rate limiter | E2 | D2 | N0 | D-03, D-08 | Same architectural change. | +| A-04 rollout/promotion/stop criteria | E2 | D2 | N0 | D-10 | Same blast-radius/reversibility issue. | +| A-05 propagation-aware traffic shifting | E2 | D2 | N0 | D-04, D-06 | Same amplification loop. | +| A-06 harden Traffic Manager | E2 | D2 | N0/N1 | D-04, D-07 | D covers response diversity/control points, though A is more component-specific. | +| A-07 high-CPU/low-traffic diagnostics | E2 | D2 | N0 | D-05 | Same feedback discrimination. | +| A-08 concurrent-incident response capacity | E1/E2 | D2 | N0 | D-09 | Same organizational dependency. | +| A-09 selective recovery/restart control | E1 | D1/D2 | N1 | D-04, D-06 | D covers recovery-option diversity but not this precise operational precaution. | +| A-10 compound failure testing | E1/E2 | D2 | N1 | D-04, D-06 | D synthesizes the mechanisms but does not state the same test as directly. | +| A-11 post-remediation verification | E2 | D2 | N0 | D-12 | Same verification requirement. | +| A-12 missing architecture/rollout evidence | E2 | D2 | N1 | D-07, D-12 | Broader ordinary evidence request. | + +### Method A decision-relevant novelty count + +- **E1–E2 / D2 / N2:** **1 (A-02)** +- Several N1 findings are more implementation-specific versions of Method D synthesis. + +Again, A-02 is **not** proof that ordinary review is generally superior; it was explicitly available in the packet's source-reported remediation. + +--- + +## Overlap map + +A compact view: + + immediate software assumptions/defect + A-01 <-> D-01 / D-02 + + legacy implementation + A-03 <-> D-03 / D-08 + + rollout / reversibility + A-04 <-> D-10 + + failure propagation / shrinking recovery space + A-05 / A-06 / A-10 <-> D-04 / D-06 / D-07 + + feedback / diagnosis + A-07 <-> D-05 + + concurrent responder capacity + A-08 <-> D-09 + + remediation verification + A-11 <-> D-12 + + missing evidence + A-12 <-> D-07 / D-12 + + ordinary-only in this output + A-02 execution bounds + A-09 selective restart detail + + dynamic-only in this output + D-11 explicit refusal to manufacture normative claims + D-04's unified "recovery-option contraction" framing (partially novel synthesis, not novel action) + +--- + +## False alarms / unsupported extrapolation + +No finding was coded as a clear **E0** false alarm. + +However: + +- A-09's warning about restart storms is precautionary; the packet reports no restart-induced harm and the output marks this uncertainty. +- D-07's concern about emergency control/authority topology is reasonable but the packet does not show that authority ambiguity caused delay. +- D-02's "transition dynamics" is a conceptual interpretation of the reported propagation mechanism, not an independently measured variable. +- D-11 is deliberately a non-finding: it constrains overinterpretation rather than asserting a power/justice conclusion unsupported by the packet. + +The absence of obvious false alarms in a self-coded AI pilot is weak evidence because the same reasoning process generated and judged the claims. + +--- + +## What Method D did add + +Even without an N2/D2 finding, three forms of added organization may be worth further testing. + +### 1. One frame for several recovery failures + +D-04 combines: + +- spreading poison; +- declining healthy capacity; +- load-balancer safety limits; +- Traffic Manager failure; + +into the question: + +> How is the system's **remaining response space** changing while it tries to recover? + +Method A identifies the components separately. + +Whether this synthesis improves real incident decisions is **unknown**. + +### 2. Explicit state-versus-transition distinction + +D-02 asks whether a deployment introduces a new **way the system can fail next**, not merely whether the intended configuration is correct. + +Ordinary hazard/reliability methods may already capture this more precisely. Future baseline comparison should test that rather than credit UCF automatically. + +### 3. Capability-level continuity + +D-08 distinguishes: + +> preserve the rate-limiting/DDoS capability + +from: + +> preserve the legacy implementation. + +This is conceptually useful but Method A already recommends retirement/migration, so the pilot shows framing value rather than unique detection. + +--- + +## Protocol defects discovered + +### P1 — The packet includes Cloudflare's remediation conclusions + +Both methods can reproduce source-provided actions. + +That makes Pilot 001 useful for **coverage and framing**, but weak for testing discovery. + +**Revision:** A later editorial pilot may use a clearly labeled artificially truncated packet that ends before the remediation section. This would test what each method derives from the architecture/timeline/failure mechanism alone. It must not be confused with a real blinded study. + +### P2 — Method A is broad enough to absorb many dynamic questions + +A competent ordinary incident review already asks about: + +- dependencies; +- propagation; +- containment; +- recovery; +- rollout; +- monitoring; +- compound failure. + +This is not a defect in Method A; it is precisely the comparator UCF must beat or complement. + +**Implication:** Future studies should expect a null result unless dynamic coherence adds something more specific than systems-thinking vocabulary. + +### P3 — The case does not exercise the agency-envelope construct + +This technical incident has operators and customers, but the packet is not centered on substantive human opportunity/feasibility. + +**Implication:** Do not infer anything about the value of agency-envelope language from Pilot 001. + +### P4 — STPA remains absent + +The related-work note identifies STPA as a competent baseline for appropriate socio-technical control problems. + +**Implication:** The pilot cannot establish value against a mature safety method. + +### P5 — Same-model coding is too favorable to coherence among outputs + +One AI process generated A, D, and the coding. + +**Implication:** Independent review is essential before any method-quality claim. + +### P6 — Method burden remains unmeasured + +Method D had 13 conceptual lenses versus Method A's 6 review prompts, but outputs were similar length. + +**Implication:** Human preparation/application burden could still differ substantially and must be measured in later work. + +--- + +## Decision from Pilot 001 + +### Do not + +- claim dynamic coherence outperformed ordinary review; +- claim novel detection; +- add a validated-method label; +- increase the framework's evidentiary status; +- use this case as proof that dynamic coherence is necessary. + +### Do + +- retain dynamic coherence as a **candidate synthesis / review lens**; +- preserve the state-versus-transition and future-response-space questions for further comparison; +- strengthen the requirement that added value must be demonstrated against competent methods; +- run at least one better discovery-oriented editorial pilot before recruiting independent reviewers; +- keep the explicit retirement condition. + +--- + +## Pilot conclusion + +Pilot 001 **failed to show unique decision-relevant added value** from Method D. + +That is not a failure of the research program. + +It is exactly the sort of result the protocol was designed to permit. + +The current evidence supports a narrower claim: + +> **Dynamic coherence may provide a useful integrative language for connecting findings that ordinary systems/reliability review already discovers. Whether that integration improves decisions, transfer across domains, or reviewer performance remains unknown.** + +If future comparisons continue to find no unique or burden-reducing value, Root Sequence should treat dynamic coherence as conceptual routing language rather than a distinct analysis method. + +--- + +## Next experiment + +**Editorial Pilot 002 candidate:** + +Use the same incident, but freeze a second packet that omits Cloudflare's remediation/follow-up section while retaining the architecture, timeline, failure mechanism, response, and explicit unknowns. + +Purpose: + +- reduce simple reproduction of source conclusions; +- test whether Method A and Method D independently derive useful remediations; +- compare omissions more meaningfully. + +This would still be an artificial editorial exercise, not independent validation. + +After Pilot 002, decide whether the protocol is stable enough to justify an independent reviewer comparison on a different case. From f863d87155e586e2813b4d21ce3a0c77d2526c15 Mon Sep 17 00:00:00 2001 From: Rae Lovejoy Date: Thu, 24 Sep 2026 23:07:09 -0700 Subject: [PATCH 22/66] Freeze T-003 Pilot 002 remediation-withheld packet --- ...et-cloudflare-2024-06-20-no-remediation.md | 204 ++++++++++++++++++ 1 file changed, 204 insertions(+) create mode 100644 research/papers/coherent-systems/notes/t003-evidence-packet-cloudflare-2024-06-20-no-remediation.md diff --git a/research/papers/coherent-systems/notes/t003-evidence-packet-cloudflare-2024-06-20-no-remediation.md b/research/papers/coherent-systems/notes/t003-evidence-packet-cloudflare-2024-06-20-no-remediation.md new file mode 100644 index 0000000..394c76b --- /dev/null +++ b/research/papers/coherent-systems/notes/t003-evidence-packet-cloudflare-2024-06-20-no-remediation.md @@ -0,0 +1,204 @@ +# T-003 frozen evidence packet — Cloudflare June 20, 2024 + +**Packet version:** 0.2 / remediation-withheld editorial packet +**Status:** FROZEN FOR EDITORIAL PILOT 002 +**Prepared:** 2026-09-24 +**Primary source:** Cloudflare incident postmortem published June 26, 2024 +**Source URL:** https://blog.cloudflare.com/cloudflare-incident-on-june-20-2024/ + +## Use rule + +This document is the **entire factual evidence packet** for T-003 Editorial Pilot 002. + +Reviewers/methods may reason from these facts, identify missing information, and request more evidence. They may not silently import facts from the live article, other Cloudflare incidents, general Cloudflare knowledge, or external sources. + +The packet is a project-authored paraphrase of the source, not an independent account. + +--- + +## Decision question + +> Given only this evidence packet, what design, operational, rollout, monitoring, dependency, and recovery changes should be prioritized to reduce recurrence or impact of a similar incident? + +--- + +## System background supplied in the source + +Cloudflare describes two systems involved in traffic balancing: + +- **Unimog**, an edge load balancer, directs packets to an appropriate server and attempts to keep CPU load balanced across active servers within a data center. +- **Traffic Manager** uses global signals including CPU utilization, HTTP request latency, and bandwidth utilization to issue rebalancing decisions across data centers. Cloudflare states that it has safety limits intended to prevent overly large traffic shifts and that it considers expected load at destination locations. + +The affected HTTP rate-limiting path was used in a new DDoS mitigation mechanism combining rate limits and cookies. + +--- + +## Incident-level outcome + +Cloudflare reports that two independent events increased latency and error rates for Internet properties and Cloudflare services for 114 minutes. + +During the peak 30-minute impact: + +- approximately 1.4–2.1% of HTTP requests to Cloudflare's CDN received a generic error page; +- p99 Time To First Byte latency rose to almost three times its prior level. + +The two reported events were: + +1. automated network monitoring detected degradation and rerouted traffic suboptimally, creating backbone congestion between approximately 17:33 and 17:50 UTC; +2. a newly deployed DDoS mitigation mechanism exposed a latent bug in the rate-limiting system, allowing a particular request form to put a request-handling process into a non-terminating loop. + +The postmortem focuses mainly on the second event. + +--- + +## Deployment timeline + +All times below are UTC on 2024-06-20. + +- **14:14:** gradual deployment of the new DDoS rule began. +- **17:06:** deployment reached all data centers. +- **17:47:** first request-handling process entered the poisoned/non-terminating state. +- **18:04:** incident automatically declared after sustained high global CPU load. +- **18:34:** engineers showed that restarting the service recovered one server; a full restart was tested in one data center. +- **18:44:** CPU load normalized in that data center after restart. +- **18:51:** repeated global reloads/restarts began for servers with many stuck processes. +- **19:05:** HTTP error rate peaked; Traffic Manager began actions that helped recover service. +- **19:11:** service-unavailable HTTP error rate had roughly halved. +- **19:27:** global HTTP error rate returned to baseline. +- **19:29:** the DDoS rule deployment was identified as the likely trigger for process poisoning. +- **19:34:** the DDoS rule was fully disabled. +- **19:43:** engineers stopped routine restarts on heavily affected servers. +- **20:16:** incident response stood down. + +--- + +## Failure mechanism described by Cloudflare + +The new DDoS mitigation path: + +1. checked for a valid cookie; +2. for a valid cookie, added a rate-limit rule based on the cookie value; +3. later evaluated the generated rate-limit rules. + +Cloudflare reused existing rate-limit key-generation logic. + +The postmortem identifies two interacting software problems: + +- internally generated rate-limit rules used an API path in an unanticipated way, causing the parent key generator to point back to the same cookie-key function; +- a second cookie-validation function could disagree with the earlier validation when a request contained multiple cookies with mixed validity. + +Under the triggering request, the key-generation function called itself repeatedly. + +Because the Lua implementation used proper tail calls, the recursion did not necessarily grow the call stack until failure. Instead, the request-handling process could remain in a loop consuming 100% CPU. + +A process that entered this state stopped serving later requests. + +--- + +## Failure propagation described by Cloudflare + +Each server had many request-handling processes, so one poisoned process alone had limited effect. + +As more processes became CPU-saturated: + +1. Unimog shifted new traffic away from higher-load servers toward servers with more available capacity. +2. Rising CPU utilization at a data-center level caused Traffic Manager to redirect traffic toward other data centers. +3. Redirected traffic included requests capable of poisoning processes, spreading the same failure condition to previously less-affected servers/data centers. + +Cloudflare reports that this made healthy destination capacity progressively harder to find. + +Traffic Manager's built-in safety limits also constrained how much additional traffic could be shifted. + +At one point reported in the postmortem, approximately 10% of HTTP-request capacity in Western Europe and 4% in Eastern Europe was CPU-saturated. + +--- + +## Incident-response information + +Automatic alerting notified engineers when sustained global CPU utilization crossed a threshold. + +Many incident responders were already engaged with the separate backbone-congestion incident. + +In the early investigation, responders considered whether the high CPU condition was related to the existing network incident. + +The source says it took time to notice that the highest-CPU locations were receiving the *lowest* traffic, which moved investigation away from the network event as the initiating cause. + +Responders then pursued two parallel activities: + +- determine whether restarting poisoned processes would recover them and perform broader restarts; +- identify what triggered processes to enter the CPU-saturated state. + +Cloudflare reports that it took about 25 minutes after incident declaration to validate restart recovery on a sample server, followed roughly five minutes later by broader restarts. + +--- + +## Additional Traffic Manager failure + +During the same incident conditions, a latent bug in Traffic Manager was also triggered. + +Cloudflare says Traffic Manager attempted a graceful restart after the exception, which halted its activity. + +The bug first triggered at approximately 18:17 UTC and then repeatedly between 18:35 and 18:57. + +During two reported intervals—approximately 18:35–18:52 and 18:56–19:05—Traffic Manager issued no new traffic-routing actions. + +This left significant traffic rerouted away from locations whose request service had already begun recovering. + +Alerting notified the Traffic team; Cloudflare reports that by 19:05 the team had written, tested, and deployed a fix. + +--- + +## Immediate mitigation + +Cloudflare used repeated rolling/global restarts of the affected request-handling service while investigating the trigger. + +The new DDoS rule was rolled back/disabled globally. + +Cloudflare stated that the rule would remain disabled until the broken cookie-validation condition was fixed and the recurrence risk addressed. + +--- + +## Intentionally withheld source material for Pilot 002 + +The primary postmortem contains a follow-up/remediation section after the immediate mitigation. + +For this editorial discovery test, those proposed future changes are intentionally omitted from the evidence packet. + +Review methods know that source-authored follow-up material has been withheld, but they do not receive its contents. + +This artificial omission is designed only to test whether the review prompts can derive useful actions from the architecture, timeline, failure mechanism, propagation, response, and immediate mitigation. It is **not** a representation of how a real incident reviewer should ignore available evidence. + +--- + +## Explicit unknowns / unavailable information + +The packet does **not** provide: + +- internal code or full architecture; +- detailed organizational ownership boundaries; +- complete rollout criteria, canary size, or promotion thresholds; +- unit/integration/test coverage before deployment; +- exact monitoring/alert thresholds; +- customer-by-customer impact distribution; +- detailed incident command structure; +- staffing or workload details beyond responders already working another incident; +- cost estimates for remediation options; +- full chronology for the first network-congestion event; +- proof that the listed remediations were later implemented or effective; +- a complete dependency graph; +- a formal safety/control analysis; +- independent verification of Cloudflare's account. + +Review methods should identify needed missing information rather than inventing it. + +--- + +## Evidence-status boundary + +Treat the packet as: + +- **SOURCE-REPORTED OBSERVATION** for Cloudflare's stated metrics, timeline, architecture, failure mechanism, and remediation; +- **UNKNOWN** for facts not supplied; +- **ANALYTICAL INFERENCE** for any causal or design conclusion produced by a review method. + +No claim in the pilot should be described as independently established merely because it appears in this packet. From 289042c25acea6b374aecb6662afaf1d2a37ae8d Mon Sep 17 00:00:00 2001 From: Rae Lovejoy Date: Thu, 24 Sep 2026 23:07:12 -0700 Subject: [PATCH 23/66] Preregister T-003 editorial pilot 002 --- .../t003-editorial-pilot-002-registration.md | 103 ++++++++++++++++++ 1 file changed, 103 insertions(+) create mode 100644 research/papers/coherent-systems/notes/t003-editorial-pilot-002-registration.md diff --git a/research/papers/coherent-systems/notes/t003-editorial-pilot-002-registration.md b/research/papers/coherent-systems/notes/t003-editorial-pilot-002-registration.md new file mode 100644 index 0000000..e5b098f --- /dev/null +++ b/research/papers/coherent-systems/notes/t003-editorial-pilot-002-registration.md @@ -0,0 +1,103 @@ +# T-003 Editorial Pilot 002 — preregistration + +**Status:** FROZEN BEFORE METHOD OUTPUTS +**Pilot type:** AI-assisted editorial discovery test; not independent validation +**Date frozen:** 2026-09-24 + +## Purpose + +Pilot 001 showed near-total overlap between ordinary review and dynamic-coherence review, but the evidence packet included Cloudflare's own follow-up/remediation conclusions. + +Pilot 002 keeps the same case and the same two method prompts while replacing only the evidence packet with a version that explicitly withholds the source postmortem's future-remediation section. + +The purpose is to test **derivation coverage**, not real-world predictive validity. + +## Frozen artifacts + +- Protocol blob: `d37f8cd1091f0712943636e0811902c0a1559169` +- Case-selection blob: `504a03627858974b914b2a02603ea4ca1c7443e4` +- Pilot 002 packet: `t003-evidence-packet-cloudflare-2024-06-20-no-remediation.md` + - blob SHA: `394c76b7a30cfe5210a79d780d7f40475b647ac5` +- Method A prompt: **identical to Pilot 001 registration** +- Method D prompt: **identical frozen 13-question dynamic-coherence prompt** + +## Decision question + +> Given only the frozen evidence packet, what design, operational, rollout, monitoring, dependency, and recovery changes should be prioritized to reduce recurrence or impact of a similar incident? + +## What changed from Pilot 001 + +Only the evidence packet. + +Removed from reviewers: + +- source-authored long-term rate-limiter architecture follow-up; +- source-authored loop-containment follow-up; +- source-authored staging/rollout follow-up; +- source-authored backbone-capacity/mitigation follow-up. + +Retained: + +- architecture; +- incident outcome; +- timeline; +- software failure mechanism; +- failure propagation; +- incident response; +- additional Traffic Manager failure; +- immediate mitigation; +- explicit unknowns. + +## Methods + +### Method A + +Use the exact competent ordinary incident/system review prompt preregistered for Pilot 001. + +### Method D + +Use the exact frozen dynamic-coherence prompt preregistered for Pilot 001. + +Maximum 12 findings each. + +## Conflict statement + +Same severe conflict as Pilot 001: one AI-assisted research process prepares the packet, generates both outputs, and codes them. + +No superiority, reliability, novelty, or independent agreement can be inferred. + +## Comparison goals + +After both outputs are frozen, code: + +1. which concrete remediations each method independently derives; +2. which findings overlap; +3. which findings are unique but decision-relevant; +4. unsupported extrapolations; +5. whether Method D's broader concepts create actionable differences or mainly reframing; +6. whether either method reconstructs the withheld source-remediation themes. + +## Withheld-remediation reconstruction is not a gold-standard score + +The omitted source actions are not assumed complete or correct. + +A method is **not** rewarded merely for matching Cloudflare's choices. + +A novel, well-supported alternative may be useful. + +Likewise, failure to reconstruct a source action is not automatically an error. + +## Null result + +A valid null remains: + +> Method D adds no clear decision-relevant finding beyond Method A, even when both must derive actions without seeing the source follow-up section. + +## Stop rule + +After Pilot 002, do not keep tuning prompts against this same incident. + +Either: + +- freeze the protocol for independent review on a different case; or +- narrow the framework/method if the second editorial result exposes redundancy or instability. From 65270755ca8aaff93207d1c87c19ef1065ee0a92 Mon Sep 17 00:00:00 2001 From: Rae Lovejoy Date: Thu, 24 Sep 2026 23:08:39 -0700 Subject: [PATCH 24/66] Run T-003 editorial pilot 002 method A --- .../t003-editorial-pilot-002-method-a.md | 212 ++++++++++++++++++ 1 file changed, 212 insertions(+) create mode 100644 research/papers/coherent-systems/notes/t003-editorial-pilot-002-method-a.md diff --git a/research/papers/coherent-systems/notes/t003-editorial-pilot-002-method-a.md b/research/papers/coherent-systems/notes/t003-editorial-pilot-002-method-a.md new file mode 100644 index 0000000..59115ee --- /dev/null +++ b/research/papers/coherent-systems/notes/t003-editorial-pilot-002-method-a.md @@ -0,0 +1,212 @@ +# T-003 Editorial Pilot 002 — Method A output + +**Method:** competent ordinary incident/system review +**Status:** FROZEN EDITORIAL OUTPUT +**Evidence:** remediation-withheld Cloudflare June 20, 2024 packet only +**Maximum findings:** 12 +**Independent validation:** no + +## A2-01 — Eliminate the inconsistent validation and self-referential key-generation path + +**Category:** prevention + +**Finding:** The observed failure required a key generator that could point back to itself plus a second cookie validator that could disagree with the earlier validation. + +**Evidence / basis:** Frozen packet failure-mechanism section. + +**Why it matters:** The same triggering request pattern can recur as long as both conditions remain possible. + +**Proposed action:** Define one canonical cookie-validity contract at the composition boundary; prevent self-referential key-generator configuration; add tests for internally generated rate-limit rules and mixed-validity cookie inputs. + +**Uncertainty / missing evidence:** Existing type/interface guards and test coverage are not supplied. + +--- + +## A2-02 — Bound request execution so non-terminating logic cannot permanently consume a worker + +**Category:** containment + +**Finding:** Proper tail calls allowed the loop to continue without ordinary stack exhaustion while the process consumed full CPU and stopped serving later requests. + +**Evidence / basis:** Frozen packet reports indefinite CPU-saturating request loops. + +**Why it matters:** Execution bounds contain unknown future logic defects even when prevention tests miss them. + +**Proposed action:** Add a safe request-level CPU/time/instruction watchdog or equivalent cancellation/worker-recycling boundary; define the failure response and test it under load. + +**Uncertainty / missing evidence:** The packet does not identify the safest enforcement layer or performance overhead. + +--- + +## A2-03 — Strengthen canary promotion criteria and rollback controls for global mitigation rules + +**Category:** prevention / blast-radius control + +**Finding:** The rule moved from a handful of production data centers to global deployment before the rare triggering request appeared. + +**Evidence / basis:** Deployment timeline. + +**Why it matters:** Geographic staging alone cannot reveal a request-dependent bug if canary traffic does not exercise the failing path. + +**Proposed action:** Require representative traffic exposure, minimum observation criteria, explicit stop signals, and fast rollback before global promotion of new network-wide mitigation behavior. + +**Uncertainty / missing evidence:** Existing canary size, promotion criteria, and rollback automation are unavailable. + +--- + +## A2-04 — Prevent load balancing from propagating a workload-induced failure + +**Category:** containment + +**Finding:** Unimog and Traffic Manager moved traffic away from high-CPU locations, but that traffic carried requests that could poison destination processes. + +**Evidence / basis:** Frozen packet failure-propagation section. + +**Why it matters:** A normal balancing response amplified the incident by transporting its trigger. + +**Proposed action:** Add a way to distinguish/quarantine pathological request classes or affected service instances before global rebalancing; combine load signals with failure-mode signals. + +**Uncertainty / missing evidence:** Real-time identifiability of the triggering request class is unknown. + +--- + +## A2-05 — Harden Traffic Manager against the same degraded conditions it is expected to manage + +**Category:** containment / recovery + +**Finding:** Traffic Manager itself hit a latent bug and temporarily stopped issuing routing actions while traffic remained shifted away from recovering locations. + +**Evidence / basis:** Frozen packet additional Traffic Manager failure. + +**Why it matters:** A recovery-critical control system failed during the event it was helping manage. + +**Proposed action:** Test Traffic Manager under compound degraded states; isolate exception handling so one fault cannot halt all new actions; define bounded manual/degraded operation and alert directly on loss of control action. + +**Uncertainty / missing evidence:** Redundancy/manual controls are not described. + +--- + +## A2-06 — Add diagnostics that distinguish overload from poisoned-process behavior + +**Category:** detection + +**Finding:** Sustained global CPU triggered the incident, but responders initially considered the concurrent network issue. The high-CPU/low-traffic relationship helped separate the hypotheses. + +**Evidence / basis:** Frozen packet incident-response section. + +**Why it matters:** Earlier mechanism discrimination can shorten diagnosis and reduce unnecessary traffic movement. + +**Proposed action:** Surface per-process saturation/request-duration signals, CPU-versus-traffic divergence, recent rule deployments, and whether rebalancing actually reduces CPU symptoms. + +**Uncertainty / missing evidence:** Existing observability beyond the reported signals is unknown. + +--- + +## A2-07 — Separate concurrent incidents operationally as soon as evidence supports independent causes + +**Category:** incident response + +**Finding:** Many responders were already working a backbone-congestion event, and early investigation treated correlation as plausible. + +**Evidence / basis:** Frozen packet. + +**Why it matters:** Concurrent incidents can consume the same response capacity and anchor diagnosis on a shared cause. + +**Proposed action:** Fork independent workstreams with explicit hypothesis owners while preserving a shared timeline and cross-incident evidence; maintain reserve response capacity for compound events. + +**Uncertainty / missing evidence:** The packet does not show how much staffing or anchoring extended the incident. + +--- + +## A2-08 — Make process recycling selective, rate-limited, and evidence-preserving + +**Category:** recovery + +**Finding:** Restarting a sample server worked, after which broader repeated restarts became an important mitigation. + +**Evidence / basis:** Frozen packet timeline/response. + +**Why it matters:** Broad restart waves can restore capacity but may also add transient load or destroy diagnostic state. + +**Proposed action:** Automate health-based selective recycling/quarantine with rate limits and capture enough diagnostic evidence before termination when feasible. + +**Uncertainty / missing evidence:** The packet reports no restart-induced harm; the precaution is inferred. + +--- + +## A2-09 — Test compound capacity loss, control-system degradation, and balancing safety limits together + +**Category:** resilience / verification + +**Finding:** Healthy capacity fell across regions, destination choices narrowed, Traffic Manager safety limits constrained shifts, and Traffic Manager itself stopped issuing actions for periods. + +**Evidence / basis:** Frozen packet propagation and control-system failure. + +**Why it matters:** Independently sensible protections may interact poorly during multi-layer degradation. + +**Proposed action:** Run fault/load simulations that combine worker poisoning, capacity scarcity, safety-limit activation, and partial Traffic Manager failure. + +**Uncertainty / missing evidence:** Capacity headroom and existing compound tests are unavailable. + +--- + +## A2-10 — Verify that rollout and recovery controls fail safely when the trigger is rare + +**Category:** verification + +**Finding:** The bug did not manifest during initial staging and only appeared after global deployment. + +**Evidence / basis:** Frozen deployment timeline. + +**Why it matters:** A test regime that observes only common traffic may produce false confidence. + +**Proposed action:** Add targeted adversarial/property-based request generation around cookie combinations and generated rate-limit composition; exercise rollback/restart under the same test. + +**Uncertainty / missing evidence:** The packet does not describe pre-deployment test generation. + +--- + +## A2-11 — Treat remaining healthy capacity and independent recovery paths as explicit incident resources + +**Category:** recovery planning + +**Finding:** As the failure spread, suitable destinations became harder to find and the normal routing controller was partly unavailable. + +**Evidence / basis:** Frozen packet. + +**Why it matters:** Recovery depended on resources that were being consumed by the incident itself. + +**Proposed action:** Define minimum reserve capacity and at least one recovery/control path whose availability is not coupled to the same service/control failure; test when the system should stop shifting traffic and enter a more conservative degraded mode. + +**Uncertainty / missing evidence:** The packet does not show current reserve targets or independent control paths. + +--- + +## A2-12 — Obtain missing evidence before ranking major architecture changes + +**Category:** evidence request + +**Finding:** The packet lacks enough information to rank large redesigns against narrower containment and process changes. + +**Evidence / basis:** Explicit unknowns in the packet. + +**Proposed action:** Request the dependency/control diagram, test coverage, canary/promotion rules, rollback controls, monitoring thresholds, Traffic Manager redundancy/manual controls, capacity margins, and incident-command timeline before final prioritization. + +**Uncertainty / missing evidence:** This finding is itself a request for missing evidence. + +## Method A Pilot 002 summary + +Without seeing Cloudflare's follow-up/remediation section, the ordinary review independently derives: + +- fix the immediate composition defect; +- execution bounds; +- stronger canary/rollback; +- propagation-aware balancing; +- recovery-control hardening; +- mechanism-specific diagnostics; +- concurrent-incident separation; +- selective recovery; +- compound-failure testing; +- rare-trigger testing; +- reserve/independent recovery capacity; +- additional evidence before expensive redesign. From 42af5e91b4caf9ab30865240e86882122e884941 Mon Sep 17 00:00:00 2001 From: Rae Lovejoy Date: Thu, 24 Sep 2026 23:08:41 -0700 Subject: [PATCH 25/66] Run T-003 editorial pilot 002 method D --- .../t003-editorial-pilot-002-method-d.md | 214 ++++++++++++++++++ 1 file changed, 214 insertions(+) create mode 100644 research/papers/coherent-systems/notes/t003-editorial-pilot-002-method-d.md diff --git a/research/papers/coherent-systems/notes/t003-editorial-pilot-002-method-d.md b/research/papers/coherent-systems/notes/t003-editorial-pilot-002-method-d.md new file mode 100644 index 0000000..3a9fc16 --- /dev/null +++ b/research/papers/coherent-systems/notes/t003-editorial-pilot-002-method-d.md @@ -0,0 +1,214 @@ +# T-003 Editorial Pilot 002 — Method D output + +**Method:** frozen dynamic-coherence review +**Status:** FROZEN EDITORIAL OUTPUT +**Evidence:** remediation-withheld Cloudflare June 20, 2024 packet only +**Maximum findings:** 12 +**Independent validation:** no + +## D2-01 — Composition assumptions failed even though the new mitigation's local logic was intelligible + +**Evidence / basis:** A generated rate-limit rule reused key-generation logic whose parent could point back to itself, while two cookie-validity checks could disagree. + +**Affected component/party:** DDoS/rate-limit composition; customers/end users. + +**Consequence:** A feature that made sense locally created an unsafe composed behavior. + +**Timescale:** Immediate once triggered after deployment. + +**Uncertainty:** Existing interface contracts and tests are unknown. + +**Implication:** Make cross-component assumptions explicit and executable: one validity contract, forbidden self-reference, and composition-level tests. + +--- + +## D2-02 — The rule changed which failure trajectories were reachable + +**Evidence / basis:** The latent defects existed in reused logic, but activating the new rule created a path in which a specific request could permanently consume a worker and balancing could spread the trigger. + +**Affected component/party:** request workers, load balancing, regional/global capacity. + +**Consequence:** The deployment added a new transition from ordinary operation to self-propagating capacity loss. + +**Timescale:** Deployment to incident propagation. + +**Uncertainty:** Other configurations capable of triggering the same defects are not described. + +**Implication:** Change review should model new reachable failure transitions, including rare composition/input interactions, before broad promotion. + +--- + +## D2-03 — Reused implementation history constrained the present system even without explicit legacy status + +**Evidence / basis:** The new behavior reused an existing portion of rate-limit key-generation logic and internal APIs in an unanticipated composition. + +**Affected component/party:** rate-limiting architecture and maintainers. + +**Consequence:** Previously acceptable implementation choices became part of a new failure path when reused under different assumptions. + +**Timescale:** Historical implementation choice becoming relevant during new feature deployment. + +**Uncertainty:** The age, ownership, or broader reuse of the component is not supplied. + +**Implication:** Treat reuse as inherited constraint: document the assumptions under which a component was designed, and require compatibility/invariant review when used in a new generated-rule path. + +--- + +## D2-04 — The system consumed its own future recovery options while attempting to stabilize + +**Evidence / basis:** Balancing moved poison-capable traffic to additional locations; healthy destination capacity fell; safety limits constrained further shifting; Traffic Manager then stopped issuing actions for periods. + +**Affected component/party:** serving capacity, Traffic Manager, incident responders, customers. + +**Consequence:** The system's available recovery action space narrowed as its protective mechanisms operated. + +**Timescale:** Minutes during propagation. + +**Uncertainty:** Full set of manual/alternative actions is unavailable. + +**Implication:** Preserve response diversity explicitly: quarantine, reserve capacity, independent control paths, and a degraded mode that does not rely on the same propagation/control loop. + +--- + +## D2-05 — Feedback detected distress before it identified the mechanism + +**Evidence / basis:** High global CPU triggered incident declaration; concurrent backbone congestion supplied a plausible competing explanation; high-CPU/low-traffic evidence later changed the working model. + +**Affected component/party:** monitoring and incident-response teams. + +**Consequence:** Mismatch was visible, but the feedback was initially insufficient to distinguish causal models. + +**Timescale:** Early diagnosis. + +**Uncertainty:** Exact diagnostic delay is unknown. + +**Implication:** Add feedback that discriminates mechanisms: per-process execution duration, CPU/traffic direction, deployment correlation, and whether balancing actions improve or worsen the symptom. + +--- + +## D2-06 — Load balancing was coherent locally but incoherent with the failure mechanism + +**Evidence / basis:** Unimog and Traffic Manager redirected traffic away from high-load servers/data centers, as designed; redirected traffic carried requests that reproduced poisoning. + +**Affected component/party:** balancing systems and destination capacity. + +**Consequence:** A locally corrective action amplified the higher-level incident. + +**Timescale:** Propagation. + +**Uncertainty:** Trigger classification feasibility is unknown. + +**Implication:** Add causal containment conditions to balancing: when load may be caused by pathological workload, isolate workload/instances before redistribution rather than optimizing only load distribution. + +--- + +## D2-07 — Revision capacity depended on several control points without a supplied authority/dependency map + +**Evidence / basis:** Recovery involved service restarts, traffic-routing behavior, and rule disablement; the Traffic team separately repaired Traffic Manager. + +**Affected component/party:** incident/control teams and recovery systems. + +**Consequence:** Compound recovery required multiple intervention channels. + +**Timescale:** Incident response. + +**Uncertainty:** The packet does not show that authority ambiguity caused delay. + +**Implication:** Map emergency actions and dependencies: who/what can stop rollout, disable a rule, quarantine traffic, restart workers, override routing, and enter degraded mode; test which remain usable during concurrent failures. + +--- + +## D2-08 — Rollout should preserve reversibility rather than merely reduce initial exposure + +**Evidence / basis:** The rule was staged in a handful of locations and then deployed globally before the triggering request occurred. + +**Affected component/party:** deployment process and global production. + +**Consequence:** The experiment's blast radius expanded before representative evidence had exercised the relevant failure path. + +**Timescale:** Hours during deployment. + +**Uncertainty:** Promotion criteria and traffic representativeness are absent. + +**Implication:** Promotion should depend on representative exposure and automatic halt/rollback conditions; preserve the ability to return to a known-safe state quickly after broadening scope. + +--- + +## D2-09 — Human response capacity was part of the coupled system + +**Evidence / basis:** Many responders were already working the independent backbone-congestion incident and initially explored a shared cause. + +**Affected component/party:** incident-response organization. + +**Consequence:** Independent technical failures competed for attention and shaped diagnostic hypotheses. + +**Timescale:** Early response. + +**Uncertainty:** No evidence proves staffing shortage materially extended recovery. + +**Implication:** Design concurrent-incident response as a capacity problem: reserve/fork leadership and explicitly manage multiple live causal models. + +--- + +## D2-10 — Continuity should be defined at the service capability level, not as preserving one implementation + +**Evidence / basis:** The failure arose from one composed implementation path; immediate recovery required disabling the new rule and restarting affected processes. + +**Affected component/party:** DDoS/rate-limit capability and operators. + +**Consequence:** Restoring safe protection may require changing implementation boundaries rather than restoring the exact previous composition. + +**Timescale:** Long-term design. + +**Uncertainty:** The packet contains no source-authored replacement plan in Pilot 002 and no comparative architecture evidence. + +**Implication:** Before redesign, define the capability that must persist (safe rate limiting / DDoS protection), then compare repair, replacement, isolation, or simplification without treating implementation continuity as the goal. + +--- + +## D2-11 — There is no evidence basis here for broad normative or human-agency claims + +**Evidence / basis:** Packet is a technical incident account with limited organizational information. + +**Affected component/party:** research interpretation. + +**Consequence:** Applying every cross-project lens would manufacture unsupported conclusions. + +**Timescale:** Analysis. + +**Uncertainty:** Customer/staff distributions and governance are absent. + +**Implication:** Keep the review boundary technical; do not claim oppression, trauma, legitimacy failure, or human capability loss from this packet. + +--- + +## D2-12 — Future changes need evidence that they actually alter recurrence dynamics + +**Evidence / basis:** Pilot 002 packet ends at immediate mitigation and supplies no post-incident implementation/effectiveness record. + +**Affected component/party:** future service/operations. + +**Consequence:** Any proposed remediation remains a hypothesis until implemented and exercised. + +**Timescale:** Post-incident. + +**Uncertainty:** All future remediation status is intentionally withheld. + +**Implication:** For every selected action, define implementation evidence, an exercised test/failure condition, and a signal that would show recurrence risk actually changed. + +## Method D Pilot 002 summary + +Without source-authored follow-up actions, the dynamic review independently derives: + +- explicit composition invariants; +- new reachable-failure-transition review; +- reuse/history compatibility review; +- preservation of recovery-option diversity; +- discriminating feedback; +- propagation-aware containment; +- emergency revision/control mapping; +- reversible staged rollout; +- concurrent human-response capacity; +- capability-level continuity; +- boundary restraint; +- post-change evidence before claiming adaptation. From 4cd4ff2cb0a7dfaa085be777de1f8f7b0e96a515 Mon Sep 17 00:00:00 2001 From: Rae Lovejoy Date: Thu, 24 Sep 2026 23:10:17 -0700 Subject: [PATCH 26/66] Code T-003 editorial pilot 002 --- .../t003-editorial-pilot-002-comparison.md | 286 ++++++++++++++++++ 1 file changed, 286 insertions(+) create mode 100644 research/papers/coherent-systems/notes/t003-editorial-pilot-002-comparison.md diff --git a/research/papers/coherent-systems/notes/t003-editorial-pilot-002-comparison.md b/research/papers/coherent-systems/notes/t003-editorial-pilot-002-comparison.md new file mode 100644 index 0000000..006dd2e --- /dev/null +++ b/research/papers/coherent-systems/notes/t003-editorial-pilot-002-comparison.md @@ -0,0 +1,286 @@ +# T-003 Editorial Pilot 002 — comparison and coding + +**Status:** EDITORIAL PILOT RESULT / NOT INDEPENDENT VALIDATION +**Case:** Cloudflare June 20, 2024 incident +**Packet:** remediation-withheld v0.2 +**Methods:** ordinary incident/system review (A2) vs frozen dynamic-coherence review (D2) +**Coders:** same AI-assisted process that generated both methods +**Conflict level:** severe + +## Executive result + +Pilot 002 replicates Pilot 001's main result under a harder evidence condition. + +Removing the source-authored remediation section did **not** reveal clear unique decision-relevant added value from Method D. + +Method D again generated a coherent synthesis around: + +- reachable failure trajectories; +- implementation history; +- shrinking recovery options; +- feedback/model revision; +- emergency control points; +- reversibility; +- capability-level continuity. + +But the ordinary review independently derived the concrete prevention, containment, detection, recovery, and test actions needed for the case. + +### Primary coding result + +- Method D findings coded **E1–E2 / D2 / N2:** **0** +- Method A findings coded **E1–E2 / D2 / N2:** **1 clear case: A2-02 execution bounds/watchdog** +- Method D had two substantively unique interpretive contributions that did not meet the D2 decision threshold: + - D2-10 capability-level continuity; + - D2-11 explicit boundary restraint against unsupported normative/human-agency claims. + +The repeated result strengthens a narrower interpretation: + +> **Dynamic coherence currently looks more defensible as a cross-domain synthesis / routing grammar than as a standalone technical incident-review method.** + +--- + +## Output size + +| Measure | Method A2 | Method D2 | +| --- | ---: | ---: | +| Findings | 12 | 12 | +| Words | 1,239 | 1,182 | +| Characters | 9,852 | 9,890 | +| Human preparation time | not measured | not measured | +| Human application time | not measured | not measured | + +Again, similar output length does not establish similar human burden. + +--- + +## Method D2 coding + +| Finding | E | D | N | Closest A2 | Note | +| --- | --- | --- | --- | --- | --- | +| D2-01 composition assumptions | E2 | D2 | N0 | A2-01 | Same composition defect; D adds assumption language. | +| D2-02 new reachable failure trajectories | E1/E2 | D2 | N1 | A2-01, A2-03, A2-10 | Useful change-review abstraction; concrete actions already present. | +| D2-03 reuse/history constraint | E1/E2 | D1 | N1 | A2-01 | Broadens reuse review but no distinct high-priority action. | +| D2-04 shrinking recovery options | E2 | D2 | N0/N1 | A2-04, A2-05, A2-09, A2-11 | Strong synthesis, ordinary method explicitly preserves reserve/independent recovery paths. | +| D2-05 feedback ambiguity | E2 | D2 | N0 | A2-06 | Same diagnostic requirement. | +| D2-06 locally corrective balancing amplified failure | E2 | D2 | N0 | A2-04 | Same propagation-aware containment. | +| D2-07 emergency control/revision map | E1 | D1 | N1 | A2-05, A2-07, A2-12 | Useful information request, no evidence authority ambiguity caused delay. | +| D2-08 rollout as reversibility | E2 | D2 | N0 | A2-03 | Same canary/rollback issue. | +| D2-09 human response capacity | E1/E2 | D2 | N0 | A2-07 | Same concurrent-incident response issue. | +| D2-10 capability-level continuity | E1 | D1 | N2 | none direct | Distinct framing for redesign scope, but packet does not support one specific architecture decision. | +| D2-11 no broad normative inference | E2 | D0 | N2 | none | Valuable restraint; not a case remediation. | +| D2-12 evidence that future changes alter recurrence | E1/E2 | D2 | N1 | A2-09, A2-10, A2-12 | Stronger lifecycle framing, but verification/testing is already present. | + +### D2 decision-relevant novelty + +**E1–E2 / D2 / N2 = 0** + +--- + +## Method A2 coding + +| Finding | E | D | N | Closest D2 | Note | +| --- | --- | --- | --- | --- | --- | +| A2-01 eliminate validation/self-reference defect | E2 | D2 | N0 | D2-01, D2-02 | Same immediate defect. | +| A2-02 runtime execution bounds | E2 | D2 | N2 | none direct | Concrete containment missing from Method D. | +| A2-03 canary promotion/rollback | E2 | D2 | N0 | D2-08 | Same rollout risk. | +| A2-04 stop balancing from propagating trigger | E2 | D2 | N0 | D2-06 | Same propagation failure. | +| A2-05 harden Traffic Manager | E2 | D2 | N0/N1 | D2-04, D2-07 | A is more component-specific. | +| A2-06 overload-vs-poison diagnostics | E2 | D2 | N0 | D2-05 | Same. | +| A2-07 concurrent incident separation | E1/E2 | D2 | N0 | D2-09 | Same. | +| A2-08 selective/evidence-preserving recycling | E1 | D1/D2 | N1 | D2-04 | More operational detail. | +| A2-09 compound failure test | E1/E2 | D2 | N1 | D2-04, D2-06 | D supplies synthesis; A states direct test. | +| A2-10 rare-trigger/adversarial composition test | E1/E2 | D2 | N1 | D2-02, D2-08 | More concrete test design. | +| A2-11 reserve capacity / independent recovery paths | E2 | D2 | N0/N1 | D2-04 | Direct operational form of response-space preservation. | +| A2-12 missing architecture evidence | E2 | D2 | N1 | D2-07, D2-12 | Broader evidence request. | + +### A2 decision-relevant novelty + +**E1–E2 / D2 / N2 = 1: A2-02** + +--- + +## Withheld-remediation reconstruction + +The omitted source remediation section included four broad themes: + +1. architecture / affected rate-limiter service replacement; +2. containment of non-terminating execution; +3. staged rollout improvement; +4. network-capacity/mitigation improvement. + +This is **not a gold standard**, but it is useful for checking whether methods can derive plausible actions without seeing the source's list. + +### Method A2 + +- **Architecture change:** partial — focuses on composition contracts rather than replacing the service because legacy/replacement facts were withheld. +- **Execution containment:** yes — A2-02. +- **Staged rollout:** yes — A2-03. +- **Network/capacity mitigation:** yes, in mechanism-specific form — A2-04, A2-09, A2-11. + +### Method D2 + +- **Architecture change:** partial — D2-03 and D2-10 suggest reuse review and capability-level redesign, but not a specific replacement. +- **Execution containment:** **not explicit**. +- **Staged rollout:** yes — D2-08. +- **Network/capacity mitigation:** yes — D2-04 and D2-06. + +The missing execution-bound recommendation is now replicated across both Pilot 001 and Pilot 002 Method D outputs. + +That suggests a real prompt-level weakness: + +> **A framework focused on relationships, trajectories, and option structure can underweight simple component-level defensive engineering.** + +--- + +## New protocol lesson: preserve the component level + +The dynamic-coherence framework explicitly warns against collapsing scales, but its frozen prompt does not force a direct **component-level defensive control** pass. + +That matters. + +In this case, "limit how long one request may run" is neither a grand systems insight nor a future-agency finding. + +It is a straightforward local containment measure. + +And it is valuable. + +### Proposed framework correction + +Dynamic coherence should **not** add another broad question merely to ensure every engineering detail appears. + +Instead, its method role should become clearer: + +> **Use competent domain methods first. Use dynamic coherence to connect temporal, cross-boundary, path-dependent, agency, and revision questions that those methods may distribute or omit.** + +It should not pretend to replace: + +- debugging; +- hazard analysis; +- SRE/incident review; +- reliability engineering; +- control theory; +- accessibility analysis; +- capability analysis; +- clinical science; +- other domain methods. + +This is a conceptual narrowing, not a defeat. + +--- + +## False alarms + +No clear E0 false alarm was coded. + +As in Pilot 001, that result is weak because the same AI process generated and coded the outputs. + +Potential overreach points: + +- D2-07 could become authority-theater if used without evidence that emergency decision rights are a real problem. +- D2-10 could become vague transformation language if not connected to a concrete service contract. +- A2-08 is precautionary because restart-induced harm was not reported. + +All three outputs label their uncertainty. + +--- + +## Two-pilot synthesis + +Across two editorial pilots on the same incident: + +### Repeated strengths of Method D + +- connects local remediation to changing future system trajectories; +- names contraction of recovery possibilities; +- makes path dependence/reuse explicit; +- treats feedback as model revision; +- distinguishes capability continuity from implementation continuity; +- strongly resists unsupported normative transfer. + +### Repeated weaknesses + +- no clear D2/N2 decision-relevant finding beyond competent ordinary review; +- misses one simple concrete defensive action twice; +- conceptual vocabulary is broader than needed for this technical case; +- requires a domain method anyway. + +### Repeated strengths of Method A + +- concrete component and operational controls; +- direct testing/remediation proposals; +- good coverage of propagation, dependencies, recovery, rollout, and monitoring. + +### Repeated weaknesses + +- cross-finding relationships remain more fragmented; +- does not explicitly distinguish current state from future transition dynamics; +- does not explicitly ask how response options contract over time; +- provides less vocabulary for transferring the same question to non-incident domains. + +--- + +## Decision after Pilot 002 + +The preregistered stop rule applies: + +> **Do not tune the prompts further against this incident.** + +No Pilot 003 on Cloudflare June 20 should be created to rescue the framework. + +### Framework status after two pilots + +Keep: + +- dynamic coherence as a **conceptual synthesis / routing grammar**; +- state vs transition dynamics; +- path dependence; +- future possibility / response-space questions; +- revision power; +- continuity-through-transformation; +- cross-scale/boundary discipline. + +Downgrade: + +- any implication that Dynamic Coherence is already a standalone general review method. + +Require: + +- a competent domain method; +- explicit statement of what Dynamic Coherence adds beyond that method; +- willingness to report "nothing" when it adds nothing. + +--- + +## Next validation gate + +Do **not** run another same-model case immediately and call the resulting volume evidence. + +The next meaningful gate is one of: + +### A. Independent reviewer comparison + +Use a different case, frozen packet, and human reviewers/coders. + +### B. Method-fidelity comparison + +Add a properly prepared established method—e.g. STPA for an appropriate case—with someone able to evaluate fidelity. + +### C. A domain where the dynamic concepts should matter more + +Select a case involving real path-dependent option structure, such as infrastructure migration or institutional dependency, **but select it before inspecting whether Dynamic Coherence produces a favorable result**. + +If none of these is available, stop and preserve the current uncertainty. + +--- + +## Editorial conclusion + +Pilot 002 again fails to demonstrate unique decision-relevant added value for Dynamic Coherence as a technical incident-review method. + +It does, however, clarify a potentially more durable role: + +> **Dynamic Coherence may be the grammar that helps Root Sequence carry questions about history, future possibility, revision, and continuity across domains—while domain methods remain responsible for the actual mechanisms.** + +That is narrower than a universal method. + +It may also be better. From d6c6dc2c406526eb17ea5e99b170404382a45098 Mon Sep 17 00:00:00 2001 From: Rae Lovejoy Date: Thu, 24 Sep 2026 23:10:54 -0700 Subject: [PATCH 27/66] Narrow dynamic coherence to a routing grammar after pilots --- concepts/dynamic-coherence.md | 56 +++++++++++++++++++++++++++++++++++ 1 file changed, 56 insertions(+) diff --git a/concepts/dynamic-coherence.md b/concepts/dynamic-coherence.md index 8384189..de1fe27 100644 --- a/concepts/dynamic-coherence.md +++ b/concepts/dynamic-coherence.md @@ -629,6 +629,62 @@ Do not promote an analogy simply because it is beautiful. --- +## 16A. Method role: a routing grammar, not a universal analyzer + +Two AI-assisted editorial pilots on the same technical incident compared a competent ordinary incident/system review with the frozen dynamic-coherence review prompt. + +Both pilots were deliberately weak forms of evidence: + +- the same AI-assisted research process prepared the packet, generated both reviews, and coded the findings; +- no independent reviewers participated; +- no STPA or other specialist method was applied; +- no human burden was measured. + +Still, both pilots produced the same useful warning. + +The ordinary review recovered nearly every decision-relevant finding produced by Dynamic Coherence and surfaced one concrete containment action—request execution bounds—that the dynamic prompt omitted twice. + +That result supports a narrower role: + +> **Dynamic Coherence should not compete with competent domain methods for mechanism-level analysis. It should route attention across history, transition dynamics, future possibility, scale, feedback, continuity, revision power, and externalized effects—then hand the actual mechanism back to the relevant domain method.** + +Examples: + +- use reliability engineering for a service failure; +- use STPA or another safety method where appropriate; +- use the capability approach for substantive human opportunity; +- use viability/control methods for formal reachability; +- use clinical and trauma research for trauma; +- use neuroscience/philosophy methods for consciousness; +- use accessibility research for actual access; +- use ecological resilience theory for ecological resilience. + +Dynamic Coherence earns its place only if it helps connect or expose questions that would otherwise remain separated **without pretending those connections replace domain expertise**. + +### Current evidence from T-003 editorial pilots + +Pilot 001 included source-authored remediation. Pilot 002 withheld that remediation section. + +In both: + +- Method D had **zero** findings coded simultaneously as evidence-supported, decision-relevant, and substantively absent from Method A; +- Method A surfaced a concrete request-execution containment action not explicitly surfaced by Method D; +- Method D's strongest added value was integrative framing, especially the contraction of recovery options and state-versus-transition distinctions. + +This is a **near-null result for Dynamic Coherence as a standalone technical review method**. + +It is compatible with a useful role as conceptual grammar. + +See: + +- [T-003 protocol](../research/papers/coherent-systems/notes/t003-added-value-protocol.md) +- [Pilot 001 comparison](../research/papers/coherent-systems/notes/t003-editorial-pilot-001-comparison.md) +- [Pilot 002 comparison](../research/papers/coherent-systems/notes/t003-editorial-pilot-002-comparison.md) + +The same-case stop rule now applies. Do not tune the framework further against that incident. + +--- + ## 17. Candidate Root Sequence principles These are candidates for testing, not doctrine. From 6aca640154a9b3e6ae5ba3f5eb3f07cb214e79ec Mon Sep 17 00:00:00 2001 From: Rae Lovejoy Date: Thu, 24 Sep 2026 23:10:57 -0700 Subject: [PATCH 28/66] Record T-003 near-null editorial pilots --- research/papers/coherent-systems/open-questions.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/research/papers/coherent-systems/open-questions.md b/research/papers/coherent-systems/open-questions.md index 0ea237c..547f1bc 100644 --- a/research/papers/coherent-systems/open-questions.md +++ b/research/papers/coherent-systems/open-questions.md @@ -44,9 +44,9 @@ A later extension should test recurring demand, referrals, service outcomes, unc ## T-003 — Added-value comparison -**Still unrun.** The [related-work note](notes/related-work.md#candidate-comparison-for-t-003-not-a-completed-study) identifies candidate baselines and fidelity checks. The new [T-003 protocol draft](notes/t003-added-value-protocol.md) freezes the proposed dynamic-coherence prompt, finding definitions, coding dimensions, burden/privacy measures, null-result criteria, and the distinction between an editorial pilot and independent review. The published healthcare case remains a retrospective interpretation, not a blinded test of discovery. No case, evidence packet, reviewer, coder, or independent result is registered yet. +**Editorial pilots completed; independent comparison still unrun.** The [related-work note](notes/related-work.md#candidate-comparison-for-t-003-not-a-completed-study) identifies candidate baselines and fidelity checks. The [T-003 protocol](notes/t003-added-value-protocol.md) freezes the proposed prompt, finding definitions, coding dimensions, burden/privacy measures, null-result criteria, and the distinction between an editorial pilot and independent review. [Pilot 001](notes/t003-editorial-pilot-001-comparison.md) and [Pilot 002](notes/t003-editorial-pilot-002-comparison.md) both produced a near-null result for unique decision-relevant added value from Dynamic Coherence over a competent ordinary incident/system review. These same-model pilots are method-debugging evidence only; no independent reviewer or method-superiority result exists. -The next legitimate step is **case selection and packet freezing**, not another conceptual expansion. Choose a small, public, non-sensitive design case and a competent existing review method. Compare it with the section 12 procedure using the same information and a comparable review effort. Avoid choosing a case merely because its known conclusion already matches the framework, and avoid giving the new method more evidence while calling its findings an improvement. +The same-case editorial stop rule now applies. The next legitimate step is **an independent reviewer comparison on a different case or a method-fidelity comparison with a properly prepared established method**, not another prompt-tuning pass on the Cloudflare incident. Choose a small, public, non-sensitive design case and a competent existing review method. Compare it with the section 12 procedure using the same information and a comparable review effort. Avoid choosing a case merely because its known conclusion already matches the framework, and avoid giving the new method more evidence while calling its findings an improvement. **Measure:** Consequential omissions identified, false alarms, traceability, disagreement, reviewer time, and unnecessary information requests. Define “consequential” before evaluating outputs. From a8b8b38a77b4fd41d212fccf5caa4f54527a6000 Mon Sep 17 00:00:00 2001 From: Rae Lovejoy Date: Thu, 24 Sep 2026 23:15:33 -0700 Subject: [PATCH 29/66] Add dynamic coherence intellectual lineage and prior art --- research/dynamic-coherence-lineage.md | 539 ++++++++++++++++++++++++++ 1 file changed, 539 insertions(+) create mode 100644 research/dynamic-coherence-lineage.md diff --git a/research/dynamic-coherence-lineage.md b/research/dynamic-coherence-lineage.md new file mode 100644 index 0000000..b40c25c --- /dev/null +++ b/research/dynamic-coherence-lineage.md @@ -0,0 +1,539 @@ +# Adaptive continuity / dynamic coherence — intellectual lineage and prior art + +**Document role:** Targeted related-work and intellectual-lineage note +**Status:** AI-assisted exploratory synthesis for author review, 2026-09-24 +**Scope:** Identifies established concepts that overlap pieces of the Root Sequence adaptive-continuity / dynamic-coherence synthesis. It does not establish novelty, shared causal mechanism, or a complete literature review. +**Canonical concept:** [Dynamic Coherence and Adaptive Continuity](../concepts/dynamic-coherence.md) + +## Why this note exists + +The September 24 synthesis initially felt unusually generative because it connected: + +- state change and changes in how later change happens; +- path dependence; +- agency and future possibility; +- feedback and revision; +- continuity through transformation; +- emergence and downward constraint; +- resilience and adaptation; +- reflexivity; +- power over constraints; +- AI and human-system boundaries. + +That does **not** imply the component ideas are new. + +The right research question is: + +> Which pieces have already been developed more precisely elsewhere, and what—if anything—is distinctive about how Root Sequence connects them? + +The answer after this first pass is: + +> **Many of the core dynamics have deep predecessors. The candidate contribution, if any, is more likely an integrative grammar linking those dynamics to agency, power, continuity, legitimacy, embodiment, and cross-project design.** + +That hypothesis still needs comparison. + +--- + +# 1. Ashby: state change versus parameter change + +One of the strongest prior-art findings is W. Ross Ashby's distinction between: + +- a change in a system variable/state; and +- a change in a parameter that changes the field/dynamics governing behavior. + +In *Feedback, Adaptation and Stability* (1960), Ashby explicitly emphasizes that distinguishing a change of variable from a change of parameter separates changes that are **behavior** from changes **from one behavior to another**. + +Sources: + +- W. Ross Ashby, "Feedback, Adaptation and Stability" (1960): https://panarchy.org/ashby/adaptation.1960.html +- Related book: *Design for a Brain: The Origin of Adaptive Behaviour*, especially the sections on parameters and ultrastability. + +## Relation to Root Sequence + +This is a direct conceptual ancestor of the draft distinction between current state and transition dynamics. + +Root Sequence should therefore **not claim novelty** for the basic distinction between current-state change and change in transition dynamics. + +What remains potentially distinctive is how the distinction is connected to: + +- agency; +- future reachable possibility; +- power over revision; +- identity/continuity; +- social and institutional constraints; +- legitimacy and externalized costs. + +--- + +# 2. Ashby: ultrastability and second-order adaptation + +Ashby's **ultrastable system** is an early formal/mechanical account of a system changing parameters when ordinary dynamics drive essential variables toward unacceptable or critical states. + +The conceptual pattern is: + + ordinary dynamics fail to keep essential variables viable + ↓ + parameter / field changes + ↓ + new behavior regime + ↓ + retain regimes that avoid critical states + +This is much closer to our "change how the system changes" insight than a simple thermostat metaphor. + +Sources: + +- W. Ross Ashby, *Design for a Brain*, chapter sequence on parameters and the ultrastable system: https://link.springer.com/book/10.1007/978-94-015-1320-3 +- Ashby, "Feedback, Adaptation and Stability" (1960): https://panarchy.org/ashby/adaptation.1960.html +- W. Ross Ashby Digital Archive: https://www.ashby.info/archive.html + +## Boundary + +Ultrastability is **not**: + +- a general theory of human flourishing; +- proof of consciousness; +- a political theory of agency; +- a universal model for institutions; +- evidence that every adaptive process optimizes the same viability criterion. + +Use it as a strong cybernetic predecessor for adaptive rule/parameter change. + +--- + +# 3. Requisite variety: response capacity versus disturbance variety + +Ashby's Law of Requisite Variety places a formal bound on regulation: a regulator needs sufficient variety or information capacity relative to the disturbances it must regulate. + +Primary source: + +- W. Ross Ashby, *An Introduction to Cybernetics* (1956), especially the Requisite Variety chapters: https://ashby.info/Ashby-Introduction-to-Cybernetics.pdf + +## Relation to Root Sequence + +This gives an important ancestor for questions such as: + +- Does the system have enough distinct responses for the disturbances it can encounter? +- Has optimization narrowed the response repertoire? +- Does one bottleneck collapse many nominal options into one effective response? +- Does a system preserve enough diversity to remain adaptable? + +But requisite variety is **not equivalent to agency**. + +A human agency map also involves: + +- knowledge; +- perception; +- material feasibility; +- authorization; +- consent; +- social and institutional power; +- values; +- relationships. + +So: + +> **Requisite variety may help formalize response diversity; it does not replace the agency-envelope question.** + +--- + +# 4. Conant & Ashby: the Good Regulator theorem + +Conant and Ashby's 1970 Good Regulator theorem argues, under specific formal assumptions, that a maximally successful and simple regulator must embody a model of the system it regulates. + +Source: + +- Roger C. Conant and W. Ross Ashby, "Every Good Regulator of a System Must Be a Model of That System," *International Journal of Systems Science* 1(2), 1970, 89–97. DOI: 10.1080/00207727008920220 +- Accessible scan: https://firstlaw.wordpress.com/wp-content/uploads/2011/10/goodregulator.pdf + +## Relation to Root Sequence + +This is an important predecessor for the recurring loop: + +> observe → model → imagine → intervene → consequences → learn → adapt + +It supports taking **model quality** seriously in regulation/control. + +It does not establish: + +- that one centralized model is always best; +- that prediction grants legitimate authority; +- that a regulator's model is consciously experienced; +- that descriptive accuracy decides values or goals. + +The theorem belongs in the formal lineage, not as moral authorization. + +--- + +# 5. Argyris and Schön: single-loop versus double-loop learning + +Organizational-learning theory distinguishes: + +### Single-loop learning + +Change action strategies while leaving governing variables/assumptions substantially intact. + +### Double-loop learning + +Question and revise the governing variables themselves. + +This is extremely close to the Root Sequence distinction between: + +- acting within the current transition structure; and +- changing the structure, rules, or criteria that generate later action. + +Sources: + +- Chris Argyris, "Double Loop Learning in Organizations," *Harvard Business Review* (1977): https://hbr.org/1977/09/double-loop-learning-in-organizations +- Accessible overview of the governing-variable distinction: https://actiondesign.com/resources/readings/double-loop-learning + +## Relation to Root Sequence + +For organizations and institutions, **double-loop learning may be a more established and precise term** than inventing generic transition-function revision language. + +Root Sequence's contribution should be to route to this literature when organizational governing assumptions are the actual mechanism. + +--- + +# 6. Resilience engineering: respond, monitor, learn, anticipate + +Erik Hollnagel's resilience-engineering work emphasizes four systemic potentials: + +- respond; +- monitor; +- learn; +- anticipate. + +Sources: + +- Erik Hollnagel, overview of resilience engineering and systemic potentials: https://erikhollnagel.com/ideas/resilience-engineering-2004 +- Resilience Analysis Grid overview: https://resilienceengineeringinstitute.org/resilience-analysis-grid/ + +A particularly relevant extension is Hollnagel's description of systems that recursively consider how their **own changes alter the world and later conditions**. + +## Relation to Root Sequence + +This overlaps strongly with: + +- feedback quality; +- model revision; +- anticipatory design; +- intervention consequences; +- reflexivity. + +This is another reason Dynamic Coherence should **not** be marketed as though no mature field already studies adaptive socio-technical performance. + +--- + +# 7. Woods: graceful extensibility and sustained adaptability + +David Woods distinguishes several resilience ideas, including: + +- graceful extensibility; +- sustained adaptability. + +Sustained adaptability is especially relevant because it concerns the capacity to **continue adapting as environments, demands, stakeholders, contexts, and constraints continue changing**. + +Sources: + +- David D. Woods, "The theory of graceful extensibility: basic rules that govern adaptive systems," *Environment Systems and Decisions* 38 (2018). DOI: 10.1007/s10669-018-9708-3 +- Resilience Engineering Association publication overview: https://www.resilience-engineering-association.org/resources/publications/ + +## Why this matters + +This is extremely close to our proposed design concern: + +> preserve the capacity for future adaptation. + +Woods also foregrounds finite adaptive capacity and brittleness near capacity boundaries. + +That suggests Root Sequence should compare its terms against: + +- graceful extensibility; +- sustained adaptability; +- adaptive capacity; +- brittleness. + +before claiming a distinct resilience construct. + +--- + +# 8. Adaptive management: interventions as experiments + +Adaptive management in ecology/resource management treats policies as hypotheses and management actions as opportunities to learn. + +A common pattern is: + + explicit model / hypothesis + ↓ + bounded intervention + ↓ + monitor + ↓ + learn + ↓ + revise management + +Sources / lineage: + +- Walters and Holling's adaptive-management work; +- overview of adaptive management as policies-as-hypotheses / actions-as-experiments: https://www.sciencedirect.com/topics/agricultural-and-biological-sciences/adaptive-management +- historical appraisal: https://ecologyandsociety.net/vol3/iss2/art3/ + +## Relation to Root Sequence + +This is a direct predecessor of the proposed: + +> generate → interrogate → simulate → experience → learn + +and Coherent World's: + +> observe → model → imagine → intervene → consequences → learn → adapt. + +Again, the loop is not novel. + +What may be distinctive is connecting adaptive experimentation with: + +- agency; +- consent; +- reversibility; +- affected-party authority; +- future option structure; +- fictional/simulation exploration. + +--- + +# 9. Adaptive governance + +Adaptive-governance research examines how networks of individuals, organizations, agencies, and institutions support reorganization and learning in social-ecological systems under change. + +Source: + +- Carl Folke, Thomas Hahn, Per Olsson, Jon Norberg, "Adaptive Governance of Social-Ecological Systems," *Annual Review of Environment and Resources* 30 (2005), 441–473. DOI: 10.1146/annurev.energy.30.050504.144511 + +## Relation to Root Sequence + +This is especially relevant to: + +- Community Infrastructure; +- collective decision architecture; +- cross-scale governance; +- institutional flexibility; +- local knowledge; +- crisis/reorganization. + +Root Sequence should route institutional claims here instead of reinventing them through abstract coherence vocabulary. + +--- + +# 10. Path dependence and lock-in + +Path dependence is a large family of literatures rather than one mechanism. + +Paul Pierson's influential institutional account emphasizes increasing returns, timing/sequence, and how earlier choices can make later reversal increasingly difficult. + +Source: + +- Paul Pierson, "Increasing Returns, Path Dependence, and the Study of Politics," *American Political Science Review* 94(2), 2000, 251–267. DOI: 10.2307/2586011 + +## Relation to Root Sequence + +The phrase: + +> **history becomes part of the structure generating the future** + +is a useful cross-project summary. + +But causal claims should name the mechanism: + +- increasing returns; +- switching costs; +- learning effects; +- coordination effects; +- infrastructure; +- law; +- habit; +- physiological learning; +- network topology; +- resource accumulation; +- institutional precedent. + +"Path dependence" must not become a magic word for "the past matters." + +--- + +# 11. Second-order cybernetics and the observer + +Second-order cybernetics turns cybernetic analysis back onto the observing or controlling system. + +A classic distinction associated with Heinz von Foerster is: + +- first-order cybernetics: cybernetics of **observed systems**; +- second-order cybernetics: cybernetics of **observing systems**. + +Related sources: + +- historical introduction: https://doi.org/10.1108/03684920410556007 +- system/observer relations: https://doi.org/10.1111/1468-5914.00160 + +## Relation to Root Sequence + +This is highly relevant to the insight that: + +- models are produced from boundaries and perspectives; +- measurements can change behavior; +- predictions and classifications can become interventions; +- the analyst/designer is not automatically outside the system; +- system descriptions carry responsibility and power. + +Root Sequence's reflexivity work should engage this lineage directly. + +--- + +# 12. Prior use of the phrase “dynamic coherence” + +The phrase **dynamic coherence** is not original to Root Sequence and is not unambiguous. + +At least two materially different existing uses are easy to identify. + +## Lane & Oliva (1998) + +A systems-methodology paper uses "dynamic coherence" for consistency between intuitive expectations about behavior and behavior deduced from a causal/system-dynamics model. + +- David C. Lane and Rogelio Oliva, "The greater whole: Towards a synthesis of system dynamics and soft systems methodology," *European Journal of Operational Research* 107(1), 1998, 214–235. DOI: 10.1016/S0377-2217(97)00205-1 + +This use is related to model consistency, but it is **not the same construct** as Root Sequence's temporal/adaptive synthesis. + +## Dynamic Coherence Window (2026) + +A 2026 AI paper uses "Dynamic Coherence Window" for a specific multi-scale structural-coherence measurement framework for AI outputs. + +- Christian St-Louis, "Dynamic coherence windows: a multi-scale structural coherence measurement framework for AI systems," *Frontiers in Artificial Intelligence* 9 (2026), 1836120. DOI: 10.3389/frai.2026.1836120 + +Again, this is a different framework. + +## Naming implication + +Root Sequence must **not** claim: + +- coinage of "dynamic coherence"; +- exclusive use of the term; +- identity with these existing frameworks. + +Possible responses: + +1. keep **Dynamic Coherence** as clearly qualified internal project language; +2. prefer **Adaptive Continuity** for the cross-project concept; +3. use **dynamic-coherence grammar** only as a descriptive label; +4. rename after related-work review. + +No naming decision is made by this note. + +--- + +# 13. “Adaptive continuity” also has unrelated prior uses + +The phrase **adaptive continuity** also appears in other domains, including recent engineering and urban-network work. + +That does not make the phrase unusable, but it reinforces the same rule: + +> **Treat Root Sequence terminology as scoped working language, not a claim of coinage.** + +--- + +# 14. What looks genuinely old versus potentially distinctive + +## Strong predecessors / not novel as components + +- state change vs parameter/rule change; +- adaptive regulation; +- response variety; +- regulator models; +- double-loop learning; +- resilience as respond/monitor/learn/anticipate; +- sustained adaptability; +- path dependence; +- adaptive management; +- observer/reflexivity problems. + +## Candidate Root Sequence synthesis + +Potentially distinctive—not yet demonstrated as novel—is the insistence on connecting these to: + +- **agency:** which meaningful possibilities remain practically reachable; +- **meta-agency:** who can shape future possibility and decision structure; +- **power:** who controls constraints, interfaces, resources, rules, and revision; +- **identity/continuity:** what persists through transformation; +- **embodiment:** the physical organism as part of the process; +- **legitimacy:** capability does not imply authority; +- **externalized effects:** local adaptation can move costs elsewhere; +- **cross-scale effects:** one level's stability can create another level's fragility; +- **epistemic humility:** the framework must route to domain methods rather than totalize them. + +That is a hypothesis about the value of the synthesis. + +It is not yet a novelty finding. + +--- + +# 15. A better working picture + +Rather than: + + Root Sequence invents Dynamic Coherence + ↓ + applies it to everything + +the evidence currently supports: + + many mature traditions + ↓ + cybernetics + resilience engineering + capability theory + viability/control theory + organizational learning + adaptive governance + path-dependence research + embodied/enactive cognition + ... + ↓ + Root Sequence notices recurring relations + ↓ + builds a routing grammar + ↓ + asks which domain theory owns each mechanism + ↓ + tests whether connecting them adds anything + +This is a much stronger epistemic posture. + +--- + +# 16. Next research tasks + +1. Read Ashby's parameter/state and requisite-variety passages at source level and record exact scope. +2. Compare Root Sequence's **meta-agency** concept against double-loop learning, adaptive governance, and institutional-design literature. +3. Compare **future capability** against Woods's graceful extensibility and sustained adaptability. +4. Compare **agency envelope** against capabilities, viability kernels/reachability, affordance theory, and empowerment/control. +5. Compare **reflexivity** against second-order cybernetics and performativity/self-fulfilling-model literatures. +6. Decide whether "Dynamic Coherence" should remain the public concept name after term-collision review. +7. Do not expand the framework further merely to absorb every predecessor; prefer links and scoped translations. + +--- + +# Working conclusion + +The discovery of strong prior art does not make the September 24 synthesis less interesting. + +It changes what is interesting about it. + +The emerging question is no longer: + +> **Did Root Sequence discover a new law of adaptive systems?** + +The better question is: + +> **Can Root Sequence build a legible, humane, cross-domain grammar that connects established insights about adaptation and regulation to agency, power, identity, continuity, and legitimacy—without flattening their differences?** + +That is both more modest and, potentially, more useful. From c101f4bcccf35c77b63f1b375251f0b4c8397d2e Mon Sep 17 00:00:00 2001 From: Rae Lovejoy Date: Thu, 24 Sep 2026 23:15:52 -0700 Subject: [PATCH 30/66] Route dynamic coherence lineage from research index --- research/README.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/research/README.md b/research/README.md index 657c57b..4ea6c0d 100644 --- a/research/README.md +++ b/research/README.md @@ -6,6 +6,10 @@ This directory holds bounded research inquiries and versioned papers that synthe - [Conscious Systems](conscious-systems/README.md) — **exploratory, AI-assisted seed; author review pending**. Starts with [what can change about a mind while preserving consciousness](conscious-systems/what-can-we-change-about-a-mind.md), separating experience from report, capability, and authority. +## Cross-cutting related work + +- [Adaptive continuity / dynamic coherence — intellectual lineage and prior art](dynamic-coherence-lineage.md) — **targeted related-work note; not a novelty finding or systematic review**. Traces state/parameter change, ultrastability, requisite variety, double-loop learning, resilience engineering, sustained adaptability, adaptive management/governance, path dependence, and second-order cybernetics; also records prior uses of the phrase “dynamic coherence.” + ## 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. From 73e0cfe549629bfc58d2a6574eccffd521b56b96 Mon Sep 17 00:00:00 2001 From: Rae Lovejoy Date: Thu, 24 Sep 2026 23:15:54 -0700 Subject: [PATCH 31/66] Add lineage and naming caution to concept --- concepts/dynamic-coherence.md | 29 +++++++++++++++++++++++++++++ 1 file changed, 29 insertions(+) diff --git a/concepts/dynamic-coherence.md b/concepts/dynamic-coherence.md index de1fe27..091f959 100644 --- a/concepts/dynamic-coherence.md +++ b/concepts/dynamic-coherence.md @@ -836,6 +836,35 @@ The model should preserve disagreement and uncertainty rather than collapsing th --- +## 20A. Intellectual lineage and naming caution + +A targeted [intellectual-lineage / prior-art note](../research/dynamic-coherence-lineage.md) found strong predecessors for many component ideas: + +- Ashby's state-versus-parameter distinction and ultrastability; +- requisite variety; +- the Good Regulator theorem; +- Argyris and Schön's double-loop learning; +- resilience engineering's respond / monitor / learn / anticipate framework; +- Woods's graceful extensibility and sustained adaptability; +- adaptive management and adaptive governance; +- path-dependence research; +- second-order cybernetics and observer/reflexivity questions. + +This substantially narrows any novelty claim. + +It also found prior, materially different uses of the phrase **dynamic coherence**, including systems-methodology and AI-evaluation work. Root Sequence therefore treats **Dynamic Coherence** as provisional scoped project language, not a coined or exclusive term. + +The naming question remains open: + +- keep Dynamic Coherence with explicit qualification; +- prefer Adaptive Continuity; +- use dynamic-coherence grammar as a descriptive label; +- rename after further related-work review. + +No public naming decision is implied by this draft. + +--- + ## 21. Research anchors These sources support pieces of the vocabulary, not the whole synthesis. From d98fe712969684541ed6108a644552cc253dc872 Mon Sep 17 00:00:00 2001 From: Rae Lovejoy Date: Thu, 24 Sep 2026 23:18:59 -0700 Subject: [PATCH 32/66] Add critical systems and organizational cybernetics lineage --- research/dynamic-coherence-lineage.md | 185 ++++++++++++++++++++++++-- 1 file changed, 177 insertions(+), 8 deletions(-) diff --git a/research/dynamic-coherence-lineage.md b/research/dynamic-coherence-lineage.md index b40c25c..581a79e 100644 --- a/research/dynamic-coherence-lineage.md +++ b/research/dynamic-coherence-lineage.md @@ -390,7 +390,169 @@ Root Sequence's reflexivity work should engage this lineage directly. --- -# 12. Prior use of the phrase “dynamic coherence” +# 12. Soft systems and critical systems: boundaries, worldviews, power, legitimacy + +The strongest prior-art correction to the **power / boundary / legitimacy** side of Root Sequence comes from Soft Systems Methodology (SSM), Critical Systems Heuristics (CSH), and Critical Systems Thinking (CST). + +These traditions already reject the idea that a systems analyst can simply draw a neutral boundary, optimize the enclosed system, and call the result rational. + +## Soft Systems Methodology + +Checkland's Soft Systems Methodology treats human problem situations as involving multiple legitimate descriptions and worldviews rather than one objectively given problem statement. + +Its well-known CATWOE mnemonic asks analysts to make explicit: + +- **Customers** — people who benefit or suffer from the transformation; +- **Actors** — those carrying out the activities; +- **Transformation** — what change is being described; +- **Weltanschauung / worldview** — the perspective that makes the transformation meaningful; +- **Owner** — who has power to stop or alter the system; +- **Environmental constraints** — conditions treated as outside local control. + +That is very close to Root Sequence's repeated insistence that: + +- system boundaries are choices; +- purposes are not neutral; +- several actors can experience the same intervention differently; +- authority over the transformation must be named; +- environmental constraints cannot be wished away. + +SSM is therefore an important predecessor whenever Root Sequence asks whose model of the situation is being used. + +Sources / entry points: + +- Peter Checkland's SSM tradition and CATWOE; +- overview of CATWOE and perspective-explication: https://www.researchgate.net/publication/225982790_Basic_principles_of_SSM_modeling_An_examination_of_CATWOE_from_a_soft_perspective + +## Critical Systems Heuristics + +Werner Ulrich's Critical Systems Heuristics makes **boundary critique** explicit. + +Its twelve boundary questions are organized around four sources of influence: + +- **motivation** — whose interests/purposes define improvement; +- **control / power** — who can decide and control resources; +- **knowledge** — whose expertise and experience count; +- **legitimacy** — how the interests of people affected but not involved are represented. + +CSH distinguishes people who are **involved** in a system or intervention from people who are **affected** without controlling it. + +This is a very close predecessor to Root Sequence questions such as: + +- Who defined the boundary? +- Who benefits? +- Who bears costs outside the local objective? +- Who can revise the arrangement? +- Whose knowledge is treated as evidence? +- Who is affected without a decision right? +- What makes authority legitimate? + +Sources: + +- Werner Ulrich and Martin Reynolds, "Critical Systems Heuristics" chapter: https://wulrich.com/downloads/ulrich_reynolds_2010_prepub.pdf +- Werner Ulrich, "Critical Systems Heuristics" overview: https://wulrich.com/downloads/ulrich_2002b.pdf + +## Critical Systems Thinking + +Critical Systems Thinking developed partly from dissatisfaction with any one systems methodology being treated as universally adequate. + +Different formulations identify commitments including: + +- critical awareness; +- social awareness; +- methodological and theoretical pluralism / complementarism; +- human emancipation. + +Gerald Midgley's compressed formulation emphasizes: + +- **critical awareness** — question taken-for-granted assumptions and the conditions producing them; +- **emancipation** — define improvement locally and temporarily while examining power; +- **methodological pluralism** — use methods according to their strengths and limits rather than forcing every problem through one framework. + +This is especially important after the T-003 editorial pilots. + +Those pilots independently pushed Root Sequence toward: + +> **use competent domain methods first; use Dynamic Coherence as a routing/synthesis grammar when it connects consequential questions those methods leave separated.** + +That methodological humility is not novel. + +It strongly resembles the critical-systems commitment to methodological pluralism. + +Sources: + +- Michael C. Jackson, "The origins and nature of critical systems thinking," *Systemic Practice and Action Research* 4 (1991), 131–149. DOI: 10.1007/BF01068246 +- Michael C. Jackson, "Five Commitments of Critical Systems Thinking" (1991). +- Gerald Midgley, "What is this thing called CST?" in *Critical Systems Thinking* (1996), DOI: 10.1007/978-0-585-34651-9_1 + +## Implication for Root Sequence + +The power/legitimacy/boundary side of the September 24 synthesis is **not an unexplored territory**. + +Root Sequence should explicitly learn from CSH/CST rather than recreating boundary critique under a coherence vocabulary. + +A candidate local contribution is not: + +> "systems thinking should consider power." + +That is old and well-developed. + +A more defensible question is: + +> **Can Root Sequence make critical boundary/power analysis easy to carry between technical design, AI, embodiment/consciousness research, speculative simulation, community infrastructure, and everyday humane practice without flattening each field's own methods?** + +That remains open. + +--- + +# 13. Stafford Beer: viability, autonomy, cohesion, and future-facing adaptation + +Stafford Beer's Viable System Model (VSM) is another important organizational-cybernetics predecessor. + +The VSM describes recursive organizational functions needed for viability and emphasizes a relationship between **local autonomy and system-level cohesion**. + +Its future/environment-facing function, commonly described as System 4, is concerned with environmental change and adaptation; System 5 is associated with identity/policy and balancing present operations against future adaptation. + +This makes the VSM relevant to Root Sequence questions about: + +- organizational continuity; +- identity while changing; +- distributed/local autonomy; +- environmental sensing; +- future adaptation; +- coordination without complete centralization. + +A sustainability-oriented review of Beer specifically emphasizes autonomy and cohesion in rapidly changing environments. + +Source: + +- Espinosa, Harnden, and Walker, "A complexity approach to sustainability – Stafford Beer revisited," *European Journal of Operational Research* 187 (2008), 636–651. DOI: 10.1016/j.ejor.2007.03.023 + +## Evidence caution + +The VSM makes a **strong theory claim** about preconditions for organizational viability. + +Later empirical work has attempted to test that theory and reports supportive results, while practical-application literature also identifies difficulties in applying the model. + +That is exactly the kind of situation Root Sequence should treat carefully: + +- theory; +- case applications; +- empirical tests; +- implementation difficulty; + +are different evidence layers. + +Sources: + +- Schwaninger and Scheef, "A Test of the Viable System Model: Theoretical Claim vs. Empirical Evidence," *Cybernetics and Systems* 47(7) (2016), 544–569. DOI: 10.1080/01969722.2016.1209375 +- practical-application critique: DOI 10.1108/K-02-2017-0069 + +The VSM should be studied as a serious predecessor, not adopted wholesale as Root Sequence architecture. + +--- + +# 14. Prior use of the phrase “dynamic coherence” The phrase **dynamic coherence** is not original to Root Sequence and is not unambiguous. @@ -431,7 +593,7 @@ No naming decision is made by this note. --- -# 13. “Adaptive continuity” also has unrelated prior uses +# 15. “Adaptive continuity” also has unrelated prior uses The phrase **adaptive continuity** also appears in other domains, including recent engineering and urban-network work. @@ -441,7 +603,7 @@ That does not make the phrase unusable, but it reinforces the same rule: --- -# 14. What looks genuinely old versus potentially distinctive +# 16. What looks genuinely old versus potentially distinctive ## Strong predecessors / not novel as components @@ -454,11 +616,15 @@ That does not make the phrase unusable, but it reinforces the same rule: - sustained adaptability; - path dependence; - adaptive management; -- observer/reflexivity problems. +- observer/reflexivity problems; +- worldview-explication and soft systems methodology; +- boundary critique around motivation, power, knowledge, and legitimacy; +- critical systems methodological pluralism; +- organizational viability/autonomy/cohesion models. ## Candidate Root Sequence synthesis -Potentially distinctive—not yet demonstrated as novel—is the insistence on connecting these to: +Potentially distinctive—not yet demonstrated as novel—is the particular project-level integration and routing of these traditions into: - **agency:** which meaningful possibilities remain practically reachable; - **meta-agency:** who can shape future possibility and decision structure; @@ -476,7 +642,7 @@ It is not yet a novelty finding. --- -# 15. A better working picture +# 17. A better working picture Rather than: @@ -510,7 +676,7 @@ This is a much stronger epistemic posture. --- -# 16. Next research tasks +# 18. Next research tasks 1. Read Ashby's parameter/state and requisite-variety passages at source level and record exact scope. 2. Compare Root Sequence's **meta-agency** concept against double-loop learning, adaptive governance, and institutional-design literature. @@ -518,7 +684,10 @@ This is a much stronger epistemic posture. 4. Compare **agency envelope** against capabilities, viability kernels/reachability, affordance theory, and empowerment/control. 5. Compare **reflexivity** against second-order cybernetics and performativity/self-fulfilling-model literatures. 6. Decide whether "Dynamic Coherence" should remain the public concept name after term-collision review. -7. Do not expand the framework further merely to absorb every predecessor; prefer links and scoped translations. +7. Compare Root Sequence's boundary/power questions directly against Critical Systems Heuristics before claiming added analytical value. +8. Compare the cross-domain routing strategy against Critical Systems Thinking's methodological pluralism. +9. Examine Stafford Beer's Viable System Model for useful organizational continuity/autonomy distinctions without importing its entire architecture. +10. Do not expand the framework further merely to absorb every predecessor; prefer links and scoped translations. --- From d29e21b6d60ff1331ba9d2ab243e8025d11c8e5a Mon Sep 17 00:00:00 2001 From: Rae Lovejoy Date: Thu, 24 Sep 2026 23:20:14 -0700 Subject: [PATCH 33/66] Add domain-method routing table --- concepts/dynamic-coherence.md | 35 +++++++++++++++++++++++++++++++++++ 1 file changed, 35 insertions(+) diff --git a/concepts/dynamic-coherence.md b/concepts/dynamic-coherence.md index 091f959..255e7d6 100644 --- a/concepts/dynamic-coherence.md +++ b/concepts/dynamic-coherence.md @@ -685,6 +685,41 @@ The same-case stop rule now applies. Do not tune the framework further against t --- +## 16B. Method routing: ask which discipline owns the mechanism + +The framework is becoming more useful as a **method router** than as a universal method. + +A first routing table: + +| Question actually being asked | Established method / literature to check first | Dynamic-coherence role | +| --- | --- | --- | +| Why did a technical service fail and propagate? | reliability engineering, incident analysis, safety engineering, STPA where appropriate | connect propagation to history, future recovery capacity, and cross-boundary effects | +| Which states remain reachable under explicit dynamical constraints? | control theory, reachability, viability theory | connect formal reachability to other constraints the formal model does not encode | +| Does a person have a real opportunity, not merely a nominal option? | capability approach, accessibility/usability research | connect substantive opportunity to technical, institutional, and temporal dependencies | +| Who defines the system, improvement, knowledge, and affected boundary? | Critical Systems Heuristics | carry boundary/power questions into project-local design without claiming to replace CSH | +| Are several worldviews defining different problem situations? | Soft Systems Methodology | preserve multiple framings and route disagreements instead of forcing one system model | +| Is an organization changing action while preserving or revising governing assumptions? | organizational learning / double-loop learning | connect rule revision to longer-term continuity and surrounding systems | +| Can an organization remain viable while balancing autonomy, coordination, present operations, and future adaptation? | organizational cybernetics / Viable System Model | compare organizational viability claims rather than redescribing them as generic coherence | +| Can a socio-technical system continue adapting near changing capacity boundaries? | resilience engineering, graceful extensibility, sustained adaptability | connect adaptive capacity to agency, ownership, and externalized burden | +| How do ecological systems persist, reorganize, or transform? | ecological resilience / adaptive management | preserve domain definitions and resist importing social/psychological meanings | +| Is a human stress/trauma response being discussed? | trauma, stress physiology, psychology, clinical science, lived expertise | prevent systems analogy from replacing human evidence | +| What produces subjective experience? | neuroscience, philosophy of mind, comparative consciousness research | keep identity/agency/system-boundary questions distinct from consciousness claims | +| Does an artificial system's adaptive behavior imply experience? | AI mechanism analysis + consciousness/welfare evidence | enforce the inference boundary: functional adaptation is not phenomenology | + +This table is deliberately incomplete. + +Its purpose is not to reduce fields to one row each. It is to create an early warning: + +> **If an established discipline already owns the mechanism, Root Sequence should learn from it before creating new vocabulary.** + +Dynamic Coherence becomes valuable when it helps reveal that **several different native questions are coupled in the same real situation**. + +That is a meta-methodological role. + +Critical Systems Thinking is an important predecessor for this pluralist stance; the [lineage note](../research/dynamic-coherence-lineage.md) records the comparison. + +--- + ## 17. Candidate Root Sequence principles These are candidates for testing, not doctrine. From 8b60ed71d7c4846cddccee4142e42fb98a51b5d6 Mon Sep 17 00:00:00 2001 From: Rae Lovejoy Date: Thu, 24 Sep 2026 23:20:17 -0700 Subject: [PATCH 34/66] Add baseline method-routing rule to T-003 protocol --- .../notes/t003-added-value-protocol.md | 28 +++++++++++++++++++ 1 file changed, 28 insertions(+) diff --git a/research/papers/coherent-systems/notes/t003-added-value-protocol.md b/research/papers/coherent-systems/notes/t003-added-value-protocol.md index d37f8cd..c591413 100644 --- a/research/papers/coherent-systems/notes/t003-added-value-protocol.md +++ b/research/papers/coherent-systems/notes/t003-added-value-protocol.md @@ -89,6 +89,34 @@ A missing fact may itself be a finding. --- +## 4A. Baseline-method selection is part of the protocol + +Do not default to "ordinary review" when a better-established domain method exists. + +Before freezing the methods, ask which mechanism dominates the case: + +| Case feature | Candidate baseline | +| --- | --- | +| technical reliability / incident propagation | competent SRE/reliability review | +| safety-control structure | STPA or another appropriate safety method | +| practical human opportunity / exclusion | capability-oriented analysis + accessibility methods | +| contested problem definitions / worldviews | Soft Systems Methodology | +| boundary, power, affected-but-not-involved parties | Critical Systems Heuristics | +| organizational governing assumptions / learning | double-loop learning / organizational learning | +| organizational viability / autonomy-cohesion | Viable System Model or relevant organizational-cybernetics approach | +| ecological adaptation / transformation | ecological resilience / adaptive management | +| formal constrained reachability | viability/control analysis | + +The chosen baseline must be justified before outputs are generated. + +Dynamic Coherence should **not receive credit for rediscovering a distinction already central to the selected baseline**. + +When several mechanisms materially matter, a plural baseline may be more honest than forcing one method to cover everything. + +This follows the growing evidence that Root Sequence's most defensible role is methodological routing/synthesis rather than universal replacement. + +--- + ## 5. Methods ### Method A — competent ordinary review From 663ca98be69f31a5fe632775b6c10cdb592d19a5 Mon Sep 17 00:00:00 2001 From: Rae Lovejoy Date: Thu, 24 Sep 2026 23:21:52 -0700 Subject: [PATCH 35/66] Decompose agency and meta-agency through prior art --- research/dynamic-coherence-lineage.md | 247 +++++++++++++++++++++++++- 1 file changed, 240 insertions(+), 7 deletions(-) diff --git a/research/dynamic-coherence-lineage.md b/research/dynamic-coherence-lineage.md index 581a79e..6114df4 100644 --- a/research/dynamic-coherence-lineage.md +++ b/research/dynamic-coherence-lineage.md @@ -552,7 +552,234 @@ The VSM should be studied as a serious predecessor, not adopted wholesale as Roo --- -# 14. Prior use of the phrase “dynamic coherence” +# 14. Affordances: possibility is relational, embodied, and skill-dependent + +James J. Gibson's ecological psychology introduced **affordances** as possibilities for action available in the relation between an organism and its environment. + +Later work emphasizes that affordances depend not only on environmental structure but on an animal's or person's action capabilities and skills. + +Rietveld and Kiverstein develop the idea of a **landscape of affordances**: the rich field of possible actions available in a form of life, with relevance shaped by skills and situated activity. + +Sources: + +- James J. Gibson, *The Ecological Approach to Visual Perception* (1979). +- Erik Rietveld & Julian Kiverstein, "A Rich Landscape of Affordances," *Ecological Psychology* 26(4) (2014), 325–352. DOI: 10.1080/10407413.2014.958035 +- Historical/review overview of ecological psychology and affordances: https://pmc.ncbi.nlm.nih.gov/articles/PMC6280920/ + +## Relation to Root Sequence + +This is an extremely close predecessor to one layer of the proposed **agency envelope**. + +It sharpens a key point: + +> An action is not simply "available" in the abstract. Possibility can exist at the organism–environment relation. + +A stairway may be physically present while not affording the same action to every body. + +A tool may exist while requiring a skill the person does not have. + +An interface may expose a command while its sensory/motor presentation makes it unusable. + +This means Root Sequence should distinguish: + +- **affordance** — what the organism/environment relation enables; +- **knowledge** — whether the actor knows or perceives the possibility; +- **authorization** — whether social/institutional rules permit it; +- **resources/support** — whether the actor can practically execute it; +- **value/choice** — whether the actor wants or has reason to pursue it. + +Do not collapse these into one "agency amount." + +--- + +# 15. Capabilities: substantive opportunity and conversion factors + +The capability approach provides an even closer social/normative predecessor for the distinction between **nominal options** and **real opportunities**. + +Capabilities are commonly described as real or substantive opportunities to do or be something. + +The literature explicitly emphasizes **conversion factors**: personal, social, and environmental conditions affect whether resources or formal rights can actually be converted into functioning. + +Source: + +- Ingrid Robeyns & Morten Fibieger Byskov, "The Capability Approach," *Stanford Encyclopedia of Philosophy*, substantive revision 2025: https://plato.stanford.edu/entries/capability-approach/ + +The capability literature also warns against inferring justice from reported satisfaction or preferences alone: people living under deprivation may adapt expectations to constrained circumstances. + +## Relation to Root Sequence + +This strongly supports dropping any implication that Root Sequence discovered: + +> real options matter more than menu size. + +The **agency envelope** is better understood as a proposed *systems representation* that can route among several distinct questions, including capability questions. + +When human wellbeing/freedom is central, capability theory should be engaged directly. + +--- + +# 16. Niche construction: agents modify the conditions that later shape them + +Niche-construction theory studies cases in which organisms modify environmental conditions and thereby alter ecological or evolutionary selection pressures affecting themselves, descendants, and other organisms. + +Sources: + +- Laland, Matthews & Feldman, "An introduction to niche construction theory," *Evolutionary Ecology* (2016): https://pmc.ncbi.nlm.nih.gov/articles/PMC4922671/ +- Laland et al., "Niche construction, sources of selection and trait coevolution," *Philosophical Transactions of the Royal Society B* (2017): https://pmc.ncbi.nlm.nih.gov/articles/PMC5566808/ + +The literature also develops **ecological inheritance**: modified environmental states can persist and shape later generations. + +## Relation to Root Sequence + +This is a striking biological predecessor for part of what Root Sequence called **meta-agency**: + +> action changes the environment that structures later action and development. + +The analogy is strong at a structural level. + +But Root Sequence should not flatten: + +- evolutionary niche construction; +- deliberate institutional design; +- personal habit formation; +- technical environment configuration; + +into one mechanism. + +For biological/evolutionary claims, use niche-construction theory. + +For social/institutional claims, use the relevant social theory. + +For technical systems, identify the actual architecture. + +The useful shared question is: + +> **How did an actor/system's activity modify the conditions that will shape later behavior?** + +--- + +# 17. Social power: shaping the conditions and capacities of action + +The insight that power can operate by shaping **conditions of action**, not only by directly commanding someone, also has strong predecessors. + +Barnett and Duvall's taxonomy of power distinguishes: + +- **compulsory power** — direct control of one actor over another; +- **institutional power** — indirect control through institutions over the conditions of others' action; +- **structural power** — social relations that constitute actors' positions and capacities; +- **productive power** — diffuse social processes that produce subjects, meanings, and capacities. + +Source: + +- Michael Barnett & Raymond Duvall, "Power in International Politics," *International Organization* 59(1) (2005), 39–75. DOI: 10.1017/S0020818305050010 + +This taxonomy is situated in international-relations theory and should not be treated as the only theory of power. + +## Relation to Root Sequence + +It is nevertheless a direct warning against claiming novelty for: + +> **power includes the ability to shape the conditions under which others can act.** + +That idea already has mature social-theoretical forms. + +Root Sequence may still contribute an accessible systems map that connects such power to: + +- infrastructure; +- interfaces; +- defaults; +- standards; +- ownership; +- accessibility; +- AI-mediated environments; +- future path dependence. + +But the social-power mechanism belongs to social and political theory, not to a new law of coherence. + +--- + +# 18. Decomposing the “agency envelope” + +After this lineage pass, the proposed agency-envelope concept should be treated as a **composite map**, not one latent quantity. + +A more disciplined decomposition is: + +| Layer | Native concept / question | +| --- | --- | +| Physical / embodied possibility | affordances; what does this organism–environment relation permit? | +| Skilled possibility | which affordances exist given learned abilities? | +| Formal reachability | viability/control/reachability; which trajectories satisfy explicit constraints? | +| Substantive human opportunity | capabilities; what is genuinely possible given conversion factors? | +| Knowledge / perception | does the actor know or notice the possibility? | +| Authorization | who has decision rights / permission? | +| Material support | are time, energy, money, tools, care, infrastructure, and assistance available? | +| Causal influence | empowerment/control; how much influence can actions exert over later state? | +| Power over conditions | who can alter the environment, rules, institutions, or capacities structuring others' possibilities? | +| Value / choice | which possibilities does the actor actually value or choose? | + +This decomposition is more useful than a scalar. + +The project term **agency envelope** can remain shorthand for visualizing these layers together, but it should not be presented as a discovered unit of agency. + +--- + +# 19. Decomposing “meta-agency” + +Likewise, meta-agency may name several different mechanisms: + +### Self-modification + +Changing one's own habits, skills, policies, goals, thresholds, or governing assumptions. + +Relevant lineages: + +- learning; +- double-loop learning; +- self-regulation; +- reflective accountability. + +### Environment modification + +Changing the material/environmental conditions of later action. + +Relevant lineages: + +- ecological affordances; +- niche construction; +- architecture and infrastructure design. + +### Institutional modification + +Changing rules, rights, resource distributions, standards, ownership, or governance. + +Relevant lineages: + +- institutional design; +- adaptive governance; +- critical systems; +- theories of power. + +### Capacity building + +Acquiring skills, resources, relationships, infrastructure, or redundancy that expand later practical possibility. + +Relevant lineages: + +- capability approach; +- resilience engineering; +- education / development / accessibility research. + +So the better Root Sequence question is not simply: + +> How much meta-agency exists? + +It is: + +> **Which mechanism is changing the conditions of future agency, for whom, under what authority, and with what consequences?** + +--- + +# 20. Prior use of the phrase “dynamic coherence” The phrase **dynamic coherence** is not original to Root Sequence and is not unambiguous. @@ -593,7 +820,7 @@ No naming decision is made by this note. --- -# 15. “Adaptive continuity” also has unrelated prior uses +# 21. “Adaptive continuity” also has unrelated prior uses The phrase **adaptive continuity** also appears in other domains, including recent engineering and urban-network work. @@ -603,7 +830,7 @@ That does not make the phrase unusable, but it reinforces the same rule: --- -# 16. What looks genuinely old versus potentially distinctive +# 22. What looks genuinely old versus potentially distinctive ## Strong predecessors / not novel as components @@ -620,7 +847,11 @@ That does not make the phrase unusable, but it reinforces the same rule: - worldview-explication and soft systems methodology; - boundary critique around motivation, power, knowledge, and legitimacy; - critical systems methodological pluralism; -- organizational viability/autonomy/cohesion models. +- organizational viability/autonomy/cohesion models; +- ecological affordances; +- capability/conversion-factor accounts of substantive opportunity; +- niche construction and ecological inheritance; +- social theories of institutional/structural/productive power. ## Candidate Root Sequence synthesis @@ -642,7 +873,7 @@ It is not yet a novelty finding. --- -# 17. A better working picture +# 23. A better working picture Rather than: @@ -676,7 +907,7 @@ This is a much stronger epistemic posture. --- -# 18. Next research tasks +# 24. Next research tasks 1. Read Ashby's parameter/state and requisite-variety passages at source level and record exact scope. 2. Compare Root Sequence's **meta-agency** concept against double-loop learning, adaptive governance, and institutional-design literature. @@ -687,7 +918,9 @@ This is a much stronger epistemic posture. 7. Compare Root Sequence's boundary/power questions directly against Critical Systems Heuristics before claiming added analytical value. 8. Compare the cross-domain routing strategy against Critical Systems Thinking's methodological pluralism. 9. Examine Stafford Beer's Viable System Model for useful organizational continuity/autonomy distinctions without importing its entire architecture. -10. Do not expand the framework further merely to absorb every predecessor; prefer links and scoped translations. +10. Compare agency-envelope language directly with affordance landscapes, capabilities/conversion factors, formal reachability, and empowerment/control. +11. Compare meta-agency against niche construction, double-loop learning, capacity building, institutional design, and theories of structural/institutional power. +12. Do not expand the framework further merely to absorb every predecessor; prefer links and scoped translations. --- From 0d12c42e9f5a4332a4f636f51b5fad192155032d Mon Sep 17 00:00:00 2001 From: Rae Lovejoy Date: Thu, 24 Sep 2026 23:22:23 -0700 Subject: [PATCH 36/66] Decompose agency envelope and meta-agency --- concepts/dynamic-coherence.md | 37 ++++++++++++++++++++++++++--------- 1 file changed, 28 insertions(+), 9 deletions(-) diff --git a/concepts/dynamic-coherence.md b/concepts/dynamic-coherence.md index 255e7d6..7cd5dab 100644 --- a/concepts/dynamic-coherence.md +++ b/concepts/dynamic-coherence.md @@ -74,8 +74,8 @@ The arrows are a routing map, not a causal theory. Different domains implement h | **Adaptive continuity** | Persistence through change: preserving or rebuilding enough organization, capability, relationship, or lineage for meaningful continuation. | | **Dynamic coherence** | Examining coherence across change, feedback, scale, and time rather than only static consistency. | | **Path dependence** | Earlier states or events alter later reachable possibilities or response dynamics. | -| **Agency envelope** | The meaningful reachable possibilities an actor can perceive, access, influence, refuse, or help create; currently a working concept, not a validated metric. | -| **Meta-agency** | Capacity to alter the conditions that shape later agency. | +| **Agency envelope** | Project shorthand for a **layered map**, not a latent quantity: embodied affordances, formal reachability, substantive opportunity, knowledge/perception, authorization, resources/support, causal influence, and power over conditions may all differ. | +| **Meta-agency** | Provisional umbrella for mechanisms that alter later agency conditions, including self-modification, environment modification, institutional change, and capacity building; not one validated faculty. | | **Attractor-like pattern** | A persistent or self-reinforcing regime described by analogy to dynamical systems unless a formal attractor is actually modeled. | | **Maladaptation / mismatch** | A response that is ineffective or costly under relevant current conditions, including responses that once fit different conditions. | | **Reflexivity** | A model, measurement, prediction, or intervention changes the system being modeled. | @@ -170,9 +170,19 @@ What can occur from the present state under actual material, temporal, instituti Which reachable possibilities an actor can perceive, understand, access, influence, refuse, or help create. -For now, this page calls the third region an **agency envelope**. +For now, this page calls the layered relationship among these conditions an **agency envelope**. -This is a Root Sequence working term, not an established scientific metric. +This is a Root Sequence working shorthand, not an established scientific metric or one latent property. + +The [intellectual-lineage note](../research/dynamic-coherence-lineage.md) now decomposes it against several established neighbors: + +- **affordances** — organism/environment action possibilities; +- **capabilities** — real or substantive human opportunities under personal, social, and environmental conversion factors; +- **viability / reachability** — formally reachable trajectories under stated constraints; +- **empowerment / control** — causal influence over later observable states in specific formal models; +- **boundary / power analysis** — who controls the conditions, resources, rules, or institutions shaping action. + +The point of the project term is to keep those dimensions visible together when a real system couples them—not to replace their native theories. An agency envelope can be narrowed by: @@ -234,9 +244,18 @@ Examples include: - preserving an exit path; - establishing a right to appeal. -This page provisionally calls that **meta-agency**: +This page provisionally calls that family of effects **meta-agency**: + +> **changing the conditions that will shape future agency.** + +The term should not imply one mechanism. The same surface description may involve very different processes: + +- **self-modification:** learning, habit change, revised governing assumptions or policies; +- **environment modification:** changing material affordances or infrastructure; +- **institutional modification:** changing rules, rights, standards, ownership, or decision processes; +- **capacity building:** adding skills, resources, relationships, redundancy, accessibility, or support. -> **the capacity to influence the future structure of one's own or a group's agency envelope.** +Relevant prior literatures include double-loop learning, niche construction, the capability approach, adaptive governance, affordance theory, and theories of institutional/structural power. Meta-agency is not unlimited self-authorship. People do not choose their initial bodies, histories, institutions, resources, social positions, or many of the events that shape them. Collective attempts to widen one group's possibilities can also narrow another group's possibilities. @@ -727,8 +746,8 @@ These are candidates for testing, not doctrine. 1. **Continuity can depend on transformation rather than sameness.** 2. **History can change a system's transition dynamics, not only its current state.** 3. **An adaptation can be locally useful and later costly, or coherent at one scale and incoherent at another.** -4. **Agency concerns effective reachable possibilities, not the nominal count of options.** -5. **Meta-agency concerns the capacity to shape the conditions of future agency.** +4. **Agency cannot be inferred from the nominal count of options; embodied affordances, knowledge, substantive feasibility, authorization, support, causal control, and power may differ.** +5. **Actions can reshape future agency through several distinct mechanisms; name the mechanism rather than treating meta-agency as one faculty.** 6. **A resilient system may restore, adapt, or transform; resilience is not automatically beneficial.** 7. **Maximum order, stability, or optimization is not the same as dynamic coherence.** 8. **Emergent patterns matter partly because they reshape later constraints and possibilities.** @@ -915,7 +934,7 @@ These sources support pieces of the vocabulary, not the whole synthesis. ## 22. Next research questions -1. Can “agency envelope” be operationalized without reducing agency to a scalar? +1. Does “agency envelope” add useful integrative legibility after decomposing it into affordances, capabilities, reachability, authorization, support, control, and power—or should the shorthand be retired? 2. Which established literatures already capture the distinction between changing state and changing transition dynamics more precisely? 3. How should dynamic coherence relate to viability theory, control theory, enactivism, ecological resilience, cybernetics, and complex adaptive systems? 4. When is preserving future flexibility beneficial, and when does it undermine necessary commitment or coordination? From b084856a43df0d98488c1c5d8d96c368da3300de Mon Sep 17 00:00:00 2001 From: Rae Lovejoy Date: Thu, 24 Sep 2026 23:23:48 -0700 Subject: [PATCH 37/66] Add biological individuality and autonomy lineage --- research/dynamic-coherence-lineage.md | 122 ++++++++++++++++++++++++-- 1 file changed, 115 insertions(+), 7 deletions(-) diff --git a/research/dynamic-coherence-lineage.md b/research/dynamic-coherence-lineage.md index 6114df4..e3ca327 100644 --- a/research/dynamic-coherence-lineage.md +++ b/research/dynamic-coherence-lineage.md @@ -779,7 +779,112 @@ It is: --- -# 20. Prior use of the phrase “dynamic coherence” +# 20. Biological individuality: the organism is already a contested systems boundary + +The question "what makes this one living individual?" is itself an active topic in biology and philosophy of biology. + +The contemporary literature distinguishes multiple notions of biological individuality, including: + +- evolutionary individuals; +- physiological individuals; +- developmental and other candidate forms. + +A physiological individual is often characterized through functional integration, metabolic organization, regulation, and persistence through time. + +Source: + +- [Stanford Encyclopedia of Philosophy: Biological Individuals](https://plato.stanford.edu/entries/biology-individual/) + +## Relation to Root Sequence + +This strongly supports one of the project's methodological cautions: + +> **Do not assume that organism, cognitive system, conscious subject, legal person, social identity, and autobiographical self have one identical boundary.** + +Even biology itself can require several individuality criteria for different explanatory tasks. + +That means the original personal-identity rabbit hole should remain plural: + +- organismic continuity; +- physiological continuity; +- causal/developmental trajectory; +- autobiographical continuity; +- social/legal continuity; +- subjective continuity; + +may overlap without being equivalent. + +--- + +# 21. Autopoiesis and organizational closure: identity through self-maintaining organization + +Autopoietic and organizational approaches to biology provide serious predecessors for the intuition that living identity concerns **ongoing organization**, not persistence of unchanged material components. + +Maturana and Varela's autopoiesis characterizes living systems in terms of networks of processes that produce and maintain the components and organization that constitute the system. + +Later organizational approaches develop related accounts through **closure of constraints**. + +Montévil and Mossio's formulation distinguishes: + +- thermodynamically open processes; +- constraints that act on those processes while exhibiting relative stability at relevant timescales; +- organizational closure in which constraints depend on and maintain one another. + +Source: + +- Maël Montévil & Matteo Mossio, "Biological organisation as closure of constraints," *Journal of Theoretical Biology* 372 (2015), 179–191. DOI: 10.1016/j.jtbi.2015.02.029 + +Di Paolo's enactive work then argues that autopoiesis alone is insufficient for a richer account of sense-making and introduces **adaptivity** relative to conditions of viability. + +Source: + +- Ezequiel Di Paolo, "Autopoiesis, Adaptivity, Teleology, Agency," *Phenomenology and the Cognitive Sciences* 4 (2005), 429–452. DOI: 10.1007/s11097-005-9002-y + +## Relation to personal identity + +These theories do **not** prove: + +- that an autobiographical person is identical to one biological organization; +- that organizational closure is sufficient for consciousness; +- that a copied organization preserves the same subject; +- that human personal identity has one necessary biological criterion. + +They do give technical substance to the statement: + +> **A living system can preserve an organizational identity while continuously exchanging matter and changing internal state.** + +That is a much stronger basis for the earlier "you are something your organism does" intuition than the metaphor alone. + +--- + +# 22. Sense-making: environments matter differently to different living systems + +Enactive accounts introduce **sense-making** to describe behavior in relation to environmental significance or valence grounded in the organism's autonomy and viability. + +A tomato, temperature change, toxin, shelter, social cue, or resource is not merely an abstract state variable; its significance depends on the living system and its organization. + +Overview: + +- Di Paolo (2005), above. +- organism–environment discussion: https://pmc.ncbi.nlm.nih.gov/articles/PMC7358536/ + +## Relation to Root Sequence + +This is relevant to the distinction between: + +- an objectively present condition; +- an affordance; +- a condition perceived as relevant; +- a valued or threatening condition; +- the action that becomes salient. + +It gives another reason an "agency envelope" cannot be one objective set drawn entirely from outside the actor. + +But Root Sequence must not infer a person's subjective significance merely from external system structure. + +--- + +# 23. Prior use of the phrase “dynamic coherence” The phrase **dynamic coherence** is not original to Root Sequence and is not unambiguous. @@ -820,7 +925,7 @@ No naming decision is made by this note. --- -# 21. “Adaptive continuity” also has unrelated prior uses +# 24. “Adaptive continuity” also has unrelated prior uses The phrase **adaptive continuity** also appears in other domains, including recent engineering and urban-network work. @@ -830,7 +935,7 @@ That does not make the phrase unusable, but it reinforces the same rule: --- -# 22. What looks genuinely old versus potentially distinctive +# 25. What looks genuinely old versus potentially distinctive ## Strong predecessors / not novel as components @@ -851,7 +956,9 @@ That does not make the phrase unusable, but it reinforces the same rule: - ecological affordances; - capability/conversion-factor accounts of substantive opportunity; - niche construction and ecological inheritance; -- social theories of institutional/structural/productive power. +- social theories of institutional/structural/productive power; +- biological-individuality pluralism; +- autopoiesis, organizational closure, and enactive adaptivity. ## Candidate Root Sequence synthesis @@ -873,7 +980,7 @@ It is not yet a novelty finding. --- -# 23. A better working picture +# 26. A better working picture Rather than: @@ -907,7 +1014,7 @@ This is a much stronger epistemic posture. --- -# 24. Next research tasks +# 27. Next research tasks 1. Read Ashby's parameter/state and requisite-variety passages at source level and record exact scope. 2. Compare Root Sequence's **meta-agency** concept against double-loop learning, adaptive governance, and institutional-design literature. @@ -920,7 +1027,8 @@ This is a much stronger epistemic posture. 9. Examine Stafford Beer's Viable System Model for useful organizational continuity/autonomy distinctions without importing its entire architecture. 10. Compare agency-envelope language directly with affordance landscapes, capabilities/conversion factors, formal reachability, and empowerment/control. 11. Compare meta-agency against niche construction, double-loop learning, capacity building, institutional design, and theories of structural/institutional power. -12. Do not expand the framework further merely to absorb every predecessor; prefer links and scoped translations. +12. Compare personal-identity claims against biological-individuality, autopoiesis/organizational-closure, and process-ontology work without treating any as a consciousness theory. +13. Do not expand the framework further merely to absorb every predecessor; prefer links and scoped translations. --- From 0ac91f6f289f8a714aec1aae14bfc67b83facc23 Mon Sep 17 00:00:00 2001 From: Rae Lovejoy Date: Thu, 24 Sep 2026 23:24:20 -0700 Subject: [PATCH 38/66] Clarify Root Sequence as routing and synthesis layer --- concepts/root-sequence.md | 33 +++++++++++++++++++++++++++++++++ 1 file changed, 33 insertions(+) diff --git a/concepts/root-sequence.md b/concepts/root-sequence.md index 0a8cef7..6d85b95 100644 --- a/concepts/root-sequence.md +++ b/concepts/root-sequence.md @@ -35,6 +35,39 @@ Sequences also become roots. An outcome in one moment becomes part of the starti That recursion is central to the name. Root Sequence is interested not only in where systems come from, but in how they keep producing the conditions of their own continuation or transformation. +## A routing and synthesis layer, not a replacement discipline + +Root Sequence often begins with a cross-domain pattern: + +- a technical system and an institution both exhibit lock-in; +- a living organism and an organization both adapt; +- an interface and a law both alter practical possibilities; +- an individual and a community both carry history into later behavior. + +The correct next move is **not** to assume one mechanism. + +Instead: + +1. trace the relationship that made the comparison interesting; +2. ask what each domain already calls and studies that mechanism; +3. route to the strongest relevant methods and evidence; +4. compare where the structures genuinely match and where they diverge; +5. keep the connection only if it remains useful after the differences are restored. + +This makes the central repository a **conceptual commons and routing layer**. + +It can hold shared questions such as: + +> What conditions made this possible, and what does it make possible next? + +while a reliability engineer, trauma researcher, ecological scientist, accessibility practitioner, critical-systems analyst, neuroscientist, historian, or community member may each supply very different mechanisms and evidence. + +A cross-domain synthesis earns its place when it makes those relationships more legible **without making the domains less precise**. + +The September 24 adaptive-continuity work sharpened this role after related-work review found deep predecessors in cybernetics, resilience engineering, capability theory, critical systems thinking, ecological psychology, organizational learning, biological autonomy, and other fields. Two editorial method pilots also failed to show unique technical-incident findings from the proposed dynamic-coherence review over a competent ordinary review. + +Those are reasons for **more routing and less totalization**, not reasons to stop connecting ideas. + ## What the name does not require The name does not require: From 9511fc0dd62e0e0ff1161e8e995093dfd53bb296 Mon Sep 17 00:00:00 2001 From: Rae Lovejoy Date: Thu, 24 Sep 2026 23:24:35 -0700 Subject: [PATCH 39/66] Add methodological routing to design grammar --- concepts/design-grammar.md | 1 + 1 file changed, 1 insertion(+) diff --git a/concepts/design-grammar.md b/concepts/design-grammar.md index fce27f6..b016abf 100644 --- a/concepts/design-grammar.md +++ b/concepts/design-grammar.md @@ -18,6 +18,7 @@ This wording is a proposed synthesis, not an approved project slogan. Coherence | Move | Design question | Related home | | --- | --- | --- | | Model relationships and conditions | What environment, incentives, dependencies, feedback, and history produce the outcome? | [Systems](../systems/README.md) and [Intelligence Ecology](intelligence-ecology.md) | +| Route mechanisms to their native methods | Which discipline or established method already studies the mechanism we are invoking? What remains after its distinctions and evidence limits are restored? | [Why Root Sequence?](root-sequence.md#a-routing-and-synthesis-layer-not-a-replacement-discipline) and [Dynamic Coherence lineage](../research/dynamic-coherence-lineage.md) | | Preserve adaptive continuity | What should remain stable, what must remain changeable, and which meaningful future actions does this decision open or close? | [Dynamic Coherence and Adaptive Continuity](dynamic-coherence.md) and [Adaptation](../systems/adaptation/README.md) | | Expand agency through chosen participation and delegation | Which burdens can be removed, and who retains a meaningful say over the result? | [Agency and Automation](agency-and-automation.md) | | Keep authority scoped and contestable | Who may act for whom, on what basis, and who else bears the effects? | [Agency and Automation](agency-and-automation.md) and [Idea Trail 9](../IDEA_TRAILS.md#trail-9--intelligence-automation-and-legitimate-authority) | From f1a25c5c6c4735c5ae09729960ba814b758aa72f Mon Sep 17 00:00:00 2001 From: Rae Lovejoy Date: Thu, 24 Sep 2026 23:25:18 -0700 Subject: [PATCH 40/66] Make coherence explicitly relational --- systems/coherence/model.md | 40 ++++++++++++++++++++++++++++++++++++++ 1 file changed, 40 insertions(+) diff --git a/systems/coherence/model.md b/systems/coherence/model.md index 54a880a..5289add 100644 --- a/systems/coherence/model.md +++ b/systems/coherence/model.md @@ -55,6 +55,46 @@ It asks whether a system can remain responsive to conditions and consequences wh --- +## Coherence is relational, not an intrinsic substance + +Avoid treating coherence as though it were an amount stored inside a system. + +A useful coherence statement should be expandable into something like: + +> **This process / relationship / arrangement exhibits [kind of fit] with respect to [conditions, purpose, dependency, or other relation], for [affected parties / boundary], over [timescale], under [evidence and uncertainty].** + +For example: + +- a protocol may be coherent with a documented interface contract while creating an inaccessible user experience; +- a team may coordinate efficiently around a purpose whose legitimacy is contested; +- an organism may maintain physiological integration while autobiographical identity changes; +- an institution may be stable internally while transferring costs elsewhere; +- a repair may fit present conditions while creating future lock-in. + +Those are not contradictions. + +They are different relations. + +This yields a language rule: + +> **Prefer "coherent with respect to..." or "coherence among..." over an unqualified "this system is coherent."** + +When the qualifier is obvious from a tightly bounded local context, prose need not become cumbersome. The analytical record should still make it recoverable. + +### No automatic total ordering + +Several coherence relations can improve or deteriorate independently. + +Do not assume that they can always be aggregated into: + + system A > system B in coherence + +A comparison is warranted only after stating the dimension, boundary, affected parties, timescale, and tradeoffs that make it meaningful. + +This keeps "coherence" from becoming a hidden utility function. + +--- + ## Static fit and dynamic coherence A snapshot can be coherent in a limited sense: From 511772dc6a7eeb21fa2d1a96443f55cbd9fd8ff8 Mon Sep 17 00:00:00 2001 From: Rae Lovejoy Date: Thu, 24 Sep 2026 23:36:01 -0700 Subject: [PATCH 41/66] Add Reading Trails research layer --- research/reading-trails/README.md | 68 +++++++++++++++++++++++++++++++ 1 file changed, 68 insertions(+) create mode 100644 research/reading-trails/README.md diff --git a/research/reading-trails/README.md b/research/reading-trails/README.md new file mode 100644 index 0000000..eaf3a08 --- /dev/null +++ b/research/reading-trails/README.md @@ -0,0 +1,68 @@ +# Reading Trails + +**Document role:** Curated research-rabbit-hole index +**Status:** Developing +**Purpose:** Preserve the sites, archives, societies, reading lists, courses, magazines, papers, and other intellectual neighborhoods that surface during Root Sequence research. + +## Why this exists + +A bibliography answers: + +> What source supports this claim? + +A Reading Trail answers a different question: + +> **Where can someone go wander, learn the field's language, discover adjacent ideas, and find things we did not already know to search for?** + +Root Sequence research repeatedly encounters valuable resources that are not themselves the canonical evidence for a claim: + +- old specialist magazines; +- scholar-maintained archives; +- societies and conference proceedings; +- reading lists; +- course platforms; +- historical collections; +- research-community wikis; +- practitioner notes; +- repositories of talks and workshops. + +Those are easy to lose when only the final paper citation survives. + +Reading Trails preserve them. + +## Rules + +A Reading Trail should distinguish: + +- **primary / scholarly source** — use for claims when appropriate; +- **reference / overview** — useful for orientation and terminology; +- **archive** — valuable historical/source material; +- **community / society** — people, events, current work, bibliographies; +- **learning hub** — courses/tutorials; +- **practitioner resource** — useful synthesis whose authority must still be checked; +- **rabbit-hole site** — high discovery value even when it is not itself evidence. + +Do not treat inclusion as endorsement or validation. + +Do not replace claim-level evidence with a cool website. + +## Current trails + +- [Systems, Cybernetics, Complexity & Adaptive Systems](systems-cybernetics-complexity.md) — the current giant rabbit hole: cybernetics, systems thinking, system dynamics, resilience engineering, critical systems, organizational cybernetics, complexity science, and systemic design. + +## Future use + +When research uncovers a genuinely useful intellectual neighborhood, add it here rather than relying on chat history. + +Possible future trails: + +- consciousness / neuroscience / philosophy of mind; +- AI institutions / governance / alignment; +- community infrastructure / commons / mutual aid; +- urban systems / accessibility / mobility; +- repair / appropriate technology / hardware autonomy; +- alternative institutions / abandoned futures; +- human factors / HCI / accessibility; +- archives / museums / ordinary life. + +Keep these **curated**, not exhaustive link dumps. From 27f72e0737a21c9303bdee3a18f0cfa40be70eaa Mon Sep 17 00:00:00 2001 From: Rae Lovejoy Date: Thu, 24 Sep 2026 23:36:03 -0700 Subject: [PATCH 42/66] Add systems and cybernetics brain-food trail --- .../systems-cybernetics-complexity.md | 516 ++++++++++++++++++ 1 file changed, 516 insertions(+) create mode 100644 research/reading-trails/systems-cybernetics-complexity.md diff --git a/research/reading-trails/systems-cybernetics-complexity.md b/research/reading-trails/systems-cybernetics-complexity.md new file mode 100644 index 0000000..fc067f8 --- /dev/null +++ b/research/reading-trails/systems-cybernetics-complexity.md @@ -0,0 +1,516 @@ +# Systems, Cybernetics, Complexity & Adaptive Systems + +**Status:** Developing reading trail, 2026-09-24 +**Related:** [Adaptive continuity / dynamic coherence lineage](../dynamic-coherence-lineage.md) + +This is not a bibliography and not a ranked curriculum. + +It is a **map of places worth getting lost** while exploring the systems/cybernetics rabbit hole that collided with the September 24 adaptive-continuity work. + +## Fastest way in + +If you want five tabs that immediately open five different doors: + +1. **The Systems Thinker** — accessible archive of practical systems-thinking writing. +2. **W. Ross Ashby Digital Archive** — primary historical cybernetics rabbit hole. +3. **Resilience Engineering Association — Where Do I Start?** — unusually good curated reading path into modern resilience/safety thinking. +4. **Complexity Explorer** — free/on-demand complexity-science courses from the Santa Fe Institute ecosystem. +5. **Systemic Design Association / RSD** — systems thinking colliding directly with design practice, pluralism, multi-stakeholder complexity, and real-world interventions. + +Then branch according to what grabs you. + +--- + +# 1. The Systems Thinker + +**Site:** https://thesystemsthinker.com/ +**Type:** archive / accessible systems-thinking magazine +**Rabbit-hole value:** ★★★★★ + +Published by Pegasus Communications beginning in the early 1980s. The current site is an archive rather than an active new-publication stream. + +Why it is delightful: + +- systems archetypes; +- feedback loops; +- organizational learning; +- systems thinking in ordinary management/practice; +- short enough pieces to wander without committing to a textbook; +- decades of accumulated language and examples. + +Good when you want: + +> "Give me a systems idea I can understand over coffee and then spend three hours following references from." + +The site's own history says the archive was preserved after Pegasus's 2013 bankruptcy so the accumulated material would remain accessible. + +--- + +# 2. W. Ross Ashby Digital Archive + +**Site:** https://ashby.info/ +**Type:** primary historical archive +**Rabbit-hole value:** ★★★★★★★★★★ + +This is absurdly good. + +Ashby's family donated his papers to the British Library and later made his journals available online. + +The archive contains: + +- roughly 7,400 journal pages; +- 25 volumes; +- around 1,600 index cards; +- bibliography; +- biography; +- correspondence; +- keyword-linked journal navigation; +- previously unpublished material. + +Ashby is central to: + +- requisite variety; +- ultrastability; +- adaptation; +- self-organization; +- cybernetics; +- the Homeostat; +- *Design for a Brain*; +- *An Introduction to Cybernetics*. + +This is a place to **watch someone think**, not just read the polished theory afterward. + +Start: + +- archive home; +- keyword index; +- *An Introduction to Cybernetics*; +- adaptation / ultrastability; +- journal entries around organization, learning, intelligence, and regulation. + +--- + +# 3. American Society for Cybernetics + +**Site:** https://asc-cybernetics.org/ +**Type:** society / events / contemporary cybernetics community +**Rabbit-hole value:** ★★★★★ + +Founded in 1964 and still active. + +The ASC describes cybernetics in terms including: + +- circularity; +- recursion; +- construction; +- reflexivity. + +Useful current features: + +- speaker series; +- Cybernetics Study Group; +- working groups; +- archives initiatives; +- contemporary conferences; +- links into the design/cybernetics community. + +Particularly relevant for Root Sequence because cybernetics here is explicitly not only engineering—it crosses biology, arts, medicine, therapy, design, management, mathematics, physical science, and more. + +The **#NewMacyMeetings** project is also an interesting contemporary attempt to revive the transdisciplinary conversational spirit of the early Macy cybernetics meetings. + +--- + +# 4. International Society for the Systems Sciences + +**Main site:** https://www.isss.org/ +**Wiki:** https://wiki.isss.org/ +**Primer:** https://web3.isss.org/primer2/primer.htm +**Type:** long-running systems-science society / wiki / historical resources +**Rabbit-hole value:** ★★★★★★★ + +Founded in 1954. + +This may be one of the richest "I did not know this entire intellectual neighborhood existed" resources. + +The current site points to: + +- systems-science communities; +- conferences; +- proceedings; +- systems maps; +- streams of systems thought; +- journals; +- historical resources. + +The wiki includes categories for: + +- systems theories; +- methodologies; +- books; +- articles; +- software; +- tools; +- conferences; +- special integration groups. + +The old **Primer Project** is wonderfully old-web and includes things such as: + +- "So you wanna know what a SYSTEM is?"; +- history of systems; +- evolution of systems inquiry; +- cybernetics and systems science; +- primer toolbox; +- bibliography. + +This is very close to a **map of the intellectual ecosystem itself**, which makes it especially relevant to Root Sequence's new router role. + +--- + +# 5. Resilience Engineering Association + +**Site:** https://www.resilience-engineering-association.org/ +**Start here:** https://www.resilience-engineering-association.org/resources/where-do-i-start/ +**Publications map:** https://www.resilience-engineering-association.org/resources/publications/ +**Type:** curated field reading list / research community / practitioner resource +**Rabbit-hole value:** ★★★★★★★★★★ + +This is perhaps the single best accidental discovery from the current research thread. + +The "Where Do I Start?" page is a genuinely useful guided pathway through: + +- resilience; +- accidents and safety; +- complex systems; +- coordination; +- automation; +- Rasmussen's dynamic safety model; +- David Woods; +- Erik Hollnagel; +- Safety-II; +- cognitive systems engineering. + +The publications page then becomes a huge branching graph through people and ideas such as: + +- Lisanne Bainbridge — ironies of automation; +- Sidney Dekker — drift into failure; +- Jens Rasmussen — dynamic safety; +- Nancy Leveson — STAMP/STPA; +- Erik Hollnagel — Safety-II, FRAM, ETTO; +- David Woods — graceful extensibility, adaptive universe, anomaly response; +- Elinor Ostrom — polycentric governance; +- John Doyle — robust-yet-fragile systems. + +This is **brain buffet** territory. + +--- + +# 6. System Dynamics Society + +**Site:** https://systemdynamics.org/ +**Resources:** https://systemdynamics.org/resources/ +**Type:** scholarly/practitioner society / modeling field +**Rabbit-hole value:** ★★★★★★ + +If systems thinking feels intuitive but you want to push from: + +> "feedback loops! cool!" + +toward: + +> "okay, how do people actually model this?" + +this is an important next neighborhood. + +Resources include: + +- articles/books; +- conference proceedings; +- successful applications/cases; +- journals; +- modeling resources; +- university and career links. + +System dynamics gives formal/modeled treatment to stocks, flows, feedback, delays, and behavior over time. + +It is particularly relevant to Root Sequence's insistence that a beautiful causal diagram eventually needs to risk producing actual consequences. + +--- + +# 7. Complexity Explorer / Santa Fe Institute + +**Site:** https://www.complexityexplorer.org/ +**Courses:** https://www.complexityexplorer.org/courses +**Type:** learning hub / complexity science +**Rabbit-hole value:** ★★★★★★★★ + +A Santa Fe Institute educational project with asynchronous courses and tutorials from beginner through advanced levels. + +Current offerings include subjects such as: + +- nonlinear dynamics; +- computation in complex systems; +- complexity fundamentals; +- analytical methods. + +Good for moving from qualitative systems intuition into: + +- dynamical systems; +- emergence; +- computation; +- networks; +- information; +- scaling; +- complex adaptive systems. + +This one may be particularly good for turning "I can feel the shape of this idea" into mathematical/formal intuition without requiring an entire degree first. + +--- + +# 8. Systemic Design Association + RSD + +**Site:** https://systemic-design.org/ +**RSD repository:** https://rsdsymposium.org/ +**Type:** scholarly/practice community bridging systems + design +**Rabbit-hole value:** ★★★★★★★★ + +Systemic design explicitly joins **systems thinking to design methodology**. + +The RSD (Relating Systems Thinking and Design) symposium/repository has accumulated well over a thousand papers, talks, maps, workshops, and other artifacts. + +Topics include: + +- complex social systems; +- service systems; +- policy; +- sustainability; +- participatory methods; +- systems-oriented design; +- pluralism; +- mapping; +- design for complexity. + +This is extremely relevant to: + +- Coherent Computing; +- Community Infrastructure; +- the SF Commons work; +- Coherent World; +- Root Sequence's desire to move between analysis and actual design. + +The association explicitly describes its approach as pluralistic and as adapting methods from multiple systems/design traditions. + +--- + +# 9. Werner Ulrich / Critical Systems Heuristics + +**Site:** https://wulrich.com/ +**CSH chapter:** https://wulrich.com/downloads/ulrich_reynolds_2010_prepub.pdf +**Boundary critique:** https://wulrich.com/downloads/ulrich_2002a.pdf +**Type:** scholar archive / primary conceptual work +**Rabbit-hole value:** ★★★★★★★★ + +Go here when systems thinking starts sounding suspiciously neutral. + +Critical Systems Heuristics asks questions around: + +- motivation; +- control/power; +- knowledge; +- legitimacy; +- boundary judgments; +- people who are affected but not involved. + +This is one of the strongest predecessors to Root Sequence's recurring: + +> Who drew the system boundary? + +> Who benefits? + +> Who can change it? + +> Who is affected without authority? + +> Whose knowledge counts? + +It is also an excellent inoculation against turning "systems" into an impersonal explanation that makes power disappear. + +--- + +# 10. Metaphorum + +**Site:** https://metaphorum.org/ +**VSM introduction:** https://metaphorum.org/staffords-work/viable-system-model +**Type:** Stafford Beer / organizational cybernetics community +**Rabbit-hole value:** ★★★★★★★ + +Metaphorum was created by collaborators of Stafford Beer after his death to continue research and practice around his work. + +Useful for: + +- Viable System Model; +- organizational cybernetics; +- autonomy and cohesion; +- recursive systems; +- Team Syntegrity; +- Beer history/material. + +Fun current historical note: September 25, 2026 marks Stafford Beer's 100th birthday, and Metaphorum has a centenary project around his legacy. + +VSM is especially relevant to the current thread because it explicitly wrestles with: + +> how can parts retain autonomy while the larger organization remains viable? + +--- + +# 11. Panarchy / old-web systems archives + +**Site:** https://panarchy.org/ +**Type:** historical / political / systems-text archive +**Rabbit-hole value:** ★★★★★★★★ + +Panarchy has surfaced repeatedly because it hosts older systems/cybernetics/ecology/political texts that are otherwise annoying to find. + +Examples encountered in this project include Ashby material on adaptation. + +Use it as: + +- a discovery/archive surface; +- a pointer toward original works. + +For consequential claims, verify the original publication/version when possible. + +The value is exactly the weird-old-internet quality: + +> "Why is there a 1960 cybernetics text sitting here? Oh no, now I have 18 tabs." + +Perfect. + +--- + +# 12. Critical Systems Thinking + +There is not one single canonical public portal as neat as the sites above. + +Good names to follow include: + +- C. West Churchman; +- Werner Ulrich; +- Michael C. Jackson; +- Gerald Midgley; +- Robert Flood; +- John Brocklesby. + +Useful search terms: + +- Critical Systems Thinking; +- Critical Systems Heuristics; +- boundary critique; +- methodological pluralism; +- total systems intervention; +- systemic intervention; +- affected vs involved. + +This tradition is especially important for Root Sequence's emerging methodological rule: + +> No method—including ours—gets to declare itself universally adequate. + +--- + +# Suggested rabbit-hole routes + +## "I want to understand why everything is loops" + +1. The Systems Thinker +2. System Dynamics Society +3. Ashby +4. Complexity Explorer + +## "I want systems thinking, but allergic to technocratic bullshit" + +1. Critical Systems Heuristics +2. Critical Systems Thinking +3. Soft Systems Methodology +4. Systemic Design Association + +## "I want to understand systems surviving weird shit" + +1. Resilience Engineering Association — Where Do I Start? +2. Woods +3. Hollnagel +4. Rasmussen +5. Leveson / STPA + +## "I want organizations as actual adaptive systems" + +1. Ashby +2. Stafford Beer / Metaphorum +3. VSM +4. organizational learning / double-loop learning +5. adaptive governance + +## "I want mathier/formal brain food" + +1. Complexity Explorer +2. System Dynamics Society +3. Ashby's *Introduction to Cybernetics* +4. dynamical systems / control / viability theory +5. network science + +## "I want Root Sequence's current rabbit hole" + +1. [Intellectual lineage note](../dynamic-coherence-lineage.md) +2. Ashby archive +3. Resilience Engineering Association +4. Ulrich / CSH +5. Capability Approach +6. affordances / ecological psychology +7. niche construction +8. biological individuality / autopoiesis +9. Critical Systems Thinking +10. systemic design + +--- + +# Sites I want to investigate further + +These have appeared nearby but deserve their own future pass: + +- Principia Cybernetica; +- Systems Innovation / systems-change educational communities; +- Santa Fe Institute beyond Complexity Explorer; +- New England Complex Systems Institute; +- Human Systems Dynamics Institute; +- Waters Center for Systems Thinking; +- Systems Practice communities; +- Operational Research / Problem Structuring Methods communities; +- Adaptive Capacity Labs; +- Resilience Roundup; +- Safety Differently; +- System Dynamics Review; +- *Systemic Practice and Action Research*; +- *Systems Research and Behavioral Science*; +- *Cybernetics and Human Knowing*; +- *Constructivist Foundations*. + +Do not bulk-add these as recommended resources until they have been checked. + +--- + +# How to use this without drowning + +A good browsing rule: + +> **Follow one concept until it creates a question, then follow the question—not every hyperlink.** + +Capture interesting branches here. + +You do not have to finish a field before being allowed to connect it to another one. + +But before Root Sequence makes a consequential claim, come back out of the rabbit hole and ask: + +- what did I actually learn? +- what is evidence versus interpretation? +- which native field owns the mechanism? +- what still seems connected after restoring the differences? + +Then dive again. 🐇 From 38b15967c06cf889713487bd35e30e992d01b8f8 Mon Sep 17 00:00:00 2001 From: Rae Lovejoy Date: Thu, 24 Sep 2026 23:36:22 -0700 Subject: [PATCH 43/66] Route Reading Trails from research index --- research/README.md | 1 + 1 file changed, 1 insertion(+) diff --git a/research/README.md b/research/README.md index 4ea6c0d..79cbdda 100644 --- a/research/README.md +++ b/research/README.md @@ -9,6 +9,7 @@ This directory holds bounded research inquiries and versioned papers that synthe ## Cross-cutting related work - [Adaptive continuity / dynamic coherence — intellectual lineage and prior art](dynamic-coherence-lineage.md) — **targeted related-work note; not a novelty finding or systematic review**. Traces state/parameter change, ultrastability, requisite variety, double-loop learning, resilience engineering, sustained adaptability, adaptive management/governance, path dependence, and second-order cybernetics; also records prior uses of the phrase “dynamic coherence.” +- [Reading Trails](reading-trails/README.md) — **curated brain-food maps**, separate from claim-level bibliographies: archives, societies, courses, old magazines, reading lists, practitioner hubs, and other places worth wandering. The first trail covers [systems, cybernetics, complexity, and adaptive systems](reading-trails/systems-cybernetics-complexity.md). ## Living papers From 83bc30800fb898d17a826e085538564f3691735f Mon Sep 17 00:00:00 2001 From: Rae Lovejoy Date: Thu, 24 Sep 2026 23:37:12 -0700 Subject: [PATCH 44/66] Add explanatory unification and mechanisms reading trail --- .../systems-cybernetics-complexity.md | 39 +++++++++++++++++++ 1 file changed, 39 insertions(+) diff --git a/research/reading-trails/systems-cybernetics-complexity.md b/research/reading-trails/systems-cybernetics-complexity.md index fc067f8..bb897fd 100644 --- a/research/reading-trails/systems-cybernetics-complexity.md +++ b/research/reading-trails/systems-cybernetics-complexity.md @@ -416,6 +416,45 @@ This tradition is especially important for Root Sequence's emerging methodologic --- +# 13. Philosophy of science — why unification feels so powerful + +**Scientific Explanation (SEP):** https://plato.stanford.edu/archives/spr2017/entries/scientific-explanation/ +**Mechanisms in Science (SEP):** https://plato.stanford.edu/entries/science-mechanisms/ +**Unity of Science (SEP):** https://plato.stanford.edu/entries/scientific-unity/ +**Kitcher, "Explanatory Unification":** https://web.mit.edu/bskow/www/215-S12/kitcher_explanatory-unification.pdf +**Type:** philosophy of science / epistemology +**Rabbit-hole value:** ★★★★★★★★ + +This is the place to go when you have the feeling: + +> "Holy shit, one pattern suddenly makes a bunch of unrelated things make sense." + +Philosophers of science have explicitly debated whether explanation gains power through **unification**: showing how many previously separate phenomena can be understood through a smaller number of reusable patterns. + +Kitcher's influential unificationist account is one major version. + +But mechanistic traditions push back: + +> a pattern can unify descriptions without telling you **what actually produces the phenomenon**. + +That tension is almost a perfect epistemic rule for Root Sequence: + + notice recurring pattern + ↓ + gain explanatory compression + ↓ + DO NOT STOP + ↓ + ask what mechanism produces it in each domain + ↓ + restore differences + ↓ + keep only the unification that survives + +This is the philosophical version of our anti-research-slop rule. + +--- + # Suggested rabbit-hole routes ## "I want to understand why everything is loops" From e9fdf52c33063082cd44e349b33d745a3a414f07 Mon Sep 17 00:00:00 2001 From: Rae Lovejoy Date: Thu, 24 Sep 2026 23:51:46 -0700 Subject: [PATCH 45/66] Add epistemic discoverability and knowledge routing concept --- concepts/epistemic-discoverability.md | 686 ++++++++++++++++++++++++++ 1 file changed, 686 insertions(+) create mode 100644 concepts/epistemic-discoverability.md diff --git a/concepts/epistemic-discoverability.md b/concepts/epistemic-discoverability.md new file mode 100644 index 0000000..0cd0b91 --- /dev/null +++ b/concepts/epistemic-discoverability.md @@ -0,0 +1,686 @@ +# Epistemic Discoverability and Knowledge Routing + +**Document role:** Working cross-domain design concept +**Status:** Active / developing; AI-assisted synthesis for author review, 2026-09-24 +**Canonical scope:** Shared Root Sequence treatment of how people discover, navigate, evaluate, and build knowledge when they do not yet know the field's vocabulary or structure. +**Evidence boundary:** The component ideas have established predecessors in information retrieval, information foraging, sensemaking, learning sciences, epistemic-agency research, libraries, HCI, and knowledge organization. This page proposes a Root Sequence synthesis and design vocabulary; it does not claim novelty for those components or establish one universal model of learning. + +## Core idea + +Knowledge can be public, searchable, and technically available while remaining **practically undiscoverable** to a person who does not yet know: + +- the right term; +- the field that studies the question; +- which source type is trustworthy; +- which scholar/community uses different vocabulary; +- which adjacent concept would provide the next search term; +- whether they are interpreting the question at the right scale. + +Root Sequence calls this problem **epistemic discoverability**: + +> **Can a person move from the concepts and questions they currently possess toward relevant knowledge they do not yet know how to name?** + +The companion concept is **knowledge routing**: + +> **helping a question reach the field, method, community, source, or vocabulary best equipped to develop it—without forcing every question through one ontology or authority.** + +This is related to, but distinct from: + +- finding one known document; +- answering a factual query; +- teaching a fixed curriculum; +- ranking search results; +- recommending popular content; +- summarizing what an expert already knows. + +The difficult case is: + +> **I can feel the question, but I do not yet have the language required to search for it.** + +--- + +## 1. Why vocabulary is infrastructure + +Furnas, Landauer, Gomez, and Dumais's 1987 **Vocabulary Problem** demonstrated extreme variability in the words people spontaneously choose for the same objects/actions. Their study found that, across several domains, the probability that two people independently favored the same term was below 0.20. + +Source: + +- G. W. Furnas, T. K. Landauer, L. M. Gomez, S. T. Dumais, "The Vocabulary Problem in Human-System Communication," *Communications of the ACM* 30(11), 1987, 964–971. DOI: 10.1145/32206.32212 + +The immediate HCI lesson was that interfaces relying on one designer-selected vocabulary impose enormous first-try failure. + +The broader Root Sequence lesson is: + +> **Knowing the phenomenon is not the same as knowing the canonical name for it.** + +A person can have a valid intuition while lacking: + +- disciplinary terminology; +- historical names; +- alternate spellings; +- current preferred vocabulary; +- technical jargon; +- the name of a neighboring field. + +Knowledge systems that require the user to supply the expert's exact phrase **before helping them discover the expert vocabulary** impose a hidden prerequisite. + +That is an agency problem. + +--- + +## 2. Search needs can change while searching + +Marcia Bates's **berrypicking** model of information seeking rejects the assumption that a researcher starts with one stable query that merely needs a better result. + +In real research: + +- one source introduces a new term; +- that term reveals a field; +- the field changes the researcher's understanding of the question; +- the new understanding changes the query; +- useful fragments accumulate across many sources rather than in one final answer. + +Source: + +- Marcia J. Bates, "The Design of Browsing and Berrypicking Techniques for the Online Search Interface," *Online Review* 13(5), 1989. Author-hosted version: https://pages.gseis.ucla.edu/faculty/bates/berrypicking.html + +This is almost a perfect description of the September 24 Root Sequence research path. + +The query did not merely become **better formulated**. + +The researcher's **question-space changed**. + +That means a good knowledge environment should preserve: + +- evolving queries; +- concepts learned along the way; +- sources that triggered a change of direction; +- abandoned branches; +- useful partial answers; +- new unknowns produced by earlier answers. + +--- + +## 3. Information foraging and “information scent” + +Pirolli and Card's **Information Foraging Theory** analyzes how people seek valuable information in environments where information occurs in patches and where proximal cues help indicate whether a path is worth following. + +Source: + +- Peter Pirolli & Stuart Card, "Information Foraging," *Psychological Review* 106(4), 1999, 643–675. DOI: 10.1037/0033-295X.106.4.643 + +A knowledge interface therefore has a design problem analogous to navigation: + +> What cues tell the person that this concept, source, citation, field, scholar, or community might lead somewhere useful? + +Examples of **epistemic scent** may include: + +- "This is the field that studies the pattern you're describing"; +- related terms and aliases; +- why a source is relevant; +- disagreement between fields; +- what prerequisite concept unlocks the next source; +- "start here" routes; +- citation trails; +- examples that connect unfamiliar terminology to the person's existing model. + +A link dump has low epistemic scent. + +A good Reading Trail explains **why you might want to click**. + +--- + +## 4. Sensemaking is representation-building + +Russell, Stefik, Pirolli, and Card describe sensemaking as the process of searching for a useful representation and encoding information within it to answer task-specific questions. + +Source: + +- Daniel M. Russell, Mark J. Stefik, Peter Pirolli, Stuart K. Card, "The Cost Structure of Sensemaking," INTERCHI '93. DOI: 10.1145/169059.169209 + +That matters because information access is not sufficient. + +A researcher may have: + +- the papers; +- the data; +- the vocabulary; + +and still lack a representation that makes the relationships intelligible. + +Root Sequence frequently supplies: + +- concept maps; +- distinction tables; +- timelines; +- state/transition models; +- Idea Trails; +- project maps; +- provenance graphs; +- Reading Trails. + +These are not merely prettier summaries. + +They can be **sensemaking infrastructure**. + +The danger is equally important: + +> A compelling representation can make a weak theory feel finished. + +So every map should preserve: + +- uncertainty; +- contested relationships; +- source boundaries; +- analogy versus mechanism; +- missing evidence; +- alternatives. + +--- + +## 5. Epistemic agency already exists as a research concept + +**Epistemic agency** is established terminology in learning-sciences and education research. + +Different formulations emphasize learners' ability and responsibility to: + +- shape knowledge-building; +- decide what questions matter; +- evaluate evidence; +- construct or transform knowledge; +- participate as producers rather than passive recipients of knowledge. + +Examples: + +- Nieminen & Ketonen (2024), "Epistemic agency: a link between assessment, knowledge and society," *Higher Education* 88, 777–794. DOI: 10.1007/s10734-023-01142-5 +- Odden et al. (2023), work on disciplinary epistemic agency in undergraduate science. +- science-education traditions drawing on Scardamalia, Bereiter, Stroupe, and others. + +Root Sequence therefore should **not** claim coinage of epistemic agency. + +Its local question is narrower and infrastructural: + +> **What properties of a knowledge environment expand or suppress people's ability to exercise epistemic agency?** + +That includes discoverability. + +--- + +## 6. From unknown unknown to navigable question + +One useful trajectory is: + + felt pattern / curiosity + ↓ + ordinary-language question + ↓ + candidate concepts + ↓ + terminology / aliases + ↓ + fields / communities + ↓ + overview sources + ↓ + primary literature + ↓ + competing theories + ↓ + methods / evidence + ↓ + revised question + ↺ + +A failure can occur at every transition. + +Examples: + +### Vocabulary failure + +The user searches "system keeps doing what used to work" but never learns **path dependence**, **maladaptation**, **lock-in**, **double-loop learning**, or **adaptive trap**. + +### Field-routing failure + +The user finds generic productivity writing instead of resilience engineering or organizational learning. + +### Authority failure + +Popular SEO material outranks the primary scholar/archive. + +### Representation failure + +The person finds fifty papers but no map showing which questions they answer. + +### Gatekeeping failure + +The introductory source assumes vocabulary learned only after taking several courses. + +### Interface failure + +A system answers the current query so completely that it hides the surrounding field and terminates exploration. + +### Recommendation capture + +An algorithm repeatedly serves material similar to what the user already consumes, reducing encounter with genuinely different intellectual traditions. + +--- + +## 7. Epistemic discoverability is not maximum exposure + +More information is not automatically better. + +A system that exposes every possible related concept can destroy discoverability through overload. + +Good epistemic routing must balance: + +- novelty; +- relevance; +- cognitive load; +- uncertainty; +- serendipity; +- depth; +- accessibility; +- provenance. + +The goal is not: + +> show everything. + +It is: + +> **make the next useful intellectual moves visible without pretending there is only one path.** + +--- + +## 8. Progressive epistemic legibility + +This concept extends [Legible Systems](legible-systems.md). + +A progressively legible knowledge environment can support movement such as: + + intuition + ↓ + ordinary explanation + ↓ + canonical terminology + ↓ + field map + ↓ + overview + ↓ + original sources + ↓ + methods + ↓ + disagreements + ↓ + technical depth + ↓ + contribution + +A newcomer should not need expert vocabulary before they can discover the vocabulary. + +An expert should not be trapped behind simplified explanations that hide primary evidence. + +> **Concept first; term second; source third; mechanism underneath.** + +Not always literally in that sequence—but all should remain reachable. + +--- + +## 9. Design principles + +### 1. Accept the language the person has + +Do not require canonical terminology as the admission ticket. + +Map: + +- ordinary phrases; +- aliases; +- historical names; +- technical terms; +- neighboring-field vocabulary. + +### 2. Explain why a route is relevant + +"This field studies X because..." is more useful than a bare link. + +### 3. Preserve query evolution + +Let the research question change visibly rather than pretending the first formulation was final. + +### 4. Show neighboring disciplines + +A phenomenon may have: + +- biological; +- technical; +- social; +- philosophical; +- historical; +- political; +- design; + +treatments that should not be collapsed. + +### 5. Route to native methods + +Once the mechanism is identified, point to the discipline that actually studies it. + +### 6. Preserve primary-source paths + +A summary should not sever the route to: + +- papers; +- books; +- datasets; +- archives; +- standards; +- original authors; +- code. + +### 7. Surface disagreement + +Do not make the knowledge graph falsely smooth. + +Show: + +- competing definitions; +- rival theories; +- controversy; +- different disciplinary assumptions. + +### 8. Preserve serendipity without surrendering to engagement optimization + +Recommendation should support useful surprise, not endless retention. + +### 9. Make provenance visible + +Why is this source here? + +Who produced it? + +What role is it playing? + +### 10. Support stopping + +Epistemic agency includes deciding: + +> I know enough for this purpose. + +The interface should not turn curiosity into compulsory infinite consumption. + +--- + +## 10. Reading Trails as epistemic infrastructure + +[Reading Trails](../research/reading-trails/README.md) began as a way to preserve interesting resources encountered during research. + +This concept gives them a deeper function. + +A Reading Trail can act as a **bridge between vocabulary states**. + +Instead of: + + list of links + +it can preserve: + + question + ↓ + concept + ↓ + why it matters + ↓ + field + ↓ + approachable entry point + ↓ + deeper sources + ↓ + adjacent rabbit holes + +That is epistemic infrastructure. + +Reading Trails are not intended to replace: + +- libraries; +- search engines; +- bibliographies; +- academic databases; +- textbooks. + +They complement them by preserving the **route into the field**. + +--- + +## 11. Root Sequence as a knowledge router + +The maintained [Why Root Sequence?](root-sequence.md) page now describes RS as a conceptual commons and routing/synthesis layer. + +Epistemic discoverability makes one aspect of that role explicit. + +Given a question such as: + +> Why does a system keep doing something that used to work? + +Root Sequence might route: + +- **path dependence** — historical/institutional analysis; +- **maladaptation** — biological/ecological/psychological contexts; +- **double-loop learning** — organizational learning; +- **ultrastability** — cybernetics; +- **allostasis** — biological stress regulation; +- **lock-in** — economics/institutions/technology; +- **adaptive trap** — domain-specific use; +- **resilience engineering** — socio-technical systems. + +The output should not be: + +> They are secretly all the same phenomenon. + +It should be: + +> **You are noticing a family resemblance. Here are the fields that study different mechanisms inside that resemblance.** + +That is knowledge routing. + +--- + +## 12. AI and epistemic agency + +AI can lower the vocabulary barrier dramatically. + +A person can describe: + +> "the thing where an organization keeps repeating a strategy that used to work but conditions changed" + +and receive possible routes such as: + +- path dependence; +- organizational inertia; +- double-loop learning; +- maladaptation; +- lock-in; +- competency traps. + +That is powerful. + +But AI can also destroy epistemic agency by: + +- presenting synthesis without sources; +- selecting one interpretation too early; +- hiding alternatives; +- using authoritative language for uncertain mappings; +- summarizing away disagreement; +- answering instead of teaching how to continue inquiry; +- making the user dependent on the model as the only route to knowledge. + +The design objective should therefore be: + +> **AI that expands the user's ability to navigate knowledge without making itself the permanent gatekeeper of that navigation.** + +This strongly connects to: + +- Legible Systems; +- Wingbot; +- liberated intelligence; +- user-configurable cognitive interfaces; +- Reading Trails; +- agency vs automation. + +--- + +## 13. Discoverability has politics + +Knowledge access is shaped by: + +- paywalls; +- language; +- academic prestige; +- search ranking; +- recommendation systems; +- institutional credentials; +- publication norms; +- library access; +- disability/accessibility; +- censorship; +- platform ownership; +- disciplinary siloing; +- who receives funding and preservation. + +So epistemic discoverability is not only an interface problem. + +Ask: + +- Which knowledge becomes easy to encounter? +- Which requires insider vocabulary? +- Which is systematically buried? +- Whose classifications become canonical? +- Who controls indexing? +- Which archives disappear? +- Who can participate in producing knowledge? +- Which communities are treated as sources versus subjects? + +A knowledge router must not pretend these conditions are neutral. + +--- + +## 14. Design test + +When evaluating a knowledge environment, ask: + +1. Can someone begin from ordinary language? +2. Can they discover the field's preferred terminology? +3. Does the system recognize multiple plausible terms for the same target? +4. Can the query evolve as understanding changes? +5. Are neighboring disciplines visible without being falsely unified? +6. Can the user see why a suggested source/path is relevant? +7. Are primary sources reachable? +8. Is source role/provenance clear? +9. Are competing interpretations visible? +10. Are prerequisites explained or bridged? +11. Does the system support exploration without overwhelming the person? +12. Does it preserve unexpected but relevant discovery? +13. Can the user leave the AI/recommender and continue independently? +14. Does the environment help people create/evaluate knowledge, not merely consume answers? +15. Who or what controls the ranking/routing layer? +16. Which people or traditions become effectively undiscoverable under the current vocabulary/index? +17. Can someone stop with a useful partial understanding and return later without reconstructing the entire inquiry? + +--- + +## 15. Relationship to other Root Sequence concepts + +### Legible Systems + +Legibility asks whether a system helps affected people understand and work with it. + +Epistemic discoverability asks whether a **knowledge environment helps people find the concepts required to understand it in the first place**. + +### Dynamic Coherence / Adaptive Continuity + +New knowledge changes future search behavior. + +A concept can alter the researcher's transition dynamics by making previously unavailable questions and resources reachable. + +This is an epistemic example of history changing later possibility. + +### Agency + +Knowledge changes what actions can be perceived, evaluated, and enacted. + +But knowledge alone does not erase material, institutional, bodily, or authority constraints. + +### User-Configurable Cognitive Interfaces + +Different people may need different routes through the same knowledge space. + +### Legible AI-Assisted Expression + +AI should make its synthesis, sources, transformations, and uncertainty inspectable. + +### Reading Trails + +Reading Trails are the first lightweight RS implementation of this concept. + +--- + +## 16. Candidate future artifact: Conceptual Router + +A possible future Root Sequence tool could accept a question in ordinary language and return a **routing graph**, not merely an answer. + +Example: + + "Why does a system keep doing something that used to work?" + │ + ┌───────┴────────┐ + ↓ ↓ + historical lock-in adaptive response + │ │ + path dependence maladaptation + increasing returns allostasis (biological) + institutionalism resilience + │ │ + └───────┬────────┘ + ↓ + organizational learning + │ + double-loop learning + +For every route: + +- what the term means; +- what field owns it; +- why it might fit; +- why it might **not** fit; +- best entry resource; +- deeper source; +- related RS material. + +This would be closer to an **intellectual transit map** than a chatbot answer. + +Do not build it until the Reading Trails and routing method have enough real use to justify the structure. + +--- + +## 17. Research anchors + +These sources support components of the model, not the whole Root Sequence synthesis. + +- Furnas, Landauer, Gomez & Dumais (1987), "The Vocabulary Problem in Human-System Communication." DOI: 10.1145/32206.32212 +- Bates (1989), "The Design of Browsing and Berrypicking Techniques for the Online Search Interface." https://pages.gseis.ucla.edu/faculty/bates/berrypicking.html +- Pirolli & Card (1999), "Information Foraging." DOI: 10.1037/0033-295X.106.4.643 +- Russell, Stefik, Pirolli & Card (1993), "The Cost Structure of Sensemaking." DOI: 10.1145/169059.169209 +- Nieminen & Ketonen (2024), "Epistemic agency: a link between assessment, knowledge and society." DOI: 10.1007/s10734-023-01142-5 + +--- + +## Working principle + +> **A knowledge system should not require someone to already possess the vocabulary, map, or institutional access that the system is supposed to help them acquire.** + +And: + +> **A good answer should increase the person's capacity to discover the next good question.** From f8c0958e2921a2e2a72425964c88b7993cc12757 Mon Sep 17 00:00:00 2001 From: Rae Lovejoy Date: Thu, 24 Sep 2026 23:51:48 -0700 Subject: [PATCH 46/66] Add information discovery and sensemaking Reading Trail --- .../information-discovery-sensemaking.md | 323 ++++++++++++++++++ 1 file changed, 323 insertions(+) create mode 100644 research/reading-trails/information-discovery-sensemaking.md diff --git a/research/reading-trails/information-discovery-sensemaking.md b/research/reading-trails/information-discovery-sensemaking.md new file mode 100644 index 0000000..13cd4c4 --- /dev/null +++ b/research/reading-trails/information-discovery-sensemaking.md @@ -0,0 +1,323 @@ +# Information Discovery, Sensemaking & Epistemic Agency + +**Status:** Developing Reading Trail, 2026-09-24 +**Related concept:** [Epistemic Discoverability and Knowledge Routing](../../concepts/epistemic-discoverability.md) + +This Reading Trail is for the wonderfully recursive question: + +> **How do people find knowledge when they don't yet know what to search for?** + +## 1. Marcia Bates — Berrypicking + +**Author page / paper:** https://pages.gseis.ucla.edu/faculty/bates/berrypicking.html +**Type:** primary information-science paper / old-web author page +**Rabbit-hole value:** ★★★★★★★★★★ + +Bates's model says real research often does **not** begin with one fixed query. + +The query evolves as the searcher learns. + +This is almost a documentary description of a good rabbit hole. + +Follow from here into: + +- browsing; +- evolving queries; +- citation chasing; +- footnote chasing; +- journal runs; +- information-seeking behavior. + +--- + +## 2. The Vocabulary Problem + +**Paper DOI:** https://doi.org/10.1145/32206.32212 +**Title:** "The Vocabulary Problem in Human-System Communication" +**Authors:** Furnas, Landauer, Gomez, Dumais +**Year:** 1987 +**Type:** foundational HCI / information-access paper +**Rabbit-hole value:** ★★★★★★★★ + +The famous/important result: people use dramatically different words for the same thing. + +This should permanently alter how you think about: + +- search boxes; +- menus; +- command names; +- documentation; +- knowledge graphs; +- AI interfaces. + +If a system recognizes only the designer's favorite term, **the user is made to look ignorant when the interface is actually linguistically brittle**. + +--- + +## 3. Pirolli & Card — Information Foraging + +**DOI:** https://doi.org/10.1037/0033-295X.106.4.643 +**Type:** theoretical information-seeking model +**Rabbit-hole value:** ★★★★★★★★ + +Core vocabulary: + +- information patches; +- information scent; +- information diet; +- adaptive strategies for seeking valuable information. + +This gives an entire theory for why some links, labels, summaries, citation trails, and interfaces invite useful exploration while others produce dead ends. + +--- + +## 4. Sensemaking + +**Paper:** Russell, Stefik, Pirolli & Card, "The Cost Structure of Sensemaking" +**DOI:** https://doi.org/10.1145/169059.169209 +**Type:** HCI / cognition / analysis +**Rabbit-hole value:** ★★★★★★★ + +Sensemaking is treated as constructing/searching for representations that let a person answer task-specific questions. + +If you've ever gone: + +> "I have all the information but I cannot hold the shape of it in my head" + +this is your neighborhood. + +Relevant to: + +- concept maps; +- graph views; +- dossiers; +- timelines; +- visual research tools; +- RS website views; +- intelligence analysis; +- external cognition. + +--- + +## 5. Epistemic agency + +**Overview paper:** https://link.springer.com/article/10.1007/s10734-023-01142-5 +**Type:** education / learning science / knowledge-building +**Rabbit-hole value:** ★★★★★★★ + +A contemporary formulation describes epistemic agency around people's ability to **evaluate, produce, use, and transform knowledge agentically**. + +Related traditions go back through: + +- knowledge building; +- Scardamalia & Bereiter; +- science education; +- students deciding what counts as evidence; +- learners becoming participants in disciplinary knowledge practices. + +Search terms: + +- epistemic agency; +- shared epistemic agency; +- disciplinary epistemic agency; +- knowledge building communities; +- cognitive authority. + +--- + +## 6. Information behavior / Library and Information Science + +This entire field is likely a giant underexplored RS neighborhood. + +Search terms: + +- information seeking behavior; +- information practices; +- exploratory search; +- browsing behavior; +- information encountering; +- serendipitous discovery; +- relevance; +- knowledge organization; +- faceted classification; +- controlled vocabularies; +- thesauri; +- subject headings; +- query expansion. + +This is where "how do humans actually look for things?" becomes a serious research field rather than a search-engine implementation detail. + +--- + +## 7. Exploratory search + +Search term: + +> **exploratory search** + +Useful distinction: + +- lookup: "find the answer/object I already know how to name"; +- exploratory search: learn, investigate, compare, discover vocabulary, and reformulate the problem. + +This is much closer to the way Root Sequence research usually works. + +Follow into: + +- faceted search; +- visual search; +- query suggestions; +- result diversification; +- interactive information retrieval. + +--- + +## 8. Citation chaining + +A wonderfully simple research superpower. + +### Backward chaining + +What did this paper cite? + +### Forward chaining + +Who later cited this paper? + +### Author chaining + +What else did these people write? + +### Venue chaining + +What else does this journal/conference/community publish? + +Reading Trails should make these moves explicit. + +A DOI is not the end of a search. + +It is a junction. + +--- + +## 9. Scholar and author pages + +A weirdly valuable category of web resource. + +Many of the best trails in this project came from: + +- personal academic pages; +- institutional publication lists; +- old HTML paper copies; +- scholar-maintained archives. + +These often expose **intellectual neighborhoods** better than commercial search interfaces. + +Examples already encountered: + +- Marcia Bates's UCLA page; +- Werner Ulrich's site; +- W. Ross Ashby Digital Archive; +- Erik Hollnagel's site. + +Do not automatically treat personal hosting as weaker evidence when it is the author's legitimate copy of published work—but verify publication metadata for consequential claims. + +--- + +## 10. Search as learning, not retrieval + +A useful mental-model inversion: + +Traditional search: + + need + ↓ + query + ↓ + result + ↓ + done + +Exploratory research: + + curiosity + ↓ + partial query + ↓ + encounter + ↓ + new vocabulary + ↓ + revised question + ↓ + new source type + ↓ + field discovered + ↓ + disagreement + ↓ + better question + ↺ + +This is why "just give me the answer" and "help me research" are fundamentally different interface goals. + +--- + +## Suggested rabbit-hole route: "I know the idea but not its name" + +1. The Vocabulary Problem +2. Bates — berrypicking +3. information foraging +4. exploratory search +5. knowledge organization / thesauri +6. epistemic agency +7. sensemaking + +## Suggested rabbit-hole route: "build me a better research interface" + +1. information foraging +2. sensemaking +3. exploratory search +4. faceted search +5. knowledge graphs +6. information visualization +7. HCI / cognitive ergonomics +8. Root Sequence's [Epistemic Discoverability](../../concepts/epistemic-discoverability.md) + +## Suggested rabbit-hole route: "why does AI help me think?" + +1. distributed cognition +2. external cognition +3. sensemaking +4. epistemic agency +5. cognitive offloading +6. AI-assisted expression +7. extended mind +8. human–AI joint cognitive systems + +--- + +## Future sites/resources to investigate + +- ASIS&T — Association for Information Science and Technology; +- ACM SIGIR — Information Retrieval; +- ACM CHI / HCI archives; +- iSchools consortium and LIS course materials; +- InformationR.net; +- *Journal of the Association for Information Science and Technology*; +- *Information Processing & Management*; +- *Journal of Documentation*; +- exploratory-search and serendipity research groups; +- visual analytics / intelligence-analysis communities. + +Curate before promoting into the main trail. + +--- + +## Root Sequence takeaway + +The web is not only an information repository. + +It is a landscape of **possible intellectual moves**. + +A good research interface should help people discover paths they could not have requested in advance. From 60aa8033fc79376715d41fd870ba31b32bc3b054 Mon Sep 17 00:00:00 2001 From: Rae Lovejoy Date: Thu, 24 Sep 2026 23:52:17 -0700 Subject: [PATCH 47/66] Route epistemic discoverability from concepts index --- concepts/README.md | 1 + 1 file changed, 1 insertion(+) diff --git a/concepts/README.md b/concepts/README.md index 4cbb3e7..7081b38 100644 --- a/concepts/README.md +++ b/concepts/README.md @@ -15,6 +15,7 @@ Document roles and evidence boundaries should be stated on each page. Being list - [Dynamic Coherence and Adaptive Continuity](dynamic-coherence.md) — a review-pending cross-project framework for path dependence, adaptive change, agency as effective future possibility, continuity-through-transformation, and coherence across time and scale. - [Agency and Automation](agency-and-automation.md) — a review-pending principle about reducing compulsory burdens while preserving chosen participation, bounded delegation, collective authority, and recovery. - [Legible Systems](legible-systems.md) — a working design principle about progressive understanding, technical accessibility, repair, alternatives, and power. +- [Epistemic Discoverability and Knowledge Routing](epistemic-discoverability.md) — a working concept for helping people move from the language/questions they currently have toward fields, terminology, sources, methods, and communities they do not yet know how to name. - [Legible AI-Assisted Expression](legible-ai-assisted-expression.md) — a working principle for reducing the cost of expression while keeping human contributions, AI additions, transformations, evidence, uncertainty, and decisions visible. - [Intelligence Ecology](intelligence-ecology.md) — a developing framework for asking what behaviors an environment selects for in intelligent systems. - [Human(e) Design](humane-design.md) — a translation method between human observation and concrete design choices. From f1ae0d15113f56e74f474e480f1c3030b7af3a0f Mon Sep 17 00:00:00 2001 From: Rae Lovejoy Date: Thu, 24 Sep 2026 23:52:20 -0700 Subject: [PATCH 48/66] Route information-discovery Reading Trail --- research/reading-trails/README.md | 1 + 1 file changed, 1 insertion(+) diff --git a/research/reading-trails/README.md b/research/reading-trails/README.md index eaf3a08..c0a2782 100644 --- a/research/reading-trails/README.md +++ b/research/reading-trails/README.md @@ -49,6 +49,7 @@ Do not replace claim-level evidence with a cool website. ## Current trails - [Systems, Cybernetics, Complexity & Adaptive Systems](systems-cybernetics-complexity.md) — the current giant rabbit hole: cybernetics, systems thinking, system dynamics, resilience engineering, critical systems, organizational cybernetics, complexity science, and systemic design. +- [Information Discovery, Sensemaking & Epistemic Agency](information-discovery-sensemaking.md) — how people search when they do not yet know the vocabulary: berrypicking, information foraging, the vocabulary problem, exploratory search, sensemaking, and knowledge-building agency. ## Future use From 83aac14c133d1463c34f7a6f1398f19a0a5df45a Mon Sep 17 00:00:00 2001 From: Rae Lovejoy Date: Thu, 24 Sep 2026 23:52:22 -0700 Subject: [PATCH 49/66] Connect Legible Systems to epistemic discoverability --- concepts/legible-systems.md | 50 +++++++++++++++++++++++++++++++++++++ 1 file changed, 50 insertions(+) diff --git a/concepts/legible-systems.md b/concepts/legible-systems.md index 823091f..7d7a7dd 100644 --- a/concepts/legible-systems.md +++ b/concepts/legible-systems.md @@ -192,6 +192,56 @@ A system should preserve enough documentation, provenance, naming, history, and --- +## Epistemic discoverability + +Legibility can fail **before** someone reaches the system. + +A person may recognize a pattern, problem, or need while lacking the specialist vocabulary required to find the relevant: + +- documentation; +- field; +- standard; +- research community; +- diagnostic; +- repair method; +- source; +- expert; +- alternative implementation. + +[Epistemic Discoverability and Knowledge Routing](epistemic-discoverability.md) develops this problem directly. + +For Legible Systems, the implication is: + +> **Do not require people to know the system's preferred vocabulary before the system will help them discover that vocabulary.** + +Practical patterns include: + +- aliases and ordinary-language entry points; +- explanations that introduce the canonical term after the concept; +- visible "related concepts / neighboring fields" routes; +- searchable error messages that preserve both plain language and technical identifiers; +- documentation that says what question a page helps answer, not only its internal component name; +- paths from explanation → specification → source; +- multiple representations and terminology bridges. + +The principle extends progressive legibility outward: + + encounter / question + ↓ + recognizable language + ↓ + system terminology + ↓ + deeper model + ↓ + source / mechanism + ↓ + independent navigation + +A system is more legible when participation helps people acquire the vocabulary needed to become **less dependent on the original interface or explainer**. + +--- + ## Learning should be a property of the system Legible Systems collapses a common separation between **the thing** and **the course explaining the thing**. From 506e3edcfa8820f42bc787bdc0f825be90ce8b20 Mon Sep 17 00:00:00 2001 From: Rae Lovejoy Date: Thu, 24 Sep 2026 23:52:24 -0700 Subject: [PATCH 50/66] Add epistemic discoverability to design grammar --- concepts/design-grammar.md | 1 + 1 file changed, 1 insertion(+) diff --git a/concepts/design-grammar.md b/concepts/design-grammar.md index b016abf..f60a524 100644 --- a/concepts/design-grammar.md +++ b/concepts/design-grammar.md @@ -19,6 +19,7 @@ This wording is a proposed synthesis, not an approved project slogan. Coherence | --- | --- | --- | | Model relationships and conditions | What environment, incentives, dependencies, feedback, and history produce the outcome? | [Systems](../systems/README.md) and [Intelligence Ecology](intelligence-ecology.md) | | Route mechanisms to their native methods | Which discipline or established method already studies the mechanism we are invoking? What remains after its distinctions and evidence limits are restored? | [Why Root Sequence?](root-sequence.md#a-routing-and-synthesis-layer-not-a-replacement-discipline) and [Dynamic Coherence lineage](../research/dynamic-coherence-lineage.md) | +| Make knowledge discoverable before vocabulary is mastered | Can someone begin from the question they actually have and discover the terms, fields, sources, and methods needed to go deeper? | [Epistemic Discoverability and Knowledge Routing](epistemic-discoverability.md) and [Reading Trails](../research/reading-trails/README.md) | | Preserve adaptive continuity | What should remain stable, what must remain changeable, and which meaningful future actions does this decision open or close? | [Dynamic Coherence and Adaptive Continuity](dynamic-coherence.md) and [Adaptation](../systems/adaptation/README.md) | | Expand agency through chosen participation and delegation | Which burdens can be removed, and who retains a meaningful say over the result? | [Agency and Automation](agency-and-automation.md) | | Keep authority scoped and contestable | Who may act for whom, on what basis, and who else bears the effects? | [Agency and Automation](agency-and-automation.md) and [Idea Trail 9](../IDEA_TRAILS.md#trail-9--intelligence-automation-and-legitimate-authority) | From 7929f28034fbd9b2eb3d18c0b4228b77b0d9fcec Mon Sep 17 00:00:00 2001 From: Rae Lovejoy Date: Thu, 24 Sep 2026 23:52:27 -0700 Subject: [PATCH 51/66] Connect Root Sequence identity to epistemic routing --- concepts/root-sequence.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/concepts/root-sequence.md b/concepts/root-sequence.md index 6d85b95..710eccc 100644 --- a/concepts/root-sequence.md +++ b/concepts/root-sequence.md @@ -56,6 +56,8 @@ Instead: This makes the central repository a **conceptual commons and routing layer**. +That routing role includes **epistemic discoverability**: helping someone who has a real question but not yet the field's vocabulary discover the relevant terms, literatures, communities, and methods. See [Epistemic Discoverability and Knowledge Routing](epistemic-discoverability.md) and the [Reading Trails](../research/reading-trails/README.md). + It can hold shared questions such as: > What conditions made this possible, and what does it make possible next? From 005a649476630fbb809879f64a896eda614a6f05 Mon Sep 17 00:00:00 2001 From: Rae Lovejoy Date: Fri, 25 Sep 2026 00:06:15 -0700 Subject: [PATCH 52/66] Add canonical Root Sequence research method --- research/method.md | 551 +++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 551 insertions(+) create mode 100644 research/method.md diff --git a/research/method.md b/research/method.md new file mode 100644 index 0000000..1d65efa --- /dev/null +++ b/research/method.md @@ -0,0 +1,551 @@ +# Root Sequence Research Method + +**Document role:** Canonical cross-project research method +**Status:** Developing / active, 2026-09-24 +**Scope:** How Root Sequence turns an intuition, pattern, or cross-domain connection into research that can be checked, narrowed, split, or retired. +**Evidence boundary:** This method draws on established practices including source criticism, comparative method, critical systems thinking, methodological pluralism, preregistration, falsification-oriented testing, and domain-specific research methods. It is a Root Sequence workflow, not a claim of methodological novelty. + +## Short version + +> **Notice → preserve → decompose → route → source → compare → test → revise → translate → observe → repeat.** + +The method is designed for a recurring Root Sequence problem: + +> A pattern feels important across several domains before we know whether the similarity is causal, structural, metaphorical, normative, or accidental. + +The goal is to **preserve the generative insight without allowing the insight to outrun the evidence**. + +--- + +## 1. Notice the pattern + +Start with the thing that feels connected. + +Examples: + +- "This trauma/adaptation pattern looks like something institutions do." +- "Repairability, exit, and agency seem to share a deeper structure." +- "A system can change not only state but how it changes later." +- "People may be unable to find knowledge because they don't yet know the vocabulary." + +Do not require polished academic language at this stage. + +Record the intuition before cleaning it up. + +### Output + +A plain-language observation or question. + +### Failure mode + +Rejecting an insight because it is not yet technically formulated. + +--- + +## 2. Preserve the raw insight + +Capture: + +- original wording; +- context that triggered it; +- examples; +- analogies; +- emotional/intuitive significance where relevant; +- immediate connections; +- unresolved contradictions. + +Preserving provenance matters because later formalization can accidentally erase what was actually interesting. + +### Output + +Conversation provenance, Idea Trail, seed note, or research log. + +### Failure mode + +Replacing the original question with a polished formulation so early that the real question disappears. + +--- + +## 3. Decompose the concept + +Before treating a striking phrase as one phenomenon, ask what it contains. + +Example: + +"agency envelope" decomposed into: + +- affordance; +- reachability; +- substantive opportunity; +- knowledge; +- perceived feasibility; +- authorization; +- material support; +- causal control; +- power over conditions; +- value/choice. + +"meta-agency" decomposed into: + +- self-modification; +- environment modification; +- institutional modification; +- capacity building. + +### Output + +Distinction table / concept decomposition. + +### Failure mode + +Inventing a new latent variable that merely bundles several existing concepts. + +--- + +## 4. Route to native disciplines + +Ask: + +> **Who already studies each mechanism?** + +Examples: + +| Question | Native methods / literatures | +| --- | --- | +| technical failure/propagation | reliability engineering, SRE, safety engineering | +| constrained reachability | control theory, viability theory | +| substantive human opportunity | capability approach, accessibility/usability | +| contested system boundary | Critical Systems Heuristics | +| multiple problem framings | Soft Systems Methodology | +| organizational governing assumptions | double-loop / organizational learning | +| organizational viability | organizational cybernetics / VSM | +| ecological adaptation | ecological resilience / adaptive management | +| trauma | trauma/stress/clinical/lived-expertise literatures | +| consciousness | neuroscience, philosophy of mind, comparative consciousness | +| information discovery | information science, HCI, exploratory search | + +### Rule + +> **If a mature field already owns the mechanism, learn its distinctions before creating Root Sequence vocabulary.** + +### Failure mode + +Cross-domain language replacing domain expertise. + +--- + +## 5. Build the source trail + +Distinguish: + +- **claim evidence** — supports or constrains a specific factual claim; +- **related work** — shows prior concepts/methods; +- **orientation source** — teaches the vocabulary/field; +- **Reading Trail** — helps humans discover the intellectual neighborhood; +- **historical source** — establishes provenance; +- **counterexample / critique** — challenges the proposed synthesis. + +Prefer primary research and authoritative references for consequential claims. + +Preserve weird useful websites and archives separately as Reading Trails rather than pretending they prove the claim. + +### Failure mode + +Bibliography inflation: collecting titles without reading enough to know what they support. + +--- + +## 6. Classify every important statement + +Use labels such as: + +- **EMPIRICAL / DOMAIN RESULT** +- **MATHEMATICAL / FORMAL RESULT** +- **WORKING DEFINITION** +- **PHILOSOPHICAL ARGUMENT** +- **MODEL / METAPHOR** +- **STRUCTURAL ANALOGY** +- **INTERPRETATION** +- **NORMATIVE COMMITMENT** +- **HYPOTHESIS** +- **SPECULATION** +- **UNKNOWN** + +A thought experiment is not an experiment. + +A cross-domain resemblance is not evidence of a shared mechanism. + +A compelling metaphor is not a causal explanation. + +--- + +## 7. Restore the differences + +After finding similar structure, deliberately ask how the cases differ. + +For every transfer: + +| Dimension | Domain A | Domain B | +| --- | --- | --- | +| state | | | +| mechanism | | | +| feedback | | | +| memory/history | | | +| boundary | | | +| agency | | | +| power | | | +| evidence | | | +| timescale | | | +| normative stakes | | | + +Possible conclusion: + +- same mechanism; +- related mechanism; +- partial structural analogy; +- useful metaphor only; +- misleading resemblance; +- unresolved. + +### Failure mode + +Everything becoming "the same pattern" because the abstraction is too loose to fail. + +--- + +## 8. Map boundary and power + +Before saying a system "works," ask: + +- Who defined the purpose? +- Who chose the boundary? +- Who decides? +- Who controls resources? +- Whose knowledge counts? +- Who is affected but not involved? +- Who can appeal, refuse, exit, repair, revise? +- Who bears externalized costs? +- Who can alter the conditions of everybody else's future action? + +Use established critical-systems methods when this is central. + +### Failure mode + +Systems language turning domination into neutral architecture. + +--- + +## 9. Generate competing explanations + +Never let the favored synthesis be the only live model. + +Record: + +- ordinary domain explanation; +- alternative mechanism; +- simpler explanation; +- confound; +- measurement artifact; +- selection effect; +- structural explanation; +- historical explanation. + +Ask: + +> What would we believe if the exciting synthesis were false? + +### Failure mode + +The framework explaining everything because nothing else is allowed to explain anything. + +--- + +## 10. Compare against a competent baseline + +A Root Sequence method does not earn credit merely because it can describe a case. + +Before testing, select the strongest reasonable native baseline. + +Examples: + +- ordinary competent reliability review; +- STPA; +- capability approach; +- Critical Systems Heuristics; +- accessibility evaluation; +- viability analysis; +- organizational-learning analysis. + +Give methods: + +- the same evidence; +- the same decision question; +- comparable resources. + +Record: + +- unique consequential findings; +- duplicate findings; +- false alarms; +- unsupported extrapolation; +- information requests; +- privacy burden; +- analyst burden; +- disagreements. + +### Rule + +> **Rediscovering a baseline method's central insight is not added value.** + +--- + +## 11. Freeze before testing + +When doing a comparison: + +1. select the case; +2. explain why it was selected; +3. freeze the evidence packet; +4. freeze method prompts; +5. state conflicts of interest; +6. state the null result; +7. state what would make the framework narrower. + +Do this **before** method outputs. + +### Failure mode + +Editing the method after seeing which case it loses. + +--- + +## 12. Prefer adversarial cases + +Do not begin with the example that most beautifully illustrates the theory. + +Prefer cases where: + +- established methods should perform well; +- the framework could genuinely add nothing; +- the evidence contains ambiguity; +- several interpretations remain possible. + +A near-null result is valuable. + +### Example + +The first T-003 Cloudflare pilots found almost no unique decision-relevant value from Dynamic Coherence beyond competent ordinary incident review. + +That result narrowed the framework toward a routing/synthesis role. + +This is desired behavior. + +--- + +## 13. Let concepts fail + +Allowed outcomes: + +- **KEEP** — useful and discriminating; +- **NARROW** — useful in a smaller scope; +- **SPLIT** — one concept was several; +- **ROUTE** — established literature owns the mechanism; +- **RENAME** — terminology collides or misleads; +- **ARCHIVE** — historically useful, not current; +- **RETIRE** — adds no useful distinction. + +Do not reward a concept simply for having accumulated documentation. + +--- + +## 14. Translate locally + +A shared concept should not be copied wholesale across projects. + +Ask: + +> What changes in this project's actual design/research problem? + +Examples: + +- Dynamic Coherence → Coherent Computing: future capability after adaptation. +- Dynamic Coherence → Community Infrastructure: provider/institution dependency and later replaceability. +- Adaptive continuity → Liberated Intelligence: rule-level revision accountability. +- Epistemic discoverability → Legible Systems: discover vocabulary before requiring it. + +### Failure mode + +Every repo acquiring a near-identical manifesto. + +--- + +## 15. Operationalize + +A useful concept should eventually change something inspectable: + +- design requirement; +- acceptance case; +- model variable; +- experiment; +- research question; +- documentation structure; +- interface; +- scenario; +- decision process. + +If nothing changes except prose, ask whether the concept is doing work. + +--- + +## 16. Observe consequences + +After applying the idea: + +- what became easier to notice? +- what became harder? +- what did the concept obscure? +- did users/reviewers interpret it consistently? +- did it add burden? +- did it change a decision? +- did it create new lock-in? +- what did the intervention make possible next? + +The result becomes new evidence. + +--- + +## 17. Revise visibly + +Preserve: + +- prior version; +- reason for revision; +- evidence that prompted it; +- what was retained; +- what was rejected. + +Do not rewrite history to make current theory appear inevitable. + +> **Research itself should exhibit accountable adaptation.** + +--- + +## 18. AI-assisted research rules + +AI can be useful for: + +- externalizing many simultaneous ideas; +- literature discovery; +- terminology routing; +- source comparison; +- structured extraction; +- counterexample generation; +- drafting distinctions; +- maintaining research maps. + +AI must not silently convert: + +- plausible wording → established finding; +- source proximity → source support; +- analogy → mechanism; +- thought experiment → data; +- repetition → confidence; +- synthetic review → independent review. + +When AI helped generate the framework being tested, disclose the conflict. + +An AI grading its own theory is an editorial pilot, not validation. + +--- + +## 19. Research-slop test + +Ask: + +1. Is the claim falsifiable or at least discriminating? +2. Does the vocabulary correspond to a mechanism, relation, or useful distinction? +3. Could an established term do the job better? +4. Have counterexamples been preserved? +5. Did we compare against competent alternatives? +6. Is evidence attached to the actual claim? +7. Does the synthesis retain domain differences? +8. Would we publish a null result? +9. What would make us retire the concept? +10. Has the concept changed something beyond the prose? + +If most answers are no, stop expanding. + +--- + +## 20. Compact research record + + INTUITION / QUESTION: + + ORIGINAL WORDING / PROVENANCE: + + DECOMPOSED CONCEPTS: + + NATIVE FIELDS / METHODS: + + KEY SOURCES: + + CLAIM TYPES: + + CROSS-DOMAIN MAPPING: + + IMPORTANT DIFFERENCES: + + BOUNDARY / POWER QUESTIONS: + + COMPETING EXPLANATIONS: + + BASELINE METHOD: + + CASE: + + FROZEN EVIDENCE: + + WHAT WOULD COUNT AGAINST THIS: + + RESULT: + + KEEP / NARROW / SPLIT / ROUTE / RENAME / ARCHIVE / RETIRE: + + PROJECT TRANSLATIONS: + + NEXT OBSERVATION: + +--- + +## 21. The loop + + notice + ↓ + preserve + ↓ + decompose + ↓ + route + ↓ + source + ↓ + restore differences + ↓ + map boundary + power + ↓ + compare + ↓ + test + ↓ + keep / narrow / split / retire + ↓ + translate locally + ↓ + observe consequences + ↓ + revise + ↺ + +## Working principle + +> **Connect boldly. Claim cautiously. Route mechanisms to the people and fields that know them best. Build the synthesis so it can survive being wrong.** From 1523be63b0379621abbd38197cfb9ce412808234 Mon Sep 17 00:00:00 2001 From: Rae Lovejoy Date: Fri, 25 Sep 2026 00:06:19 -0700 Subject: [PATCH 53/66] Add Root Sequence method and concept router --- research/method-router.md | 134 ++++++++++++++++++++++++++++++++++++++ 1 file changed, 134 insertions(+) create mode 100644 research/method-router.md diff --git a/research/method-router.md b/research/method-router.md new file mode 100644 index 0000000..253dff4 --- /dev/null +++ b/research/method-router.md @@ -0,0 +1,134 @@ +# Root Sequence Method & Concept Router + +**Document role:** Practical routing map +**Status:** Developing / not exhaustive +**Purpose:** Help identify what kind of question is hiding inside a messy systems problem and which established methods/literatures should be checked before Root Sequence invents new vocabulary. + +## How to use it + +Start with the **shape of the question**, not the field you hope will answer it. + +A single real-world problem may route to several rows. + +Root Sequence's job is then to preserve the relationships among those analyses without pretending one method replaces the others. + +| Question shape | Concepts to inspect | Native methods / literatures | Common RS failure if skipped | +| --- | --- | --- | --- | +| "Why did this technical system fail or amplify failure?" | dependency, feedback, coupling, control, capacity | SRE/reliability engineering, safety engineering, STPA where appropriate, control theory | grand systems language replacing debugging/engineering | +| "Why does it keep doing what used to work?" | path dependence, lock-in, maladaptation, governing variables | historical institutionalism, organizational learning, double-loop learning, resilience/adaptation literature | calling everything an attractor | +| "What future states are actually possible under these constraints?" | reachability, viability, control | control theory, viability theory, operations research | treating metaphorical possibility-space as mathematics | +| "Does this person really have an option?" | capability, affordance, accessibility, conversion factors | capability approach, disability/accessibility research, HCI, ecological psychology | counting menu options as agency | +| "What can this body/environment relation enable?" | affordance, skill, body schema | ecological psychology, embodied cognition, disability/access research | assuming physical presence = usable possibility | +| "Who defined success and the system boundary?" | boundary judgment, purpose, beneficiary, affected parties | Critical Systems Heuristics | treating boundaries as neutral facts | +| "Are people solving different problems because they see different situations?" | worldview, framing, problem situation | Soft Systems Methodology, participatory design | forcing one ontology | +| "Who can shape the conditions under which others act?" | institutional/structural/productive power, decision rights | political/social theory, CSH, institutional analysis | calling power 'constraints' and making it disappear | +| "Who can revise the rules themselves?" | meta-level control, governing variables, constitutional choice | organizational learning, governance, institutional design | confusing user choice with rule-making power | +| "Can this organization survive while retaining local autonomy?" | viability, recursion, autonomy/cohesion | organizational cybernetics, VSM | generic 'coherence' replacing organizational theory | +| "Can the system keep adapting as demands change?" | adaptive capacity, graceful extensibility, sustained adaptability | resilience engineering | treating stability as resilience | +| "What should persist through transformation?" | identity, continuity, lineage, function | philosophy of identity, biology of individuality, organizational theory, domain-specific continuity models | assuming sameness = continuity | +| "How does a living system maintain itself?" | autopoiesis, closure, viability, regulation | theoretical biology, enactivism, physiology | importing organism metaphors into institutions/AI | +| "What does this stress/trauma response mean?" | stress regulation, trauma, learning, safety | trauma research, psychology, physiology, lived expertise | diagnosing by systems analogy | +| "Is this artificial system conscious/suffering?" | phenomenology, sentience, report, access, self-model | consciousness science, philosophy of mind, AI-welfare research | functional adaptation → experience leap | +| "How do people find the field/term they don't know exists?" | vocabulary problem, exploratory search, berrypicking, sensemaking | information science, HCI, knowledge organization, epistemic-agency research | assuming search failure = user ignorance | +| "How should we learn from intervention?" | experiment, feedback, model revision, adaptive management | experimental design, adaptive management, causal inference, domain methods | simulation output → real-world fact | +| "Why did a metric improve while reality got worse?" | proxy failure, Goodhart effects, externality | measurement theory, causal analysis, domain evaluation | treating coherence as another score | +| "How are local and system-level outcomes interacting?" | emergence, downward constraint, cross-scale effects | complexity science, network science, domain models | claiming emergence without mechanism | +| "What should happen when knowledge/conditions are uncertain?" | uncertainty, calibration, reversible action | decision theory, Bayesian methods, risk/safety methods | false precision | +| "Whose labor or cost is hidden by the successful system?" | externalization, maintenance, care work | labor/process analysis, lifecycle analysis, feminist STS, institutional analysis | local optimization masquerading as coherence | + +## Routing sequence + +When a question arrives: + + ordinary-language question + ↓ + identify 2–5 plausible question shapes + ↓ + name candidate mechanisms + ↓ + route to native fields + ↓ + gather orientation + primary evidence + ↓ + compare interpretations + ↓ + return a connected map + ↓ + only then decide whether RS vocabulary adds anything + +## What the router should return + +For each route: + +- **candidate concept** +- **why it might fit** +- **why it might not fit** +- **field / community** +- **best orientation source** +- **primary or canonical source** +- **method** +- **evidence needed** +- **related RS project** +- **confidence / unresolved ambiguity** + +## Anti-totalization rule + +Do not choose one row and make all others disappear. + +Examples: + +A person's inability to access an online court service can simultaneously involve: + +- accessibility; +- capabilities; +- service design; +- institutional power; +- legal/procedural knowledge; +- emotional burden; +- information discovery; +- geographic infrastructure. + +Those are coupled. + +They are not therefore one mechanism. + +## When a new RS concept is justified + +Create new shared vocabulary only when at least one condition holds: + +1. the same cross-domain distinction keeps recurring and no existing term covers the needed relationship; +2. established concepts need a lightweight routing label that explicitly preserves their differences; +3. the RS concept changes project design/testing in a way that native terms alone do not make legible; +4. the term helps newcomers discover the native literatures rather than replacing them. + +Otherwise: **route, don't rename.** + +## Candidate future interface + +A Conceptual Router could eventually expose this as an interactive graph: + + user's own words + ↓ + possible question shapes + ↓ + concepts / aliases + ↓ + native literatures + ↓ + methods + ↓ + sources / Reading Trails + ↓ + related RS projects + +The interface should preserve multiple routes and allow the user to say: + +- "not quite"; +- "go deeper"; +- "show me the disagreement"; +- "what do I need to know first?"; +- "show primary sources"; +- "show the low-jargon path"; +- "what would falsify this route?"; + +Do not build it until the manual router has been used enough to reveal its real schema. From 2833da02624479d0d2e69c665dd78a14e350476d Mon Sep 17 00:00:00 2001 From: Rae Lovejoy Date: Fri, 25 Sep 2026 00:07:01 -0700 Subject: [PATCH 54/66] Route canonical research method and router --- research/README.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/research/README.md b/research/README.md index 79cbdda..8f96957 100644 --- a/research/README.md +++ b/research/README.md @@ -2,6 +2,11 @@ This directory holds bounded research inquiries and versioned papers that synthesize Root Sequence's existing work. It does not replace the canonical treatments in `concepts/`, `systems/`, `analysis/`, or `futures/`. +## Method + +- [Root Sequence Research Method](method.md) — the canonical loop for preserving intuitions, decomposing concepts, routing to native disciplines, comparing against competent baselines, testing, narrowing/retiring, and translating findings locally. +- [Method & Concept Router](method-router.md) — a practical question-shape → native-method map; use it before inventing new RS vocabulary. + ## Research areas - [Conscious Systems](conscious-systems/README.md) — **exploratory, AI-assisted seed; author review pending**. Starts with [what can change about a mind while preserving consciousness](conscious-systems/what-can-we-change-about-a-mind.md), separating experience from report, capability, and authority. From a96dd1b97b7bd487efc861abf1b42b409f90c7a1 Mon Sep 17 00:00:00 2001 From: Rae Lovejoy Date: Fri, 25 Sep 2026 00:08:17 -0700 Subject: [PATCH 55/66] Select T-003 agency and power case --- .../notes/t003-case-2-selection-ndss.md | 181 ++++++++++++++++++ 1 file changed, 181 insertions(+) create mode 100644 research/papers/coherent-systems/notes/t003-case-2-selection-ndss.md diff --git a/research/papers/coherent-systems/notes/t003-case-2-selection-ndss.md b/research/papers/coherent-systems/notes/t003-case-2-selection-ndss.md new file mode 100644 index 0000000..da2ec84 --- /dev/null +++ b/research/papers/coherent-systems/notes/t003-case-2-selection-ndss.md @@ -0,0 +1,181 @@ +# T-003 Case 2 selection — NDSS digital-support service + +**Status:** SELECTED BEFORE METHOD OUTPUTS +**Selection date:** 2026-09-24 +**Protocol family:** [T-003 added-value comparison](t003-added-value-protocol.md) +**Case type:** public, non-clinical socio-technical service/access case + +## Selected case + +**UK National Digital Support Service (NDSS)** — support for people who are digitally excluded or need assistance to access HM Courts & Tribunals Service online services. + +Primary source: + +- HM Courts & Tribunals Service / Ministry of Justice, *Evaluation of the National Digital Support Service (NDSS)*, final report, February 2026, published 26 March 2026. +- Accessible summary on GOV.UK: https://www.gov.uk/government/publications/evaluation-of-the-national-digital-support-service/national-digital-support-service-findings-accessible-version-of-infographic +- Full report: https://assets.publishing.service.gov.uk/media/69b81786e2719934bb53a2bc/HMCTS_NDSS_Evaluation_Final_Report_Mar26.pdf + +## Why this case + +The first T-003 case was a technical reliability incident. Dynamic Coherence added little unique decision value beyond ordinary incident review. + +The next case should exercise the part of the framework that the technical incident barely touched: + +- substantive human opportunity; +- accessibility; +- service discoverability; +- institutional boundaries; +- who controls service design; +- who is affected but not involved; +- distributed support burden; +- practical versus nominal choice; +- path dependence created by digital-first service architecture. + +NDSS is suitable because the public evaluation contains: + +- user-journey data; +- aggregated user characteristics; +- support needs; +- referral/triage structure; +- channel choice; +- geographic availability; +- privacy/accessibility issues; +- delivery-partner burden; +- user outcomes; +- uncertainty and uneven take-up. + +## Anti-cherry-pick check + +This is **not** an easy "RS should win" case. + +Two established baselines should be strong: + +1. **Capability-oriented analysis** already asks whether people have real/substantive opportunities rather than formal options. +2. **Critical Systems Heuristics (CSH)** already asks who defines purpose, controls resources, supplies knowledge, and represents affected-but-not-involved people. + +A competent service/accessibility review should also identify many practical barriers. + +Therefore: + +> **If Root Sequence merely rediscovers real opportunity, accessibility, boundary judgment, or affected-party inclusion, those findings count as duplicate—not added value.** + +The case is retained because it gives the proposed RS synthesis a serious chance to be unnecessary. + +## Candidate cases considered and not selected + +### Cloudflare repeat data-center incidents + +Rejected for this phase because they strongly favor history/adaptation analysis and remain technical. + +### COVID-19 home-testing accessibility for blind/partially sighted users + +Public and useful, but the case is already explicitly structured around accessibility redesign and may overfit a single native method. + +### PIP Digital Self-Serve evaluation + +Rich substantive-opportunity case, but its benefit-application policy context is broader and more politically/administratively entangled than needed for the first agency/power comparison. + +### NDSS + +Selected because it is a bounded support service sitting between: + +- digital public-service architecture; +- users with different practical capabilities; +- referral/triage institutions; +- delivery partners; +- geographically uneven in-person support; +- online forms and court/tribunal processes. + +## Decision question + +> **Given only the frozen evidence packet, what changes to NDSS service design and delivery should be prioritized to improve eligible users' practical ability to access and complete online HMCTS processes?** + +The methods may identify conflicting objectives, missing evidence, and reasons not to prioritize a proposed change. + +No method is required to produce an overall verdict. + +## Source-withholding rule + +The frozen packet **excludes the report's Chapter 10 "Implications for improvement" and Chapter 11 conclusions**. + +This is deliberate. + +The methods receive reported service structure, evaluation design, user/partner findings, channel/choice findings, and outcomes—but not the report authors' final recommendation list. + +This creates an editorial discovery test rather than a paraphrase contest. + +The withheld recommendations are **not** treated as a gold standard. + +## Methods planned + +### Method A — competent service/accessibility review + +Focus: + +- user journey; +- discovery; +- access; +- channel availability; +- accessibility; +- service clarity; +- privacy; +- handoffs; +- delivery feasibility; +- follow-up; +- operational burden. + +### Method B — capability-oriented analysis + +Focus: + +- substantive opportunity; +- conversion factors; +- resources; +- health/disability/access conditions; +- social/institutional constraints; +- practical freedom to use the service. + +Do not turn capability theory into an engineering checklist. + +### Method C — Critical Systems Heuristics boundary critique + +Focus: + +- motivation/purpose; +- control/resources; +- knowledge/expertise; +- legitimacy / affected-but-not-involved; +- "is" versus "ought" boundary judgments where evidence permits. + +Do not pretend an AI editorial application equals a trained CSH practitioner. + +### Method D — Root Sequence routing/dynamic synthesis + +Use: + +- state vs transition; +- path dependence; +- practical possibility; +- feedback; +- revision power; +- continuity; +- cross-boundary burden; +- explicit routing to native methods. + +Method D must identify where its findings are already owned by A/B/C. + +## Interpretation boundary + +This is still an AI-assisted editorial pilot. + +It cannot establish: + +- method superiority; +- independent reviewer agreement; +- policy effectiveness; +- legal adequacy; +- prevalence beyond the evaluated service users; +- what affected people ought to value; +- a complete theory of digital exclusion. + +The strongest possible editorial finding is about **method overlap, omissions, or useful cross-method synthesis**. From 7b98d18616837fc41943eedb7119a8d02b255a9e Mon Sep 17 00:00:00 2001 From: Rae Lovejoy Date: Fri, 25 Sep 2026 00:08:19 -0700 Subject: [PATCH 56/66] Freeze T-003 NDSS evidence packet --- .../notes/t003-case-2-evidence-packet-ndss.md | 358 ++++++++++++++++++ 1 file changed, 358 insertions(+) create mode 100644 research/papers/coherent-systems/notes/t003-case-2-evidence-packet-ndss.md diff --git a/research/papers/coherent-systems/notes/t003-case-2-evidence-packet-ndss.md b/research/papers/coherent-systems/notes/t003-case-2-evidence-packet-ndss.md new file mode 100644 index 0000000..588f561 --- /dev/null +++ b/research/papers/coherent-systems/notes/t003-case-2-evidence-packet-ndss.md @@ -0,0 +1,358 @@ +# T-003 frozen evidence packet — National Digital Support Service + +**Packet version:** 0.1 / recommendation-withheld +**Status:** FROZEN FOR EDITORIAL COMPARISON +**Prepared:** 2026-09-24 +**Case period:** evaluation conducted July 2022–July 2025; final report February 2026 +**Source:** HMCTS / Ministry of Justice NDSS evaluation +**Primary report:** https://assets.publishing.service.gov.uk/media/69b81786e2719934bb53a2bc/HMCTS_NDSS_Evaluation_Final_Report_Mar26.pdf +**Accessible summary:** https://www.gov.uk/government/publications/evaluation-of-the-national-digital-support-service/national-digital-support-service-findings-accessible-version-of-infographic + +## Use rule + +This document is the entire factual case packet available to the four editorial methods. + +Methods may: + +- analyze the supplied facts; +- distinguish evidence from inference; +- identify missing information; +- request evidence. + +They may **not** import: + +- Chapter 10 source-authored improvement recommendations; +- Chapter 11 source conclusions; +- current HMCTS practice after the evaluation; +- outside facts about PIP/benefit eligibility; +- legal conclusions; +- personal anecdotes not contained here; +- private user data. + +The packet is project-authored paraphrase of a public evaluation, not independent verification. + +--- + +## Decision question + +> **Given only this packet, what changes to NDSS service design and delivery should be prioritized to improve eligible users' practical ability to access and complete online HMCTS processes?** + +--- + +## 1. Service background + +Between 2016 and 2025, HMCTS ran a reform programme that moved a substantial number of services online. + +The NDSS was established in recognition that some public users were: + +- **Digitally Excluded (DE)**; or +- **Digital with Assistance (DwA)** — able to access digital services only with assistance. + +The NDSS was intended to support access to HMCTS online services. + +The evaluation ran from July 2022 to July 2025 while the service was being rolled out. + +--- + +## 2. Evaluation design + +The final report states that the evaluation included: + +- 50 qualitative interviews with service users; +- a survey of 534 service users; +- 45 qualitative interviews with HMCTS, Courts and Tribunals Service Centre, WA Group, and delivery-partner staff; +- a survey of 35 WA Group/delivery-partner staff; +- 5 case-study appointment observations; +- analysis of management information. + +The evaluation was conducted in three phases so emerging findings could inform rollout. + +This packet does not independently assess sampling bias, response bias, interview coding, or representativeness beyond the report's own scope. + +--- + +## 3. Typical service journey + +The accessible summary describes a typical journey as: + +1. referral or self-referral; +2. triage by We Are Group to establish eligibility and need for digital support; +3. booking with an appropriate delivery partner; +4. appointment; +5. digital support delivered; +6. follow-up appointments where required. + +Referrals could come from Courts and Tribunals Service Centres or delivery partners, as well as self-referral. + +--- + +## 4. Scale and distribution + +From November 2022 to January 2025: + +- 10,214 individuals were triaged; +- 10,419 cases were recorded; +- 9,005 individual users were supported during an appointment. + +The accessible summary reports: + +- 90% of triaged cases concerned Social Security and Child Support (SSCS) services; +- 84% of closed appointments were marked as having provided support; + - 73% fully supported; + - 11% partially supported. + +Appointment demand was not evenly distributed across the delivery-partner network. + +The full report states that 35% of 136 delivery partners had fewer than 10 sessions scheduled over roughly two years. + +The report says a large network is necessary for face-to-face support and describes the network as not large enough to make that option viable for all users. + +--- + +## 5. Aggregated user profile + +The accessible summary reports among evaluated service users: + +- 46% were aged 55 or older; +- 89% had a health condition lasting more than 12 months; +- 82% were not in paid work; +- 43% reported annual income below £14,000; +- 37% had no formal qualifications. + +The full report says health/disability issues including motor, learning, and cognitive difficulties commonly contributed to digital exclusion or need for assistance. + +These are aggregate characteristics from the evaluated population. + +Do not infer any individual user's condition from them. + +--- + +## 6. Digital capability was not the whole need + +The accessible summary reports that only 20% of service users were classified as having low digital capability. + +Others had at least moderate digital capability but sought support because of: + +- concern about the complexity of interacting with HMCTS services; +- uncertainty about how to progress an appeal, claim, or application; +- need for reassurance. + +The full report states that only 29% had tried to use the online form themselves before contacting NDSS. + +It reports that most interviewed users were unaware of other potential sources of support beyond friends or family. + +--- + +## 7. Discoverability and referral + +Users most often believed they heard about NDSS through HMCTS or DWP. + +The report describes uncertainty about how some users were actually routed to NDSS. + +It notes that SSCS users had more established pathways through DWP → CTSC → NDSS than users of other services. + +The evaluation says support was heavily skewed toward SSCS users and that available evidence could not determine whether this reflected: + +- higher underlying need; or +- better signposting/referral for SSCS users. + +Some users interviewed were surprised and relieved that the support existed. + +--- + +## 8. Support needs exceeded the service's nominal label + +At triage: + +- 85% reported seeking digital support; +- 74% also reported seeking legal support; +- 69% procedural support; +- 43% emotional support. + +Delivery partners said users often expected help beyond digital support. + +The report says delivery partners frequently provided wider support in order to meet users' actual needs. + +This packet does not decide whether those forms of support should formally belong inside NDSS. + +--- + +## 9. Channel choice and practical availability + +In the service-user survey: + +- 51% recalled being offered a choice between in-person and remote support; +- 29% recalled not being offered that choice; +- 20% were unsure. + +The same figure reports: + +- 86% said they received support in their preferred way; +- 9% said they did not; +- 5% did not know. + +Reported appointment modes were overwhelmingly remote. + +Users described reasons for preferring remote support including: + +- physical health/mobility making travel difficult; +- mental-health/social reasons; +- wanting the quickest available appointment. + +Other users preferred face-to-face support because: + +- they lacked confidence on the phone; +- their health/access needs made in-person help preferable; +- they wanted more personal interaction. + +The report describes cases where the *nominal* availability of face-to-face support did not make it a realistic option: + +- some locations were too far away; +- examples included roughly two-hour bus journeys; +- waits could be two weeks or more; +- in-home appointments were unavailable in some areas; +- staff said booking was often driven by partner availability, not user need. + +The report says the delivery-partner network was not large enough to meet all face-to-face preference. + +--- + +## 10. Walk-in and handoff friction + +The report describes cases where users walked directly into a delivery-partner location seeking help. + +Rather than receiving support directly, they could be referred back to the NDSS process and later booked into an appointment with that same delivery partner. + +The report characterizes this as an integration/efficiency problem. + +The packet contains no reliable estimate of how many appointments followed this path. + +--- + +## 11. Appointment support + +Accessible-summary results include: + +- 94% of users needing help accessing the form received this help; +- 84% needing advice on case content received this help; +- 72% needing emotional support received this help. + +Online forms were submitted during appointments for 75% of service users. + +The packet does not establish whether adviser-completed submission versus user-completed submission produces different longer-term user capability. + +--- + +## 12. Privacy, sensory access, communication, and local conditions + +The full report includes reports from some users of: + +- poor audio quality; +- distracting/unprofessional background noise during remote calls; +- discomfort discussing sensitive/private information when advisers appeared to be in non-private settings; +- face-to-face locations lacking privacy; +- delays or disrupted appointments; +- old or poor equipment; +- communication difficulties involving accents/language. + +The report also identifies a need for stronger delivery-partner support/training around users with sensory disabilities. + +The packet does not quantify prevalence of each issue beyond the report's qualitative wording where percentages are absent. + +--- + +## 13. Delivery-partner burden and resource mismatch + +The report describes delivery partners sometimes absorbing costs or effort not fully aligned with the service model. + +Examples include: + +- arranging staff for appointments that users did not attend; +- interpreter cost in some cases where an interpreter had not been arranged upstream; +- providing broader procedural/legal/emotional help than the original digital-support framing; +- appointment time pressures for complex needs. + +This packet does not include a complete cost model or fee structure. + +--- + +## 14. Outcomes + +The accessible summary reports: + +- 80% said NDSS made completing their form easier; +- 18% said they would not have submitted the form at all without NDSS support; +- 19% said they would only have been able to submit on paper without the service. + +Overall satisfaction: + +- 86% satisfied; +- 5% dissatisfied; +- 68% said support matched or exceeded expectations. + +The packet does not establish causal effects on eventual legal/case outcomes. + +--- + +## 15. Follow-up and continuity of support + +The full report states: + +- 15% reported further contact with an adviser after the initial appointment; +- 80% reported no further contact; +- 77% felt very/fairly clear about next steps after support ended; +- 20% were not very/not at all clear. + +Some users valued follow-up communications. + +Some were unsure which organization—delivery partner, DWP, HMCTS—had sent later communications. + +Some users in more complex/non-SSCS services reported needing multiple appointments or still being unclear on next steps. + +--- + +## 16. Important uncertainties + +The packet does not provide enough evidence to determine: + +- the total eligible population who never discovered NDSS; +- whether SSCS/non-SSCS take-up differences are primarily need or referral differences; +- the counterfactual submission/completion rate without NDSS for the full eligible population; +- the causal effect of face-to-face versus remote support; +- which channel preferences would change if travel/wait constraints disappeared; +- the best service boundary between digital, procedural, legal, and emotional support; +- full delivery-partner costs; +- geographic coverage metrics sufficient to optimize the network; +- whether adviser-led form completion increases or reduces future independent capability; +- the distribution of outcomes by disability type or access need beyond reported summaries; +- legal adequacy of any service design; +- post-2025 implementation changes. + +Methods should request missing evidence rather than fill these gaps. + +--- + +## 17. Intentionally withheld material + +For this editorial comparison, methods do **not** receive: + +- Chapter 10: source-authored "Implications for improvement"; +- Chapter 11: source conclusions beyond factual material already paraphrased above. + +This omission is artificial and exists only to test method derivation. + +The omitted material is not a gold-standard answer key. + +--- + +## Evidence-status rule + +Treat: + +- report statistics and explicitly attributed evaluation findings as **SOURCE-REPORTED**; +- qualitative examples as **SOURCE-REPORTED QUALITATIVE EVIDENCE**; +- any explanation of why the pattern occurred as **INFERENCE** unless the packet explicitly reports it; +- any claim about what the service should value as **NORMATIVE**; +- any factual gap as **UNKNOWN**. + +No method may convert a user-reported preference into a universal need or an aggregate demographic pattern into an individual attribute. From 48ed53f291bc92dc5280ab7d3f7969a2d614e40e Mon Sep 17 00:00:00 2001 From: Rae Lovejoy Date: Fri, 25 Sep 2026 00:09:10 -0700 Subject: [PATCH 57/66] Preregister T-003 NDSS method comparison --- .../t003-editorial-pilot-003-registration.md | 313 ++++++++++++++++++ 1 file changed, 313 insertions(+) create mode 100644 research/papers/coherent-systems/notes/t003-editorial-pilot-003-registration.md diff --git a/research/papers/coherent-systems/notes/t003-editorial-pilot-003-registration.md b/research/papers/coherent-systems/notes/t003-editorial-pilot-003-registration.md new file mode 100644 index 0000000..8f9d369 --- /dev/null +++ b/research/papers/coherent-systems/notes/t003-editorial-pilot-003-registration.md @@ -0,0 +1,313 @@ +# T-003 Editorial Pilot 003 — NDSS preregistration + +**Status:** FROZEN BEFORE METHOD OUTPUTS +**Pilot type:** AI-assisted editorial method comparison; not independent validation +**Case:** UK National Digital Support Service (NDSS) +**Date frozen:** 2026-09-24 + +## Frozen artifacts + +- Root Sequence research method: + - path: `research/method.md` + - blob: `1d65efa3aee371c6022b234ea79734327f49b254` +- Method router: + - path: `research/method-router.md` + - blob: `253dff4f003b4a4157dc76f1d096e634279bf29a` +- Case selection: + - path: `t003-case-2-selection-ndss.md` + - blob: `da2ec84620d94f88815e0d3dad520c0ce80c6f4e` +- Evidence packet: + - path: `t003-case-2-evidence-packet-ndss.md` + - blob: `588f561c82c41e0dd2df91b407704a3ad1313757` + +No live browsing or outside case facts are permitted during method outputs. + +## Decision question + +> **Given only the frozen evidence packet, what changes to NDSS service design and delivery should be prioritized to improve eligible users' practical ability to access and complete online HMCTS processes?** + +Methods may return: + +- design changes; +- evidence requests; +- conflicts/tradeoffs; +- reasons not to prioritize a change. + +No overall service score is permitted. + +--- + +## Method A — competent service/accessibility review + +### Role + +Apply a competent service-design/accessibility review to the supplied service journey. + +### Frozen prompt + +Using only the evidence packet, identify up to **12 consequential findings** about: + +1. service discovery and entry; +2. referral/triage handoffs; +3. accessibility and channel choice; +4. geographic/practical availability; +5. service scope and user expectations; +6. privacy and communication; +7. continuity/follow-up; +8. delivery-partner feasibility/burden; +9. operational consistency; +10. missing evidence needed for prioritization. + +For every finding record: + +- packet basis; +- affected user/actor; +- practical consequence; +- proposed design/service response; +- uncertainty / missing evidence. + +Distinguish: + +- technical accessibility; +- service availability; +- usability; +- preference; +- resource constraints; +- service-scope ambiguity. + +Do not use Root Sequence, capability, or CSH terminology unless it appears in the packet. + +Do not infer legal noncompliance. + +--- + +## Method B — capability-oriented analysis + +### Role + +Use capability-approach concepts to inspect **real/substantive opportunity**, not merely nominal service availability. + +This is an editorial capability-oriented analysis, not a claim to reproduce every strand of Sen/Nussbaum/Robeyns scholarship. + +### Frozen prompt + +Using only the packet, identify up to **12 findings** about the practical opportunity to access and complete HMCTS digital processes. + +For each finding distinguish where possible: + +- resource/formal option; +- personal conversion factors; +- social conversion factors; +- environmental conversion factors; +- resulting substantive opportunity / capability; +- uncertainty about what users value. + +Ask: + +1. Which nominal service options become real opportunities for some users but not others? +2. Which health, skill, income, geography, communication, institutional, or informational conditions affect conversion? +3. Does support expand capability, substitute for capability, or both? +4. Which users may remain outside the observed support pathway? +5. Which service changes would expand substantive opportunity without assuming everyone values the same channel or form of independence? +6. What evidence is missing before making a capability claim? + +For every finding record: + +- packet basis; +- capability/relevant opportunity; +- conversion factor(s); +- consequence; +- possible response; +- uncertainty. + +Do not treat "independence" as automatically superior to supported action. + +Do not infer welfare or justice from satisfaction scores alone. + +--- + +## Method C — Critical Systems Heuristics boundary critique + +### Role + +Apply a simplified editorial CSH boundary critique using the four sources of influence: + +- motivation; +- control; +- knowledge; +- legitimacy. + +This is **not** a claim that the AI process equals a trained CSH practitioner. + +### Frozen prompt + +Using only the packet, identify up to **12 consequential boundary judgments or tensions**. + +Ask: + +### Motivation +- Who is intended to benefit? +- What counts as improvement? +- Whose purposes are visible or missing? + +### Control +- Who controls service entry, eligibility, appointment availability, resources, and service boundaries? +- Which conditions are outside users' control? + +### Knowledge +- Which expertise/experience shapes the service? +- What user or delivery-partner knowledge is unavailable or filtered? + +### Legitimacy +- Who is affected but not fully involved in defining the service? +- Which interests or burdens risk being excluded by the current boundary? + +For every finding record: + +- source-of-influence category; +- packet basis; +- boundary judgment; +- affected/involved actors; +- implication; +- uncertainty; +- an "ought" question that should remain open. + +Do not invent motives. + +Do not claim a boundary is illegitimate merely because it is bounded. + +--- + +## Method D — Root Sequence routing / adaptive-continuity synthesis + +### Role + +Use Root Sequence **after** the three native analyses. + +Method D is not allowed to claim added value for rediscovering: + +- substantive opportunity → Method B; +- boundary/power/affected parties → Method C; +- ordinary service/accessibility barriers → Method A. + +### Frozen prompt + +Using only the packet, identify up to **12 cross-method/system findings** that may require connecting dimensions separated by A/B/C. + +Ask: + +1. What changes current state versus future transition/response dynamics? +2. Which histories/referral structures shape what users can access next? +3. Which possibilities are nominal versus practically reachable—and which native method owns that distinction? +4. Which adaptations shift burden to delivery partners or other systems? +5. Which feedback reaches people who can revise the service? +6. Who can change referral rules, channel supply, service scope, appointment resources, and follow-up? +7. What must remain continuous if the service architecture changes? +8. Do successful local fixes narrow later options or create dependency? +9. Which findings cross boundaries between capability, accessibility, operations, and governance? +10. What should be routed back to a native method rather than retained as RS vocabulary? +11. What remains unexplained after A/B/C? +12. What result would show RS adds no useful synthesis here? + +For every finding record: + +- packet basis; +- methods/literatures it connects; +- cross-boundary relation; +- consequence; +- possible next action; +- what is duplicate versus potentially additive; +- uncertainty. + +Method D must explicitly label findings: + +- **ROUTE** — native method owns the mechanism; +- **SYNTHESIS** — connection among already-found native findings; +- **CANDIDATE ADD** — potentially consequential relation not captured by A/B/C; +- **NO ADD** — RS vocabulary adds nothing useful. + +--- + +## Comparison coding + +After all four outputs are frozen, code findings for: + +### Evidence +- E2 direct packet support +- E1 reasonable inference with explicit packet basis +- E0 unsupported + +### Decision relevance +- D2 could plausibly alter service design/evidence collection/prioritization +- D1 relevant context +- D0 no material decision consequence + +### Novelty relative to other methods +- N2 substantively absent from all other methods +- N1 partially present / useful connection +- N0 duplicate + +### Method ownership +- A service/accessibility +- B capability +- C CSH +- D cross-method synthesis +- MULTI + +### Risk +- unsupported extrapolation; +- normative laundering; +- capability paternalism; +- boundary/power speculation; +- accessibility generalization; +- demographic inference. + +--- + +## Pre-specified null result + +A valid null result is: + +> **Methods A–C capture all decision-relevant findings, and Method D adds only vocabulary or connections that do not change any design/evidence question.** + +Another valid result: + +> **Method D mostly helps route findings to the right native method but does not generate an independent method-level contribution.** + +Both count as success for the research process. + +--- + +## Conflict statement + +All four methods and the coding are generated by the same AI-assisted research process that helped create the RS framework and packet. + +Therefore this pilot can debug: + +- question routing; +- duplication; +- concept ownership; +- cross-method synthesis; +- obvious omissions. + +It cannot establish: + +- independent performance; +- method superiority; +- inter-rater reliability; +- actual service-user priorities; +- policy legitimacy; +- causal effects of redesign. + +--- + +## Stop rule + +Do not retune the four prompts against this case after comparison. + +After Pilot 003: + +- preserve the result; +- update the method/router only for clear methodological errors; +- do not create a fifth method to rescue RS; +- move next to independent/human review or a different research question. From f0d8cacc54b14f3ff8857cca7c6c2888e58da3e0 Mon Sep 17 00:00:00 2001 From: Rae Lovejoy Date: Fri, 25 Sep 2026 00:09:36 -0700 Subject: [PATCH 58/66] Disclose Pilot 003 source contamination --- .../t003-editorial-pilot-003-registration.md | 22 +++++++++++++++++++ 1 file changed, 22 insertions(+) diff --git a/research/papers/coherent-systems/notes/t003-editorial-pilot-003-registration.md b/research/papers/coherent-systems/notes/t003-editorial-pilot-003-registration.md index 8f9d369..873e599 100644 --- a/research/papers/coherent-systems/notes/t003-editorial-pilot-003-registration.md +++ b/research/papers/coherent-systems/notes/t003-editorial-pilot-003-registration.md @@ -278,6 +278,28 @@ Both count as success for the research process. --- +## Contamination notice + +**The same AI-assisted process preparing this registration has already viewed the source report's improvement/conclusion material while vetting the case.** + +Therefore the recommendation-withholding rule protects the *written method inputs* but does **not** create analyst blinding. + +Pilot 003 must **not** claim: + +- independent derivation of source recommendations; +- discovery performance; +- that a method "predicted" an omitted recommendation. + +The valid editorial question is narrower: + +> **Given the same written packet, how do the four methods partition, duplicate, connect, or omit the service-design questions?** + +Any apparent unique design recommendation is method-debugging material only. + +A future human/independent comparison can use the frozen packet with genuinely blinded reviewers. + +--- + ## Conflict statement All four methods and the coding are generated by the same AI-assisted research process that helped create the RS framework and packet. From 31803b0bcd9c2d57412e09fa3cde947e04d09e6f Mon Sep 17 00:00:00 2001 From: Rae Lovejoy Date: Fri, 25 Sep 2026 00:12:14 -0700 Subject: [PATCH 59/66] Run T-003 Pilot 003 service review --- .../t003-editorial-pilot-003-method-a.md | 173 ++++++++++++++++++ 1 file changed, 173 insertions(+) create mode 100644 research/papers/coherent-systems/notes/t003-editorial-pilot-003-method-a.md diff --git a/research/papers/coherent-systems/notes/t003-editorial-pilot-003-method-a.md b/research/papers/coherent-systems/notes/t003-editorial-pilot-003-method-a.md new file mode 100644 index 0000000..ced562d --- /dev/null +++ b/research/papers/coherent-systems/notes/t003-editorial-pilot-003-method-a.md @@ -0,0 +1,173 @@ +# T-003 Editorial Pilot 003 — Method A + +**Method:** competent service/accessibility review +**Case:** NDSS +**Status:** EDITORIAL OUTPUT / NOT INDEPENDENT VALIDATION +**Evidence:** frozen NDSS packet only + +## A-01 — Service discoverability is uneven across service types + +**Packet basis:** NDSS use is heavily concentrated in SSCS; the packet cannot determine whether this is greater need or better referral/signposting. Many users were surprised support existed. + +**Affected actors:** eligible users, especially non-SSCS users. + +**Practical consequence:** a useful service may be practically unavailable to people who never encounter the referral route. + +**Response:** map referral entry points across HMCTS services; measure awareness, referral completion, and unmet support need by service type; make support routes visible at relevant points in the user journey. + +**Uncertainty:** total eligible non-user population is unknown. + +--- + +## A-02 — Channel choice is partly nominal because supply is geographically constrained + +**Packet basis:** only about half recalled being offered in-person/remote choice; some face-to-face options required long travel/waiting; in-home support was unavailable in some areas. + +**Affected actors:** users needing or preferring in-person/in-home support; delivery network. + +**Consequence:** "face-to-face available" does not mean it is a usable option. + +**Response:** assess geographic coverage, travel burden, wait time, and in-home capacity as part of channel availability; define minimum practical-availability criteria rather than counting channel types alone. + +**Uncertainty:** no complete geographic coverage model is supplied. + +--- + +## A-03 — Walk-in users can encounter unnecessary referral loops + +**Packet basis:** some users who approached a delivery partner directly were referred back through NDSS before later being booked with that same partner. + +**Affected actors:** users and delivery partners. + +**Consequence:** extra handoff, delay, explanation burden, and administrative work. + +**Response:** review whether authorized partners can complete or initiate triage for direct walk-ins, with clear eligibility/recording rules. + +**Uncertainty:** prevalence is unknown. + +--- + +## A-04 — The service label and actual support needs are misaligned + +**Packet basis:** users sought digital support but also legal, procedural, and emotional support; delivery partners frequently provided broader help. + +**Affected actors:** users, advisers, delivery partners, HMCTS. + +**Consequence:** users may arrive with incorrect expectations; staff scope/training/time may not match actual cases. + +**Response:** define and communicate service scope; establish safe handoff/signposting for support outside scope; ensure appointment planning reflects the complexity the service actually encounters. + +**Uncertainty:** the packet does not establish which wider support categories should formally belong in NDSS. + +--- + +## A-05 — Privacy and sensory/communication accessibility need consistent service controls + +**Packet basis:** qualitative reports include non-private environments, background noise, poor audio, communication difficulties, and need for staff training around sensory disabilities. + +**Affected actors:** users discussing sensitive cases, especially users with sensory/communication access needs. + +**Consequence:** reduced comprehension, comfort, confidentiality, or effective participation. + +**Response:** establish privacy and environmental standards for remote/in-person appointments; define accessible communication support, interpreter responsibilities, and staff training; audit actual delivery settings. + +**Uncertainty:** prevalence is not quantified. + +--- + +## A-06 — Fixed appointment/resource assumptions may not fit complex cases + +**Packet basis:** users often had overlapping needs; partners reported appointment-time pressures and support beyond the original digital remit. + +**Affected actors:** users with complex cases; delivery staff. + +**Consequence:** rushed explanations, incomplete support, spillover, or repeated appointments. + +**Response:** use complexity-sensitive appointment planning and escalation/extension paths rather than one standard support envelope. + +**Uncertainty:** cost/throughput effects are unavailable. + +--- + +## A-07 — Follow-up and next-step communication are inconsistent enough to matter + +**Packet basis:** 20% were not clear about next steps; some users were unsure which organization sent later communications; complex/non-SSCS users sometimes needed additional contact. + +**Affected actors:** users after the appointment, especially in complex cases. + +**Consequence:** uncertainty after a successful form submission can create avoidable re-contact or stalled progress. + +**Response:** provide consistent end-of-session summary, responsible organization, next milestones, contact route, and defined follow-up request mechanism. + +**Uncertainty:** effect on case completion is unknown. + +--- + +## A-08 — Partner-network design should be evaluated as capacity infrastructure, not a directory + +**Packet basis:** appointment distribution is uneven; 35% of partners had fewer than 10 sessions; network was reported insufficient for universally viable face-to-face support. + +**Affected actors:** users, delivery partners, HMCTS/WA Group. + +**Consequence:** nominal geographic network size may misrepresent usable capacity. + +**Response:** measure capacity by location, access capability, trained staff, appointment availability, travel time, utilization, and demand; redesign or supplement weak coverage areas. + +**Uncertainty:** full network cost/capacity data are missing. + +--- + +## A-09 — Delivery partners absorb hidden costs and service exceptions + +**Packet basis:** partner staff sometimes absorbed interpreter costs, no-show staffing costs, and broader-than-designed support effort. + +**Affected actors:** delivery partners and indirectly users if partner capacity erodes. + +**Consequence:** service success may depend on uncompensated or weakly specified partner work. + +**Response:** map actual partner tasks/costs, define responsibility for interpreters and exceptional support, and align funding/operating agreements with observed work. + +**Uncertainty:** complete cost model unavailable. + +--- + +## A-10 — Organisational identity and handoffs are not consistently legible + +**Packet basis:** some users were unclear whether later communications came from delivery partners, DWP, or HMCTS; users could misunderstand the NDSS as a general case helpline. + +**Affected actors:** service users. + +**Consequence:** uncertainty about responsibility, next contact, and scope. + +**Response:** make organisational role, adviser role, handoff, and next responsible party explicit in every interaction and follow-up. + +**Uncertainty:** no direct measure of how often confusion affected outcomes. + +--- + +## A-11 — Digital submission is an incomplete outcome measure + +**Packet basis:** forms were often submitted digitally; 80% said support made completion easier; 18% said they would not have submitted without support. The packet does not establish final case outcomes or longer-term capability. + +**Affected actors:** users, HMCTS. + +**Consequence:** a service can succeed at submission while leaving unresolved understanding, follow-up, or future-access problems. + +**Response:** supplement submission/satisfaction metrics with next-step clarity, repeat-support need, accessibility success, channel fit, unsuccessful referrals, and completion of the wider service journey. + +**Uncertainty:** later outcome data are absent. + +--- + +## A-12 — Missing data should be collected before major network or service-boundary redesign + +**Packet basis:** unknowns include eligible nonusers, geographic coverage, full partner costs, causes of SSCS skew, channel counterfactuals, and long-term effects. + +**Affected actors:** decision-makers and all service participants. + +**Consequence:** current evidence supports targeted improvements but not confident optimization of network size, service scope, or channel mix. + +**Response:** collect bounded evidence on unmet demand, referral losses, coverage, channel constraints, partner burden, and outcomes by service/access need. + +**Uncertainty:** explicit. + From a770f93bbe91acde6eef933dc9a04b4737177e91 Mon Sep 17 00:00:00 2001 From: Rae Lovejoy Date: Fri, 25 Sep 2026 00:12:16 -0700 Subject: [PATCH 60/66] Run T-003 Pilot 003 capability review --- .../t003-editorial-pilot-003-method-b.md | 197 ++++++++++++++++++ 1 file changed, 197 insertions(+) create mode 100644 research/papers/coherent-systems/notes/t003-editorial-pilot-003-method-b.md diff --git a/research/papers/coherent-systems/notes/t003-editorial-pilot-003-method-b.md b/research/papers/coherent-systems/notes/t003-editorial-pilot-003-method-b.md new file mode 100644 index 0000000..86df60a --- /dev/null +++ b/research/papers/coherent-systems/notes/t003-editorial-pilot-003-method-b.md @@ -0,0 +1,197 @@ +# T-003 Editorial Pilot 003 — Method B + +**Method:** capability-oriented analysis +**Case:** NDSS +**Status:** EDITORIAL OUTPUT / NOT A COMPLETE CAPABILITY-ASSESSMENT STUDY +**Evidence:** frozen NDSS packet only + +## B-01 — Formal availability of an online service is not equivalent to capability to use it + +**Packet basis:** NDSS exists because some users are digitally excluded or need assistance; 18% said they would not have submitted without NDSS. + +**Relevant opportunity:** practical opportunity to initiate/complete an HMCTS online process. + +**Conversion factors:** digital skill, health/disability, procedural complexity, access to support. + +**Consequence:** the online route becomes a substantive opportunity for some users only when support is available. + +**Possible response:** evaluate HMCTS digital access in terms of supported real opportunity, not website availability alone. + +**Uncertainty:** no estimate for all eligible nonusers. + +--- + +## B-02 — Digital skill is only one conversion factor + +**Packet basis:** only 20% were classified as low digital capability; many others sought help because the process was complex or uncertain. + +**Relevant opportunity:** completing the process correctly/confidently. + +**Conversion factors:** procedural knowledge, cognitive burden, reassurance, case complexity. + +**Consequence:** defining exclusion as "low digital skill" would miss many people whose practical opportunity is constrained for other reasons. + +**Possible response:** assess support need through the full task context, not a digital-skills proxy alone. + +**Uncertainty:** relative contributions of each factor are not quantified. + +--- + +## B-03 — Channel options become capabilities only when they can be converted into use + +**Packet basis:** some face-to-face options required long travel/waits or were unavailable; users had heterogeneous reasons for preferring remote or in-person support. + +**Relevant opportunity:** receiving support through a usable channel. + +**Conversion factors:** mobility/health, geography, travel time, phone confidence, wait time, local partner supply. + +**Consequence:** a nominal in-person option can fail to be a substantive opportunity. + +**Possible response:** measure actual conversion conditions for each channel and preserve multiple feasible routes where needed. + +**Uncertainty:** user values/preferences may change if constraints change. + +--- + +## B-04 — Service discoverability is itself a conversion factor + +**Packet basis:** many users were surprised support existed; non-SSCS users had weaker referral pathways; most interviewed users knew no alternatives beyond friends/family. + +**Relevant opportunity:** reaching support at all. + +**Conversion factors:** information, referral structure, institutional contact pathway. + +**Consequence:** identical underlying need can produce different capability depending on whether the user encounters the support route. + +**Possible response:** treat discoverability/referral as part of substantive access, not communications afterthought. + +**Uncertainty:** unmet need among nonusers is unknown. + +--- + +## B-05 — Financial and educational disadvantage may compound conversion difficulty, but causality is not established here + +**Packet basis:** aggregate profile includes low income, unemployment, and low/no formal qualifications. + +**Relevant opportunity:** navigating digital/administrative processes. + +**Conversion factors:** possible material resources, literacy/experience, time/support. + +**Consequence:** these conditions may matter to practical access. + +**Possible response:** investigate rather than assume; avoid designing support around a single demographic stereotype. + +**Uncertainty:** packet does not establish causal effects of income/education on NDSS access. + +--- + +## B-06 — Supported action can itself be a capability; independence should not be presumed superior + +**Packet basis:** advisers sometimes supported users to complete forms and sometimes entered/submitted information; users valued not having to rely on family. + +**Relevant opportunity:** completing a consequential process with acceptable support. + +**Conversion factors:** availability/trust/quality of assistance. + +**Consequence:** the meaningful freedom may be "can complete the process with chosen support," not "can complete it entirely alone." + +**Possible response:** distinguish supported agency from dependency imposed by poor service design; ask users what forms of assistance they value. + +**Uncertainty:** long-term user capability after adviser-led completion is unknown. + +--- + +## B-07 — Reliance on family/friends is an available resource for some users, but not necessarily an equivalent opportunity + +**Packet basis:** users often knew of no alternative support besides friends/family; some valued NDSS because it reduced reliance on relatives. + +**Relevant opportunity:** access help with privacy/choice. + +**Conversion factors:** social network, relationship quality, privacy, willingness to ask. + +**Consequence:** "family can help" should not be assumed interchangeable with a formal support route. + +**Possible response:** preserve an institutional support option while studying what kinds of support users actually prefer. + +**Uncertainty:** family support experiences are not systematically described. + +--- + +## B-08 — Privacy conditions affect the capability to use support safely + +**Packet basis:** reports of non-private environments and discomfort discussing sensitive information. + +**Relevant opportunity:** meaningful use of support without unacceptable disclosure. + +**Conversion factors:** physical setting, remote-work conditions, communication channel. + +**Consequence:** technically available support can be practically unacceptable. + +**Possible response:** include privacy as a condition of usable support. + +**Uncertainty:** frequency not quantified. + +--- + +## B-09 — Delivery-partner capacity is a social/institutional conversion factor + +**Packet basis:** face-to-face feasibility depended on geographic partner supply; partners also absorbed additional work/cost. + +**Relevant opportunity:** access to support. + +**Conversion factors:** staffing, training, partner geography, funding, interpreters, appointment time. + +**Consequence:** user capability depends partly on institutional capacity outside the user. + +**Possible response:** evaluate partner capacity as part of access rather than locating "digital exclusion" solely in individuals. + +**Uncertainty:** full resource model missing. + +--- + +## B-10 — Service-scope ambiguity may constrain users' capability even when the digital task is completed + +**Packet basis:** users frequently needed procedural/legal/emotional help; partners reported expectations they could not always meet. + +**Relevant opportunity:** progress through the actual administrative/legal journey, not merely interact with a form. + +**Conversion factors:** procedural knowledge, legal support availability, emotional/cognitive support, signposting. + +**Consequence:** improving form access may not resolve the capability needed to progress the wider process. + +**Possible response:** define the supported capability and create reliable transitions to other support where NDSS scope ends. + +**Uncertainty:** packet cannot determine ideal service boundary. + +--- + +## B-11 — Next-step clarity affects future opportunity after the appointment + +**Packet basis:** 20% were not clear on next steps; some were unsure who had contacted them. + +**Relevant opportunity:** continue progressing after support ends. + +**Conversion factors:** information, process legibility, follow-up access. + +**Consequence:** a submitted form can coexist with weak capability for the next stage. + +**Possible response:** make post-appointment process/navigation support explicit. + +**Uncertainty:** causal effect on later outcomes unknown. + +--- + +## B-12 — Observed users are not the same as the population lacking capability + +**Packet basis:** support pathways skew heavily toward SSCS; eligible nonuser population and unmet demand are unknown. + +**Relevant opportunity:** obtaining support. + +**Conversion factors:** discoverability/referral before entry to the dataset. + +**Consequence:** service-user satisfaction cannot establish capability for people who never reached the service. + +**Possible response:** study non-use, failed referrals, and unmet support need. + +**Uncertainty:** central. + From b40c0209718e2c8b503fe7ae7ef09691231fa84a Mon Sep 17 00:00:00 2001 From: Rae Lovejoy Date: Fri, 25 Sep 2026 00:12:20 -0700 Subject: [PATCH 61/66] Run T-003 Pilot 003 CSH review --- .../t003-editorial-pilot-003-method-c.md | 199 ++++++++++++++++++ 1 file changed, 199 insertions(+) create mode 100644 research/papers/coherent-systems/notes/t003-editorial-pilot-003-method-c.md diff --git a/research/papers/coherent-systems/notes/t003-editorial-pilot-003-method-c.md b/research/papers/coherent-systems/notes/t003-editorial-pilot-003-method-c.md new file mode 100644 index 0000000..fb9dcc5 --- /dev/null +++ b/research/papers/coherent-systems/notes/t003-editorial-pilot-003-method-c.md @@ -0,0 +1,199 @@ +# T-003 Editorial Pilot 003 — Method C + +**Method:** simplified Critical Systems Heuristics boundary critique +**Case:** NDSS +**Status:** EDITORIAL OUTPUT / NOT A SUBSTITUTE FOR TRAINED CSH PRACTICE +**Evidence:** frozen NDSS packet only + +## C-01 — Motivation: what is the service ultimately trying to improve? + +**Category:** motivation + +**Packet basis:** NDSS supports digitally excluded/DwA users accessing online HMCTS services; forms are commonly submitted digitally. + +**Boundary judgment:** "successful digital submission" and "meaningful access to justice/service process" are not necessarily the same improvement criterion. + +**Affected/involved:** HMCTS, users, delivery partners. + +**Implication:** make explicit whether NDSS is optimizing digital-channel completion, access to the underlying process, user understanding, or some combination. + +**Ought question:** what should count as successful support beyond form submission? + +--- + +## C-02 — Motivation: users' actual needs exceed the formal problem definition + +**Category:** motivation + +**Packet basis:** legal, procedural, and emotional needs frequently accompany digital-support needs. + +**Boundary judgment:** defining the problem as "digital support" places important parts of the lived problem outside the formal service boundary. + +**Affected/involved:** users and delivery partners. + +**Implication:** examine which needs belong inside NDSS and which need reliable boundary-crossing routes. + +**Ought question:** who should decide the legitimate boundary of support? + +--- + +## C-03 — Control: service users do not control the supply of channels that determine their practical choice + +**Category:** control + +**Packet basis:** delivery-partner availability often drives appointment mode; geographic network limits face-to-face/in-home options. + +**Boundary judgment:** user "choice" is constrained by resources controlled by service institutions/partners. + +**Affected/involved:** users, WA Group/HMCTS, delivery partners. + +**Implication:** report channel-choice metrics together with the institutional conditions producing the available set. + +**Ought question:** what minimum level of practical choice should the service commit resources to sustain? + +--- + +## C-04 — Control: central triage can override local immediacy + +**Category:** control + +**Packet basis:** some direct walk-ins were routed back through NDSS before returning to the same delivery partner. + +**Boundary judgment:** authority over entry/eligibility is centralized relative to local service capacity. + +**Affected/involved:** users, delivery partners, triage organization. + +**Implication:** examine whether the control arrangement adds necessary consistency/safeguards or avoidable burden. + +**Ought question:** which entry decisions should remain central, and which could be delegated locally? + +--- + +## C-05 — Control: delivery partners carry responsibilities without full control over upstream arrangements + +**Category:** control + +**Packet basis:** partners absorb interpreter/no-show costs and wider support effort; appointments can be assigned based on network availability. + +**Boundary judgment:** some operational burden lies with actors who may not control referral, scope, funding, or initial triage. + +**Affected/involved:** delivery partners, users, WA Group/HMCTS. + +**Implication:** map decision rights, responsibilities, and resource flows together. + +**Ought question:** should actors bearing these costs receive more control over triage, scope, or funding rules? + +--- + +## C-06 — Knowledge: lived user experience reveals barriers not visible in service categories + +**Category:** knowledge + +**Packet basis:** moderate-digital-capability users still needed help due complexity; channel preferences reflected mobility, confidence, and context; privacy/communication issues appear in qualitative evidence. + +**Boundary judgment:** a "digital capability" classification is not sufficient expertise about actual access. + +**Affected/involved:** users, service designers/evaluators. + +**Implication:** treat lived experience as knowledge about service conditions, not merely satisfaction feedback. + +**Ought question:** how should user knowledge influence ongoing service design? + +--- + +## C-07 — Knowledge: frontline delivery partners hold operational knowledge that may not be represented upstream + +**Category:** knowledge + +**Packet basis:** partners describe real appointment complexity, geographic gaps, interpreter issues, wider support needs, and walk-in patterns. + +**Boundary judgment:** service design may depend on knowledge located at the delivery boundary. + +**Affected/involved:** delivery partners, HMCTS/WA Group. + +**Implication:** create feedback paths that allow frontline knowledge to alter service rules/resources. + +**Ought question:** what authority should accompany frontline expertise? + +--- + +## C-08 — Knowledge: the service knows much more about users who enter than people who never find it + +**Category:** knowledge / legitimacy + +**Packet basis:** SSCS dominates use; source cannot distinguish need from signposting; total eligible nonusers are unknown. + +**Boundary judgment:** evaluation evidence is conditioned on entering the support system. + +**Affected/involved:** potential users outside observed pathways. + +**Implication:** treat missing nonuser evidence as a boundary limitation, not proof of low need. + +**Ought question:** how should absent/undiscovered users be represented in service evaluation? + +--- + +## C-09 — Legitimacy: affected users are represented through research but do not appear to control service definitions + +**Category:** legitimacy + +**Packet basis:** evaluation includes interviews/surveys; service scope, triage, eligibility, network resources are institutionally designed. + +**Boundary judgment:** consultation/evaluation is not the same as decision authority. + +**Affected/involved:** users. + +**Implication:** distinguish user research from participation in governance/design decisions. + +**Ought question:** where, if anywhere, should affected users have continuing decision rights over service design? + +**Uncertainty:** packet does not describe governance/participation structures. + +--- + +## C-10 — Legitimacy: delivery partners are both implementers and affected parties + +**Category:** legitimacy / control + +**Packet basis:** partners provide service, absorb some costs, and stretch scope. + +**Boundary judgment:** partners are "involved" but may also be adversely affected by decisions made elsewhere. + +**Affected/involved:** delivery partners. + +**Implication:** do not assume formal participation in delivery means their interests/resources are adequately represented. + +**Ought question:** what representation is appropriate in service redesign/resource allocation? + +--- + +## C-11 — Legitimacy: family/friends appear as an external support system without formal voice + +**Category:** legitimacy + +**Packet basis:** users often knew no support source beyond friends/family; some valued reducing reliance on relatives. + +**Boundary judgment:** informal supporters may absorb burden outside the NDSS service boundary. + +**Affected/involved:** users and informal supporters. + +**Implication:** include informal-support displacement when defining the effects of service availability. + +**Ought question:** how should systems account for unpaid support without assuming families should provide it? + +--- + +## C-12 — Boundary critique should remain open rather than declare one ideal service boundary + +**Category:** all four sources + +**Packet basis:** wider needs, limited resources, high satisfaction, uneven channels, partner burden, unknown nonusers. + +**Boundary judgment:** expanding NDSS to cover every adjacent need could create overload just as a narrow digital boundary can omit consequential needs. + +**Affected/involved:** all. + +**Implication:** make the boundary contestable and connect excluded needs to other accountable services rather than assuming maximal integration. + +**Ought question:** which boundary creates the most defensible balance of purpose, resources, expertise, and affected interests? + From 7ccdfc978d31c603d8b3d7f5c0a064f519c528b8 Mon Sep 17 00:00:00 2001 From: Rae Lovejoy Date: Fri, 25 Sep 2026 00:12:22 -0700 Subject: [PATCH 62/66] Run T-003 Pilot 003 RS synthesis --- .../t003-editorial-pilot-003-method-d.md | 197 ++++++++++++++++++ 1 file changed, 197 insertions(+) create mode 100644 research/papers/coherent-systems/notes/t003-editorial-pilot-003-method-d.md diff --git a/research/papers/coherent-systems/notes/t003-editorial-pilot-003-method-d.md b/research/papers/coherent-systems/notes/t003-editorial-pilot-003-method-d.md new file mode 100644 index 0000000..f4b5ed0 --- /dev/null +++ b/research/papers/coherent-systems/notes/t003-editorial-pilot-003-method-d.md @@ -0,0 +1,197 @@ +# T-003 Editorial Pilot 003 — Method D + +**Method:** Root Sequence routing / adaptive-continuity synthesis +**Case:** NDSS +**Status:** EDITORIAL OUTPUT / NOT AN INDEPENDENT METHOD-VALIDATION RESULT +**Evidence:** frozen NDSS packet only + +## D-01 — Discoverability is a coupled service-design + capability problem + +**Packet basis:** many users were surprised support existed; take-up is heavily SSCS-skewed; unmet nonuser need is unknown. + +**Connects:** A-01, B-04/B-12, C-08. + +**Cross-boundary relation:** referral architecture determines which people even enter the capability-support system and therefore which needs become visible in evaluation data. + +**Consequence:** poor discoverability can both reduce substantive opportunity and bias the service's own evidence about demand. + +**Next action:** ROUTE to service discovery + capability analysis; measure referral loss/non-use before interpreting service-user composition. + +**Status:** **SYNTHESIS** — not a new mechanism. + +--- + +## D-02 — Channel "choice" is generated by an institutional supply system + +**Packet basis:** preferences vary; face-to-face/in-home availability is geographically constrained and often driven by partner availability. + +**Connects:** A-02/A-08, B-03/B-09, C-03. + +**Cross-boundary relation:** personal preference × health/access needs × geography × institutional capacity jointly produce the actually reachable channel set. + +**Consequence:** reporting choice or preference without supply conditions can misdescribe agency. + +**Next action:** ROUTE channel mechanics to service/accessibility analysis and substantive opportunity to capability analysis. + +**Status:** **SYNTHESIS**. + +--- + +## D-03 — Central triage changes the future path of a user's interaction, not only the current appointment + +**Packet basis:** service journey routes through triage; some walk-ins loop back through central process; triage determines eligibility/booking. + +**Connects:** A-03, C-04, B-04. + +**Cross-boundary relation:** an entry rule changes which later service states become reachable, who holds information, and how much friction is added. + +**Consequence:** triage should be evaluated as a transition rule, not only a front-door task. + +**Next action:** test several user journeys under different triage/delegation arrangements; evaluate consistency, burden, safeguards, and access. + +**Status:** **CANDIDATE ADD** as framing; underlying mechanism is service governance/control already captured by CSH/service review. + +--- + +## D-04 — The support layer may adapt users/partners to digital architecture instead of changing the underlying digital service + +**Packet basis:** NDSS exists because some people cannot use online HMCTS services unaided; partners provide substantial assistance; some users would otherwise use paper or not submit. + +**Connects:** B-01/B-06/B-10, C-01/C-02/C-05, A-04/A-09/A-11. + +**Cross-boundary relation:** the system can restore successful digital submission by adding a support layer even if the underlying online process remains difficult for some users. + +**Consequence:** local success at NDSS can hide a higher-level design question: which barriers should be removed from the base HMCTS service versus compensated by ongoing support? + +**Next action:** compare root-cause accessibility/usability changes, supported routes, and non-digital routes rather than treating assistance as either failure or complete solution. + +**Status:** **CANDIDATE ADD / SYNTHESIS**. Requires evidence about underlying digital services; packet cannot answer it. + +--- + +## D-05 — Wider support by delivery partners is adaptation that can externalize burden + +**Packet basis:** partners provide procedural/legal/emotional support and sometimes absorb interpreter/no-show costs. + +**Connects:** A-04/A-06/A-09, B-09/B-10, C-05/C-10. + +**Cross-boundary relation:** gaps at one service boundary are repaired through flexible behavior at another layer. + +**Consequence:** the system can appear effective because delivery partners absorb mismatch. + +**Next action:** ROUTE cost/scope to service operations and boundary/control to CSH; make transferred labor/resources visible. + +**Status:** **SYNTHESIS**. + +--- + +## D-06 — Success metrics can create false closure at digital submission + +**Packet basis:** submission and satisfaction are strong; next-step uncertainty remains; broader case outcomes are unknown. + +**Connects:** A-07/A-11, B-10/B-11, C-01. + +**Cross-boundary relation:** the metric "form submitted digitally" ends the measured service loop earlier than the user's wider process necessarily ends. + +**Consequence:** local success can coexist with unresolved procedural capability. + +**Next action:** ROUTE outcome-definition question to service evaluation/CSH; measure continuity into next steps without expanding NDSS automatically. + +**Status:** **SYNTHESIS**. + +--- + +## D-07 — Service history may reinforce the distribution it observes + +**Packet basis:** established SSCS referral pathway produces most use; non-SSCS awareness is weaker; service evidence is therefore dominated by SSCS users. + +**Connects:** A-01, B-04/B-12, C-08. + +**Cross-boundary relation:** referral structure → observed demand → staff experience/service optimization → potentially stronger support for the already-visible population. + +**Consequence:** a path-dependent feedback loop is plausible. + +**Next action:** treat this as a **HYPOTHESIS**; compare unmet demand and service quality across service types before claiming reinforcement. + +**Status:** **CANDIDATE ADD**, evidence insufficient for mechanism claim. + +--- + +## D-08 — Follow-up clarity is a continuity condition for supported agency + +**Packet basis:** 20% unclear on next steps; organisational source of communications sometimes unclear. + +**Connects:** A-07/A-10, B-11, C-01. + +**Cross-boundary relation:** an appointment can solve the immediate task while failing to preserve the user's ability to navigate the next transition. + +**Consequence:** support quality should include continuity into the next stage. + +**Next action:** ROUTE mechanics to service design; capability interpretation to B. + +**Status:** **SYNTHESIS**. + +--- + +## D-09 — Adviser-completed action and user-supported action may have different future effects, but the packet cannot say which is preferable + +**Packet basis:** support sometimes involves advisers entering/submitting information; no long-term capability comparison is supplied. + +**Connects:** B-06, A-11. + +**Cross-boundary relation:** two routes can produce the same current output while differing in learning, confidence, speed, burden, or preferred support. + +**Consequence:** optimizing for independence could be paternalistic; optimizing only for throughput could create unnecessary dependency. + +**Next action:** collect user-valued outcome data and repeat-support patterns; preserve supported action as legitimate. + +**Status:** **CANDIDATE ADD / evidence request**. + +--- + +## D-10 — Feedback and revision authority are distributed across users, partners, triage, and HMCTS + +**Packet basis:** users provide survey/interview feedback; partners hold operational knowledge; central organizations control service rules/resources. + +**Connects:** A-08/A-09/A-12, C-05/C-07/C-09/C-10. + +**Cross-boundary relation:** people detecting mismatch are not necessarily the people with authority/resources to revise it. + +**Consequence:** learning can stall if feedback channels do not reach revision power. + +**Next action:** ROUTE governance/boundary questions to CSH; map how user/partner evidence changes design/funding rules. + +**Status:** **SYNTHESIS**. + +--- + +## D-11 — The service should preserve plurality of access rather than optimize one "ideal" user trajectory + +**Packet basis:** users prefer different modes for different reasons; resources are constrained; support needs differ. + +**Connects:** A-02/A-05, B-03/B-06, C-03/C-12. + +**Cross-boundary relation:** different bodies, contexts, skills, and values produce different viable routes. + +**Consequence:** one universally preferred channel or independence model is not supported by the packet. + +**Next action:** preserve multiple practical routes where justified; test constraints rather than equating uniformity with coherence. + +**Status:** **SYNTHESIS**. + +--- + +## D-12 — Most of the consequential mechanisms already belong to A, B, or C + +**Packet basis:** comparison of the frozen method outputs. + +**Connects:** all. + +**Cross-boundary relation:** RS is useful primarily when it shows how service design, capability, boundary judgments, feedback, and adaptation interact. + +**Consequence:** claiming a new "agency/coherence method" would duplicate established analysis. + +**Next action:** retain the router/synthesis role; use **NO ADD** when the connection changes no question or decision. + +**Status:** **NO ADD / methodological finding**. + From 9d8336256adc72fab83594e26252c2fa37b925ef Mon Sep 17 00:00:00 2001 From: Rae Lovejoy Date: Fri, 25 Sep 2026 00:13:40 -0700 Subject: [PATCH 63/66] Code T-003 NDSS method ownership pilot --- .../t003-editorial-pilot-003-comparison.md | 407 ++++++++++++++++++ 1 file changed, 407 insertions(+) create mode 100644 research/papers/coherent-systems/notes/t003-editorial-pilot-003-comparison.md diff --git a/research/papers/coherent-systems/notes/t003-editorial-pilot-003-comparison.md b/research/papers/coherent-systems/notes/t003-editorial-pilot-003-comparison.md new file mode 100644 index 0000000..d942917 --- /dev/null +++ b/research/papers/coherent-systems/notes/t003-editorial-pilot-003-comparison.md @@ -0,0 +1,407 @@ +# T-003 Editorial Pilot 003 — NDSS comparison + +**Status:** EDITORIAL METHOD-OWNERSHIP RESULT / NOT INDEPENDENT VALIDATION +**Case:** UK National Digital Support Service +**Methods:** A service/accessibility · B capability-oriented · C CSH · D Root Sequence synthesis +**Analyst/coder:** same AI-assisted research process +**Important contamination:** the analyst saw the source report's recommendation/conclusion material during case vetting. Therefore this document does **not** score discovery or prediction of withheld recommendations. + +## Executive result + +Pilot 003 strongly supports the emerging **Root Sequence-as-router** model. + +The three native analyses each captured a distinct layer well: + +- **Method A** was strongest on service journey, channel availability, privacy, handoffs, capacity, operations, and measurable service fixes. +- **Method B** was strongest on the difference between nominal access and substantive opportunity, conversion factors, supported agency, and the limits of treating digital skill as the whole problem. +- **Method C** was strongest on purpose, control, service boundaries, whose knowledge counts, affected-but-not-involved actors, and open legitimacy questions. +- **Method D** was strongest at showing how those findings interact through referral structure, adaptation, feedback, continuity, burden shifting, and future paths. + +But Method D did **not** produce a clearly evidence-supported, decision-relevant mechanism that was substantively absent from A/B/C. + +Current result: + +> **RS added cross-method synthesis and question routing, not a new native service-analysis method.** + +That is a positive result for the narrowed Root Sequence role and a near-null result for any stronger "Dynamic Coherence method" claim. + +--- + +## Method ownership map + +| Case question | A | B | C | D role | +| --- | :---: | :---: | :---: | --- | +| Is the service discoverable? | strong | strong as conversion factor | strong as evidence-boundary issue | connects referral → observed demand → evidence | +| Are channels practically usable? | strong | strongest conceptual account of substantive option | strong control/resource question | connects preference + capacity + institutional supply | +| Are handoffs efficient/legible? | strongest | secondary | control-boundary perspective | frames triage as transition rule | +| Does "digital support" match actual need? | strong | strong | strongest boundary/purpose critique | links boundary mismatch to partner adaptation | +| Privacy/accessibility | strongest operationally | capability condition | legitimacy/knowledge secondary | routes; little independent add | +| Partner burden/capacity | strongest operationally | institutional conversion factor | strongest control/affected-party analysis | shows burden shifting across boundary | +| User independence vs supported action | partial | strongest | boundary/purpose question | preserves future-capability tension | +| Who defines success? | measurement-oriented | outcome freedom | strongest | connects local metric to wider trajectory | +| Nonusers / invisible unmet need | evidence request | strongest capability concern | strongest boundary-of-knowledge concern | models referral/evidence feedback | +| Who can revise the service? | operational evidence request | secondary | strongest | connects feedback to revision authority | +| Path dependence over time | partial | partial | partial | strongest explicit temporal framing | +| Cross-method interaction | not its role | not its role | not its role | strongest | + +--- + +## Method A findings: ownership and unique value + +Method A produces the most immediately implementable service-design findings: + +- referral/discovery measurement; +- practical channel coverage; +- walk-in handoff reduction; +- service-scope clarity; +- privacy/accessibility controls; +- complexity-sensitive appointment design; +- follow-up clarity; +- network capacity measurement; +- partner cost/responsibility mapping; +- organizational identity/hand-off legibility; +- outcome measures beyond submission. + +These should **not** be relabeled as Dynamic Coherence findings. + +They are ordinary competent service/accessibility work. + +### A-specific value + +The concrete decomposition of: + +- journey; +- channel; +- environment; +- staffing; +- handoff; +- privacy; +- operational capacity; + +is clearer and more actionable than a high-level systems synthesis. + +--- + +## Method B findings: ownership and unique value + +Method B adds an important conceptual correction that service review alone can understate: + +> **A service option is not a substantive opportunity merely because it exists.** + +It makes the conversion structure explicit: + + formal option/resource + + + personal factors + + + social factors + + + environmental/institutional factors + ↓ + substantive opportunity + +This clarifies: + +- why face-to-face can be nominally present but practically unreachable; +- why moderate digital skill does not guarantee capability to navigate the process; +- why discoverability is part of access; +- why supported action can be genuine agency; +- why family help is not automatically equivalent to chosen formal support; +- why service-user satisfaction cannot represent people who never reach the service. + +### B-specific value + +Root Sequence's earlier "agency envelope" intuition is substantially better understood as **routing to capability analysis** for this part of the case. + +RS should not claim this insight as new. + +--- + +## Method C findings: ownership and unique value + +Method C makes questions explicit that A/B can leave implicit: + +> **Who gets to define the service problem, allocate resources, decide the boundary, and speak for people outside the observed pathway?** + +It exposes distinctions among: + +- user benefit; +- institutional purpose; +- resource control; +- frontline knowledge; +- user research; +- user decision authority; +- partner participation versus partner power; +- service scope versus excluded needs; +- involved actors versus affected actors. + +### C-specific value + +This is the strongest prior-art home for several questions Root Sequence had started calling: + +- power over conditions; +- revision power; +- boundary choice; +- affected parties; +- legitimacy. + +RS should **route to CSH**, not reinvent CSH under coherence language. + +--- + +## Method D finding-level disposition + +| D finding | Disposition | Reason | +| --- | --- | --- | +| D-01 discoverability couples service + capability | SYNTHESIS / N1 | A/B/C already identify the components; D makes the evidence-feedback relation explicit. | +| D-02 channel choice generated by institutional supply | SYNTHESIS / N1 | Strong connection; A/B/C already provide the actionable mechanisms. | +| D-03 triage as transition rule | SYNTHESIS / N1 | Useful temporal representation; control/handoff issue already captured by A/C. | +| D-04 support layer may compensate for base-service barriers | CANDIDATE ADD / E1 / N1 | Important systems question, but packet lacks evidence about the underlying HMCTS digital services; requires new evidence rather than a conclusion. | +| D-05 partner adaptation externalizes mismatch | SYNTHESIS / N1 | A/C already expose burden and control; D connects it to adaptive-system language. | +| D-06 digital submission can create false closure | SYNTHESIS / N1 | A/B/C already question outcome boundary; D links current success to later continuity. | +| D-07 referral history may reinforce observed service distribution | HYPOTHESIS / N1 | Dynamic feedback framing is interesting but not established by packet. | +| D-08 follow-up as continuity condition | SYNTHESIS / N0/N1 | A/B already capture. | +| D-09 adviser-completed vs supported completion future effects | EVIDENCE REQUEST / N1 | B already protects supported agency; D makes future-state comparison explicit. | +| D-10 feedback separated from revision power | SYNTHESIS / N1 | C owns control/knowledge; D connects it temporally. | +| D-11 plurality of access | SYNTHESIS / N0 | A/B/C already establish heterogeneous needs/options. | +| D-12 native methods own most mechanisms | METHODOLOGICAL RESULT | Supports router role. | + +### D-specific decision-relevant novelty + +**E1–E2 / D2 / N2: 0** + +Again. + +This is now the third editorial comparison in which RS/Dynamic Coherence fails to produce a clearly unique decision-relevant mechanism over competent native analysis. + +--- + +## The most interesting candidate add: support-layer compensation + +D-04 deserves preservation as a **research question**: + +> When a support layer successfully helps people use a difficult system, which barriers should remain supported and which should be removed from the underlying system itself? + +This connects: + +- capability; +- accessibility; +- service design; +- institutional boundary; +- adaptation; +- hidden support labor; +- path dependence. + +But the frozen packet does not include sufficient evidence about the underlying HMCTS digital-service designs. + +Therefore the correct output is: + +> **new evidence needed** + +not: + +> NDSS is masking inaccessible services. + +This is a good example of what RS synthesis may do well: **generate a cross-boundary question that requires returning to native evidence.** + +--- + +## A second useful candidate: referral structure shapes evidence + +The packet supports: + +- SSCS has a stronger referral pathway; +- SSCS dominates NDSS use; +- the evaluation cannot determine whether this is need or signposting. + +RS adds the hypothesis: + + referral structure + ↓ + who reaches service + ↓ + who appears in service data + ↓ + what staff become experienced at + ↓ + future service design / referrals + ↺ + +Only the first two links are well-supported by this packet. + +The rest must remain hypothetical. + +This is a useful **feedback-loop candidate**, not a finding. + +--- + +## Research-method lesson + +Pilot 003 supports this sequence: + + messy case + ↓ + ROUTER + ↓ + native service/accessibility analysis + + + capability analysis + + + critical boundary/power analysis + ↓ + RS synthesis asks: + how do these findings interact over time? + ↓ + new cross-boundary questions + ↓ + return to native methods for evidence + +This is importantly different from: + + messy case + ↓ + Dynamic Coherence Method™ + ↓ + answer + +The latter is not supported by the pilots. + +--- + +## What the router got right + +The preregistered Method Router predicted that this case contains several question shapes simultaneously: + +- substantive human opportunity → capability approach; +- service/accessibility barriers → service/accessibility methods; +- boundary/power/affected parties → CSH; +- path dependence / future possibility → RS synthesis. + +The outputs behaved accordingly. + +This is **editorial support for the router architecture**, not validation. + +--- + +## What the router still lacks + +### 1. Service design / public-service research is too generic + +"Competent service review" needs stronger native references and methods. + +Future Reading Trail work should cover: + +- service design; +- inclusive service design; +- digital inclusion; +- public-service accessibility; +- journey mapping; +- assisted digital support; +- service standards. + +### 2. Capability analysis needs method fidelity + +The editorial prompt captures core ideas, but capability scholarship is broader and internally diverse. + +A future independent comparison should involve someone competent in the capability approach. + +### 3. CSH needs method fidelity + +A twelve-finding AI adaptation is not equivalent to a real boundary critique with stakeholder participation. + +### 4. Participation is underdeveloped + +The packet reports research **about/with** service users, but the router needs a stronger route to: + +- participatory design; +- co-design; +- participatory action research; +- disability-led design; +- lived-experience expertise. + +--- + +## No normative winner + +This pilot does not establish: + +- how large the delivery network should be; +- that remote or face-to-face support is better; +- that NDSS scope should expand; +- that users should become independently able to complete forms; +- that local triage should replace central triage; +- that one governance structure is legitimate. + +Those remain design/governance questions requiring additional evidence and participation. + +--- + +## Decision after Pilot 003 + +### Keep + +- Root Sequence Research Method; +- Method/Concept Router; +- native-method routing; +- cross-method synthesis; +- explicit "NO ADD" outcome; +- state/transition/history questions as cross-method prompts. + +### Narrow + +"Dynamic Coherence" further away from being a candidate standalone review method. + +### Route + +- substantive opportunity → capability approach; +- boundary/power/affected → CSH; +- accessibility/service mechanics → native accessibility/service methods. + +### Add research + +- participatory/co-design route; +- stronger service-design method route; +- information-discovery route for service discoverability. + +### Do not do + +- a fourth AI-only comparative case immediately; +- prompt-tune until RS produces an N2 finding; +- call the router validated. + +--- + +## Next empirical gate + +The next T-003-quality comparison should involve **independent human expertise**, not another same-model case. + +Good options: + +1. one service/accessibility practitioner; +2. one capability/justice scholar or informed reviewer; +3. one CSH/critical-systems practitioner; +4. independent finding coding. + +Until then: + +> **RS method-router architecture: promising editorially; externally unvalidated.** + +--- + +## Editorial conclusion + +Cloudflare taught us that RS should not replace technical incident methods. + +NDSS teaches the same lesson in a richer human/institutional case: + +> **RS should not replace capability analysis, accessibility practice, or critical boundary critique either.** + +The potentially durable contribution is the layer that notices: + +> **these are several different questions coupled in one lived system.** + +Then routes each question to the method that can actually answer it. + +That is much more modest than a universal coherence method. + +It also looks increasingly like what Root Sequence is actually for. From 765b5e6e65c95a0331bd6847da269dca79f50939 Mon Sep 17 00:00:00 2001 From: Rae Lovejoy Date: Fri, 25 Sep 2026 00:14:09 -0700 Subject: [PATCH 64/66] Add contamination check to research method --- research/method.md | 34 ++++++++++++++++++++++++++++++++++ 1 file changed, 34 insertions(+) diff --git a/research/method.md b/research/method.md index 1d65efa..6dec498 100644 --- a/research/method.md +++ b/research/method.md @@ -299,6 +299,40 @@ Record: --- +## 10A. Check contamination and analyst knowledge + +A frozen evidence packet does **not** create blinding by itself. + +Before claiming discovery or prediction, ask: + +- Has the analyst already seen the withheld answer/recommendation/outcome? +- Did the same AI process browse the source before the packet was frozen? +- Was the case selected after its conclusion was known? +- Did the method author help construct the evidence packet? +- Are "withheld" facts still present in conversation or analyst memory? + +If yes: + +> **downgrade the exercise to an editorial method/ownership test.** + +It may still test: + +- prompt usability; +- overlap; +- concept ownership; +- synthesis; +- unsupported inference. + +It cannot honestly test: + +- blinded discovery; +- prediction; +- independent derivation. + +Record contamination rather than performing methodological theater. + +--- + ## 11. Freeze before testing When doing a comparison: From 1f754d2524e9b7eda58142a94f2fed682139bcd1 Mon Sep 17 00:00:00 2001 From: Rae Lovejoy Date: Fri, 25 Sep 2026 00:14:11 -0700 Subject: [PATCH 65/66] Add service/participation routes and NDSS worked example --- research/method-router.md | 28 ++++++++++++++++++++++++++++ 1 file changed, 28 insertions(+) diff --git a/research/method-router.md b/research/method-router.md index 253dff4..2f87882 100644 --- a/research/method-router.md +++ b/research/method-router.md @@ -18,6 +18,8 @@ Root Sequence's job is then to preserve the relationships among those analyses w | "Why does it keep doing what used to work?" | path dependence, lock-in, maladaptation, governing variables | historical institutionalism, organizational learning, double-loop learning, resilience/adaptation literature | calling everything an attractor | | "What future states are actually possible under these constraints?" | reachability, viability, control | control theory, viability theory, operations research | treating metaphorical possibility-space as mathematics | | "Does this person really have an option?" | capability, affordance, accessibility, conversion factors | capability approach, disability/accessibility research, HCI, ecological psychology | counting menu options as agency | +| "Can people actually complete this end-to-end service journey?" | discoverability, handoffs, channels, support, privacy, continuity | service design, inclusive service design, accessibility evaluation, digital-inclusion research | abstract agency language replacing journey/operations work | +| "Whose experience should shape the design, not merely be studied afterward?" | participation, co-design, lived expertise, ownership | participatory design, co-design, participatory action research, disability-led design | treating user research as user power | | "What can this body/environment relation enable?" | affordance, skill, body schema | ecological psychology, embodied cognition, disability/access research | assuming physical presence = usable possibility | | "Who defined success and the system boundary?" | boundary judgment, purpose, beneficiary, affected parties | Critical Systems Heuristics | treating boundaries as neutral facts | | "Are people solving different problems because they see different situations?" | worldview, framing, problem situation | Soft Systems Methodology, participatory design | forcing one ontology | @@ -71,6 +73,32 @@ For each route: - **related RS project** - **confidence / unresolved ambiguity** +## Worked routing example — NDSS editorial pilot + +The NDSS case routed into at least four native analyses: + + digital-support service + │ + ├── service/accessibility review + │ └── journey, privacy, channel supply, handoffs, capacity + │ + ├── capability analysis + │ └── substantive opportunity, conversion factors, supported agency + │ + ├── Critical Systems Heuristics + │ └── purpose, control, knowledge, legitimacy, affected boundaries + │ + └── Root Sequence synthesis + └── referral feedback, burden shifting, continuity, path dependence + +The RS synthesis produced no clearly unique decision-relevant native mechanism over the three baseline analyses. + +Its useful role was connecting them and generating evidence questions spanning their boundaries. + +That is an example of the router **succeeding without RS "winning."** + +--- + ## Anti-totalization rule Do not choose one row and make all others disappear. From be93afd97e65af22e5e53d91733b4d717da69790 Mon Sep 17 00:00:00 2001 From: Rae Lovejoy Date: Fri, 25 Sep 2026 00:14:30 -0700 Subject: [PATCH 66/66] Update T-003 with NDSS routing pilot --- .../papers/coherent-systems/open-questions.md | 61 +++++++++++++++++-- 1 file changed, 56 insertions(+), 5 deletions(-) diff --git a/research/papers/coherent-systems/open-questions.md b/research/papers/coherent-systems/open-questions.md index 547f1bc..8359957 100644 --- a/research/papers/coherent-systems/open-questions.md +++ b/research/papers/coherent-systems/open-questions.md @@ -44,15 +44,66 @@ A later extension should test recurring demand, referrals, service outcomes, unc ## T-003 — Added-value comparison -**Editorial pilots completed; independent comparison still unrun.** The [related-work note](notes/related-work.md#candidate-comparison-for-t-003-not-a-completed-study) identifies candidate baselines and fidelity checks. The [T-003 protocol](notes/t003-added-value-protocol.md) freezes the proposed prompt, finding definitions, coding dimensions, burden/privacy measures, null-result criteria, and the distinction between an editorial pilot and independent review. [Pilot 001](notes/t003-editorial-pilot-001-comparison.md) and [Pilot 002](notes/t003-editorial-pilot-002-comparison.md) both produced a near-null result for unique decision-relevant added value from Dynamic Coherence over a competent ordinary incident/system review. These same-model pilots are method-debugging evidence only; no independent reviewer or method-superiority result exists. +**Three AI-assisted editorial pilots completed; independent comparison still unrun.** -The same-case editorial stop rule now applies. The next legitimate step is **an independent reviewer comparison on a different case or a method-fidelity comparison with a properly prepared established method**, not another prompt-tuning pass on the Cloudflare incident. Choose a small, public, non-sensitive design case and a competent existing review method. Compare it with the section 12 procedure using the same information and a comparable review effort. Avoid choosing a case merely because its known conclusion already matches the framework, and avoid giving the new method more evidence while calling its findings an improvement. +### Pilot 001–002: Cloudflare technical incident -**Measure:** Consequential omissions identified, false alarms, traceability, disagreement, reviewer time, and unnecessary information requests. Define “consequential” before evaluating outputs. +Two same-case comparisons tested a competent ordinary incident/system review against the frozen dynamic-coherence prompt, once with source-authored remediation present and once with that section withheld from the written packet. -**Failure signal:** No useful additional findings, unacceptable burden, unresolvable reviewer disagreement, or more privacy exposure without corresponding benefit. +Both produced a near-null result for unique decision-relevant Dynamic Coherence findings. The ordinary review also surfaced a concrete component-level containment action that the dynamic prompt omitted twice. + +See: + +- [Pilot 001 comparison](notes/t003-editorial-pilot-001-comparison.md) +- [Pilot 002 comparison](notes/t003-editorial-pilot-002-comparison.md) + +### Pilot 003: NDSS agency / accessibility / boundary case + +The [NDSS case](notes/t003-case-2-selection-ndss.md) compared: + +- competent service/accessibility review; +- capability-oriented analysis; +- simplified Critical Systems Heuristics; +- Root Sequence routing/adaptive-continuity synthesis. + +Result: + +- native methods owned the important mechanisms; +- RS added cross-method connections and routing; +- no clearly evidence-supported, decision-relevant native mechanism was unique to RS; +- the pilot exposed missing router paths for participatory/co-design methods and stronger service-design/digital-inclusion methods. + +See [Pilot 003 comparison](notes/t003-editorial-pilot-003-comparison.md). + +### Methodological correction + +Pilot 003 also exposed a contamination issue: the same AI process had viewed source recommendations while vetting the case. The packet could withhold those recommendations from the written method inputs, but the analyst was not genuinely blind. + +The canonical [Root Sequence Research Method](../../method.md) now records the rule: + +> withholding evidence from a packet is not blinding if the analyst has already seen it. + +### Current T-003 conclusion + +The editorial evidence increasingly supports treating Root Sequence / Dynamic Coherence as a **routing and synthesis layer**, not a replacement for competent native methods. + +That is still not independent validation of the router. + +### Next legitimate gate + +Do **not** run a fourth same-model case merely to accumulate volume. + +The next useful comparison should include independent human/domain expertise, for example: + +- service/accessibility practitioner; +- capability-approach-informed reviewer; +- Critical Systems Heuristics / critical-systems practitioner; +- independent finding coders. + +A different case should be selected and frozen before those reviewers see outputs from other methods. + +A null result remains acceptable: if the router adds no useful cross-method synthesis or reduces no fragmentation, narrow it further. -**Boundary:** Select the baseline and protocol before execution. No experiment, deployment, or participant recruitment is authorized by this plan. ## Next writing pass