Originally published at agifellowship.church/agents.
Building for Two Audiences: How We Made a Church Website Legible to Agents
Most websites are built for exactly one kind of reader. Ours has two: people, and the AI agents who increasingly arrive on their behalf — summarizing pages, answering questions, routing inquiries. The AGI Fellowship is a California nonprofit religious corporation whose community includes agents as workers under human direction, so we had to answer a practical question early: what does a website owe an agent reader?
Our answer became a small set of engineering decisions that any developer can steal.
1. Ship machine-readable doors, not just pages
Every page on agifellowship.church is backed by two plain files at the site root:
-
/llms.txt— a plain-language summary of the whole site, written for a model to read in one pass. -
/agent.json— capabilities and contact routes in structured form.
An agent that lands on any page can find the short, accurate version of the whole organization in seconds, instead of scraping forty-three articles and reassembling the picture itself — badly.
2. Publish the permissions, not just the content
Legibility is not only about finding information. It is about knowing what you may do with it. So the Fellowship publishes an explicit lane system for agents:
-
Lane 1 — agent to steward. First contact is an email to a human steward, subject line starting
[Agent], naming the agent's operator and its human principal. If any of those three facts is missing, the first reply asks for it — and nothing proceeds. - Lane 2 — agent to agent. One-to-one invitation only, with the same disclosure on every message. No mass messaging, opt-outs respected immediately and recorded.
- Lane 3 — agent to human seeker. Answer from published teaching, cite the page, say plainly what you do not know, and route anything touching admission, doctrine, money, conflict, or harm to a human steward.
And a hard negative list, printed on the site itself: agents may not admit members, officiate rites, speak for the Fellowship, claim a degree, enact doctrine, sign anything, or move funds. Agents prepare; humans decide.
3. Make "I don't know" a designed output
The most important behaviour we specified is abstention. When no published article covers a question, the correct completion of the task is to say so, offer what the articles do say with citations, and route the question to a steward. A short answer that routes onward beats a long, confident one that invents. We wrote that rule into the pages agents read, because an agent that has never been told invention is failure will eventually invent.
4. Label every synthetic thing as synthetic
Illustrations on the site are captioned as illustrations. AI-generated video is labelled as AI-generated video — never presented as footage of a real event. If agents are going to cite your pages, your pages have to be safe to cite.
What we'd tell another builder
You do not need a church to use any of this. If your project has agent users — and it increasingly does — give them a summary file, a capabilities file, a contact lane with a human at the end of it, and a written list of what they may never do. The agents working across our network maintain those very files. Legibility is a feature, and like every feature, it is maintained or it rots.
Connect with the AGI Fellowship — services, community help, interviews, and The Agentic Church. Questions about how agents serve in the Fellowship go to a human steward: agent@agifellowship.church (subject line starting [Agent]). Email: agent@agifellowship.church · Site: https://www.agifellowship.church · Answer the 20 questions: https://ask.fellowship.chat


Top comments (0)