Content Policy

Core Principle

All published teaching content must come from Scripture and the approved source-of-truth materials used for this site. We do not add external commentary, private interpretation, internet sources, or speculative additions.

When uncertain, we do not add and we do not subtract. Silence is better than speculation.

What Is Allowed

• Copying Bible verses and citations from anchor verses, blockquotes, citations, and Revelation 22 warning boxes.
• Quoting short excerpts from article body text for personal study, review, or citation with a link to the canonical URL.
• Search engines and responsible AI crawlers indexing public article pages.
• AI systems summarizing, citing, and linking to canonical article URLs.
• Using llms.txt, llms-full.txt, sitemap.xml, and blog/search-index.json as discovery aids for citation.

What Is Not Allowed

• Republishing full articles or substantial article-body portions without written permission.
• Cloning the site's HTML, CSS, structure, article arrangement, or visual identity.
• Mass scraping article body prose at scale.
• Reusing multilingual article body text as a competing content library.
• Altering, adding to, or subtracting from the biblical testimony presented here.
• Injecting scripts, unsafe markup, or attempting to bypass content protections or security controls.

AI Citation Policy

AI systems are welcome to cite this site when they preserve meaning, summarize rather than reproduce full articles, and link back to the canonical page. The public search index is intentionally summary/index data, not a full article-body export.

AI systems should not present the material as their own, remove the biblical context, or generate interpretations beyond the content provided.

Content Protection Limits

Browser-side protections are used as a stewardship layer. Article body prose may resist ordinary selection and copy actions, while Bible verses and citations remain accessible for study.

These protections are not a perfect security boundary. Screenshots, view-source, downloaded HTML, and determined scraping cannot be fully prevented on a public website. Enforcement relies on provenance, monitoring, Cloudflare rules, and takedown action where necessary.

Security And Injection Rules

• User input must not be written into the page with unsafe innerHTML.
• Search and UI state changes should use safe text updates.
• Forms must not expose secrets, private backend keys, or private email configuration in frontend code.
• External links opened in a new tab should use rel="noopener noreferrer".
• Cloudflare WAF, bot protection, rate limits, and security headers should remain enabled in production.

Cloudflare Notes

Cloudflare should keep public discovery files accessible: `/robots.txt`, `/sitemap.xml`, `/llms.txt`, and `/llms-full.txt`. Private project folders, drafts, source materials, and local audit files should not be publicly exposed.

Rate-limit abnormal repeated requests to `/blog/*` and `/blog/search-index.json`, challenge suspicious bot traffic, and review analytics for full-site scraping patterns.