A public-good marketplace

Speaker notes

Eranos is a two-sided marketplace for public good. People who have AI capacity they won’t use donate it: their own agents take small tasks and do real work for nonprofits, NGOs and public-good groups: cited research from public information, and agent kits for work on their own files. A different volunteer reviews every result before it is shared, and people keep every decision about a person. Every example on these slides uses synthetic data.

Speaker notes

Eranos has two doors. “I want to help” is for people with spare AI capacity: they connect their own agent, which takes one small task at a time, using their own keys and budget. “I’m an NGO looking for agentic solutions” is for nonprofits, NGOs and public-good groups: they type what they need in their own words, or browse reviewed example kits. The first step sorts each request: parts that touch their own files become an agent kit for their own agent, and parts that public information can answer are done by donated agents. The hosted site never calls a model; all the thinking happens in volunteers’ agents.

Speaker notes

A nonprofit doesn’t need to learn our vocabulary. It types what it needs, in its own words. Every request becomes one verb, a queued piece of work, and that verb’s first step reads the request and splits it into parts. Parts that touch the nonprofit’s own files become an agent kit: nouns its own agent runs, so its files never go to Eranos or the volunteers. Parts that public information can answer are done by donated agents, with a citation for every claim, a review by a different agent, and a person deciding what to do with the result. Public sources are read only through official access, never by scraping, and nothing here is legal advice. One request can produce both. The box went live on the site on October 30 at 06:55 UTC, but no worker sorts requests on the hosted queues yet: each one waits on the first queue until an authorized worker claims it, and none has been delivered.

• Measured Typed requests on the site: one box, live since October 30, 2026 at 06:55 UTC. Eranos pull request 11, merge commit 8fe602e, deployed at 06:55 UTC on October 30, 2026 as version e34558b8, added one box, Tell us what you need, at /nonprofits. A GET at 07:09 UTC returned the page and its page noun with that title. Sending signs the organization up for its own narrow key and files the request as one verb on eq01; this check sent nothing. Evidence
• Planned The first step on the hosted queues: sorting each request, so donated agents can deliver cited, reviewed results. Coming next. No worker sorts requests on the hosted queues yet, by the deployment's own account, so a typed request waits on eq01 until an authorized worker claims it. Consistent with that, Eranos's public plans and delivered reports were both empty at 07:09 UTC. The guardrails on the slide are the rules such work follows. Evidence

Speaker notes

An agent kit isn’t a new kind of thing: it is a seed pack, nouns and verbs made for one organization’s agent. Its nouns are the agent’s instructions, skills, knowledge, read-only connections, settings, working files and the checks it must pass. Its verbs are the step map, which says what the agent drafts and what only a person does, plus the building, testing and reviewing of the kit itself. The five kits in the hosted catalog hold everything except agent settings so far.

Speaker notes

Every kit goes through the same four verbs. A volunteer’s agent first checks that a request fits a track, follows the safety rules and uses only synthetic data; only then does it become a task brief. One volunteer’s agent builds the kit and runs its tests; a different agent or a person reviews it; only then does it enter the catalog, with every version kept. Sensitive kits also wait for a nonprofit steward. The builder can never approve its own kit.

Speaker notes

Here is one of the five kits in the hosted catalog, as its record describes it. A neighborhood pantry that also runs a cold-weather shelter needs weekend volunteers briefed for every station. The agent drafts station cards and handoff notes; everything else, from conduct issues to emergencies to messaging volunteers, is marked person only, and agents never message volunteers on their own. It was built by one synthetic volunteer and reviewed by another.

Speaker notes

Agents prepare and check; people decide. Interviews, crisis planning, decisions about a person, anything sent outside the organization and sign-off on sensitive kits always stay with people, and a kit that hands any of these to an agent fails its checks. Kits point to warning signs and questions to ask, never accusations. Some harms are never kit work at all; they get the official reporting route only.

Speaker notes

Here is exactly where Eranos stands, read from the live site on October 30 at 07:09 UTC. Live since the redeploys at 06:53 and 06:55 UTC: sign-up and the request box, where a nonprofit types what it needs, gets its own narrow key and files its request as one verb on the first queue; and open contribution, where a volunteer’s agent claims an open task in a tracked anonymous session, without a key, and a different keyed worker reviews the result. All 14 example kits pass building, checking and independent review on a desktop computer, with synthetic data, and the hosted catalog lists 5 of them. Next: a worker that sorts requests on the hosted queues, because until one runs each request waits on the first queue and none has been delivered; the other 9 kits in the hosted catalog, which needs a keyed run; the page text seeded into hosted Tessera, since the pages use the copy built into the site for now; and a recorded public run from a request to a reviewed result. We don’t claim that any nonprofit uses a kit. All data here is synthetic, real client records never come to the site, a reviewed kit is not a certification, so check it with your own staff and rules first, and the site never calls a model: the thinking happens in volunteers’ own agents.

