🌱 The Root Sequence

New, returning, or overloaded? Read START-HERE.md for the smallest useful map.

Root Sequence is an independent interdisciplinary research initiative exploring how intelligence, technology, and social systems shape one another.

This repository holds research and developing ideas that connect different parts of Root Sequence. Individual projects keep their own direction and maintain their detailed work separately.

Work here ranges from research notes to experimental tools. Evidence and review status vary, and the working paper is AI-assisted and still awaits author review. The material does not establish a finished theory or a validated universal framework.

Rae Lovejoy, who started Root Sequence, uses AI both as an accessibility aid and as a tool for developing the work. Read about accessibility, contributions, and review.

Where to begin

• Research: current work, with evidence and review notes.
• Ecosystem map: see what belongs in each project.
• Idea Trails: follow a question across projects. The trail browser links to individual documents.
• Wiki: recurring terms and the work they refer to.
• Refresh checklist: what is complete and what still needs review.

For a shorter introduction, read Start here.

Why “Root Sequence”?

A root is an underlying condition, relationship, history, dependency, or constraint from which visible outcomes can grow. A sequence is how conditions unfold through time, feedback, choice, adaptation, and consequence.

Together, the name asks: What conditions made this possible, and what does it make possible next? Sequences can become roots for whatever follows, so the inquiry is recursive rather than a search for one first cause or one predetermined path.

The inquiry also asks how an arrangement's constraints shape available possibilities: which limits are fundamental, which depend on current conditions, what connections should be preserved, and what different futures could become reachable through change. An obstacle can be real without being inevitable; an imagined alternative can be possible without yet being accessible.

Read the maintained explanation in Why “Root Sequence”?.

Public Seed v0.1

The reader-facing website source lives in site/. The published professional refresh introduces the project and routes readers into the research, related projects, and participation paths without replacing their canonical homes. The website directory also records approval, validation, and deployment boundaries.

---

Recurring questions and lenses

Root Sequence does not require one master framework. It uses several kinds of lenses for different jobs:

• systems/ develops analytical principles, models, and methods for examining structure, power, feedback, failure, and recovery;
• concepts/ holds shared definitions, cross-project frameworks, design principles, and methods, including Legible Systems;
• Idea Trails follow recurring questions across projects without making every project use the same answer;
• founding-texts/ preserves founding manifestos, early cycles and metaphors, normative essays, and historical orientations.

The Liberation Cycle, Visibility Loop, and Roots → Signals → Growth → Fruits → Compost sequence are retained as exploratory and expressive models. They are not the repository's information architecture or evidence that every person, system, movement, or intelligence follows one mechanism.

---

📂 Repository map

• site/ — reader-facing Public Seed website source; not a replacement for research or the Wiki
• research/ — bounded inquiries and synthesis papers, including What If It All Works? on progress, access, perfection, and the ethics of what's left out; underlying concepts and evidence retain their canonical homes
• research/methods/ — shared error-correcting inquiry methods, including epistemic contrast and deliberative inquiry
• founding-texts/ — founding texts, early models, manifestos, normative essays, and historical orientations
• systems/ — analytical principles, models, and methods for understanding system behavior
• concepts/ — shared definitions, cross-project frameworks, design principles, and methods
• analysis/ — system diagnosis (power, capitalism, infrastructure)
• ideology/ — political and cultural frameworks
• futures/ — trajectories, alternatives, and resilience
• commons/ — practical outputs (zines, maps, fragments)
• /wiki/ — migration pointer to the standalone Root-Sequence/wiki repository
• /cli/ — experimental scripts and tools, including the Idea Trail browser generator
• /assets/ — visuals and diagrams
• THOUGHT_ROUTING.md — the organization-wide RS? capture and routing convention

root_map.md is the canonical repository architecture and content-routing guide. The organization-wide map lives in ECOSYSTEM.md, recurring cross-project questions are traced in IDEA_TRAILS.md, their document-level relationships are browsable in IDEA_TRAIL_INDEX.md, and the cross-project vocabulary/history layer lives in the standalone Root-Sequence/wiki repository. The latest comprehensive cleanup record is in AUDIT.md.

---

📚 Start Here

Suggested entry points:

• Public Seed website source — approved professional refresh, publication workflow, and deployment records
• Coherence Is a Systems Property — v0.1-dev living-paper scaffold; AI-assisted and awaiting author review
• Conscious Systems — exploratory research question on experience, physical organization, and possible artificial systems; AI-assisted and awaiting author review
• Ecosystem Map — understand the wider project family
• Root Sequence Wiki — browse terms, phrases, projects, provenance, and conceptual archaeology
• Idea Trails — understand the recurring questions and how each project transforms them
• Idea Trail Browser — browse actual documents grouped by trail and role
• Idea Trail Metadata Convention — lightweight visible + machine-searchable metadata for participating documents
• IDEA_TRAIL_GRAPH.yml — machine-readable document ↔ trail graph used to generate the browser
• Thought Routing (RS?) — capture a thought once, find one canonical home, and add deliberate cross-project links without duplicate substance
• Epistemic Contrast — compare differently situated accounts to expose assumptions, mechanisms, convergence, disagreement, and missing evidence
• Deliberative Inquiry — build sufficient shared understanding before consequential collective judgment or authorization
• Design Grammar — review-pending map of recurring cross-project design questions
• Agency and Automation — review-pending treatment of delegation, chosen activity, compulsory labor, and collective authority
• Legible Systems — design systems that can be simple to use without remaining mysterious
• Founding texts and early orientations — browse exploratory models, manifestos, normative essays, and historical project pointers by role

---

🌌 Why This Exists

This project explores systems as living, interdependent processes.

Existential Euphoria explores a felt orientation Rae connects to this inquiry: wonder, interdependence, and the possibility of living more humanely, with room for contradiction and ordinary life. The original reflection and provisional RS connections keep “good” and “coherent” open to examination; no shared emotional state is required to participate.

Ideas move between technical work and questions about how people live together. A pattern noticed in one field may suggest a question elsewhere, but the connection needs examination. The models remain provisional and can change as the work develops.

---

🧠 Context

Influences include:

• systems thinking
• free software and self-hosting
• resilience practices
• post-work and alternative infrastructures

---

📝 Notes

This repository is intentionally incomplete.

Some documents are stable. Others are drafts, fragments, or early explorations.

The goal is not perfection, but continuity and iteration.

---

🔧 Navigation maintenance convention

For work across Root Sequence repositories, substantive structural changes should update their navigation in the same change.

When a file, concept, system, canonical treatment, or project relationship is added, moved, renamed, retired, or materially expanded:

1. update the nearest relevant README or local index;
2. update any affected canonical map / Idea Trail / project index;
3. update a top-level README only when the change matters at that level;
4. avoid unrelated README churn merely to make every repository look synchronized.

If a reader could reasonably miss the new work because the old navigation does not point to it, the navigation is part of the change.

This convention is intended to keep repository work self-indexing rather than relying on memory or a later cleanup pass.

---

🔄 Use & Remix

Root Sequence’s own material is released under CC0 1.0. Check the original source and any separate terms before reusing third-party or contributed material. Related projects keep their own permissions.

Collaborating on the inquiry

The commons collaboration proposal explores how people can contribute and disagree while keeping clear boundaries around responsibility and decisions. The practices remain proposals for review.