Start Here — Root Sequence Wiki¶

TC;DP: The Wiki helps answer “What is this called, where does it belong, how is it connected, and where is the real work?”

For a comprehensive working briefing, continue to PROJECT-CONTEXT.md.

In one sentence¶

The Root Sequence Wiki is the public navigation, vocabulary, provenance, and conceptual-memory layer for the ecosystem.

If you remember only three things¶

1. The Wiki points to substantive work; it does not replace the repositories that own it.
2. Public content must stand on its own and never depend on the private overlay.
3. A short definition should preserve status, provenance, ambiguity, and the canonical destination when those matter.

Current reality¶

The repository contains a public knowledge graph, site, lexicon, phrases, project records, entity pages, and tools for validation and private-overlay merging. It is a map, not a universal encyclopedia, second conceptual commons, fiction canon, or automatic publication channel for private material.

The smallest useful map¶

• entities/ — public entities with stable identities and relationships.
• LEXICON.md and PHRASES.md — navigable vocabulary and recurring language.
• PROJECTS.md — curated project meaning and relationships.
• PROJECT_CONTEXTS.md — rollout-aware links to merged repository briefings.
• AUTO_PROJECTS.md — machine-maintained public repository discovery.
• ARCHITECTURE.md — data and site architecture.
• PRIVATE_OVERLAY.md — how private context extends the public base without leaking into it.

Where it fits¶

Root Sequence and its sibling projects own arguments, designs, implementations, practices, research, and stories. The Wiki keeps those homes findable and records enough history to prevent names and relationships from becoming dependent on memory.

What to do next¶

• Looking something up: search the entities, lexicon, phrases, or projects.
• Adding an entry: keep it concise, record provenance, and link to the canonical source.
• Writing the substantive treatment: put it in the owning project and let the Wiki point there.
• Handling private knowledge: use wiki-private; publication into the public Wiki is an explicit decision.

Go deeper¶

Read the full README, Project Context Index, and Wiki Architecture. If an entry becomes the argument itself, it has probably outgrown the Wiki.