Public surface. Private engine. Receipts always.
Diverse Data Centers is a protected public project surface for a community-hosted micro data center initiative. The project explores small-footprint compute infrastructure hosted by trusted local institutions, including churches, ministry campuses, community facilities, and small Black-owned businesses, with local income or savings, community benefit, and measurable environmental return built into the operating model.
This repository is a protected public project surface. It is not the full source code, operational system, private workflow, or data room.
Data center growth is usually described from the perspective of large landholders, utilities, hyperscalers, and capital providers. Diverse Data Centers asks a different question:
What if trusted community institutions could participate in infrastructure ownership, stewardship, and benefit, instead of only living near the consequences?
The project frames data center capacity as a civic, economic, and environmental design challenge. The public materials focus on the visible mission, status, workflows, and boundaries. The private engine remains protected.
- Church and ministry leaders evaluating mission-aligned infrastructure opportunities.
- Small Black business owners evaluating revenue, resilience, space, power, and reputational fit.
- Investors and partners evaluating an early-stage infrastructure thesis.
- Community stakeholders looking for proof that the project gives back instead of extracting.
- FaithCheltenham.com readers who need a clear public project page.
flowchart LR
Public["Public project surface"] --> Host["Host readiness path"]
Host --> Review["Private review layer"]
Review --> Diligence["Protected diligence room"]
Diligence --> Reporting["Public-safe receipts"]
Reporting --> Web["FaithCheltenham.com"]
The selected first product surface is Host Readiness And Stewardship Flow. It helps a church, community facility, or small Black-owned business understand whether their site could become a host location, what requirements would be reviewed, what remains private, and how community/environmental return could be measured.
- Project purpose and thesis.
- Public workflow diagrams.
- Public-safe screenshots and visual assets.
- High-level product direction.
- Ownership, security, privacy, commercial use, and trademark policies.
- WordPress page draft for FaithCheltenham.com.
- Source code.
- Prompts and agent instructions.
- Credentials, secrets, cookies, and tokens.
- Private workflows, operational infrastructure, deployment systems, and data room materials.
- Investor/admin mechanics, protected documents, and runtime data.
- Legal, medical, benefits, family, customer, and unpublished creative records.
Status: public surface prepared; private engine protected.
The private working project is a Next.js investor MVP with public pages, a gated investor room, admin operations, local JSON-backed demo persistence, and a Supabase-ready future schema. Public development is transitioning to a Fantasia-first workflow.
More detail lives in docs/WORKFLOW_DIAGRAMS.md.
- Project brief: docs/PROJECT_BRIEF.md
- Status: docs/STATUS.md
- Public/private boundary: docs/PUBLIC_PRIVATE_BOUNDARY.md
- WordPress page draft: wordpress/page.md
Copyright (c) Faith Cheltenham. All rights reserved.
No source release. No public license. No redistribution permission. No training permission. No commercial reuse. No implied permission.