Author SHA1 Message Date
inference-admin abadbfef40 Merge pull request 'Terms: permit serving others through the co-op; state the notice and grace we actually give' (#10) from tos/institutional-use-and-termination-notice into main
Reviewed-on: #10
2026-11-22 00:14:06 +00:00
inference-admin 0ad009894c Updated date 2026-11-22 00:13:52 +00:00
inference-admin e72adad923 Merge pull request 'docs(agentic-systems): cover the whole agent fleet, not one bot' (#20) from docs/agentic-systems-fleet into main
Reviewed-on: #20
2026-11-21 16:46:09 +00:00
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-admin 03d357f1e0 Terms: permit serving others through the co-op; state the notice and grace we actually give
Two edits, both from the institutional-membership discussion (co-op/support#32).

**§4.** The prohibition on reselling or redistributing access is removed — the
bullet now prohibits sharing account credentials and nothing else — and §4 ends
with the permission stated plainly: you may provide a service of your own, so
long as your use remains subject to these Terms and you carry the acceptable-use
and privacy expectations to the people you serve. Resale stops being the thing we
prohibit; failing to carry the Terms downstream is the thing we prohibit. That
also settles the question raised in #32 of whether charging at-cost rates counts
as resale: it no longer has to.

**§8.** Termination now describes what the system does rather than what we might
wish it did: we write to you before anything changes, you get a seven-day grace
period with access continuing, and if no contribution arrives the monthly
allowance stops renewing and access pauses while the account and data stay in
place. Removal per the Charter is separate and unchanged.
2026-11-13 23:19:33 +00:00
4 changed files with 101 additions and 78 deletions

No files matched your search

+6 -3
View File
@@ -1,6 +1,6 @@
# Terms of Service
**Last updated:** October 6, 2026
**Last updated:** November 21, 2026
## In plain language
@@ -55,10 +55,12 @@ You agree not to use the service to:
- Use AI outputs as the **sole basis for consequential decisions** — legal, medical, financial, employment, housing, or safety-critical — without appropriate human review and professional oversight.
- Use the service for **high-risk or fail-safe** applications (e.g. critical infrastructure, life-support, weapons systems).
- Attempt to circumvent usage limits, the privacy architecture, or rate limits.
- Share your account credentials, or resell or redistribute access to the service.
- Share your account credentials.
You are **responsible for what you submit and what you do with AI outputs**, and you must have the rights needed to submit your content.
You may use the service to provide a service of your own, as long as your use remains subject to these Terms, along with the acceptable-use and privacy expectations in §4 and §7.
## 5. Usage limits
- Membership includes a **monthly credit budget** (currently $15 of usage, the same for every member regardless of what you pay).
@@ -83,7 +85,8 @@ Privacy is a core value, but it is **not uniform across the service** — and th
- You may leave at any time by cancelling on Open Collective.
- On leaving, your account is deactivated (data preserved for reactivation). You may request full deletion.
- We may remove members per the Charter (Code of Conduct, non-payment).
- **If your dues stop**, we write to you before anything changes, and you then have a **seven-day grace period** in which your access continues. If no contribution arrives, your monthly allowance stops renewing and your access pauses until it resumes. Your account and your data stay in place.
- We may remove members per the Charter (Code of Conduct, continued non-payment).
## 9. Governance
+1 -1
View File
@@ -72,7 +72,7 @@ law are.
| 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. Neither Tinfoil nor the co-op can read the exchange in plaintext at inference time. | Hardware enclaves, verifiable through remote attestation — a technical guarantee, not only a policy. |
| **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. |
+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.
+11 -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