Skip to content
wiki.fftac.org

Transforming Wiki FFTAC Org Into A Concept Driven Wiki - Source Excerpt 03 - Target information architecture

Back to Transforming Wiki FFTAC Org Into A Concept Driven Wiki

Summary

This source excerpt begins near Target information architecture and preserves the surrounding evidence from Wiki.FFTAC.org/agent-file-handoff/Archive/2026-05-11-improvement-concept-layer/Transforming wiki.fftac.org into a concept-driven wiki.md.

**Source path:** Wiki.FFTAC.org/agent-file-handoff/Archive/2026-05-11-improvement-concept-layer/Transforming wiki.fftac.org into a concept-driven wiki.md

The build guide recommends linting for broken links, stale review dates, missing owners, duplicate pages, unresolved contradictions, and uncited claims. The wizard also says to run deterministic lint before scale. That should now be extended with **public-IA linting**. citeturn1view3turn13view8

Recommended new lint rules:

' ' ' text
fail if public URL matches /\/part-\d{2}\/?$/i
fail if public URL matches /\/(?:index|readme|body|theme|page)(?:-[a-f0-9]{6,})?\/?$/i
fail if page_type in {topic,site,decision,glossary,operations} and slug contains opaque hash
fail if public title matches /^(?:\d{2}\s+)?(?:Part|Index|Readme|Body|Theme|Page)\b/i
fail if public page lacks canonical_url or breadcrumb_parent
fail if topic page lacks at least one source_record
fail if source record lacks at least one derived_topic_page or source_only=true
fail if public/internal visibility conflicts with summary text such as "not public site content"
warn if anchor text matches /^(part\s+\d{1,2}|click here|read more|website|article)$/i
warn if public page has no incoming internal links
' ' ' 

These lints are directly aligned with current LlmWikis goals and with Google’s advice on descriptive URLs, descriptive anchor text, and internal links to important pages. citeturn24view0turn24view3turn23view0turn23view2

## Target information architecture

The target model should preserve the archive while giving the public site a simpler promise:

**answer-focused pages first, evidence second, raw preservation third.** This matches the current home-page boundary, preserves source authority, and aligns with LlmWikis’ own dual-audience navigation contract. citeturn1view0turn26view0

### Site hierarchy

The public hierarchy below is intentionally typed. Each top-level route answers a different kind of question.

' ' ' mermaid
flowchart TD
    ROOT["/"] --> START["/start/"]
    ROOT --> TOPICS["/topics/"]
    ROOT --> SITES["/sites/"]
    ROOT --> SOURCES["/sources/"]
    ROOT --> DECISIONS["/decisions/"]
    ROOT --> OPS["/operations/"]
    ROOT --> GLOSSARY["/glossary/"]
    ROOT --> MIGRATIONS["/migrations/"]
    ROOT --> SEARCH["/search/"]
    ROOT --> AGENTS["/for-ai-agents/"]

    TOPICS --> T1["/topics/antichrist/"]
    TOPICS --> T2["/topics/protocol5/"]
    T1 --> T1A["/topics/antichrist/books/"]
    T1 --> T1B["/topics/antichrist/legends-and-mythology/"]
    T2 --> T2A["/topics/protocol5/iota-converter/"]

    SITES --> S1["/sites/fftac-org/"]
    SITES --> S2["/sites/anti-christ-org/"]
    SITES --> S3["/sites/spiralist-org/"]

    SOURCES --> SR1["/sources/fftac-org/books-on-the-antichrist/"]
    SOURCES --> SR2["/sources/spiralist-org/protocol5-iota-converter/"]

    T1A --> SR1
    T2A --> SR2
    T1A --> GLOSSARY
    T2A --> DECISIONS
' ' ' 

This design is preferable because it separates **topic intent** from **site provenance**. A page like `Books on the Antichrist` should live under `Topics`, while the source evidence behind it should live under `Sources`, and the site that originally supplied the source should live under `Sites`. That is the cleanest way to preserve both human navigation and provenance. citeturn1view0turn8view1turn26view0turn24view0turn22view0

Recommended canonical route families:

' ' ' text
/start/

/topics/{topic}/
/topics/{topic}/{subtopic}/
/topics/{topic}/{subtopic}/{detail}/

/sites/{site}/
/sites/{site}/architecture/
/sites/{site}/operations/
/sites/{site}/sources/

/sources/{site}/{source-slug}/

/decisions/{yyyy}/{decision-slug}/
/operations/{runbook-slug}/
/glossary/{term}/
/migrations/{yyyy-mm-dd}-{slug}/
/search/
' ' ' 

### URL pattern mapping

