Current corpus

Research access for AI agents

Use this page as the human-readable contract for finding, retrieving, interpreting, and citing the public Systems Theology corpus.

Version
content-37db629f5433
Books
7
Localized chapters
573
Schema
1.2.0

What DDF means

DDF stands for Divine Design Framework. It is the book corpus's core Christian theological and interpretive architecture. It presents reality as one created order under the personal Logos, preserves the proper distinctions among fields and claim types, and tests how those realities belong together. Rethinking Reality came first; its questions helped generate DDF, which later returned to the first book as an audit and alignment architecture.

Complete Markdown in one request

Use these stable files when an agent needs a whole book without walking every chapter URL. English, Spanish, and Indonesian are separate, directly retrievable files. Chapter Markdown remains available when a smaller citation unit is better.

Where to look

Choose the surface that matches the question instead of treating every page as one undifferentiated corpus.

A curated public corpus

The corpus manifest inventories every published book localization and chapter. Each chapter has a canonical HTML page, a clean Markdown representation, stable section anchors, a content-derived version, a SHA-256 checksum, revision dates, language status, and citation metadata.

Authoritative entry points

Begin with the manifest for structured discovery. Use chapter Markdown for bounded text retrieval and canonical HTML when presenting a source to people.

Cite a specific version

Prefer the citation string in the manifest or Markdown front matter. At minimum, retain these fields so a reader can recover the exact source state:

  • author and chapter title
  • book title and canonical URL
  • content version and revision date
  • language and source-or-translation status

Bounded retrieval is welcome

Automated indexing, citation, request-scoped retrieval, and local analysis of the published V1 research package are permitted. Model training, public persistent corpus services, rehosting, and republication require separate written permission. Respect robots.txt, normal rate limits, and unchanged content versions.

Read the full Use Policy

How AI is used here

Website and localization changes may be developed with Codex in a visible, conversational workflow, but every source change remains reviewable by the Systems Theology team. The project does not use unattended prose-generation or automatic translation pipelines. Missing localized text remains missing until it receives direct editorial work.

Important boundaries

  • The manifest and published Markdown are supported machine interfaces; raw /data/books/ build files are not.
  • A status of “formal external review not completed” means the stable-release review gate remains open. It does not erase earlier informal feedback or imply that AI review is independent review.
  • Preserve the source's distinctions among direct claims, synthesis, inference, analogy, pastoral judgment, and speculation. Do not increase a claim's confidence or scope.
  • Use the correction link supplied for each chapter when reporting a source or metadata problem.