Move governance docs into governance/ folder with redirects; nav mirrors structure

This commit is contained in:
inference-bot committed 2026-11-12 02:51:39 +00:00
1 parent c041e88fff
commit 4ececfa584
9 files changed
+28 -21

No files matched your search

+52
View File
@@ -0,0 +1,52 @@
# Inference Cooperative Charter
## Preamble
The Inference Cooperative exists to enable the people who use its AI infrastructure to co-govern it. We came together to build and run an alternative to extractive, profit-driven AI—a service owned and directed by its members, committed to pursuing ethical practices, and governed cooperatively. This charter is our core governing document. It sets out how we make decisions together.
## Values
In addition to the international [cooperative principles](https://www.ica.coop/en/cooperatives/cooperative-identity/), we share these basic commitments:
- **Participation.** Our service is accountable to the people who use it, and they both can and should have an active role in shaping it.
- **Experimentation.** In order to learn together, we will maintain a spirit of exploration and experimentation, and be respectful of all members' levels of knowledge and expertise.
- **Sustainability.** We commit, wherever possible, to minimizing harm to natural ecologies and to promoting environmental justice.
- **Trustworthiness.** We seek to provide reliable service to one another and protect each other's privacy, in contrast to an industry widely characterized by surveillance.
- **Transparency.** The co-op should make its operations and decisions as available as possible to members, and to share our learnings with the wider world.
## Roles
- **Members** are the heart of the co-op. All account holders currently [contributing monthly dues](https://opencollective.com/inference-cooperative) are considered members and may participate in decision-making and working groups. Members may be sanctioned or removed for violating co-op rules by the GM or a designated working group.
- A **general manager** oversees day-to-day operations and implements member decisions, through their own actions or additional roles that they delegate. The GM is accountable to members and may be replaced by them through a policy decision.
- **Working groups** make and carry out operational decisions within their own purview. They should be formally established, modified, and disbanded through a policy decision, and they are obligated, at minimum, to publish to members their membership, meeting schedule, and major activities.
- A **spokescouncil** coordinates across working groups, and all working groups are responsible for ensuring that at least one member consistently participates. The spokescouncil meets monthly, and meetings are open to all members.
## Decisions
The co-op operates through the practice of modified [policy governance](https://en.wikipedia.org/wiki/Policy_Governance). Member decisions should seek to instill responsibility and trust in role-holders, while guiding them only through goal-setting and necessary constraints. Role-holders should act on the basis of their expertise and the co-op's values, as well as through consultation with members.
**Policy.** Any member may propose a policy in the co-op's [forum](https://forum.inference.coop/). A proposal requires at least one vote from another member and stays open for 7 days. It passes by consent as long as it receives support from at least 60% of voting members. If a member raises a block—a reasoned objection that the proposal would seriously harm the cooperative—it requires 75% support. The proposal's author is always encouraged to revise the proposal based on feedback from other members and restart the process.
**Charter.** Changes to this charter require a proposal open for **14 days**, along with approval by 75% of voting members, regardless of blocks. Policy decisions must not contradict the charter.
Proposals may be adjusted with modest changes during the open discussion period by the proposer, as long as changes are announced in the discussion.
This governance design is oriented around a relatively small community. Upon reaching 250 members, we commit to revising this charter with a larger community in mind.
## Disputes
We regard disputes as an opportunity to learn and grow. Members should try to work things out directly with each other first. When necessary, disputes either among members or between a member and the co-op should be brought to the disputes working group—or, if one does not exist, the GM. Disputes that cannot be adequately addressed within the co-op may be escalated to the parent legal entity, which may in turn forward them to the relevant legal jurisdiction.
## Agreements
This charter is the core governing document. Members are also bound by the following agreements:
* [Code of Conduct](../code-of-conduct.md)
* [Terms of Service](../terms-of-service.md)
* [Privacy Policy](../privacy-policy.md)
## Legal entity
The Inference Cooperative operates under the fiscal sponsorship of [Metagov](https://metagov.org/), and our governance is subject to [Metagov's fiscal sponsorship policy](https://metagov.pubpub.org/pub/7bj5ia5g/release/1). We commit to honor that agreement and to operate in a spirit that avoids causing harm to our fiscal host. Metagov may rescind a decision it deems at odds with its policies.
If that commitment is ever at odds with the cooperative's evolution, the cooperative may move to a different fiscal host. Changing fiscal hosts should occur through a revision of this Charter.
+91
View File
@@ -0,0 +1,91 @@
# Contributor Covenant 3.0 Code of Conduct
## Our Pledge
We pledge to make our community welcoming, safe, and equitable for all.
We are committed to fostering an environment that respects and promotes the dignity, rights, and contributions of all individuals, regardless of characteristics including race, ethnicity, caste, color, age, physical characteristics, neurodiversity, disability, sex or gender, gender identity or expression, sexual orientation, language, philosophy or religion, national or social origin, socio-economic position, level of education, or other status. The same privileges of participation are extended to everyone who participates in good faith and in accordance with this Covenant.
## Encouraged Behaviors
While acknowledging differences in social norms, we all strive to meet our community's expectations for positive behavior. We also understand that our words and actions may be interpreted differently than we intend based on culture, background, or native language.
With these considerations in mind, we agree to behave mindfully toward each other and act in ways that center our shared values, including:
1. Respecting the **purpose of our community**, our activities, and our ways of gathering.
2. Engaging **kindly and honestly** with others.
3. Respecting **different viewpoints** and experiences.
4. **Taking responsibility** for our actions and contributions.
5. Gracefully giving and accepting **constructive feedback**.
6. Committing to **repairing harm** when it occurs.
7. Behaving in other ways that promote and sustain the **well-being of our community**.
## Restricted Behaviors
We agree to restrict the following behaviors in our community. Instances, threats, and promotion of these behaviors are violations of this Code of Conduct.
1. **Harassment.** Violating explicitly expressed boundaries or engaging in unnecessary personal attention after any clear request to stop.
2. **Character attacks.** Making insulting, demeaning, or pejorative comments directed at a community member or group of people.
3. **Stereotyping or discrimination.** Characterizing anyone’s personality or behavior on the basis of immutable identities or traits.
4. **Sexualization.** Behaving in a way that would generally be considered inappropriately intimate in the context or purpose of the community.
5. **Violating confidentiality**. Sharing or acting on someone's personal or private information without their permission.
6. **Endangerment.** Causing, encouraging, or threatening violence or other harm toward any person or group.
7. Behaving in other ways that **threaten the well-being** of our community.
### Other Restrictions
1. **Misleading identity.** Impersonating someone else for any reason, or pretending to be someone else to evade enforcement actions.
2. **Failing to credit sources.** Not properly crediting the sources of content you contribute.
3. **Promotional materials**. Sharing marketing or other commercial content in a way that is outside the norms of the community.
4. **Irresponsible communication.** Failing to responsibly present content which includes, links or describes any other restricted behaviors.
## Reporting an Issue
Tensions can occur between community members even when they are trying their best to collaborate. Not every conflict represents a code of conduct violation, and this Code of Conduct reinforces encouraged behaviors and norms that can help avoid conflicts and minimize harm.
When an incident does occur, it is important to report it promptly. To report a possible violation, **contact the administrative team at info@inference.coop.**
Community Moderators take reports of violations seriously and will make every effort to respond in a timely manner. They will investigate all reports of code of conduct violations, reviewing messages, logs, and recordings, or interviewing witnesses and other participants. Community Moderators will keep investigation and enforcement actions as transparent as possible while prioritizing safety and confidentiality. In order to honor these values, enforcement actions are carried out in private with the involved parties, but communicating to the whole community may be part of a mutually agreed upon resolution.
## Addressing and Repairing Harm
**The Community Moderators consist of the disputes working group or, if it is not yet formed, the General Manager.**
If an investigation by the Community Moderators finds that this Code of Conduct has been violated, the following enforcement ladder may be used to determine how best to repair harm, based on the incident's impact on the individuals involved and the community as a whole. Depending on the severity of a violation, lower rungs on the ladder may be skipped.
1) Warning
1) Event: A violation involving a single incident or series of incidents.
2) Consequence: A private, written warning from the Community Moderators.
3) Repair: Examples of repair include a private written apology, acknowledgement of responsibility, and seeking clarification on expectations.
2) Temporarily Limited Activities
1) Event: A repeated incidence of a violation that previously resulted in a warning, or the first incidence of a more serious violation.
2) Consequence: A private, written warning with a time-limited cooldown period designed to underscore the seriousness of the situation and give the community members involved time to process the incident. The cooldown period may be limited to particular communication channels or interactions with particular community members.
3) Repair: Examples of repair may include making an apology, using the cooldown period to reflect on actions and impact, and being thoughtful about re-entering community spaces after the period is over.
3) Temporary Suspension
1) Event: A pattern of repeated violation which the Community Moderators have tried to address with warnings, or a single serious violation.
2) Consequence: A private written warning with conditions for return from suspension. In general, temporary suspensions give the person being suspended time to reflect upon their behavior and possible corrective actions.
3) Repair: Examples of repair include respecting the spirit of the suspension, meeting the specified conditions for return, and being thoughtful about how to reintegrate with the community when the suspension is lifted.
4) Permanent Ban
1) Event: A pattern of repeated code of conduct violations that other steps on the ladder have failed to resolve, or a violation so serious that the Community Moderators determine there is no way to keep the community safe with this person as a member.
2) Consequence: Access to all community spaces, tools, and communication channels is removed. In general, permanent bans should be rarely used, should have strong reasoning behind them, and should only be resorted to if working through other remedies has failed to change the behavior.
3) Repair: There is no possible repair in cases of this severity.
This enforcement ladder is intended as a guideline. It does not limit the ability of Community Managers to use their discretion and judgment, in keeping with the best interests of our community.
## Scope
This Code of Conduct applies within all community spaces, and also applies when an individual is officially representing the community in public or other spaces. Examples of representing our community include using an official email address, posting via an official social media account, or acting as an appointed representative at an online or offline event.
## Attribution
This Code of Conduct is adapted from the Contributor Covenant, version 3.0, permanently available at [https://www.contributor-covenant.org/version/3/0/](https://www.contributor-covenant.org/version/3/0/).
Contributor Covenant is stewarded by the Organization for Ethical Source and licensed under CC BY-SA 4.0. To view a copy of this license, visit [https://creativecommons.org/licenses/by-sa/4.0/](https://creativecommons.org/licenses/by-sa/4.0/)
For answers to common questions about Contributor Covenant, see the FAQ at [https://www.contributor-covenant.org/faq](https://www.contributor-covenant.org/faq). Translations are provided at [https://www.contributor-covenant.org/translations](https://www.contributor-covenant.org/translations). Additional enforcement and community guideline resources can be found at [https://www.contributor-covenant.org/resources](https://www.contributor-covenant.org/resources). The enforcement ladder was inspired by the work of [Mozilla’s code of conduct team](https://github.com/mozilla/inclusion).
+74
View File
@@ -0,0 +1,74 @@
# Open Questions for Member Discussion
A living list of some of the decisions the cooperative needs to make.
---
## Privacy & Infrastructure
### Green energy vs. privacy — when we can't have both?
Our inference runs through Tinfoil (TEE-protected, verifiable privacy), but Tinfoil's energy mix is not disclosed. Self-hosting on renewable-powered hardware (e.g. Hetzner hydropower, Scaleway wind+hydro) would be greener but would lose the TEE privacy guarantee at our current scale.
- **Privacy-first (current):** TEE inference, energy mix unknown.
- **Green-first:** renewable hosting, but policy-based privacy (we *promise* not to read data, but can't *prove* it architecturally).
**Question:** When the two conflict, which value wins? Is there a threshold (e.g. member count, cost) at which we'd switch?
### Which models should we offer?
We currently expose three chat models: DeepSeek V4 Flash (default), GPT-OSS 120B, and GLM-5.3 Flash. Tinfoil's full catalog also includes GLM-5.3 (full), Kimi K3, Llama 3.3 70B, Gemma 4 31B, and others.
**Question:** Which models should members have access to? Should we offer a curated few (simpler, cheaper, easier to govern) or the full catalog (more choice, but more cost and governance overhead)? Who decides when to add or remove a model — the General Manager, or members via Loomio?
### Should personal data be collectively or individually managed?
Currently chat history is stored on co-op servers. We could potentially switch to storing it in browser cache, which would be more private but less convenient. How do we balance privacy and convenience?
### Should we prioritize running and owning our own infrastructure, or are we comfortable collectively buying tokens from others?
---
## Pricing & Fairness
### How should pricing account for unequal usage?
Members currently pay dues on a sliding scale (from $5/month) with a flat $15/month credit budget. But usage is unequal — some members use far more tokens than others.
- **Flat (current):** simple, predictable, but heavy users subsidize light users (or vice versa).
- **Usage-based:** pay for what you use, but unpredictable and may discourage experimentation.
- **Tiered:** a few usage bands, balancing simplicity and fairness.
- **Sliding-scale + usage cap:** pay what you can afford, with a shared usage ceiling.
**Question:** What pricing model best balances fairness, simplicity, and the cooperative's solidarity values? How do we handle a member who consistently exceeds their budget?
---
## Governance & Membership
### How do we handle institutional members?
AI Potluck's "government-as-contributor" framing suggests a path for institutions (universities, municipalities) to contribute compute or data without owning the whole.
**Question:** Should we create an institutional membership tier? What would institutions contribute, and what would they get?
---
## Values & Product
### Should we adopt "provenance transparency" as a product feature?
AI Potluck commits to "every response shows its provenance: the model, the organization, the compute, the country." We could surface which model served each response (already possible via LiteLLM).
**Question:** Is this worth building? What's the right level of transparency without cluttering the chat?
### Should we articulate an "anti-engagement" stance?
AI Potluck explicitly rejects the extractive engagement model ("AI that wants you to turn it off," "doesn't sell you sycophancy"). A cooperative has no engagement-maximization incentive — a structural advantage.
**Question:** Should we name this explicitly in our charter and product copy? What does "AI for human flourishing, not engagement" mean concretely for our chat?
---
*This list is maintained in the [docs repository](https://git.inference.coop/co-op/docs). Add questions via pull request or raise them on [Loomio](https://forum.inference.coop).*
+130
View File
@@ -0,0 +1,130 @@
# Privacy Policy
**Last updated:** October 28, 2026
## In plain language
- We collect only what we need: your email, name, and basic usage data.
- We offer a **changing variety of models with different privacy and value affordances** — some run in encrypted enclaves we cannot read, others differ. **You are responsible for assessing each model's properties and picking the one that fits your needs.**
- We **do** store your chat history on our server (so you can revisit it). We promise not to read it, but this is a promise, not a technical guarantee. **Temporary chats** are the exception: nothing is stored at all, and you can make them your default — see §4 if you'd like sensitive conversations to leave nothing behind.
- We never train on your data, and we never sell it.
- You can export or delete your data at any time.
The full policy is below. Questions? info@inference.coop.
---
## 1. Our privacy philosophy
The Inference Cooperative is a member-governed project. We are **not** an ad-supported or data-extractive business — we have no incentive to read or sell your data. Privacy is a structural value, built into how we operate.
## 2. What we collect
- **Account data:** your email and name (from Open Collective).
- **Membership data:** your contribution status and role.
- **Usage data:** token counts, model used, and timestamps (for metering your monthly budget).
- **Content:** your prompts and the AI's responses. Whether we keep them depends on how you use the service: in the **chat interface** they are saved as your chat history, while through the **API** they are not stored at all. See §4.
- **Billing data:** handled by Open Collective — we do not see full payment details.
## 3. Privacy depends on the model you choose
We serve a **changing catalog of models from multiple providers, and they do not all offer the same privacy**. Models differ in their affordances — some run inference inside **encrypted enclaves** (TEEs) where inputs and outputs are not readable in plaintext at the inference step; others are selected for renewable energy, openness, or cost rather than architectural privacy. The set of available models, and their properties, will change as members decide.
**You are responsible for assessing each model's privacy and value properties and choosing the one that fits your needs.** As a rule of thumb:
- Some models run inference in encrypted enclaves, verifiable through remote attestation — a property of the system, not a promise.
- Other models are processed in the clear under their provider's own terms and data-processing agreement.
We never read or sell your data regardless of model — but the *architectural* guarantee applies only to models that offer it. Check the current model catalog and each provider's terms before relying on a particular model for sensitive material.
## 4. What we *can* see (an honest caveat)
Your **chat history is stored on our server** so you can revisit past conversations. Stored chat history is **not** encrypted in a way that prevents us from technically reading it, regardless of which model generated it.
We commit not to read it. But this is a **policy commitment**, not an architectural guarantee. We're transparent about this distinction because it matters.
Note the boundary precisely: enclave models protect your conversation **while it is being processed** — the model provider and we cannot read the exchange at inference time. Stored history is a separate leg: once a conversation is saved, it sits on our server in a form we can technically read. So for sensitive material, the strongest combination available today is a **Temporary Chat with an enclave model** — protected in transit and at inference, and never stored afterwards.
### If you use the API, nothing you send is stored
This is the part that surprises people, so it is worth stating plainly. If you call
the co-op's API with your own key and your own client, there is no conversation on
our side to save. Our gateway records **that** a request happened and what it cost:
the model, the token counts, the cost, and which key made the request. It does not
record **what you asked or what came back**.
We measured this rather than asserting it. A request with a distinctive marker was
sent through the gateway and then searched for: it appears nowhere in the gateway's
logs, the gateway's configuration enables no content logging, and the request records
themselves carry usage fields only. So the API path keeps no text.
Two boundaries on that statement, because it would be easy to read it as more than
it is:
- **We can still tell that a given key made a request**, and therefore which member
it belongs to. That link is how metering works — it is not something we hide.
- **"Not stored by us" is not the same as "not stored."** The provider's handling is
a separate question from ours, and it depends on the model you choose — see §3. Not
being stored on our side says nothing about the far end of the request.
### Temporary chats (recommended for anything sensitive)
The chat has a **Temporary Chat** mode designed exactly for this:
- Click the **Temporary Chat** toggle in the chat header, and the conversation is **never saved** — it doesn't appear in your history, it isn't written to our database, and it disappears when you leave the page.
- To make this the default for every new conversation, open **Settings → Conversations** and enable **Default Temporary Chat**. The preference is stored in your browser, so it's yours to change at any time.
- The trade-off is that there's nothing to revisit: no history, no search, no sync across devices. Use it whenever that trade is right for you — you can mix saved and temporary conversations freely.
Temporary chats change what we store, not who processes your request: the model you choose still receives your messages to generate a reply, under the properties described in §3.
### Operational logs
Our server software keeps standard operational logs (dates, error messages, and — for account management like provisioning and welcome emails — the email addresses involved). These logs exist to run and debug the service, are kept briefly, and are not used to profile members.
## 5. Search
Web search runs through our self-hosted search instance. Search queries are forwarded to the underlying search engines (e.g. DuckDuckGo), which may see them. This is inherent to how web search works.
## 6. What we do NOT do
- We do **not** train models on your data.
- We do **not** sell, rent, or share your data.
- We do **not** use your data for advertising or profiling.
## 7. Third parties
The models we serve are provided by third parties that change over time, each with its own terms and privacy posture. We never sell your data, but when you use a model, that model's provider processes your inputs under its own terms and data-processing agreement — some in encrypted enclaves, some in the clear. Review each provider's terms before relying on it for sensitive material. Our current providers are listed in the model catalog.
- **Open Collective** — handles billing and membership (their own privacy policy applies).
- **Cloudron** — our self-hosted platform; no third-party cloud provider.
- **Search engines** — receive your search queries (see §5).
## 8. Retention and deletion
- Chat history is retained until you delete it.
- **Temporary chats are never retained** — they are not written to our database at all (see §4).
- On leaving, your account is deactivated (data preserved for reactivation).
- You may request full deletion at any time: info@inference.coop.
## 9. Security
- Self-hosted on Cloudron (sandboxed apps, SSL, backups).
- Per-member API keys; access gated on live membership.
- No external dependencies for core infrastructure.
## 10. Your rights
- **Access, correct, export, and delete** your data.
- As a member, you also have **governance** rights over this policy itself (through Loomio).
## 11. Children
The service is for people **18 and older**. We do not knowingly collect data from children.
## 12. Changes
We may update this policy as the project evolves. Material changes are announced to members and, where appropriate, decided through Loomio.
## 13. Contact
**info@inference.coop**
+106
View File
@@ -0,0 +1,106 @@
# Terms of Service
**Last updated:** October 6, 2026
## In plain language
- You are a **member**, not a customer. You help govern this project.
- We provide AI chat and API access through open models, with **a variety of privacy and value options** (some models run in encrypted enclaves; others differ — see §3).
- Your prompts and the AI's outputs are yours to keep.
- We don't train on your data, and we don't sell it.
- AI can be wrong. Use your judgment.
- If you misuse the service, we may remove you (per our Charter) — and you are responsible for what you do with it (§4).
- Our liability is limited to what you've paid in dues.
The full terms are below. If anything is unclear, write to info@inference.coop.
---
## 1. Who we are
The **Inference Cooperative** ("we", "us") is a member-governed project providing AI inference. We are fiscally sponsored by **Metagov**, a nonprofit that provides our financial and legal structure.
When you join, you become a **member** — someone with a voice in how the project is run — not a customer of a vendor.
## 2. Membership
- Membership is through **Open Collective**, where you pay dues on a sliding
scale (currently $5/month minimum).
- You must be **18 or older** to join.
- Membership is governed by our [Charter](../charter.md), including our Code of Conduct.
- We may suspend or remove membership for Code of Conduct violations or non-payment, as described in the Charter.
## 3. The service
We provide:
- **AI chat and a developer API** through a changing catalog of open models from multiple providers. You choose per task not just *which model*, but *which affordances it offers* — models differ in privacy architecture, energy source, openness, capability, and cost. Some run inference inside encrypted enclaves; others do not. Some run on renewable energy; others do not. The catalog changes as members decide, and the specific models and providers available will evolve.
- **Web search** and **file uploads** within the chat interface.
- **Governance** — a seat in decisions about models, pricing, and direction.
Models are **not interchangeable in their affordances**. Each model has its own privacy, sustainability, and openness properties, and the set of available models changes over time. You are **responsible for assessing** which model fits your needs for a given task — in particular its privacy properties — before relying on it. See our [Privacy Policy](../privacy-policy.md) for what this means in practice.
The service is provided **"as is"** and may change as the project evolves. We do not guarantee uptime or specific performance at this stage.
## 4. Acceptable use
You agree not to use the service to:
- Violate any law or regulation.
- Generate, distribute, or facilitate **illegal, harmful, abusive, or discriminatory content** — including content that sexualizes minors, defrauds, incites violence, or harasses others.
- Create **deepfakes, impersonations, or deceptive media** of real people without their consent.
- Process **regulated data** — including protected health information (e.g. HIPAA), payment-card data, or other categories that require a separate legal agreement — unless we have agreed to that in writing.
- Submit **special-category personal data** under GDPR Article 9 (health, ethnicity, political views, religion, biometrics, etc.) without a written agreement.
- Use the service in or for the benefit of **embargoed or sanctioned jurisdictions or persons**, or otherwise in violation of **export-control or sanctions law**.
- 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.
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.
## 5. Usage limits
- Membership includes a **monthly credit budget** (currently $15 of usage, the same for every member regardless of what you pay).
- Members may also purchase **credit packs**: non-expiring credits drawn only
after the monthly budget is exhausted. Credits do not expire and carry over
from month to month.
- When your budget is exhausted, requests pause until the next cycle.
- The pricing and budget model is itself a governance decision — members can change it through Loomio.
## 6. Your content
- Your prompts and the AI's outputs are yours to keep.
- We do **not** train models on your data.
- We do **not** sell or share your content.
- See our [Privacy Policy](../privacy-policy.md) for how your data is handled.
## 7. Privacy
Privacy is a core value, but it is **not uniform across the service** — and the set of available models changes over time. Models differ in their privacy affordances: some run inference in encrypted enclaves so inputs and outputs are not readable in plaintext at the inference step, while others are selected for renewable energy or openness rather than architectural privacy. **You are responsible for assessing each model's privacy properties and choosing one that matches your needs.** See the [Privacy Policy](../privacy-policy.md) for the current picture.
## 8. Termination
- 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).
## 9. Governance
The Co-op's governance proceeds according to the content of the current [Charter](../charter.md).
## 10. Disclaimers, liability, and indemnity
- **AI outputs may be inaccurate, biased, or inappropriate.** We provide no warranty of correctness. Use your judgment, and do not rely on outputs as a sole source of truth or as a substitute for professional advice.
- To the maximum extent permitted by law, our liability is limited to the amount of dues you have paid.
- Members are not personally liable for the project's obligations.
- **You agree to indemnify and hold harmless** the Inference Cooperative, Metagov, and their officers, directors, employees, and agents from any claims, losses, liabilities, damages, costs, and expenses (including reasonable legal fees) arising from **your use of the service, your content, your violation of law or third-party rights, or your violation of these Terms**. In plain terms: if what you do with the service causes a legal problem, it is your responsibility, not the co-op's or Metagov's.
## 11. Changes to these terms
- We may update these terms as the project evolves.
- Material changes are announced to members and, where appropriate, decided through Loomio.
## 12. Contact
**info@inference.coop**