The mapping below converts the currently observed route shapes—including hash-suffixed source pages, `part-*` pages, numeric archive-doc pages, and generic code-file pages—into typed canonical routes with clearer intent. The old examples are drawn from current pages such as `Books On The Antichrist`, the Protocol5 converter, `01 Start Here`, `02 Site Map`, and generic `Index` and `Style` source pages. citeturn8view0turn8view1turn8view3turn8view4turn11view0turn11view4

| Old pattern | Example old path | New canonical pattern | Example new path | Redirect strategy |
|---|---|---|---|---|
| Site memory hub | `/fftac-org/` | Site hub | `/sites/fftac-org/` | 301 |
| Site source-files index | `/spiralist-org/source-files/` | Site sources index | `/sites/spiralist-org/sources/` | 301 |
| Archive index | `/spiralist-org/archive/` | Archive or migrations hub | `/migrations/` or `/archive/spiralist-org/` | 301 after classification |
| Source record with hash slug | `/fftac-org/source/books-on-the-antichrist-2b793fdc/` | Source record | `/sources/fftac-org/books-on-the-antichrist/` | 301 |
| Chunk page | `/fftac-org/source/books-on-the-antichrist-2b793fdc/part-01/` | Topic hub or verified child page | `/topics/antichrist/books/` | 301 |
| Chunk page with strong section intent | `/spiralist-org/source/improving-the-protocol5-justaniota-iota-1-converter-part-2-36d293c7/part-02/` | Topic detail page | `/topics/protocol5/iota-converter/semantic-overlay/` | 301 |
| Numeric docs archive page | `/anti-christ-org/source/01-start-here-b6c2d70a/` | Site orientation page | `/sites/anti-christ-org/start/` | 301 |
| Numeric docs archive page | `/anti-christ-org/source/02-site-map-b3544d46/` | Site IA page | `/sites/anti-christ-org/information-architecture/` | 301 |
| Generic code-file page | `/anti-christ-net/source/index-77572fee/` | Developer/source record | `/sources/anti-christ-net/theme-index-php/` | 301 or noindex target |
| Generic stylesheet page | `/anti-christ-net/source/style-c77d7072/` | Developer/source record | `/sources/anti-christ-net/theme-style-css/` | 301 or noindex target |
| Duplicated preservation variant | `/sources/...hashed-variant.../` | Single canonical source record + artifact list | `/sources/{site}/{semantic-slug}/` | 301 all variants to one target |

Two nuances matter here. First, hashes should move out of canonical public URLs and into metadata such as `source_hash`, `checksum`, or `legacy_ids`. Google explicitly recommends readable words over long ID strings in URLs, and MediaWiki treats page names as central to linking and identity. citeturn24view0turn24view3turn22view0

Second, not every old page deserves an equally indexable new page. Some public legacy URLs currently point to internal or developer-only material. Those pages should either become **developer reference routes**, **noindex source records**, or **private/internal pages**, rather than being carried forward as general public entry pages. That is especially important where the current summary already says the page is not public site content. citeturn25view2turn26view3turn26view4

### Naming rules

The naming rules below are the minimum needed to stop the current URL and title drift.

' ' ' text
Public title rules
- Use a noun phrase that names the subject, task, decision, or site section.
- Do not begin titles with sequence numbers such as 01, 02, or 14 unless the number is semantically essential.
- Do not publish public titles that are only file roles: Index, Readme, Body, Theme, Page.
- If the source is a code file, combine component + file purpose:
  "Anti-Christ.net theme index template"
  not "Index".

Public URL rules
- Use lowercase slugs.
- Use hyphens between words.
- Use semantic words, not opaque hashes.
- Maximum public depth: 4 path segments after the domain for canonical pages.
- Keep dates only where the date is the meaning:
  `/decisions/2026/...`
  `/migrations/2026-05-10-...`
- Keep source-site provenance in `/sources/` and `/sites/`, not in `/topics/`.
- Never use `part-01`, `part-02`, or similar chunk counters in public canonical URLs.

Section and child-page rules
- If a section is important enough to rank or be shared, give it its own descriptive child route.
- Otherwise expose it as a named anchor under the canonical page.
- Fragments are acceptable for user landing, but high-value legacy URLs should map to real child pages when the section has standalone search intent.
' ' ' 

These rules align with Google’s guidance to keep URLs simple, logical, and intelligible to humans, use readable words instead of long IDs, use audience language, and separate words with hyphens. They also align with Google’s guidance to use descriptive anchor text and ensure important pages are linked internally. citeturn24view0turn24view1turn24view3turn23view0turn23view2

### Templates and required metadata

The table below extends the current LlmWikis metadata and trust guidance into a publication-ready schema. It is intentionally explicit because the current wiki already shows that metadata about ownership, review, public indexing, and route hierarchy will not emerge reliably from source extraction alone. citeturn26view3turn26view4turn26view5turn10view5turn10view6turn10view8
Website health report