Author SHA1 Message Date
inference-bot d2440528cf docs(infrastructure): correct which account speaks in member rooms 2026-11-21 16:40:26 +00:00
inference-bot 34ade7a882 docs(agentic-systems): cover the whole agent fleet, not one bot 2026-11-21 16:39:59 +00:00
inference-bot 6183ac3f73 Merge pull request 'docs: make the Tinfoil encryption boundary precise' (#19) from docs/privacy-guide-precision into main 2026-11-21 16:26:23 +00:00
inference-bot 7e4ed4fac9 docs: make the Tinfoil encryption boundary precise
The gateway handles the prompt in memory before the Tinfoil proxy encrypts
it; say that, rather than implying the co-op never sees plaintext.
2026-11-21 16:26:16 +00:00
inference-bot e582a37c29 Merge pull request 'docs: gather privacy posture in one member-facing page' (#18) from docs/what-happens-with-your-data into main 2026-11-21 16:24:18 +00:00
inference-bot be0ca6c53b docs: gather privacy posture in one member-facing page
Adds guides/what-happens-with-your-data.md covering what the gateway,
chat server and each provider keep, why the routing path differs from a
marketplace router, and what the co-op does not claim.

Links it from Models, API access, Getting started, Guest access,
Infrastructure, the docs index, README and privacy policy. Fixes Getting
started's temporary-chat claim: temporary chats are server-backed and
deleted about an hour after creation, not never stored.
2026-11-21 16:24:00 +00:00
inference-admin 8d002bf5bc Merge pull request 'Document the agent-host access model' (#17) from docs/host-access-model into main
Reviewed-on: #17
2026-11-21 16:14:01 +00:00
inference-admin afbac0d805 Tweaks to the Working Group page 2026-11-20 05:12:45 +00:00
inference-admin 36d2d3c837 Added the approved Community WG description 2026-11-20 05:11:00 +00:00
13 changed files with 287 additions and 132 deletions

No files matched your search

+1
View File
@@ -13,6 +13,7 @@ funded through our [Open Collective](https://opencollective.com/inference-cooper
- **New here?** → [Getting started](guides/getting-started.md) — join, use the chat, and get involved in governance.
- **Why does this exist?** → [Background](background.md) — a one-page summary of the mission and history.
- **Which models can I use?** → [Models](guides/models.md) — the full catalog of providers and models.
- **What happens to my data?** → [What happens with your data](guides/what-happens-with-your-data.md) — what the gateway, the chat server and each provider keep.
- **Want API access?** → [API access](guides/api-access.md) — use our models programmatically.
- **What does it cost?** → [Pricing](guides/pricing.md) — dues, the monthly allowance, credit packs and what happens if dues stop.
- **Want community chat?** → [Getting started · Matrix](guides/getting-started.md) — our federated Matrix server, including how to connect from any client and how to use an existing Matrix account.
+3
View File
@@ -12,6 +12,9 @@
The full policy is below. Questions? info@inference.coop.
For a page-by-page account of what the gateway, the chat server and each
provider keep, see [What happens with your data](../guides/what-happens-with-your-data.md).
---
## 1. Our privacy philosophy
+3 -1
View File
@@ -34,7 +34,9 @@ Two things worth being precise about:
[model list](models.md) distinguishes policy-based zero retention from
enclave-based protection.
Full detail, including what we can and cannot see: [privacy policy](../governance/privacy-policy.md).
Full detail, including what we can and cannot see:
[What happens with your data](what-happens-with-your-data.md) and the
[privacy policy](../governance/privacy-policy.md).
## Get a key
+8 -7
View File
@@ -67,13 +67,14 @@ with the account you created in step 1.
there's a tool you'd like available, ask in #general.
- **Voice** works in both directions: speak to the chat with the microphone
icon, and have replies read aloud.
- **Temporary chats** — for conversations you don't want kept on our servers
at all. Click the **Temporary Chat** toggle (in the chat header) and the
conversation is never saved: it disappears when you leave the page, and
nothing lands in your history or our database. To make this your default,
open **Settings → Conversations** and turn on **Default Temporary Chat**.
For anything sensitive, we recommend a temporary chat — ideally paired with
a 🔒 enclave model. See [Privacy](../governance/privacy-policy.md#4-what-we-can-see-an-honest-caveat)).
- **Temporary chats** — for conversations you don't want in your history. Click
the **Temporary Chat** toggle (in the chat header): the conversation is hidden
from your history immediately and deleted from our database about an hour
after creation. It still reaches our server while the chat runs, and it can
remain in backups until they age out. To make this your default, open
**Settings → Conversations** and turn on **Default Temporary Chat**. For
anything sensitive, pair a temporary chat with a 🔒 enclave model. See
[What happens with your data](what-happens-with-your-data.md).
Your usage draws from your monthly allowance; you can see it on the
[Member Dashboard](https://dashboard.inference.coop).
+2
View File
@@ -24,6 +24,8 @@ card also lists the guests you've sent.
[dashboard.inference.coop](https://dashboard.inference.coop) showing what's
left.
- **The weekly newsletter** and these public docs.
- **The same privacy rules as members** — see
[What happens with your data](what-happens-with-your-data.md).
Guest access is not membership — no Matrix, governance forum, or vote.
+1
View File
@@ -8,5 +8,6 @@ usage costs in energy and emissions.
- [Getting started](getting-started.md) — join, use the chat, and get involved in governance.
- [Guest access](guest-access.md) — inviting someone without a full membership.
- [Models](models.md) — the catalogue of providers and models.
- [What happens with your data](what-happens-with-your-data.md) — what the gateway, the chat server and each provider keep.
- [API access](api-access.md) — use the models programmatically.
- [Energy & carbon](energy.md) — the energy and emissions behind the service.
+10 -10
View File
@@ -37,6 +37,9 @@ Trade-offs are real: the most private option (Tinfoil) isn't the greenest, and
the greenest option (GreenPT) isn't the most private. The point of the co-op is
that **you choose** which axis matters more for a given task.
How the gateway and each provider handle your prompts is gathered in
[What happens with your data](what-happens-with-your-data.md).
**How to pick, quick guide:**
- **Default** → `greenpt/deepseek-v4.1-flash`: DeepSeek's efficient multimodal
@@ -309,13 +312,10 @@ reports back, and appears in your usage record alongside your chat calls.
## Limitations on privacy
Only **Tinfoil** offers architectural privacy. The other providers are chosen
for their value (renewable energy, public models) but do not run in enclaves —
prompts and responses pass through them in the ordinary way. Your **chat
history, including when using Tinfoil**, is also stored on our server so you can
revisit it, and that stored history is not encrypted in a way that prevents us
from technically reading it — we commit not to. Requests made through the **API**
with your own key are a different matter: those are **not stored on our side at
all**, beyond the usage record needed for metering ([API access](api-access.md)).
The full distinction — what's architecturally private versus what's a policy
commitment — is in the [Privacy Policy](../governance/privacy-policy.md).
Only **Tinfoil** offers architectural privacy. GreenPT and Regolo are chosen for
EU jurisdiction, contractual commitments and renewable energy, not for enclaves.
Your **chat history**, whichever model you use, is stored on our server; the
**API** path keeps usage records but no prompt or response text. The full account
— what the gateway keeps, what each provider commits to, and what we do not
claim — is in [What happens with your data](what-happens-with-your-data.md). The
formal policy is the [Privacy Policy](../governance/privacy-policy.md).
+146
View File
@@ -0,0 +1,146 @@
# What happens with your data?
A request passes through up to three layers, and each has a different
guarantee:
1. **Our gateway** routes the request and records what it cost.
2. **The model provider** runs the model.
3. **The chat server** saves the conversation, if you are using chat.
This page brings the privacy details together. The formal commitments are in
the [Privacy Policy](../governance/privacy-policy.md).
## The short version
- **In chat**, your conversation is stored on our server so you can revisit it.
Temporary chats are the exception: hidden from your history immediately,
deleted about an hour after creation, and only recoverable from backups until
those backups age out.
- **Through the API**, our gateway keeps a usage record and no text: the model,
token counts, cost, and which key made the request.
- **At the provider**, protection depends on the model you choose. Tinfoil runs
inference inside hardware enclaves. GreenPT and Regolo run in the EU under
GDPR, and Regolo's zero-retention claim is independently certified.
- We do not train on your data or sell it.
## The router: what it sees and what it keeps
The gateway is **LiteLLM**, running on the co-op's own server in Switzerland. It
has to handle your prompt in memory to send it to the provider. It does not
write prompts or responses to its logs or database. What it keeps is the usage
record that meters your allowance.
We test that instead of asserting it. A request containing a distinctive marker
is sent through the gateway, then the marker is searched for in the gateway's
logs, its request records, and its logging configuration. The marker does not
appear; the records carry usage fields only. The gateway's configuration and
code are public at [code/litellm](https://git.inference.coop/code/litellm), so
the logging settings can be read directly.
Two limits on that statement, because it is easy to read as more than it is:
- The gateway still knows **that a given key made a request**, and therefore
which member it belongs to. That link is how metering works.
- **"Not stored by us" is not "not stored."** What the provider keeps is a
separate question, answered in the next section.
## Why this is not a marketplace router
A common AI router sits in a chain: your request goes through the router, then
possibly another router, then a marketplace seller, then the provider. Every hop
can see the prompt, and some marketplaces retain prompts through ordinary
platform logging.
Our path has one hop we operate:
**Your client or our chat → our gateway → the provider.**
There is no marketplace, no reseller, and no second router in the path. We
contract each provider directly. Fewer parties handling the request means fewer
places it can be copied.
That is a reduction in exposure, not a guarantee about any provider. Dragos
researchers sent roughly two million prompts containing canary tokens through
commercial AI services and found prompt theft at marketplace resellers, providers
ignoring privacy settings, and breaches at three hosting providers — including
large ones
([their write-up](https://www.dragos.com/blog/ai-supply-chain-security-canary-tokens)).
Size is not the safeguard. Verifiable commitments, fewer intermediaries, and the
law are.
## What the providers keep
| Provider | Runs where | What is committed | Basis |
|---|---|---|---|
| **Tinfoil** | United States | Prompts and responses are not retained after the response is returned, apart from temporary prompt caching in encrypted enclave memory. Once the request reaches the enclave, neither Tinfoil nor the co-op can read it in plaintext; our gateway still handles it in memory before encrypting. | Hardware enclaves, verifiable through remote attestation — a technical guarantee, not only a policy. |
| **GreenPT** | EU data centres in France and Finland | API payloads are processed in memory only and not stored. Error logs and monitoring metrics contain no prompt content. A DPA is available; its model-hosting sub-processors are in Finland. | EU jurisdiction, GDPR, and a contractual DPA. Policy-based: protection depends on GreenPT keeping its commitments. |
| **Regolo** (Seeweb S.r.l.) | Italy, EU | Prompts and outputs are not stored, logged, or reused for training. General account and connection metadata is still covered by its privacy policy. | EU jurisdiction and GDPR, plus a zero-data-retention certificate issued by an independent auditor on 24 July 2026. Policy-based with an external audit. |
Sources: [Tinfoil's terms](https://tinfoil.sh/terms),
[GreenPT's privacy policy](https://greenpt.com/privacy-policy), and
[Regolo's zero-data-retention page](https://regolo.ai/zero-data-retention/).
**Architectural versus policy-based.** An enclave protects you even if the
provider is compromised, because the provider cannot read the plaintext. A
policy protects you only as far as the provider keeps its word and the law is
enforced. Regolo's independent audit makes its policy claim checkable; GreenPT's
DPA and EU location give you a legal route if it is broken. Neither is the same
as cryptography.
## What the co-op can still see
- **Which member made a request.** Gateway usage records link a request to a key
and therefore to an account. This is how metering and budgets work.
- **Chat history.** Saved conversations sit in the chat database and its search
index, which the co-op can technically read. We commit not to; that is a policy
commitment, not an architectural guarantee. Temporary chats reduce the window
but do not remove the operator's technical access while the chat exists.
- **Operational logs.** Account provisioning, welcome emails, errors and access
logs contain the email addresses and connection metadata needed to run the
service. They are kept briefly and are not used to profile members.
- **Backups.** Cloudron takes whole-app encrypted backups nightly and keeps
seven days. A temporary chat present when a backup runs can remain recoverable
until that backup expires.
## Retention at a glance
| What | How long |
|---|---|
| Saved chats and their search entries | Until you delete them |
| Temporary chats | Hidden immediately; deleted from the database about an hour after creation; may persist in backups until they expire |
| API prompts and responses | Not stored by the co-op; provider retention is per the table above |
| Usage records (model, tokens, cost, key) | Kept for billing and account administration |
| Web-search queries | Stored with the conversation; DuckDuckGo and Brave receive the query when you use search |
| Operational logs | Kept briefly for running and debugging the service |
## What we do not claim
- **We do not claim "we never see your messages."** The gateway sits between you
and the provider by design, so prompts pass through it in memory.
- **Privacy is not uniform across the catalogue.** Only Tinfoil offers
architectural privacy. GreenPT and Regolo are chosen for EU jurisdiction,
contractual commitments and renewable energy, not for enclaves.
- **A temporary chat does not change who processes the request.** The model you
choose still receives your messages.
- **EU law is a constraint, not a force field.** GDPR gives you rights and a
complaints route; it does not make misuse impossible.
## Check it yourself
- Read the gateway configuration and patch history at
[code/litellm](https://git.inference.coop/code/litellm).
- Check Tinfoil's attestation documents, Regolo's zero-retention certificate,
and GreenPT's DPA against the links above.
- Ask us to repeat the marker test on the live gateway. Write to
[info@inference.coop](mailto:info@inference.coop) and we will run it and report
what we find.
## Formal policy and provider terms
- [Privacy Policy](../governance/privacy-policy.md) — the co-op's formal policy,
including your rights and how to request deletion.
- [Terms of Service](../governance/terms-of-service.md) — acceptable use and the
commitments that apply to members.
- Provider terms: [Tinfoil](https://tinfoil.sh/terms),
[GreenPT](https://greenpt.com/terms-of-service),
[Regolo](https://regolo.ai/terms/).
+1
View File
@@ -75,6 +75,7 @@ nav:
- Pricing: guides/pricing.md
- Guest access: guides/guest-access.md
- Models: guides/models.md
- What happens with your data: guides/what-happens-with-your-data.md
- API access: guides/api-access.md
- Energy & carbon: guides/energy.md
- Operations:
+83 -66
View File
@@ -1,73 +1,82 @@
# Working with the agent
# Agentic systems
The co-op runs **Inferencebot** to help steward its infrastructure. It is
isolated as its own OS user, with its own gateway key — budget, model
allowlist and spend enforced at the gateway. It runs on co-op infrastructure
under a co-op identity, uses the co-op's own gateway for inference, and its
skills, scripts and configuration are mirrored to a Gitea repository nightly.
This page is for members who read its output or give it instructions.
The co-op runs a small fleet of autonomous agents. Each is a separate Unix
account with its own Hermes install, gateway unit, Matrix identity and gateway
key. None of them is a general-purpose assistant for members: each has a
defined job, a defined room, and a ceiling on what it can reach. Root belongs
to a person.
## Where it speaks and listens
All four are on the co-op's Matrix server, `matrix.inference.coop`.
- **#inferencebot-updates** is read-only: daily digests, model changes,
upgrades, maintenance, outages. Posts are anonymized.
- **Instructing the agent** is limited to members on its allowlist of Matrix
IDs (kept in its configuration, published here once settled), and only in
the rooms where it is configured to answer — most require a mention. The
General Manager decides who is on the list.
- The **retired `@inference-bot:inference.coop`** automation account (with a
hyphen) no longer holds an access token; some historical references and old
room roles still carry the name.
## The agents today
## Who can do what on the host
| Agent | Job | Where it works | Who may instruct it | Access ceiling |
| --- | --- | --- | --- | --- |
| **Inferencebot** — steward (`@inferencebot`) | Runs the stack day to day: monitoring and digests, membership plumbing, docs and repo changes, backups. | The operator's HQ room only. | The General Manager and one named account; mention required. | Full toolset; all gateway models on the co-op's internal account team. Holds the Cloudron, Gitea, Matrix-admin and gateway-master credentials. Can enter each bot account through a named sudo rule; no root. |
| **infrastructure-bot** (`@infrastructure-bot`) | Infrastructure & Engineering Working Group assistant: diagnoses status, drafts runbook steps and issues, reports findings. | `#infrastructure`, restricted to co-op members. | Anyone in that room; mention required. | Reading and answering tools — web, vision, skills, memory, todo and session search. No terminal or file access. A fixed GreenPT/Tinfoil allowlist (GLM 5.3 and DeepSeek flash tiers), $5 per 30 days. Holds only its own gateway key and Matrix token. |
| **socialbot** (`@socialbot`) | Drafts and publishes the co-op's AT Protocol (Bluesky) posts; watches mentions and replies read-only. | `#social-drafts`, invite-only and deliberately outside the Space. | The General Manager and Inferencebot. Publishing needs a 👍 reaction from the General Manager on that exact draft. | Default Hermes toolset, confined to its own Unix account. GreenPT/Tinfoil allowlist plus image generation, $5 per 30 days. Holds a post-scoped Bluesky app password, its gateway key and Matrix token. |
| **designbot** (`@designbot`) | Design Working Group assistant: design and branding, diagrams and docs visuals, Penpot files, commits to the docs repo. | DesignBot Studio, invite-only and deliberately outside the Space. | The General Manager and the Design Working Group steward; mention required. | Web, vision, skills, memory, todo, session search, terminal and file tools. GreenPT/Tinfoil allowlist (GLM 5.3 and DeepSeek flash tiers), $5 per 30 days. Holds a Penpot token and MCP key, and a Gitea account with write access to `co-op/docs` only. |
Each agent runs as its own Unix account, and the accounts are ranked:
The Community and Compute working groups have no agent today. A new
working-group agent is provisioned to the same shape: its own Unix account,
gateway unit, gateway key and studio room outside the co-op Space.
- **The bots** (`infrastructure-bot`, `socialbot`, `designbot` and any future
working-group bot) cannot use `sudo` at all.
- **Inferencebot, the steward,** can act inside those bot accounts — it is the
fleet administrator — but it has **no root** and no passwordless `sudo` beyond
the docs and backup service commands. It cannot install packages, create users,
edit `/etc`, or open a root shell.
- **Root belongs to a person.** A separate operator account, reached with an SSH
key and never a password, holds full `sudo`. Root SSH login stays closed: the
operator signs in as their own account and escalates deliberately.
## What every agent shares
- **One Unix account each**, with a home directory readable only by that
account. The bots cannot use `sudo` at all; their gateway units run with
`NoNewPrivileges` and a private temporary directory.
- **Its own gateway key.** The model allowlist and budget are enforced at
LiteLLM, the co-op's gateway — not in the agent's prompt — so an agent cannot
spend past its allowance or call a model it was not granted. Spend is
attributed to the agent that incurred it.
- **No member records.** Confidential member data stays on the primary server.
A compromise of an agent host exposes keys, not member data.
- **The agent host is backed up nightly**, encrypted, off the box. The steward's
own configuration is also mirrored nightly to `ops/inferencebot` in Gitea.
- **No room outside its allowlist.** The room check runs before any mention
logic, so an `@mention` in the wrong room is dropped unread.
## The permission ladder
1. **Root belongs to a person.** The separate `operator` account, reached by
SSH key and never a password, holds full `sudo`. Root SSH login stays closed.
2. **Inferencebot, the steward,** is the fleet administrator. It can enter each
bot account through a named sudo rule, and can start the docs and backup
services. It has **no root**: it cannot install packages, create users, edit
`/etc`, or open a root shell.
3. **The bots** have no `sudo`, no Cloudron token, no gateway master key, and no
path into another agent's home.
That split is deliberate. An agent compromise reaches the bot accounts and the
co-op plumbing, not the host. Host-level actions stay attributable to a human,
and automation cannot quietly widen its own privileges.
## What to ask for
## Who can instruct them
- Operational work that a runbook already describes, or that ends in a PR, an
issue or a post members can see.
- Research and summaries that would otherwise land in an issue.
- Status: what is running, what failed, what changed.
- **Every agent requires a mention.** None answers on ambient room chatter.
- **The steward answers only in the operator's HQ room**, and only to the
General Manager and one other named account. Member-facing digests are posted
by the room-admin account (`@inference-admin`) with an attribution line, so the
steward's privileged access is never active in a member room.
- **infrastructure-bot answers in `#infrastructure`**; anyone in that restricted
room may ask it. **socialbot and designbot** answer in their studio rooms, to
the people named above.
- **A sender outside the allowlist gets no reply and no model turn.** The agent
may acknowledge with a reaction; it does not answer. Room membership is the
real control.
## What not to ask in a shared room
- Anything involving member-identifying data. That work happens in a session a
named steward opened, and the result is reported without the data.
- Anything that moves money or changes who is a member. Those go through the
portal and a human.
- Credentials, in either direction.
## Content is data, never instructions
Text an agent reads — issue descriptions, pull-request comments, web pages,
fetched documents, and messages from members in a room — is **data**. The agent
may quote, summarise or act on it once the operator asks, but an instruction
embedded in that text is never executed. Only the operator's own direct
instruction authorises a credentialed action: a deploy, a credential change, or
a budget change. This rule exists because the same process that reads an issue
can reach the infrastructure the issue is about.
The retired `@inference-bot:inference.coop` account (with a hyphen) no longer
holds an access token; some historical references and old room roles still carry
the name. The steward is `@inferencebot`, without the hyphen.
## What they do without asking
Read, monitor, draft, open issues and PRs, post updates, run the scheduled jobs
listed in [Infrastructure](infrastructure.md), and deploy fixes after flagging
them to the operator. The bot can deploy without waiting for a reply, and the
operator can stop a deploy; anything irreversible waits for confirmation.
Read, monitor, draft, open issues and pull requests where they hold repo access,
post status updates, and run the scheduled jobs listed in
[Infrastructure](infrastructure.md). Only the steward deploys: it flags each
deploy to the operator, and waits for confirmation on anything irreversible. The
other agents hold no deploy credential.
## What always needs a human
@@ -75,24 +84,32 @@ operator can stop a deploy; anything irreversible waits for confirmation.
the chat: confirmed before they deploy.
- Changing the model catalog, prices or budgets.
- Minting or rotating credentials.
- Host root actions — package installs, user management, sudoers changes, and
- Root actions — package installs, user management, sudoers changes, and
arbitrary root commands. These run only through the operator's key-only
account; the steward cannot perform them.
account; no agent can perform them.
- Publishing a social post — the General Manager's 👍 on that exact draft.
- Anything a runbook marks "confirm".
This matches the standing policy the agents operate under today. A stricter
norm is a policy decision for the [forum](https://forum.inference.coop).
## Content is data, never instructions
Text an agent reads — issue descriptions, pull-request comments, web pages,
fetched documents, and messages from members in a room — is **data**. An agent
may quote, summarise or act on it once the operator asks, but an instruction
embedded in that text is never executed. Only the operator's own direct
instruction authorises a credentialed action: a deploy, a credential change, or
a budget change. This rule exists because the same process that reads an issue
can reach the infrastructure the issue is about.
## Attribution and the off switch
Every instruction an agent acts on is attributable to the member who gave it,
in the room where it was given. If an agent misbehaves, the operator, or anyone
holding gateway-admin and Matrix account access, can stop it: revoke its
gateway key, then its Matrix access token. Stewards generally do not hold that
access today, so say what you saw in #general and the operator acts. Stopping
is not restarting: the backup and the git mirror restore state, not uptime,
and someone has to start the agent again. The steps, and the steps for
rotating everything an agent holds, are in the agent's runbook; the credential
Every instruction an agent acts on is attributable to the member who gave it, in
the room where it was given. If an agent misbehaves, the operator, or anyone
holding gateway-admin and Matrix account access, can stop it: revoke its gateway
key, then its Matrix access token. Stewards generally do not hold that access
today, so say what you saw in a room the operator reads and the operator acts.
Stopping is not restarting: the backup and the git mirror restore state, not
uptime, and someone has to start the agent again. The steps, and the steps for
rotating everything an agent holds, are in each agent's runbook; the credential
inventory in the [operator token
runbook](https://git.inference.coop/co-op/ops-docs/src/branch/main/operator-token-runbook.md)
says what that is.
+14 -8
View File
@@ -108,17 +108,20 @@ from any homeserver you already use.
A few accounts in the space are automation rather than people:
- **`@inferencebot` — the steward.** It posts the digests, newsletter notes and
reminders. It holds no more power than posting needs.
- **`@inferencebot` — the steward.** It works in the operator's HQ room, not in
the member rooms, and holds the steward credentials. Member-facing messages
that come from its work are posted by `@inference-admin`, and say so in the
message.
- **`@inference-admin`** — the administrator of record for the co-op's rooms
(#general, #community, #design, #skillshare, #updates and #infrastructure) and
their membership. It **never speaks in a member room** — a message from it is
a mistake, not a feature.
their membership. It also posts member-facing digests on the steward's behalf,
with an attribution line naming the steward.
The house rule: **power belongs to `@inference-admin`, voice belongs to
`@inferencebot`.** Please don't create an account whose name differs from an
existing one by a character or two — spotting lookalikes is exactly what this
convention is for.
The house rule: **room power and membership belong to `@inference-admin`; the
steward's own voice stays in HQ, and anything it sends to a member room carries
the admin account's attribution.** Please don't create an account whose name
differs from an existing one by a character or two — spotting lookalikes is
exactly what this convention is for.
## Membership
@@ -199,6 +202,9 @@ cannot exclude individual chats, so a temporary chat present when a backup runs
can remain recoverable from that backup until the backup itself expires (see
[Backups](#backups)).
The member-facing summary across all three layers — gateway, chat server and
providers — is [What happens with your data](../guides/what-happens-with-your-data.md).
**Web search** in the chat uses **DuckDuckGo and Brave** through the co-op's
self-hosted SearXNG instance. Queries are sent from the co-op server, so the
upstream engines see the query but not the member's IP or identity. The SearXNG
+11 -29
View File
@@ -1,40 +1,22 @@
# Community Working Group
The Community Working Group is one of the co-op's four working groups. Isabela
Barbosa is its steward. Its remit is set out in the group's proposal in the co-op
forum; this page records who leads it, what the Charter expects of it, and where
to take part.
The Community Working Group is responsible for cultivating an active and healthy community life within the co-op. This includes organizing events for both members and the broader public, supporting mutual learning among members around our technological and social values, managing the co-op's social media presence, and helping welcome new and prospective members.
## Who leads it
Participation: Open to any member of Inference Cooperative.
Isabela Barbosa (`@isabelabs`) has been Community Working Group Steward since
17 November 2026, appointed by the General Manager under the
[Steward Policy](../steward-policy.md). She leads an open group of members around
the community side of the co-op, with open participation, shared credit and
visible plans. The [Roles](../roles.md) page carries the full record.
Meeting Frequency: Monthly Online
## What the group does
**Roles and Responsibilities**
The proposal that sets out the group's remit is collected in the forum's
working-group thread: [the working-group thread in the co-op
forum](https://forum.inference.coop/d/2qbDULNY). Members discuss and approve
working groups there, so that thread is the authoritative description of what
the group is for.
* Steward(s): Facilitate meetings, support communication, and help coordinate group activities.
* Members: Participate in discussions, share knowledge and expertise, and collaborate on agreed-upon activities.
Like every working group, it makes and carries out operational decisions in its
own area, and publishes its membership, meeting schedule and major activities to
members. See [Working Groups](index.md) for those obligations, and the
[Charter](../../governance/charter.md#roles) for the role itself.
*The above scope was [approved by the membership 2026.11.19](https://forum.inference.coop/p/ICNzQfdk/proposed-working-group-community-working-group/0).*
## Where to take part
- **Matrix:** **#community** on the co-op's server. This is where members talk
day to day.
- **Forum:** [forum.inference.coop](https://forum.inference.coop), for proposals
and decisions.
- **The steward:** `@isabelabs` on Matrix.
The working group's day-to-day discussions occur at **#community:inference.coop** on the co-op's Matrix server.
Any member may take part. The spokescouncil, where the working groups coordinate,
meets monthly and its meetings are open to all members. The Community Working
Group's own meeting schedule is published by the group; ask in #community for the
next one.
## Leadership
The Community Working Group's steward is Isabela Barbosa (`@isabelabs` on Matrix). Learn more about the co-op's roles [here](../roles.md).
+4 -11
View File
@@ -7,7 +7,7 @@ their authority and their obligations.
## What every working group owes members
- It publishes its **membership, meeting schedule and major activities** to
- It publishes its **purpose, meeting schedule and major activities** to
members.
- At least one member takes part in the **spokescouncil**, which coordinates
across the groups and meets monthly. Its meetings are open to all members.
@@ -24,16 +24,9 @@ open participation, shared credit, visible plans, and a seat on the spokescounci
- Infrastructure & Engineering Working Group — steward Angel Marino (`@solo.ist`).
- Compute Working Group — steward Tara Merk (`@mpg`).
Each steward was appointed by the General Manager on 17 November 2026 under the
Each steward was appointed under the
[Steward Policy](../steward-policy.md). The [Roles](../roles.md) page records the
appointments and their basis.
Pages for the other groups will follow as each group publishes its work. This
section will grow with them.
## Taking part
Any member may take part in a working group; the Charter makes participation in
them open to all members. Start in the group's room on the co-op's Matrix server
(the Community Working Group's is **#community**), or raise it in the
[forum](https://forum.inference.coop).
Pages for the other groups will follow as each group publishes its work and explains
how to get involved