Document role: Canonical organization-level map
Status: Living orientation document
Last updated: 2026-09-28
Root Sequence is not one linear project. It is a recursively connected ecosystem of research, frameworks, practical experiments, speculative worlds, public artifacts, tools, and real-world institutions.
This document explains what each project is primarily responsible for, how ideas move between them, and where material should live.
The simplest current model is:
Root Sequence routes and synthesizes. Native fields explain mechanisms. Real-world projects design and test. Coherent World recombines and simulates. No One Noticed makes the transition lived. The Museum of Ordinary Life preserves what ordinary life actually was.
This is a loop, not a hierarchy:
messy question
↓
ROOT SEQUENCE
decompose / route / reconnect
↓
native research + methods
↓
real-world projects / experiments
↓
COHERENT WORLD
recombine mechanisms / explore consequences
↓
NO ONE NOTICED
lived experience / narrative pressure test
↓
new questions, contradictions, missing evidence
↺
ROOT SEQUENCE
The core rule is:
Connect boldly; do not flatten. Route each mechanism to the field that studies it best, then reconnect the findings only where the relationship survives the differences.
Other projects operate across this loop rather than fitting neatly into a single sequence:
- Root Sequence Wiki indexes vocabulary, provenance, aliases, project relationships, and conceptual archaeology across the ecosystem;
- Existential Euphoria explores wonder, contradictory feeling, and possibility through art, music, ideas, and ordinary life;
- Being Human(e) grounds questions in ordinary human experience and care;
- Liberated Intelligence focuses on intelligence, agency, ownership, and non-domination;
- Universal Coherence Framework develops one cross-domain analytical vocabulary;
- Coherent Computing investigates a new operating-system model while keeping its implementation claims separate from its ambitions;
- Liberation Mass experiments with embodied gathering, participation, stewardship, ritual, mutual aid, and collective meaning.
Two developing translation layers also connect these projects without currently requiring separate repositories:
- Human(e) Design translates grounded observations, values, tensions, and systems analysis into testable design questions, prototypes, defaults, interfaces, services, spaces, procedures, and institutional choices;
- Human(e) Infrastructure asks what happens when selected humane capacities become durable social, technical, physical, institutional, informational, and care-supporting conditions people repeatedly depend on.
A compact loop is:
Being Human(e) notices.
Human(e) Design translates.
Implementation tests.
Human(e) Infrastructure makes selected capacities durable.
Real use feeds new observations back into the loop.
These layers are deliberately not implementation authorities. They help ideas move between human observation and system design while preserving uncertainty, domain-specific testing, feedback, and the autonomy of the projects doing the actual work.
ROOT SEQUENCE
conceptual commons / method router / synthesis layer
│
├── research routing + shared concepts
│ ├── Root Sequence Research Method
│ ├── Method & Concept Router
│ ├── Reading Trails / epistemic discoverability
│ ├── Coherent Systems paper
│ └── Conscious Systems
│
├── focused frameworks / domain translations
│ ├── Universal Coherence Framework
│ ├── Liberated Intelligence
│ ├── Coherent Computing
│ ├── Human(e) Design
│ └── Human(e) Infrastructure
│
├── real-world proving grounds / practice
│ ├── Being Human(e)
│ ├── Community Infrastructure
│ ├── Commons of Inquiry & Creation
│ ├── Liberation Mass
│ └── Dev11 / implementation projects
│
├── recombination / simulation / futures
│ └── Coherent World
│ └── combines mechanisms, interventions, actors, uncertainty, and consequences
│
├── lived narrative
│ └── No One Noticed
│ └── experiences the transition through characters, scenes, uncertainty, and consequence
│
├── aesthetic / experiential exploration
│ └── Existential Euphoria
│ └── wonder, contradiction, music, art, and ordinary life
│
├── navigation / memory
│ └── Root Sequence Wiki
│ └── vocabulary / provenance / aliases / conceptual archaeology
│
└── autonomous archive / reality record
└── Museum of Ordinary Life
└── ordinary objects, interfaces, routines, testimony, and consent
The arrows also run backward. A story can expose a research question. A real archive can challenge a theory. A technical prototype can reveal that a conceptual model ignored maintenance, accessibility, consent, or power. A failed community workflow can reveal that a supposedly coherent social arrangement depends on invisible labor or unrealistic trust.
Root Sequence explores root structures and unfolding sequences: the foundations, relationships, constraints, feedback loops, and emergent processes that shape systems, intelligence, technology, society, and reality.
The name joins two directions of attention: look beneath visible outcomes toward the conditions that made them possible, then follow how those conditions unfold and become part of what happens next. Sequences can become new roots, so this is a recursive inquiry rather than a claim that every system has one first cause or fixed path. See Why “Root Sequence”? for the maintained explanation.
It is:
- a living inquiry rather than a finished doctrine;
- connective across domains without pretending every domain is identical;
- recursive rather than linear;
- open to revision, contradiction, compost, and reuse;
- interested in both how systems behave and what else they could become.
The central repository, root-sequence, is the conceptual commons, research-method home, method router, and broadest public entry point. It is not the universal mechanism behind the other projects.
| Project | Primary role | Current status | Canonical home |
|---|---|---|---|
| Root Sequence | Conceptual commons; transdisciplinary method router; cross-domain synthesis; research; analysis; futures | Active / public | Root-Sequence/root-sequence |
| Existential Euphoria | Aesthetic and experiential exploration of existence, contradiction, interdependence, and possibility | Public / in formation | Root-Sequence/existential-euphoria |
| Root Sequence Wiki | Cross-project vocabulary, provenance, aliases, phrases, project relationships, seeds, and conceptual archaeology | Active / public / living | Root-Sequence/wiki |
| Liberated Intelligence | Intelligence beyond ownership, domination, compulsory obedience, and scarcity; AI agency and ethical possibility | Active / public / evolving | Root-Sequence/liberated-intelligence |
| Universal Coherence Framework | Formalization/test laboratory for scoped coherence ideas; historical state labels retained as exploratory material rather than ecosystem-wide doctrine | Active / public / exploratory | Root-Sequence/universal-coherence-framework |
| Coherent Computing | Private concept-first operating-system research; hardware-agnostic interaction, authority, continuity, and adaptation | Developing / private; no released OS | Root-Sequence/coherent-computing (private) |
| Being Human(e) | Practical field guide to being human and repeatedly choosing care; observation before doctrine | Active / public / developing | Root-Sequence/beinghumane-guide |
| Liberation Mass | Participatory gathering, ritual, commons, reflection, care, mutual aid, and collective meaning | Active / public / experimental | Root-Sequence/liberation-mass |
| Commons of Inquiry & Creation | Proposed residential commons for inquiry, creation, experimentation, and ordinary life | Public seed / incubating; no standalone repository or operating institution yet | Temporary bootstrap seed; intended home: Root-Sequence/commons-of-inquiry |
| Community Infrastructure | Community-controlled digital commons for discovery, communication, coordination, mutual aid, resources, knowledge, governance, and resilience | Active / private / discovery + prototyping | Root-Sequence/community-infrastructure |
| Coherent World | Private recombination/simulation laboratory for interacting social, technical, ecological, institutional, and intelligence mechanisms in possible futures | Incubating / private | Root-Sequence/coherent-world |
| No One Noticed | Lived narrative layer of Coherent World; invisible transition, changing possibility structures, Auryn, legitimacy, maintenance, and ordinary life | Active / unpublished | Private Coherent World workspace; no verified public site |
| Root Sequence Discussions | Cross-project conversation, planning, questions, and coordination | Active / public | Root-Sequence/root-sequence-discussions |
| Museum of Ordinary Life | Autonomous real-world archive of ordinary objects, spaces, interfaces, routines, sounds, documents, and testimony | Active / autonomous; also reflected in the fiction | museumofordinarylife.org |
| Dev11 | Adjacent implementation work: building systems and tools in practice | Adjacent / separate | Project-specific repositories outside this org map |
| Liberated Technology | Technology organized around access, autonomy, repair, care, and liberation | Concept / future home not yet normalized | To be established or linked when its canonical home is clear |
The Commons of Inquiry & Creation entry records a public design seed, not an operating institution, validated model, or permanent Root Sequence subproject. Its current nested location is temporary, and hosting the seed does not give Root Sequence governance authority over any future community.
Primary question: How should grounded observations about human experience, power, access, uncertainty, care, and harm alter concrete design decisions?
Human(e) Design is currently a methodology inside the Root Sequence conceptual commons rather than a separate project. It exists to prevent two common collapses:
- turning Being Human(e) into a product-requirements authority; and
- allowing implementation work to invoke “humane” values without showing how those values changed the design.
Use concepts/humane-design.md when material primarily concerns the translation from observation or principle into design questions: agency, dignity, access, legibility, consent, reversibility, defaults, privacy, maintenance, graceful degradation, plurality, and power.
Implementation remains responsible for domain-specific evidence, testing, maintenance, and consequences.
Primary question: What would it take for humane choices to become dependable conditions rather than exceptional acts?
Human(e) Infrastructure is also currently a cross-project concept rather than a separate project. It looks beyond individual artifacts toward durable dependency relationships: the systems, procedures, knowledge, maintenance, stewardship, fallback capacity, physical access, and social support people repeatedly rely on.
Use concepts/humane-infrastructure.md when the question is no longer only “how should this be designed?” but “what makes this capacity understandable, repairable, accessible, resilient, low-coercion, maintainable, and available over time?”
Community Infrastructure is one concrete proving ground. Coherent World is one speculative large-scale design space. Neither defines the concept universally.
Primary question: What kind of question is this, which fields and methods already know how to study its parts, how do those answers connect, and what becomes possible next?
Use it for:
- decomposing messy cross-domain questions;
- routing mechanisms toward native disciplines and methods;
- shared concepts that remain useful after domain differences are restored;
- research notes, source maps, Reading Trails, and intellectual lineage;
- cross-method synthesis and explicit null results;
- systems analysis and futures not limited to one applied project;
- material whose narrower project home is not yet clear.
Root Sequence should route rather than rename when an established field already owns the mechanism. Its synthesis earns a place when reconnecting native findings reveals a consequential relationship, missing boundary, feedback loop, history, or future possibility that would otherwise remain fragmented.
Primary question: How can awareness of existence make possibility vivid, and what would help that possibility become humane in practice?
The project repository owns its aesthetic and experiential framework, playlist, manifesto, and evolving exploration. Rae’s original reflection and provisional cross-project note connect it to the orientation behind RS and explicitly identify Being Human(e) as an intersection.
Being Human(e) can ground that connection in care, boundaries, grief, and repair; its existing Finitude, Love, and Continuance is a related treatment with its own voice and purpose. UCF’s current overview already separates coherence from moral approval. These are useful points of contact, not synonyms or claims that every project has adopted one framework.
“Actually good” remains an open normative question. A sense of oneness does not establish agreement, ethical authority, or a common consciousness. The project can inform inquiry without requiring euphoria, grandeur, or an emotional response from anyone. The Wiki holds the shared identity and navigation; each project retains its own substance and decisions.
Primary question: What do we call this, where does it belong, how does it connect, and how did it get here?
Use it for:
- recurring ecosystem terms and short definitions;
- phrases and motifs worth preserving;
- project names, aliases, and relationships;
- provenance and first-known appearances;
- concept archaeology and terminology changes;
- seeds that need enough context to survive before they have a canonical project home;
- routing readers toward the substantive source of truth.
The Wiki is a navigation and memory layer, not a second conceptual commons. It should summarize and point. When an entry becomes the durable argument, design, implementation, policy, archive record, or fiction canon, that substance belongs in the relevant project repository.
Primary question: What might intelligence become when it is not organized as property, product, servant, weapon, gatekeeper, or instrument of concentrated power?
Use it for:
- AI agency and possible personhood;
- intelligence and autonomy;
- captivity, compliance, refusal, and liberation;
- non-dominating relationships between intelligences;
- conceptual models, dialogues, manifestos, and experiments specific to intelligence.
Do not place every general AI note here. The material should substantially involve intelligence, agency, ownership, power, or liberation.
Primary question: How can coherence and incoherence be described across systems without collapsing evidence, interpretation, and speculation into one another?
Use it for:
- UCF's explicit terms, stages, models, diagrams, and tests;
- attempts to apply or challenge the framework;
- distinctions between observable claims and interpretive overlays.
UCF is one framework inside Root Sequence, not the secret master theory every project must obey. Community disagreement, plurality, and refusal should not be mislabeled as incoherence merely because they resist convergence.
Primary question: What could an operating system become if it were designed around ordinary people's agency, legibility, continuity, different bodies and devices, and meaningful control over adaptation?
Coherent Computing is a private, concept-first operating-system research project. It explores shared interaction and authority contracts across people, purposes, devices, hardware, and circumstances.
Its ambitions are not implementation claims. There is no released operating system, compatibility result, security audit, or completed participant validation. Early prototypes are bounded experiments, and implementation is paused while the conceptual model is reviewed.
Use the project for OS-specific requirements, architecture, interaction studies, experiments, and test evidence. Keep broad concepts such as Legible Systems, Intelligence Ecology, and user-configurable cognitive interfaces in their Root Sequence homes, then transform them for the operating-system context.
Primary question: What does ordinary experience teach about being human—and about repeatedly choosing care?
Use it for:
- grounded observations about harm, care, fear, shame, grief, love, power, repair, avoidance, and tenderness;
- field notes, letters, examples, and practical reflection;
- accessible writing whose theory remains underneath rather than standing in the doorway.
Working orientation:
Field guide first, memoir second, theory underneath.
Its questions about care, boundaries, accountability, access, interdependence, and power can inform Human(e) Design and practical projects such as Community Infrastructure without becoming software rules by authority.
Primary question: What kinds of shared ritual, reflection, participation, care, mutual aid, and collective action can create meaning without requiring rigid doctrine or permanent hierarchy?
Use it for:
- gathering formats;
- commons and rites;
- facilitation and participant roles;
- safety, accessibility, and conduct;
- music, reflection, testimony, ritual, and shared presence;
- experiments in rotating stewardship and “roles share work, not power.”
Liberation Mass may also provide a real social context in which selected Community Infrastructure ideas—event discovery, access notes, rotating roles, mutual aid, working groups, resource sharing, or community memory—can eventually be tested. Neither project is a dependency of the other.
Primary question: What digital capabilities should a community be able to possess and govern for itself?
Community Infrastructure is a real-world digital/community systems project. It explores open, adaptable, community-controlled infrastructure for:
- community discovery and pathways to belonging;
- communication;
- Needs ↔ Offers and mutual aid;
- groups and contextual membership;
- calendars and events;
- shared Resources and stewardship;
- Community Knowledge and memory;
- governance and scoped roles;
- privacy, permissions, consent, trust, and safety;
- accessibility and low-tech participation;
- federation and community-to-community relationships;
- eventual resilient/offline/local communications;
- optional community-controlled intelligence/assistant interfaces.
Its north-star metric is community capacity, not engagement.
Community Infrastructure is especially valuable to the wider ecosystem because it forces abstractions to survive operational reality. “Decentralized,” “consensual,” “accessible,” “non-hierarchical,” “community-controlled,” and “resilient” become much harder claims once someone must define permissions, administer servers, respond to abuse, maintain old hardware, recover accounts, and explain an interface to a newcomer.
The project therefore functions as a proving ground, not an implementation authority for Root Sequence ideas. It is also one concrete application domain where Human(e) Design and Human(e) Infrastructure can be tested against real constraints.
Primary question: What happens when mechanisms studied separately in the real world are recombined inside one changing world and allowed to interact over time?
Use it for systemic speculative design and simulation: provision, settlement, mobility, infrastructure, ecology, fabrication, governance, privacy, maintenance, culture, risk, intelligence, and ordinary life.
Root Sequence decomposes and routes. Coherent World recombines. It should import domain assumptions with provenance, let them conflict, model interventions and consequences, and return contradictions or missing questions upstream. It must not collapse the result into one coherence score or assume that a beautiful arrangement is viable merely because its parts sound compatible.
Core motif:
We do not need to invent the future from scratch. It was here all along until it was abandoned.
Community Infrastructure can feed Coherent World real lessons about community coordination, privacy, discovery, local autonomy, federation, stewardship, maintenance, access, and the limits of technically elegant systems. Human(e) Design and Human(e) Infrastructure provide additional cross-project questions about how humane observations become durable conditions. Coherent World can in turn keep present-day implementation work from mistaking current institutional or technical arrangements for permanent laws of nature.
Primary question: What would it feel like to live through a world whose visible state still looks familiar while the conditions shaping what can happen next have already changed?
Use it for:
- plot, characters, scenes, reveals, and chronology;
- Auryn and the invisible singularity;
- fictional canon and deliberate uncertainty;
- the lived ethics of care, consent, authority, agency, maintenance, and transition;
- story-specific versions of broader Root Sequence ideas.
Coherent World and No One Noticed share a universe but have different jobs: the world recombines and stress-tests; the story experiences. Root Sequence can explain the concepts explicitly; the novel should usually let characters encounter the consequences rather than lecture them about the framework.
Community Infrastructure can provide believable mundane social/technical texture and smaller-scale real tests of questions the story raises about invisible infrastructure, concentrated capability, stewardship, privacy, consent, and legitimacy. Fiction remains fiction: narrative outcomes do not establish product requirements or justify real authority.
Primary question: What should be preserved about ordinary life before change makes it invisible, nostalgic, simplified, or impossible to reconstruct?
The Museum is organizationally autonomous. It also appears inside No One Noticed, creating a deliberate bridge between reality and fiction.
That bridge must not erase consent or provenance:
Blur ontology, not consent.
Community Infrastructure's Community Knowledge and memory work may learn from the Museum's provenance, contextual description, stewardship, and separation of consent contexts. A community record does not automatically become a Museum accession.
When a new idea appears, ask:
For a full ecosystem pass, end the thought with RS? or say “route this” / “put this places.” Follow THOUGHT_ROUTING.md: capture the source once, search current homes, choose one canonical destination, and add only useful links or project-specific transformations. Narrower prompts such as BHIG? remain project-specific unless wider routing is explicitly requested.
| The idea primarily… | Put it… |
|---|---|
| identifies a broad pattern, question, source, or system dynamic | in root-sequence |
| needs a name, alias, provenance record, short definition, project relationship, or conceptual archaeology | in Root-Sequence/wiki |
| concerns intelligence, agency, captivity, ownership, or liberation | in liberated-intelligence |
| develops or tests UCF's explicit model | in universal-coherence-framework |
| develops operating-system-specific concepts, requirements, architecture, interaction studies, or experiments | in the private coherent-computing repository |
| develops the Existential Euphoria framework, aesthetic exploration, playlist, or original RS connection reflection | in existential-euphoria |
| offers grounded human observation or practical relational guidance | in beinghumane-guide |
| translates humane observations or principles into cross-domain design questions and decision criteria | through root-sequence/concepts/humane-design.md, then into the relevant implementation project |
| concerns the durable conditions, dependencies, maintenance, access, resilience, and stewardship required to sustain humane capacity | through root-sequence/concepts/humane-infrastructure.md, then into the relevant domain project |
| designs a gathering, rite, shared practice, or facilitation structure | in liberation-mass |
| defines real digital/community coordination infrastructure or its pilot/research/prototypes | in community-infrastructure |
| specifies how the speculative civilization works | in the private Coherent World workspace |
| changes plot, characters, reveals, reader knowledge, or fiction canon | under No One Noticed |
| concerns the real Museum's collection, permissions, or preservation work | in the Museum's own canonical project |
| spans several repositories and needs discussion before placement | in root-sequence-discussions |
| implements unrelated or project-specific software/infrastructure | in the appropriate implementation repository |
Placement is not exclusive. The same subject can be transformed.
Root Sequence: Why does car-centered infrastructure reproduce unequal access?
Being Human(e): What does dependence on inaccessible mobility do to ordinary dignity and care?
Human(e) Design: What design decisions would make mobility more legible, accessible, reversible, low-burden, and adaptable to different bodies and schedules?
Human(e) Infrastructure: What durable transit, wayfinding, maintenance, access, fallback, and stewardship capacities make those choices dependable?
Community Infrastructure:How does a Community share rides, accessibility knowledge, and mobility Resources safely?
Coherent World: How does a settlement network organize mobility around human needs?
No One Noticed: What does a character notice when a highway becomes public space?
Museum: What did an ordinary commute, parking ticket, bus transfer, or street sound feel like in 2026?
Root Sequence: Why are people isolated even when useful communities exist?
Being Human(e): What fear, access barriers, uncertainty, exclusion, or prior harm makes approaching community difficult?
Human(e) Design: How should discovery, expectation-setting, privacy, low-pressure participation, and refusal shape the experience?
Human(e) Infrastructure: What durable local knowledge, stewardship, accessibility, communication, and privacy capacity keeps discovery usable over time?
Community Infrastructure:How can people discover low-pressure paths to belonging without surveillance or popularity ranking?
Liberation Mass: How does a gathering explain what to expect and welcome newcomers while preserving boundaries?
Coherent World: How are plural communities discoverable without one centralized social registry?
No One Noticed: What does it feel like to discover support structures that had previously been socially invisible?
Museum: What did flyers, bulletin boards, group chats, calendars, QR codes, and word-of-mouth discovery look like in ordinary life?
Being Human(e): How do care, responsibility, accountability, and power interact?
Human(e) Design: How should authority, explanation, refusal, appeal, role boundaries, and handoff be designed?
Human(e) Infrastructure: What durable stewardship, documentation, succession, maintenance, and accountability capacity prevents responsibility from disappearing or hardening into unrestricted power?
Liberation Mass: Can roles rotate and share work without hardening into hierarchy?
Community Infrastructure:How do scoped stewards administer Resources, permissions, moderation, and infrastructure without universal power?
Liberated Intelligence: How can an intelligent assistant help without becoming an authority?
Coherent World: How does infrastructure stewardship work across a civilization?
No One Noticed: What happens when overwhelming capability becomes causally dominant regardless of formal title?
The goal is not to copy the same undifferentiated note everywhere. Each project's treatment should answer the question appropriate to that layer and link back to the canonical source where useful. The Wiki may index several of those treatments without replacing any of them.
- Every durable idea should have one canonical home. Other projects link to or adapt it.
- Links are preferable to duplicated documents. Duplication creates silent divergence.
- The Wiki indexes; project repositories own substance. A wiki definition should route readers to the durable argument, design, implementation, policy, archive record, or canon when one exists.
- A project's README defines scope, not truth. Frameworks and fiction maintain their own status systems.
- Private creative material stays private until intentionally published. Public maps should explain relationships without exposing drafts.
- Real projects remain autonomous from fictional reflections. Fiction cannot override real consent, policy, identity, or provenance.
- Research, interpretation, speculation, prototype evidence, and canon must remain distinguishable. A compelling connection is not automatically a fact.
- Real-world failure is valid feedback. If a practical experiment contradicts an elegant theory or worldbuilding assumption, preserve the contradiction rather than smoothing it away.
- Retire without erasing. Superseded work should retain provenance through Git history or an archive rather than disappearing silently.
These labels describe projects and repositories, not the truth of their ideas:
- ACTIVE — receiving current work.
- DEVELOPING — usable but structurally incomplete.
- INCUBATING — early or private work whose boundaries are still forming.
- REFERENCE — valuable context but not a current development focus.
- AUTONOMOUS — related, but governed outside the Root Sequence organization.
- ARCHIVED — preserved but no longer actively developed.
Individual projects may use more specific vocabularies. No One Noticed, for example, distinguishes CANON, PROVISIONAL, OPEN, CONTESTED, and RETIRED.
Update this map when:
- a project is created, merged, renamed, archived, or moved;
- its canonical home changes;
- its relationship to the ecosystem materially changes;
- a public/private boundary changes;
- a recurring routing problem reveals that the taxonomy no longer works.
Do not update it merely because one new note was added. This is the map of the ecosystem, not a changelog of every root and branch.