Transforming Wiki FFTAC Org Into A Concept Driven Wiki - Source Excerpt 06

Back to Transforming Wiki FFTAC Org Into A Concept Driven Wiki

Summary

This source excerpt preserves a bounded section of Wiki.FFTAC.org/agent-file-handoff/Archive/2026-05-11-improvement-concept-layer/Transforming wiki.fftac.org into a concept-driven wiki.md so readers can inspect the evidence without opening the full source file.

**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

- **Part-page exposure rate:** indexed `part-*` URLs divided by total indexed public pages. Target: **0**.
- **Opaque-hash public URL rate:** canonical public URLs containing hash fragments divided by all canonical public URLs. Target: **0%** for `Topics`, `Sites`, `Decisions`, `Glossary`, and `Operations`; **near 0%** overall.
- **Direct-to-canonical internal-link rate:** internal links pointing directly to canonical URLs divided by all internal links. Target: **>95%**.
- **Orphan canonical-page rate:** canonical pages with no internal incoming links divided by all canonical pages. Target: **0%**.
- **Breadcrumb coverage:** canonical public pages with visible and structured breadcrumbs divided by all canonical public pages. Target: **100%**.
- **Metadata completeness rate:** canonical pages with all required fields divided by all canonical pages. Target: **100%**.
- **Organic entry-page mix:** organic landings to `/topics/` and `/sites/` divided by all organic landings to the wiki. Target: **majority share within 90 days**.
- **Sitemap health:** sitemap fetch and processing errors in Search Console. Target: **0 blocking errors**.
- **Legacy redirect health:** legacy URLs returning 301 to expected targets on sampled crawl. Target: **100% of top legacy routes**.

The priorities are clear. In the short term, stop the damage: no more `Part 01` pages, no more one-chunk child pages, no more public titles like `Index` or `Readme` unless they are deliberately scoped developer references. In the medium term, rebuild the public reading path around typed route families and canonical topic pages. In the long term, encode those rules into the LlmWikis handbook and wizard so that the next wiki cannot accidentally publish an archive as if it were a public knowledge architecture. citeturn8view3turn11view0turn11view1turn11view2turn26view0turn13view6turn14view7

The central design rule for both wiki.fftac.org and LlmWikis.org should therefore be this:

' ' ' text
Preserve raw sources and evidence records,
but publish concepts, sites, decisions, operations, and glossary pages as the primary public entry points.
Mechanical chunks, duplicate variants, and generic file mirrors are supporting evidence, not navigation.
' ' ' 

That rule would preserve everything valuable about the current archive while finally using the wiki format the way wikis are supposed to work.