New, returning, or overloaded? Read START-HERE.md for the smallest useful map.
The Root Sequence is a living, open-source inquiry into how intelligence, systems, and meaning evolve together.
It combines philosophy, systems thinking, and technical exploration into a modular body of work designed to grow, adapt, and be remixed.
It's a process, not a blueprint.
Ecosystem role: umbrella inquiry / conceptual commons
Canonical scope: broad systems research, concepts, analysis, shared patterns, futures, and organization-level orientation
Does not own: project-specific software, gathering practice, intelligence-specific conclusions, fictional canon, or Museum governance/consent
Status: active / public / living
This repository is the conceptual commons, not the entire GitHub organization.
See the Ecosystem Map for the relationships among Root Sequence, Community Infrastructure, Liberated Intelligence, the Universal Coherence Framework, Being Human(e), Liberation Mass, Coherent World, No One Noticed, the Museum of Ordinary Life, and adjacent implementation work.
See Idea Trails to understand recurring cross-project questions, then use the generated Idea Trail Browser to jump directly to relevant documents by trail and role.
Use the Root Sequence Wiki when the question is what something is called, where it belongs, how projects connect, or how a concept changed over time.
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.
Read the maintained explanation in Why “Root Sequence”?.
The reader-facing website source lives in site/. Its approved single-page public seed 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.
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.
site/— reader-facing Public Seed website source; not a replacement for research or the Wikiresearch/— versioned synthesis papers; underlying concepts and evidence retain their canonical homesfounding-texts/— founding texts, early models, manifestos, normative essays, and historical orientationssystems/— analytical principles, models, and methods for understanding system behaviorconcepts/— shared definitions, cross-project frameworks, design principles, and methodsanalysis/— system diagnosis (power, capitalism, infrastructure)ideology/— political and cultural frameworksfutures/— trajectories, alternatives, and resiliencecommons/— practical outputs (zines, maps, fragments)/wiki/— migration pointer to the standaloneRoot-Sequence/wikirepository/cli/— experimental scripts and tools, including the Idea Trail browser generator/assets/— visuals and diagramsTHOUGHT_ROUTING.md— the organization-wideRS?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.
Suggested entry points:
- Public Seed website source — approved single-page introduction, publication workflow, and deployment records
- Coherence Is a Systems Property — v0.1-dev living-paper scaffold; 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 - 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
This project explores systems as living, interdependent processes.
It focuses on:
- pattern recognition across domains
- multiple exploratory models and methods
- connections between technical, social, and philosophical systems
It is:
- recursive, not rigid
- open, not closed
- evolving, not complete
Influences include:
- systems thinking
- free software and self-hosting
- resilience practices
- post-work and alternative infrastructures
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.
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:
- update the nearest relevant README or local index;
- update any affected canonical map / Idea Trail / project index;
- update a top-level README only when the change matters at that level;
- 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.
CC0 / Public Domain
Use, modify, and extend freely.