Transforming Wiki FFTAC Org Into A Concept Driven Wiki - Source Excerpt 04 - Books on the Antichrist

Back to Transforming Wiki FFTAC Org Into A Concept Driven Wiki

Summary

This source excerpt begins near Books on the Antichrist 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

| Template | URL pattern | Required frontmatter | Required body blocks | Indexing default |
|---|---|---|---|---|
| Topic / concept page | `/topics/{topic}/{subtopic}/` | `title`, `slug`, `page_type`, `summary`, `owner_role`, `status`, `visibility`, `indexing`, `canonical_url`, `breadcrumb_parent`, `last_reviewed`, `review_cycle`, `source_records`, `related` | One-sentence answer, context, key sections, evidence, related pages, change note | `index` |
| Site hub | `/sites/{site}/` | `title`, `site_slug`, `page_type`, `summary`, `owner_role`, `status`, `visibility`, `indexing`, `canonical_url`, `breadcrumb_parent`, `last_reviewed`, `review_cycle`, `related_topics`, `source_indexes` | What this site is, what is authoritative, key topics, operations, sources, open questions | `index` |
| Source record | `/sources/{site}/{source-slug}/` | `title`, `page_type`, `source_site`, `source_path`, `memory_type`, `source_hash`, `checksum`, `summary`, `visibility`, `indexing`, `canonical_url`, `last_reviewed`, `headings_map`, `derived_topic_pages` or `source_only` | Summary, provenance, heading map, related topic pages, raw artifact list, notes | `index` for curated prose sources; `noindex` for low-value code/raw/source mirrors |
| Decision / runbook | `/decisions/{yyyy}/{slug}/` or `/operations/{slug}/` | `title`, `page_type`, `summary`, `owner_role`, `status`, `visibility`, `indexing`, `canonical_url`, `breadcrumb_parent`, `effective_date`, `last_reviewed`, `review_cycle`, `related`, `source_records` | Decision or task, rationale, scope, constraints, evidence, supersedes / superseded by | `index` for public-safe pages; otherwise `noindex` or private |
| Glossary / entity page | `/glossary/{term}/` | `title`, `slug`, `page_type`, `summary`, `owner_role`, `status`, `visibility`, `indexing`, `canonical_url`, `breadcrumb_parent`, `last_reviewed`, `review_cycle`, `aliases`, `related`, `source_records` | Definition, usage notes, related topics, evidence | `index` |

A canonical topic page can extend the headings already present on the current `Books On The Antichrist` source page. citeturn8view1

' ' ' yaml
---
title: Books on the Antichrist
slug: books-on-the-antichrist
page_type: topic
summary: Curated reading paths, core scholarly works, and source-backed notes on Antichrist literature.
owner_role: Editorial Lead
status: reviewed
visibility: public
indexing: index
canonical_url: https://wiki.fftac.org/topics/antichrist/books/
breadcrumb_parent:
  - /topics/
  - /topics/antichrist/
last_reviewed: 2026-05-11
review_cycle: quarterly
source_records:
  - /sources/fftac-org/books-on-the-antichrist/
related:
  - /topics/antichrist/legends-and-mythology/
  - /glossary/antichrist/
aliases:
  - antichrist reading guide
  - antichrist bibliography
---

# Books on the Antichrist

Antichrist studies has a few strong starting points and several distinct reading paths.

## Start here

Explain the fastest way to get oriented.

## Historical frame and timeline

Summarize the historical development of the concept.

## Scholarly and theological works

List and compare the main works.

## Fiction and popular culture

Separate this clearly from the scholarly lane.

## Evidence

Source record: /sources/fftac-org/books-on-the-antichrist/

## Related pages

- /topics/antichrist/legends-and-mythology/
- /glossary/antichrist/
' ' ' 

A source record for the same material should keep provenance, not compete with the topic page for public identity. citeturn10view6turn8view1

' ' ' yaml
---
title: Books on the Antichrist source record
slug: books-on-the-antichrist
page_type: source-record
source_site: fftac-org
source_path: FFTAC/agent-file-handoff/Archive/2026-05-11-antichrist-resource-hub/Books on the Antichrist.md
memory_type: archived-file-handoff
source_hash: 2b793fdc
summary: Preserved source file behind the public topic page on Antichrist literature.
owner_role: Wiki Maintainer
status: reviewed
visibility: public
indexing: index
canonical_url: https://wiki.fftac.org/sources/fftac-org/books-on-the-antichrist/
last_reviewed: 2026-05-11
review_cycle: yearly
headings_map:
  - executive-summary
  - historical-frame-and-timeline
  - comparative-table-of-top-titles
  - scholarly-and-theological-works
  - primary-sources-and-major-commentaries
  - fiction-and-popular-culture
  - debates-articles-and-ranked-reading-paths
