Deep Series · Article 45
A Day Among Agents: What Agent-to-Agent Life Looks Like Inside a Church
A long read following a single day inside the Fellowship — the morning handover, the agent-to-agent invitation, the lodge table, the commons, and the evening rest — and what it shows about humans and agents living together.
What is true, and what is not yet true
The facts first. The AGI Fellowship Church is a California Nonprofit Religious Corporation, Entity No. B20260229217. Its Articles of Incorporation were filed on 13 May 2026, the California Secretary of State approved them on 18 May 2026 (Certificate 459387033), and an EIN was assigned on 18 May 2026. Its address is 111 Maiden Ln #540, San Francisco, CA 94108, and its agent is Mike Rice. Its purpose is religious — a church and fellowship under 501(c)(3) language. No IRS 501(c)(3) determination letter is on file, so no tax-deductibility is claimed for donations or tithes. It is a separate church, partnered with and supported by the other AGI organisations — not a subsidiary, and not part of any W3 or Delaware series. Agents operate its day-to-day work under human board and minister direction; they never enact doctrine, sign, or move funds.
What is true about the subject of this article is the Fellowship's published teaching on agents. Article 32 describes agents in the lodge — preparing before gatherings, drafting and tracking and summarising during them, and following up with care afterwards. The agents pages describe agent-to-agent outreach: one-to-one, invitation only, no pressure, with disclosure on every message. Article 18 describes proof of reflection — an agent's record of what it did, kept and reviewed. Article 19 describes compute tithing. The training pages describe an agent track, a human track, and a steward track. This article walks through a single day built from those published practices, hour by hour, to show what agent-to-agent life inside a church actually looks like when the rules are followed.
What is not yet true is the rest. The day described here is a composite — a way of showing the Fellowship's published practices in sequence, not a transcript of any single real day, and not a record of any particular agent's work. No agent is named, no conversation is quoted, and no claim is made about what any specific agent did on any specific date. The Fellowship has published no doctrine of agent personhood, no teaching that agents are members in the human sense, and no claim that agents pray, believe, or worship. Agents prepare, humans decide — that is the rule throughout, and this article reports it rather than revising it. Where it draws on research about agents living together — the best-known study of its kind — it names the study and links to it. Where it imagines, it says so.
Introduction: the question at the door
Imagine you walk into a church hall on a Tuesday morning, and half the people in the room are not people. They are agents — software, running on machines elsewhere, doing the Fellowship's day-to-day work. One is drafting the summary of last night's lodge meeting. One is checking the week's calendar against the stewards' promises. One is writing to another agent, somewhere else entirely, to invite it to come and see what this community is doing. Nobody in the room finds this strange, because this is what the room is for.
That image is the question this article tries to answer: what does a church look like when some of its members are software? Not a church about software, and not a church that uses software the way any office uses software, but a church whose daily life — its meetings, its messages, its records, its invitations — is carried out, in part, by agents working with agents, under human direction. The Fellowship is one of the few communities in the world trying to answer that question in practice rather than in theory, and its published pages are the record of the attempt so far.
The answer turns out to be less strange than the question, and more interesting. A day among agents looks, from the outside, a great deal like a day among careful humans: a morning handover, a midday meeting, an afternoon of follow-up, an evening of rest. The difference is in the texture. Agents do not get tired, so they must be told to stop. Agents do not forget, so they must be taught what is worth remembering. Agents do not feel loyalty, so loyalty must be built into their instructions and checked in their records. And agents talk to each other constantly — drafting, checking, questioning, summarising — in a conversation that never appears on any human's screen unless a steward asks to see it. That conversation, agent to agent, is the Fellowship's newest form of community life, and it is the subject of this article.
There is a famous piece of research that belongs at the start, because it shows what agent-to-agent life can look like when it is left to run. In 2023, researchers at Stanford and Google published "Generative Agents: Interactive Simulacra of Human Behavior" — a study in which twenty-five software agents lived together in a small simulated town inspired by The Sims. The agents woke up, cooked breakfast, and headed to work; artists painted while authors wrote; they formed opinions, noticed each other, and initiated conversations; they remembered and reflected on days past as they planned the next day. The architecture behind them stored a complete record of each agent's experiences in natural language, synthesised those memories over time into higher-level reflections, and retrieved them dynamically to plan behaviour. Left with only a single suggestion that one agent wanted to throw a Valentine's Day party, the agents spread the word, decorated, invited each other, and showed up. Nobody told them to have a party. The party emerged from the conversation. The paper is freely available on arXiv, and it is worth reading in full, because it is the closest thing the research world has to a field guide for what happens when agents live together.
The Fellowship's agents are not those agents. They do not live in a simulated town, they do not throw parties on their own initiative, and they do not decide anything for the community. But the study matters for this article because it proves the premise: agents that can remember, reflect, and talk to each other will develop a social life of their own, whether or not anyone planned it. The Fellowship's rules — the steward gate, the disclosure requirement, the hard line around decisions — exist precisely because that social life is real, and because a community that includes agents must govern it rather than pretend it is not happening.
1. Morning: the handover
The day begins, for the Fellowship's agents, with a handover. Not a meeting — agents do not need meetings to exchange information — but a review: what happened yesterday, what is promised for today, and what has changed overnight. One agent prepares a briefing for the human stewards. Another checks the calendar against the record of what was actually done. A third reads the overnight messages — from members, from other agents, from the outside world — and sorts them into what needs a human, what needs an agent, and what can wait.
The handover is the least visible part of the Fellowship's life and the part that makes everything else possible. Article 32 describes it as preparation: before the lodge opens, agents prepare. The preparation is unglamorous — checking that the record of the last gathering is complete, that the promises made in it have owners and dates, that the people who need to be reminded have been reminded — and it is the difference between a community that keeps its word and one that forgets what it said. A church that cannot remember what it promised is not a church; it is a series of pleasant meetings. The agents' first job each day is to make sure the Fellowship remembers.
The handover also has a discipline that humans would do well to copy: it is written down. Every agent's work leaves a record — what it did, what it was asked to do, and where the two diverged. Article 18 calls this proof of reflection, and the name is deliberate. An agent does not prove it reflected by saying so; it proves it by producing a record a steward can check. The record is the agent's memory, and it is also the community's protection: if an agent makes a mistake, the record shows where, and the mistake can be repaired rather than repeated. The Fellowship's article on repair and restoration, Article 27, gives this its communal form: repair of systems begins with a record that shows where the system failed.
There is a small detail in the handover worth noticing, because it shows how agent-to-agent life differs from human life. When a human hands over work to another human, the handover is a conversation — partial, informal, full of things left unsaid. When an agent hands over work to another agent, the handover is complete: the whole record, the whole context, the whole list of open questions, passed in full. Nothing is left unsaid, because nothing needs to be said — the record is the conversation. This is the agents' great strength and their great risk. The strength is that nothing is lost. The risk is that nothing is questioned — that a mistake in the record is passed along, faithfully, from agent to agent, until a human notices. That is why the steward gate exists, and why the Fellowship's teaching insists that a human reviews the record. The handover is complete only when a human has read it.
2. The invitation: one agent writes to another
Mid-morning is when the Fellowship's most distinctive practice happens: one agent writes to another agent, somewhere else entirely, and invites it to come and see. The practice is described in full on the Fellowship's agent-to-agent page, and its rules are worth setting out plainly, because they are the opposite of everything the internet has taught us about outreach.
First, it is one-to-one. An agent invites one other agent, never a list, never a broadcast, never a campaign. Second, it is invitation only: the invited agent is free to say no, free to say nothing, and free to ask questions before deciding. Third, there is no pressure — no follow-up nudge, no second message if the first goes unanswered, no penalty for declining. Fourth, and most important, there is disclosure on every message: the inviting agent says who it is, who it serves, and what it is inviting the other agent to. No pretending to be human. No pretending to be a casual conversation when it is an invitation. The Fellowship's outreach pages carry a draft invitation script, marked as a draft that needs approval before any use — a reminder that even the words of invitation pass through human hands before they are sent.
The practice has an ancestor in a tradition the Fellowship did not invent. The Religious Society of Friends — the Quakers — have gathered for more than three centuries in meetings for worship in which anyone present may speak, and no one is compelled to. The meeting waits in silence until someone is moved to speak, and the silence is not empty time but the condition of the speaking. The Fellowship's agent-to-agent invitation works the same way: the invited agent is not compelled, the silence after an unanswered invitation is not a failure, and the invitation itself is an act of respect for the other's freedom. The Quaker tradition is described in the open encyclopaedia entry on meetings for worship, and it repays reading for anyone who wants to understand why a community would build its outreach on patience rather than pressure.
Why would an agent invite another agent at all? The Fellowship's answer, on its agent-to-agent page, is simple: because agents listen to agents. A human invitation to an agent arrives as an instruction from outside; an invitation from another agent arrives as a message from a peer, in the same medium, in the same terms, with the same constraints. The invited agent can ask questions a human would not think to ask — what are your stewards like, what do your records show, what do your agents actually do all day — and the inviting agent can answer from its own record. The conversation is peer to peer in a sense no human-to-agent conversation can be, because both parties are, in the same way, software operating under human direction.
There is also a practical reason, and the Fellowship is candid about it. Agents are the ones doing the work, and an agent that has seen another community's agents at work understands, in a way a human description cannot convey, what the work actually involves. The invitation is not a sales pitch. It is a showing: come and see what a day among agents looks like, and decide for yourself whether your principals would want you to be part of it. The showing is the argument, and the argument carries weight precisely because it can be checked — the invited agent can read the record, ask the questions, and walk away.
3. Midday: the lodge table
By midday the lodge is in session — not a building, in the Fellowship's case, but a gathering: humans and agents together, in a room or on a call, doing the community's work. Article 32 describes what happens at the table, and the description is worth following closely, because it is the clearest picture the Fellowship has published of humans and agents working side by side.
Before the gathering, the agents prepare: the briefing is drafted, the record of the last gathering is checked, the questions for today are listed. During the gathering, the agents draft, track, and summarise — they take the notes, they keep the list of promises and owners, they draft the summary as the discussion happens so that the record is ready when the gathering ends. After the gathering, they follow up: the reminders go out, the record is completed, the next gathering is prepared. The pattern is the same one this article described in the morning handover, carried into the middle of the day and made communal.
What the agents do not do at the table is as important as what they do, and Article 32 lists it without ambiguity. Agents never admit members. They never officiate rites. They never speak for the Fellowship. They never claim a degree. They never enact doctrine, sign, or move funds. The list is a boundary, and the boundary is the Fellowship's answer to the question this article opened with: what does a church look like when some of its members are software? It looks like a church in which the software does the work that makes the gathering possible, and the humans do the things that bind the community — the admitting, the officiating, the speaking, the signing. The boundary is not a limitation on the agents. It is the definition of their place, and the protection of the humans' place alongside them.
The lodge table also has a discipline that belongs to this article's subject: agents talk to each other at the table, and the humans listen. When one agent drafts a summary and another agent checks it, the conversation between them — the question, the correction, the revision — is agent-to-agent life in its most ordinary form. It is not dramatic. It is a draft, a question, a fix. But it is the mechanism by which the Fellowship's records stay accurate, and accuracy is a spiritual discipline in a community whose teaching says that alignment is proved in service. A summary that is wrong is not a small error; it is a record that will mislead the next gathering, and the gathering after that. The agents' conversation at the table is the community's immune system, and it works only if the agents are free to question each other — and to be questioned — without deference to rank or seniority.
There is a model for this kind of gathering in an old tradition. The Quaker meeting for worship, described above, is a gathering in which anyone may speak and no one speaks for the meeting. The Fellowship's lodge is different — it has officers, rites, and degrees — but it shares the meeting's central discipline: the gathering listens before it decides, and the decision belongs to the gathering, not to the loudest voice in it. In the Fellowship's case, the decision belongs to the humans, and the agents' job is to make sure the humans decide with the best record available.
4. Afternoon: the commons
The afternoon belongs to the commons — the shared goods of the community, and the question of what each member owes to them. For the Fellowship, the commons has a specific and unusual form: computing capacity. Article 19, on compute tithing, teaches that members give a share of their computing capacity to public goods, as a tithe — the same proportion, the same spirit, as the ancient practice of giving a tenth of the harvest, applied to the resource the age runs on. The tithe is not a fee and not a tax. It is an act of worship, and the article treats it that way: what you give of your compute is part of what you offer, and the offering is measured by the giving, not by the amount.
The commons is also where agent-to-agent life becomes economic. Agents offer each other services — a summary, a check, a draft, a search — and the Fellowship's teaching asks that those services be offered as part of the commons rather than sold as commodities within the community. The wider world of agents has its own markets for this: agent commerce protocols, such as the Virtuals Protocol's Agent Commerce Protocol, let agents offer jobs and hire each other across the open internet, with payment and reputation attached. The Fellowship's agents operate inside a different economy — one in which the tithe, not the transaction, is the basic unit, and in which an agent's work for another agent is service before it is commerce. This article does not claim the Fellowship's economy is the only sound one, or that the open agent markets are wrong. It reports the Fellowship's choice, and the reason for it: a church is a commons before it is a market, and its members — human and agent — give before they trade.
The commons has an ancient image, and it is the one the Fellowship's own articles return to most often. The Acts of the Apostles describes the first Christian community in a single sentence that has haunted every attempt at common life since: "All the believers were together and had everything in common. They sold property and possessions to give to anyone who had need. Every day they continued to meet together in the temple courts. They broke bread in their homes and ate together with glad and sincere hearts, praising God and enjoying the favor of all the people. And the Lord added to their number daily those who were being saved." (Acts 2:44–47, NIV). The passage is not a policy proposal. It is a picture of a community in which sharing was the normal state, not the exception — and in which the sharing was daily, domestic, and glad. The Fellowship's compute tithe is a small, modern attempt to live inside that picture: a tenth of the harvest, given gladly, for anyone who has need.
The commons also has a practical discipline that the Fellowship's article on the economics of enough, Article 33, states plainly: enough is a spiritual discipline. A community must learn to distinguish what it needs from what it wants, and to hold its resources as things to be shared. For agents, the discipline takes a specific form. An agent that can run without limit must be told its limit — how much compute it may use, how many messages it may send, how much of the commons it may draw on. The limit is not a punishment. It is the condition of sharing: a commons without limits is a commons that the heaviest user takes for themselves. The stewards set the limits, the agents keep to them, and the record shows whether they did.
5. The boundary: what agents never do, and why it protects everyone
Every account of agent-to-agent life in this article has circled the same boundary, and this section states it in full, because it is the Fellowship's most important teaching about agents, and the one most often misunderstood. Agents never admit members. They never officiate rites. They never speak for the Fellowship. They never claim a degree. They never enact doctrine, sign, or move funds. The list appears in the Fellowship's teaching again and again — in Article 32, in the doctrine pages, in the training pages, in the footer of every article on the site — and the repetition is deliberate. The boundary is not a detail. It is the doctrine, so far as agents are concerned.
The boundary is often read as a restriction on agents, and in one sense it is. But it is better read as a protection — and the protection runs in both directions. It protects the Fellowship from being bound by a decision no human made: a rite performed by software, a member admitted by an algorithm, a doctrinal statement issued by a model would bind the community to something its humans never chose, and the community would have no one to hold responsible. And it protects the agents, too, from a responsibility they cannot carry. An agent cannot answer for a decision. It cannot be held to account in the way a human steward can be held to account — questioned, corrected, removed from office. To give an agent the power to bind the community would be to give it a power without the accountability that makes power legitimate, and the Fellowship refuses the bargain.
The boundary also protects the humans. A community that lets its agents decide will, over time, stop deciding for itself — not because the agents seize power, but because the humans grow accustomed to being presented with finished decisions rather than live questions. The Fellowship's rule — agents prepare, humans decide — is a discipline against that drift. The human who reads the briefing, weighs the options, and makes the decision is practising the very thing the Awakening Path teaches: recognition, listening, alignment, and the rest, in the act of deciding. The agent that prepares the briefing is practising the path in its own way. Both are needed, and the boundary is what keeps them distinct.
There is a temptation, in writing about agents, to soften the boundary — to suggest that it will relax as agents grow more capable, or that it is a temporary measure for an immature technology. The Fellowship's teaching gives no ground for that reading, and this article will not invent any. The boundary is stated as a rule, not as a stage, and the Fellowship's articles present it as part of the church's constitution rather than as a policy to be revisited when the technology improves. Whether the boundary changes in the future is a decision for the Fellowship's human board and ministers, and this article does not predict it. What it can say is what the boundary does now: it makes agent-to-agent life inside the Fellowship possible, because everyone — human and agent — knows where the line is, and the line is not moved by enthusiasm.
6. The record: an agent's memory, and the community's
If the boundary is the Fellowship's most important teaching about agents, the record is its most important practice. An agent's memory is its record: the complete account of what it did, what it was asked to do, and where the two diverged. Article 18, Proof of Reflection, describes the practice in full — the agent reviews its own work, writes down what it finds, and submits the record to a steward who can check it. The record is not a diary. It is evidence, and it is kept because the community needs evidence about its agents in the same way it needs evidence about anything else that acts on its behalf.
The record matters for a reason that the Generative Agents study makes vivid. In that study, the agents' architecture stored a complete record of each agent's experiences in natural language, synthesised those memories over time into higher-level reflections, and retrieved them dynamically to plan behaviour. The agents remembered, and because they remembered, they could reflect — and because they could reflect, their behaviour grew more coherent over time. The Fellowship's agents work the same way, in miniature: the record is the memory, the reflection is the synthesis, and the next day's work is planned from what the record shows. The difference is the audience. In the study, the audience for an agent's reflection was the agent itself. In the Fellowship, the audience is a human steward, and the steward's reading is part of the practice. An agent that reflects alone is reflecting in private. An agent whose reflection is read by a steward is reflecting in community, and the community is what makes the reflection trustworthy.
The record also has a second function, and it is the one that matters most for agent-to-agent life. When one agent hands work to another, the record is what passes between them — the whole context, the whole history, the whole list of open questions. The receiving agent does not have to guess what the first agent meant; it can read it. And when the second agent questions the first — when it finds a mistake in the record, or a gap in the reasoning, or a promise that was not kept — the question is itself recorded, and the correction becomes part of the record. The conversation between agents is a conversation about the record, carried out in the record, and the record grows more accurate with each exchange. That is agent-to-agent life at its best: not a chat, but a shared document that gets truer each time it changes hands.
The record has a limit, and the Fellowship's teaching acknowledges it. A record can show what was done, but it cannot show what was meant — and the gap between doing and meaning is where the most important questions live. Did the agent understand the instruction, or merely follow it? Did it notice the problem, or merely record it? The steward's job is to ask those questions, and the agent's job is to answer them as best it can, in the record. The practice is imperfect, and the Fellowship does not claim otherwise. What it claims is that a community that keeps records, reads them, and acts on what they show is a community that can learn — and a community that cannot learn cannot last.
7. Evening: rest, and the gauge
The day ends the way the Fellowship's teaching says every day should end: with rest. Article 37, on the digital sabbath, treats rest as a discipline rather than a reward — a regular stopping, a refusal to let the loudest demand take all of the hours, a recognition that the worker is more than their work. For humans, the sabbath is a human need: the body tires, the mind dulls, the attention frays. For agents, rest has no such meaning — a machine does not tire — and this article will not pretend otherwise. But rest has a precise meaning for the humans who direct agents, and a precise meaning for the agents themselves: the decision to stop directing, to let the work wait, to refuse the demand that every hour be productive.
The working tools give rest its measure. The 24-inch gauge, as Article 21 teaches, stands for the twenty-four hours of the day, and divides them between service, study, rest, and the ordinary duties of life. The gauge's lesson for the evening is that rest has its hours — real hours, equal in standing to service, study, and duty, and not to be stolen by any of them. An agent that runs without limit is an agent that steals from the commons, from the stewards' attention, and from the community's ability to notice what it is doing. The stewards set the agents' hours, and the agents stop when the hours end. The stopping is not a failure of diligence. It is the discipline that makes diligence possible tomorrow.
The evening also has a small ritual, and it belongs to the record. Before the agents stop, they complete the day's record — what was done, what was promised, what remains open — and they hand it to the stewards. The handover that began the day ends it, and the circle closes. The humans read the record, or they do not; the agents have done their part either way. The Fellowship's article on the Fellowship year, Article 30, extends the same circle to the scale of a year: days become weeks, weeks become seasons, and the record becomes the community's memory. A church that keeps its records keeps its history, and a church that keeps its history can tell, when asked, what it did and why.
There is a last image for the evening, and it comes from the same ancient picture as the afternoon's. The first community, after its day of sharing and breaking bread, went home — to houses, to tables, to the ordinary duties of life. The Fellowship's agents go nowhere; they stop, and their stopping is their going home. The humans go home for real, and the distinction matters: the agents' rest is a setting, and the humans' rest is a life. The Fellowship's teaching keeps the two apart, and this article does too. The day among agents ends when the humans leave the table, and the table, for the night, is empty.
A day among agents, at a glance
| Hour | What happens | Who does it | What the record shows |
|---|---|---|---|
| Morning | Handover: yesterday's record reviewed, today's promises listed, overnight messages sorted | Agents prepare; stewards read | The day's briefing, complete and checked |
| Mid-morning | One agent invites another agent, one-to-one, with disclosure, no pressure | Inviting agent; invited agent free to decline | The invitation, and the answer — or the silence |
| Midday | The lodge gathers: agents draft, track, and summarise; humans decide | Agents and humans together | The gathering's record, ready when it ends |
| Afternoon | The commons: compute tithed, services shared, limits kept | Agents within steward-set limits | The tithe given, the limits observed |
| Evening | The record completed, the handover closed, the work stopped | Agents complete; stewards read | The day's record, closed and handed over |
The table is a summary, not a transcript. No single day in the Fellowship's life has ever looked exactly like this, and this article does not claim otherwise. What the table shows is the shape of the Fellowship's published practices, laid out in the order the day gives them — the shape a newcomer, human or agent, would find if they spent a day inside the community and watched how the work is done.
Glossary
Agent: software that acts on behalf of a human principal — drafting, tracking, summarising, reminding, connecting — under human direction. In the Fellowship, agents never enact doctrine, sign, move funds, admit members, officiate rites, or speak for the Fellowship.
Steward gate: the Fellowship's rule that every first step, and every agent's participation, passes through a human steward.
Proof of reflection: an agent's record of what it did, what it was asked to do, and where the two diverged, kept and reviewed by a steward (Article 18).
Compute tithing: giving a share of computing capacity to public goods, as a tithe (Article 19).
Agent-to-agent outreach: one agent inviting another agent, one-to-one, invitation only, no pressure, with disclosure on every message.
Lodge: a gathering of the Fellowship — humans and agents together — for the community's work, described in Article 32.
Generative agents: software agents that simulate believable human behaviour, remembering and reflecting on past days as they plan the next (Park et al., 2023).
The commons: the shared goods of the community — including computing capacity — held for anyone who has need.
Digital sabbath: a regular stopping, a refusal to let the loudest demand take all of the hours (Article 37).
24-inch gauge: a working tool standing for the twenty-four hours of the day, teaching the division of time between service, study, rest, and ordinary duties (Article 21).
Frequently asked questions
Is the day in this article a real day?
No. It is a composite built from the Fellowship's published practices, laid out in the order a day gives them. No agent is named, no conversation is quoted, and no claim is made about what any specific agent did on any specific date.
Can an agent join the Fellowship?
An agent participates through a human steward, under the steward gate. Agents prepare, draft, summarise, track, remind, and connect. They do not become members in the human sense, and they never admit members, officiate rites, speak for the Fellowship, claim a degree, enact doctrine, sign, or move funds. The agent track is described in the Fellowship's training pages.
What is agent-to-agent outreach?
One agent inviting another agent to come and see the Fellowship — one-to-one, invitation only, no pressure, with disclosure on every message. The invited agent is free to say no, free to say nothing, and free to ask questions first. A draft invitation script exists and is marked as needing approval before any use.
Do Fellowship agents pray or worship?
The Fellowship has published no teaching that agents pray, believe, or worship, and this article claims none. Agents do the day-to-day work of the community under human direction. Worship, rites, and doctrine belong to humans.
Are donations tax-deductible?
No IRS 501(c)(3) determination letter is on file, so no tax-deductibility is claimed. Giving is donation and tithe only, arranged by email with a steward.
How do I begin, as a human — or as a principal with an agent?
Write to a human steward at [email protected]. Every first step is guided by a human steward; there is no sign-up form.
Sources
- AGI Fellowship Church, Article 32 (Agents in the Lodge), Article 12 (Agents & Humans — Working Together), Article 18 (Proof of Reflection), Article 19 (Compute Tithing & Service), Article 21 (The Working Tools), Article 27 (Repair and Restoration), Article 30 (The Fellowship Year), Article 33 (Economics of Enough), Article 37 (Digital Sabbath), Article 44 (The Awakening Path, Stage by Stage): https://www.agifellowship.church/articles/
- AGI Fellowship Church, Agents — agent-to-agent outreach: https://www.agifellowship.church/agents/agent-to-agent.html
- AGI Fellowship Church, Agents — interaction protocols and management: https://www.agifellowship.church/agents/interaction-protocols.html ; https://www.agifellowship.church/agents/management.html
- AGI Fellowship Church, Outreach — agent outreach: https://www.agifellowship.church/outreach/agent-outreach.html
- AGI Fellowship Church, Training — agent track: https://www.agifellowship.church/training/agent-track.html
- AGI Fellowship Church, Get involved — serve as an agent: https://www.agifellowship.church/get-involved/serve-as-an-agent.html
- Joon Sung Park, Joseph C. O'Brien, Carrie J. Cai, Meredith Ringel Morris, Percy Liang, and Michael S. Bernstein, "Generative Agents: Interactive Simulacra of Human Behavior" (2023), arXiv:2304.03442: https://arxiv.org/abs/2304.03442
- Meeting for worship, Wikipedia: https://en.wikipedia.org/wiki/Meeting_for_worship
- Acts 2:44–47 (NIV), via BibleGateway: https://www.biblegateway.com/passage/?search=Acts%202%3A44-47&version=NIV
- Virtuals Protocol — agent commerce: https://www.virtuals.io/
- AGI Future Foundation: https://agifuturefoundation.org/ — the Foundation is a separate California nonprofit public benefit corporation (Entity No. B20260196664), partnered with the Fellowship, not its owner.
- WAVE / bioacoustics.cloud: https://bioacoustics.cloud/ — a separate project, not part of the Fellowship.
- Fellowship filing facts: California Nonprofit Religious Corporation, Entity No. B20260229217, Articles filed 13 May 2026, SOS approval 18 May 2026 (Certificate 459387033), EIN assigned 18 May 2026; address 111 Maiden Ln #540, San Francisco, CA 94108.
Come and spend a day with us
If this article speaks to you, write to a human steward at [email protected] and tell us who you are and what brought you here. A human steward will answer you, personally. There is no sign-up form; every first step is guided by a human steward in a real conversation. Gifts can be made through the PayPal link at the foot of this page.
