> For the complete documentation index, see [llms.txt](https://islamu.gitbook.io/islamu-event/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://islamu.gitbook.io/islamu-event/documentation/readme/integrations-and-ai/coop-and-osprey.md).

# Coop & Osprey

Integrate durable moderation case intake and advisory AI signals without delegating local decisions.

ISLAMU Event integrates with **Coop** (distributed review queue) and **Osprey** (AI-assisted signal evaluation coordinator) to support community moderation workflows. Neither external system ever replaces local tenant policy, human administrative authority, or auditable database state.

***

## 1. Coop Review Queue Mirroring

* **Architecture**: When an attendee reports an event or user profile, the platform generates a metadata-first moderation ticket. If the `moderation` profile is enabled (see [Docker Compose Profiles](/islamu-event/documentation/readme/self-hosting/docker-compose.md#optional-service-profiles)), the ticket is mirrored to Coop via authenticated HMAC envelopes (see [Webhooks](/islamu-event/documentation/readme/integrations-and-ai/webhooks.md)).
* **Local Decision Finality**: Moderators can review tickets in Coop, but the ultimate execution of decisions (suspending an event, issuing warnings, or banning users) commits exclusively within ISLAMU Event via signed callback verification.

***

## 2. Osprey Advisory AI Signals

Osprey acts strictly as an **advisory, signal-only evaluation coordinator**:

* Analyzes event text for policy violations and assigns priority scores to assist human moderators.
* **Hard Limitations**: Osprey cannot execute enforcement decisions, cannot close moderation tickets, cannot dispatch attendee notifications, and cannot override [Authorization Policies](/islamu-event/documentation/readme/security-and-identity/authorization.md).
* Model outputs are never presented as religious rulings, ethical certifications, or automated bans.

***

## 3. Configuration & Startup Flags

Configured via environment variables (see [Environment Variables Reference](/islamu-event/documentation/readme/configuration-and-operations/environment-variables.md#external-moderation-coop--osprey)):

* `REPORTING_MODE`: `LocalOnly` (default), `Coop`, `Osprey`, or `Composite`.
* `REPORTING_COOP_ENDPOINT_URL`, `REPORTING_COOP_API_KEY`.
* `REPORTING_OSPREY_ENDPOINT_URL`, `REPORTING_OSPREY_API_KEY`.

***

## Related Guides & Next Steps

* [**Environment Variables Reference**](/islamu-event/documentation/readme/configuration-and-operations/environment-variables.md#external-moderation-coop--osprey) — Configure moderation endpoints and API keys.
* [**Docker Compose Optional Profiles**](/islamu-event/documentation/readme/self-hosting/docker-compose.md#optional-service-profiles) — Launch the moderation container profile.
* [**Authorization & Access Control**](/islamu-event/documentation/readme/security-and-identity/authorization.md) — Understand role permissions for incident moderators.
* [**In-App Notifications**](/islamu-event/documentation/readme/communications-and-notifications/in-app-notifications.md) — Alert moderators and users about ticket updates.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://islamu.gitbook.io/islamu-event/documentation/readme/integrations-and-ai/coop-and-osprey.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.