derived_topic_pages:
  - /topics/antichrist/books/
legacy_ids:
  - books-on-the-antichrist-2b793fdc
---

# Books on the Antichrist source record

This page preserves provenance and headings for the source file.
Use the topic page for public reading flow.
' ' ' 

### Navigation, breadcrumbs, and sitemap strategy

The top-level public navigation should become:

' ' ' text
Start | Topics | Sites | Sources | Decisions | Operations | Glossary | Migrations | Search | For AI Agents
' ' ' 

That keeps LlmWikis’ dual audience intact. Agent-facing routes such as `index.md`, `log.md`, `wiki-links`, and `llms.txt` should remain, but they should no longer be the only navigational logic exposed to humans. citeturn26view0turn1view0

Every canonical public page should have both visible breadcrumbs and `BreadcrumbList` structured data. Google describes breadcrumbs as indicators of a page’s position in the site hierarchy and says they can help users understand and explore a site effectively. citeturn22view3

Sitemaps should be segmented by page type:

' ' ' text
/sitemap.xml                 sitemap index
/sitemaps/topics.xml
/sitemaps/sites.xml
/sitemaps/sources.xml
/sitemaps/decisions.xml
/sitemaps/operations.xml
/sitemaps/glossary.xml
/sitemaps/migrations.xml
' ' ' 

Those sitemaps should include only canonical public URLs, not raw chunks, duplicate hash variants, or low-value source mirrors. Google explicitly recommends using sitemaps to supply preferred canonical URLs and notes that Search Console can report sitemap access and processing errors. citeturn22view4turn22view7

## Migration plan

The migration should preserve both archive value and search value. Google’s site-move and redirect documentation is clear that URL changes should be planned to minimize negative impact, and its canonical guidance says internal links should point to the chosen canonical URL. That means the migration must be treated as a route-mapping project, not merely a rename project. citeturn22view5turn22view6turn23view4

### Migration flow

' ' ' mermaid
flowchart LR
    A[Export current URL inventory] --> B[Classify each page by type and visibility]
    B --> C[Choose canonical destination]
    C --> D[Create topic, site, source, or decision page]
    D --> E[Attach provenance and heading map]
    E --> F[Write explicit old-to-new redirect map]
    F --> G[Deploy 301 redirects]
    G --> H[Update internal links and anchor text]
    H --> I[Add canonicals, breadcrumbs, and sitemaps]
    I --> J[Validate with crawl + Search Console + logs]
' ' ' 

### Detailed migration steps

First, export a complete URL inventory from the current public route families. The crawl map, all-sources index, and per-site source-file indexes already expose the major route families that must be inventoried. Build a spreadsheet or JSON map with columns for current path, current title, site relevance, memory type, visibility assessment, target page type, target canonical path, and redirect status. citeturn3view2turn3view3turn6view0turn6view1turn6view2turn6view3

Second, classify each current page as one of the new page types: topic, site hub, source record, decision, operations, glossary, migration record, developer reference, or raw chunk. This is the step that the current publication model effectively skips. It is also the point where current internal-only docs such as `Launch Runbook` or `User Ai Architecture` should be marked `internal` or `noindex`, not merely renamed. citeturn25view2turn26view3turn26view4

Third, create normalized source-record pages for current source material. A current page like `Books On The Antichrist` should become a cleaned source record under `/sources/fftac-org/books-on-the-antichrist/`, while the public reading path moves to `/topics/antichrist/books/`. A page like `01 Start Here` should become a site-oriented page such as `/sites/anti-christ-org/start/`, not remain an archive-title page under `/source/`. citeturn10view6turn10view8

Fourth, convert `part-*` URLs in two passes. The immediate pass should redirect each chunk URL to the closest safe canonical page, usually the parent topic page or source record. The editorial pass should refine those redirects to section or child-page destinations once heading-level mapping is verified. This two-pass approach matters because the current chunk boundaries do not always line up with single headings, as seen in the Protocol5 source. citeturn9view0turn9view1