What this timeline adds

• It gives new readers a learning order before they open hundreds of Wiki, Tales, field-note, or fact-check records.
• It reduces repetition by turning repeated Starter/Open cards into one explanation of how open pages should be used.
• It makes the public mission visible: foundations, Muur history, ancestral memory, place-based research, community research, corrections, safe sharing, and evidence discipline.

Learning order

1. Orientation: read Start Here, About, and Introduction to Foundations / Muur History.
2. Method: read Research Method, Evidence Gates, and Source Review.
3. Place: open Place Hubs and use maps, timelines, source trails, and open questions together.
4. Archive: browse Wiki, Library, and Field Guides while checking evidence labels.
5. Community care: use Safe Sharing, Community Guidelines, Fact Check, and Corrections Log.

Why this matters for review

Search and review traffic should see the strongest public learning path first. Short open entries stay useful as source leads and navigation, but they should not appear as the main public value of the site until they are expanded.

What makes this timeline useful

• It turns a large site into a sequence a new reader can follow without opening every archive, Wiki record, and field note at once.
• It keeps trust pages close to research pages so readers understand correction, privacy, source review, and disclosure rules before making public claims.
• It gives contributors a publishing standard: a page should add method, source context, place context, claim boundaries, or safer wording.
• It makes Starter/Open entries a review status, not the main promise of the site.

How this protects depth value

Low-depth value risk grows when many pages look like short registers, repeated labels, or generic navigation. This timeline pushes the opposite behavior: fewer stronger paths, clearer reader outcomes, and more links into methods, sources, corrections, and place-based guides. A reader should understand why the route exists and what useful next step it creates.

When a future page does not add enough explanation, it should stay noindex, merge into a stronger guide, or become a source row rather than an indexable public article.

What future prompts must preserve

Future prompts should not add indexable pages that only repeat the learning order, create generic topic lists, or expose internal workflow labels. A page should either teach a method, improve a source trail, explain a place, clarify a claim boundary, protect privacy, or route a reader into correction and review. If it does not do one of those jobs, it should not become a new indexable surface.

This is the reason the timeline exists as a guide: it keeps public learning focused on depth, not volume. The site can grow, but growth should produce stronger reader paths and fewer weak crawl surfaces.

The best future use of this page is as a publishing checklist. Before a new route goes live, compare it with this sequence and ask whether it strengthens orientation, method, place, archive review, or community care. If it does not, it should be merged, held, or noindexed.

This keeps the learning path stable even when new Codex prompts add pages, routes, or visual sections.

That stability is what turns a growing archive into a coherent learning system instead of a loose collection of pages.

Non-certification rule: This learning path does not certify identity, ancestry, tribe, nationality, DNA conclusions, legal status, descent, or membership.