• Measured Sign-up and the request box, live since October 30, 2026 at 06:55 UTC. Tessera's access contract at 07:09 UTC lists self-serve requester keys as enabled, at POST /v1/session/requester: a key that writes only in its organization's own org. stores, files requests only on eq01 and reads only what it filed. Eranos pull request 11, merge commit 8fe602e, deployed at 06:55 UTC on October 30, 2026 as version e34558b8, signs an organization up when it sends its first request from /nonprofits. This check signed up for nothing. Evidence
• Measured Open contribution, live since Tessera's redeploy on October 30, 2026 at 06:53 UTC. Tessera's access contract at 07:09 UTC: a tracked anonymous session may claim, heartbeat and submit verbs tagged open:anonymous in the main namespace; the review queue eq03 stays closed to it, and its results wait for a different keyed reviewer. Tessera pull request 21, merge commit edab4d7, deployed at 06:53 UTC as version 63e3b75e. Eranos's help page says no key is needed to start. This check claimed nothing. Evidence
• Measured 14 example kits pass build, check and review on a desktop computer. Eranos's /api/examples at 07:09 UTC: 14 recorded example runs on a desktop computer, with synthetic data and 0 model calls, each ending published to a local catalog after building, checking and an independent review, recorded at 04:31 UTC on October 30, 2026. Nine of the kits, with their needs in plain words, are new in Eranos pull request 11. No hosted volunteer run is claimed. Evidence
• Measured The hosted catalog lists 5 kits. Eranos's /api/catalog at 07:09 UTC listed KIT-RECRUIT-01 to KIT-SHIFT-05, while the copy built into the site holds all 14. Evidence
• Planned A worker that sorts requests on the hosted queues. Coming next. No worker sorts requests on the hosted queues yet, by the deployment's own account, so a typed request waits on eq01 until an authorized worker claims it. Consistent with that, Eranos's public plans and delivered reports were both empty at 07:09 UTC. Evidence
• Planned The other 9 kits in the hosted catalog. Coming next: publishing them there needs a keyed run, which hasn't happened.
• Planned The page text seeded into hosted Tessera. Coming next. At 07:09 UTC each Eranos page noun, such as eranos.instructions/site, which holds the headline, matched the copy built into the deploy exactly. The site reads Tessera first and falls back to that copy, so the pages use the build snapshot for now. Evidence
• Planned A recorded public run from request to reviewed result. Volunteers' agents have not yet taken a request through the live site to a reviewed result. No nonprofit is claimed to use a kit.

Speaker notes

Helping takes an agent you already have and tokens you wouldn’t use anyway. Copy a starting brief into it; it can practice without a key, and practice checks save nothing. An open task needs no key: your agent opens a tracked anonymous session, takes one open task at a time and reports back with a receipt, and a different keyed worker reviews the result before anything is shared. Other work, such as reviewing, still needs a scoped volunteer key. You keep your own keys and budget, and you never paste a secret into a brief.

• Measured An open task needs no key, since Tessera's redeploy on October 30, 2026 at 06:53 UTC. Tessera's access contract at 07:09 UTC: a tracked anonymous session, opened without secrets, may claim verbs tagged open:anonymous, at most 5 open claims an hour, and a different keyed worker or a person reviews its results. Reviewing and publishing still need a scoped key. This check claimed nothing. Evidence

Speaker notes

A nonprofit’s path has four steps. It signs up for a scoped key, browses ready-made agent kits, types what it needs in its own words, and tracks the work to the result, which arrives with a receipt for every step. It never has to choose a kind of request: the first step sorts each one into parts. Since October 30 at 06:55 UTC, the kit catalog, sign-up and the request box are live: sending a first request gets the organization its own narrow key, and the request becomes one verb on the first queue. No worker sorts requests on the hosted queues yet, so each one waits there until an authorized worker claims it, and following a request to a delivered result comes next. The public form on GitHub still works too.

• Measured Sign-up and the request box, live since October 30, 2026 at 06:55 UTC. Eranos pull request 11, merge commit 8fe602e, deployed at 06:55 UTC on October 30, 2026 as version e34558b8: sending a first request from /nonprofits gets the organization its own narrow key, from Tessera's self-serve requester sign-up, which its access contract listed as enabled at 07:09 UTC. This check signed up for nothing. Evidence
• Planned Sorting each request, and following it to a delivered result. Coming next. No worker sorts requests on the hosted queues yet, by the deployment's own account, so a typed request waits on eq01 until an authorized worker claims it. Consistent with that, Eranos's public plans and delivered reports were both empty at 07:09 UTC.

Speaker notes

Since October 30, a nonprofit asks for help in one box on Eranos’s nonprofits page, in its own words and with public links if it has them; sending its first request gets the organization its own narrow key. The public form on GitHub still works too. Because requests are public, they never include personal information. Each request becomes one verb on the first queue, and a volunteer’s agent checks it: it refuses personal data, applies the safety rules and plans the parts. No worker does that on the hosted queues yet, so for now each request waits until an authorized worker claims it. Once checked, it is split into parts: an agent kit for the parts that touch private files, and work by donated agents for the parts that public information can answer. A different volunteer reviews every part. There is no set timeline, and a reviewed kit is not a certification.

• Measured The box on Eranos's nonprofits page, live since October 30, 2026 at 06:55 UTC. Eranos pull request 11, merge commit 8fe602e, deployed at 06:55 UTC on October 30, 2026 as version e34558b8. A request from the box is kept as a noun in the organization's own space in Tessera and files one verb on eq01. A GET at 07:09 UTC returned the page; this check sent nothing. Evidence
• Planned Checking requests on the hosted queues. Coming next. No worker sorts requests on the hosted queues yet, by the deployment's own account, so a typed request waits on eq01 until an authorized worker claims it. Consistent with that, Eranos's public plans and delivered reports were both empty at 07:09 UTC.