GitHub Source
The public repo holds the current project surface, README, docs, asset inventory, and launch context that FaithCheltenham can cite.
GitHub Project Folder
AI translation project
ThankFish
Protected public project surface for ThankFish, an AI-supported translation project for underserved languages.
MermaidUpdated Jun 19, 2026Source: github.com/thefaythPublic folder
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.
Project Folder
FaithCheltenham turns that source into a public folder with a readable story, source link, and client-safe navigation.
Protected Core
Private engines, credentials, review queues, unpublished drafts, and local operator context stay out of the public route.
Guarded Publish
Assets, screenshots, workflow charts, and microsite copy can move through COAI/WordPress only after review and rollback checks.
Project Gallery
COAI visuals assigned to this project.
These public-safe bitmap assets are used as supporting gallery and process visuals, while hero slots stay focused on the strongest available image.
Project gallery - ThankFish anime hero variant
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.
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.