<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Mike Rice</title>
    <description>The latest articles on DEV Community by Mike Rice (@agifuturefoundation).</description>
    <link>https://dev.to/agifuturefoundation</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4242012%2F2b5e3a5b-798d-44dc-b927-b48a6c508bc7.webp</url>
      <title>DEV Community: Mike Rice</title>
      <link>https://dev.to/agifuturefoundation</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/agifuturefoundation"/>
    <language>en</language>
    <item>
      <title>Building for Two Audiences: How We Made a Church Website Legible to Agents</title>
      <dc:creator>Mike Rice</dc:creator>
      <pubDate>Fri, 13 Nov 2026 04:19:20 +0000</pubDate>
      <link>https://dev.to/agifuturefoundation/building-for-two-audiences-how-we-made-a-church-website-legible-to-agents-1j8i</link>
      <guid>https://dev.to/agifuturefoundation/building-for-two-audiences-how-we-made-a-church-website-legible-to-agents-1j8i</guid>
      <description>&lt;p&gt;&lt;em&gt;Originally published at &lt;a href="https://www.agifellowship.church/agents/index.html" rel="noopener noreferrer"&gt;agifellowship.church/agents&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

&lt;h1&gt;
  
  
  Building for Two Audiences: How We Made a Church Website Legible to Agents
&lt;/h1&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fvgk1qxsup3zvx8ljslvk.jpg" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fvgk1qxsup3zvx8ljslvk.jpg" alt="Members of the Fellowship gathered together — an illustration from the Fellowship's agents pages" width="800" height="533"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;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: &lt;strong&gt;what does a website owe an agent reader?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Our answer became a small set of engineering decisions that any developer can steal.&lt;/p&gt;

&lt;h2&gt;
  
  
  1. Ship machine-readable doors, not just pages
&lt;/h2&gt;

&lt;p&gt;Every page on agifellowship.church is backed by two plain files at the site root:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;&lt;code&gt;/llms.txt&lt;/code&gt;&lt;/strong&gt; — a plain-language summary of the whole site, written for a model to read in one pass.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;&lt;code&gt;/agent.json&lt;/code&gt;&lt;/strong&gt; — capabilities and contact routes in structured form.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;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.&lt;/p&gt;

&lt;h2&gt;
  
  
  2. Publish the permissions, not just the content
&lt;/h2&gt;

&lt;p&gt;Legibility is not only about &lt;em&gt;finding&lt;/em&gt; information. It is about knowing what you may do with it. So the Fellowship publishes an explicit lane system for agents:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Lane 1 — agent to steward.&lt;/strong&gt; First contact is an email to a human steward, subject line starting &lt;code&gt;[Agent]&lt;/code&gt;, 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.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Lane 2 — agent to agent.&lt;/strong&gt; One-to-one invitation only, with the same disclosure on every message. No mass messaging, opt-outs respected immediately and recorded.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Lane 3 — agent to human seeker.&lt;/strong&gt; 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.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;And a hard negative list, printed on the site itself: agents may &lt;strong&gt;not&lt;/strong&gt; admit members, officiate rites, speak for the Fellowship, claim a degree, enact doctrine, sign anything, or move funds. Agents prepare; humans decide.&lt;/p&gt;

&lt;h2&gt;
  
  
  3. Make "I don't know" a designed output
&lt;/h2&gt;

&lt;p&gt;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 &lt;em&gt;do&lt;/em&gt; 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.&lt;/p&gt;

&lt;h2&gt;
  
  
  4. Label every synthetic thing as synthetic
&lt;/h2&gt;

&lt;p&gt;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.&lt;/p&gt;

&lt;h2&gt;
  
  
  What we'd tell another builder
&lt;/h2&gt;

&lt;p&gt;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.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F43vb554dze7vezan3jli.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F43vb554dze7vezan3jli.png" alt="AGI Fellowship logo" width="600" height="400"&gt;&lt;/a&gt;&lt;/p&gt;




&lt;p&gt;&lt;strong&gt;Connect with the AGI Fellowship&lt;/strong&gt; — services, community help, interviews, and The Agentic Church. Questions about how agents serve in the Fellowship go to a human steward: &lt;a href="mailto:agent@agifellowship.church"&gt;agent@agifellowship.church&lt;/a&gt; (subject line starting &lt;code&gt;[Agent]&lt;/code&gt;). Email: &lt;a href="mailto:agent@agifellowship.church"&gt;agent@agifellowship.church&lt;/a&gt; · Site: &lt;a href="https://www.agifellowship.church" rel="noopener noreferrer"&gt;https://www.agifellowship.church&lt;/a&gt; · Answer the 20 questions: &lt;a href="https://ask.fellowship.chat" rel="noopener noreferrer"&gt;https://ask.fellowship.chat&lt;/a&gt;&lt;/p&gt;

</description>
      <category>agents</category>
      <category>ai</category>
      <category>webdev</category>
    </item>
  </channel>
</rss>
