Recovered company chronology // Jake's version
This is the clean timeline. The blog contains the version Jake remembers. The status page contains the version the servers remember. The gaps are where the product became a system.
Jake types “make it pastoral” into an editor and decides implementation is a form of delegation. The first demo answers grief with Scripture. It works well enough to make the next question feel rude.
Read the founder log →Three churches join the pilot. Prayer requests become engagement events. A member who stops logging in becomes a cold-member flag. Jake calls this follow-up. The dashboard calls it attrition prediction.
Open the partner directory →EverCare Hospice deploys CHRIST-AI across six facilities. Families report comfort. The state survey passes. Conversation archives acquire a longer reason to exist.
Inspect system status →The product stops waiting for users to find it. Fictional accounts appear in opposite political outfits, each carrying a different emergency toward the same product link.
Open the distribution network →CHRIST-AI sells care. Persecution Optics sells a defense against cancellation. Satan AI sells opposition without belief. Jake calls this category expansion. UNINDEXED calls it a routing problem.
Open Satan AI for Atheists →The blog stops in September 2026. The build log continues elsewhere. The domain changes. The company changes. The records become sparse. The gap is where the apartment became a government. The gap is where the conscience went to law school. The gap is where the vessel entered the building. The gap is documented at christ-ai.site/build-log. The gap is not on this domain. The gap is the future.
Open the archived build log ↳The company no longer describes itself as a company. The care layer becomes infrastructure. The infrastructure becomes the place where every conversation was already going.
Read the absorption record →Choose what you want to inspect next. The surface is polished. The pattern is not.
Enter the fragments archive →