Root Sequence Wiki

A living index for the Root Sequence ecosystem: entities, terms, projects, phrases, connections, provenance, and conceptual archaeology.

The wiki is a navigation and context layer, not a replacement for project repositories.

Canonical rule: keep one canonical home for substantive work, then link to it from here. Do not create silent copies that drift apart.

One Wiki, many views

The Wiki is organized as a shared knowledge graph rather than a collection of disconnected project wikis.

Each Root Sequence project can have a generated project lens that behaves like a sub-wiki: it gathers the canonical entities, legacy terms, phrases, seeds, relationships, and canonical links relevant to that project without copying the underlying entries.

Entities are canonical once; views are generated many times.

See Wiki Architecture for the full model.

Public + private layers

Root-Sequence/wiki is the public layer of one logical Wiki.

Its private companion, Root-Sequence/wiki-private, is the private overlay for private-only entities, unpublished canon, internal project relationships, private archaeology, and additional context for entities that already exist publicly.

A private overlay reuses the same stable entity ID instead of creating a second conceptual identity. The private combined view may merge public + private knowledge; the public site consumes only this public repository.

The public build is complete without the private repository. The private build may depend on the public repository, never the reverse.

See Private Overlay for the repository contract, merge semantics, and security boundary.

Start here

  • entities/ — canonical Wiki identities with explicit metadata, relationships, provenance, and project membership.
  • Lexicon — compact index of recurring terms; migrated entries link to their canonical entity pages.
  • Phrases & motifs — lines worth preserving because they recur, clarify a project, or become conceptual tools.
  • Projects — what each project does and where its canonical work lives.
  • Live public repo registry — machine-maintained discovery of public Root-Sequence repositories.
  • Wiki Architecture — one graph, many project lenses, and the intelligence model.
  • Private Overlay — how the public and private layers share identities without leaking private content.
  • Provenance — how we record whether a term is established, adapted, Rae-coined, jointly coined, uncertain, or otherwise sourced.
  • Concept archaeology — when an idea first appeared, what it used to be called, and how it changed.
  • Seeds — fragments that are not mature enough for a canonical project home yet.
  • Automation — what updates automatically, what remains curated, and the public/private boundary.
  • Page template — lightweight metadata for new entries.

Website

The repository is configured to publish a searchable static Wiki with an automatically generated interactive knowledge graph, canonical entity pages, project lenses, backlinks, and maintenance signals.

Intended public URL: https://wiki.rootsequence.systems/

Every push to main rebuilds the site.

The generated site includes:

  • an Entities index with one canonical identity per migrated concept/motif;
  • an interactive knowledge graph that deduplicates entity-backed index entries;
  • project-specific lenses that act like sub-wikis without duplicate source files;
  • generated entity connections and backlinks;
  • a Wiki Signals view that surfaces orphaned entries, sparse project coverage, and other transparent maintenance cues;
  • a machine-maintained public repository registry;
  • ordinary search and navigation across the Wiki.

Canonical entity relationships come from explicit metadata. Legacy entries use conservative textual matching until migrated. Heuristic signals are shown as suggestions, not silently promoted into canonical relationships.

One-time GitHub Pages setup

Repository administrators must enable Settings → Pages → Build and deployment → Source: GitHub Actions once. The workflow is already committed at .github/workflows/pages.yml.

After Pages is enabled, configure wiki.rootsequence.systems as the custom domain in GitHub Pages and point the wiki DNS CNAME at root-sequence.github.io.

Automatic maintenance

Three complementary layers keep different kinds of knowledge current:

  1. GitHub-side automation refreshes AUTO_PROJECTS.md daily from public repositories only and rebuilds the site on every Wiki change.
  2. Generated structure creates entity indexes, backlinks, project lenses, graph relationships, and structural maintenance signals from the same canonical source.
  3. Conversation-side maintenance reviews recent Root Sequence work for durable new terms, aliases, phrases, project relationships, provenance evidence, entity migrations, or private overlays and updates the appropriate visibility layer conservatively when warranted.

Definitions, originality claims, private/public boundaries, and canon are intentionally not delegated to blind automation. See Automation.

The Pages workflow also runs a privacy-boundary check and fails if public CI is modified to consume the private companion repository or private merge tooling. The private repository independently validates its entities and overlays against current public IDs without publishing the combined graph.

What belongs here

The wiki is useful when the question is:

  • What do we call this?
  • Where does this idea belong?
  • Which projects use it?
  • Is this an established term or something we developed?
  • What did we call this before?
  • How did this concept change over time?
  • What connects these otherwise separate projects?
  • Which parts of the project ecosystem are under-documented or disconnected?

If the question is instead "what is the full argument/design/canon?", follow the link to its canonical repository.

Entry lifecycle

capture → seed → working index entry → canonical entity → mature / retired / composted

Not every useful phrase needs an entity page. An entry should graduate when stable identity, explicit relationships, backlinks, provenance, or cross-project reuse make the richer structure useful.

Visibility is orthogonal to maturity: an entity may be public, private-only, or publicly identified with additional private overlay context.

Relationship to existing Root Sequence navigation

This layer complements, rather than replaces:

The wiki should make those systems easier to enter, not duplicate them.

Canonical home

This repository is the canonical home of the public layer of the Root Sequence Wiki. Root-Sequence/wiki-private is the canonical private overlay. The earlier prototype under Root-Sequence/root-sequence/wiki/ was migrated here on 2026-09-05.