FC Faith Cheltenham Public home for systems, campaigns, and client-ready work
GitHub Project Folder

Community infrastructure

Diverse Data Centers

Protected public project surface for community-hosted micro data center infrastructure with public proof and a private engine.

MermaidUpdated Jun 19, 2026Source: github.com/thefaythPublic folder
Faith Cheltenham projects hero
Project Source Diverse Data Centers GitHub source Public folder Protected core
Repodiverse-data-centers LaneCommunity infrastructure UpdatedJun 19, 2026 BoundaryPublic proof, private engine
Workflow

How this project moves from source to site.

Each project folder is intentionally boring in the best way: source, route, boundary, publish checks. That lets the public site show momentum without leaking control.

01

GitHub Source

The public repo holds the current project surface, README, docs, asset inventory, and launch context that FaithCheltenham can cite.

02

Project Folder

FaithCheltenham turns that source into a public folder with a readable story, source link, and client-safe navigation.

03

Protected Core

Private engines, credentials, review queues, unpublished drafts, and local operator context stay out of the public route.

04

Guarded Publish

Assets, screenshots, workflow charts, and microsite copy can move through COAI/WordPress only after review and rollback checks.

Public Surface

What this folder is allowed to show.

  • Public repo description, README-level story, visible docs, source assets, and safe product framing.
  • Workflow diagrams, launch status, offer context, screenshots, and project navigation once reviewed.
  • Links to GitHub and approved FaithCheltenham route families.
Protected Core

What stays private.

  • Credentials, local paths, private queues, unpublished drafts, admin actions, customer data, and recovery material.
  • Operator-only automation remains behind Fantasia, COAI gates, WordPress auth, or private infrastructure.
  • Public pages can show proof without handing away the engine.