LLM Wiki Publication Architecture

wiki.fftac.org now uses a concept-first publication architecture over the existing archive. Public readers should see durable page families first, while the source archive remains available for provenance and recovery.

Route Families

Family	Use
/topics/	Concept and explanation pages.
/sites/	Site hubs and authority boundaries.
/sources/	Curated source records and source registry pages.
/decisions/	Durable architecture and editorial decisions.
/operations/	Runbooks, setup guidance, and publication checks.
/glossary/	Shared vocabulary.
/migrations/	Redirects, route cleanup, and archive-to-concept work.
/for-ai-agents/	Machine-oriented discovery and traversal rules.

Legacy memory routes such as /fftac-org/, /memory/sources/, and /transfer-log/ remain valid evidence routes, but they should not be the only public way to understand the wiki.

Canonical URL Rules

• Use lowercase, hyphenated, human-readable slugs.
• Keep concept, site, decision, operations, and glossary pages free of opaque hashes.
• Keep mechanical chunk labels out of canonical public navigation.
• Put raw source mirrors behind source records and mark low-value mirrors as archive evidence.
• Link internally to canonical pages instead of relying on redirects.

Metadata Rules

Every canonical public page should declare page_type, summary, owner_role, status, visibility, indexing, canonical_url, breadcrumb_parent, last_reviewed, review_cycle, and either related or source_records.

Discovery Rules

• /llms.txt stays compact.
• /llms-full.txt exposes page type, route, and summaries for agents.
• /sitemap.xml is a sitemap index.
• /sitemaps/{page_type}.xml exposes canonical routes by page family.
• /.well-known/wiki.fftac.org.json and the REST catalog expose the same core boundaries.