> 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/contributing/clean-room-ip-and-licensing.md).

# Clean-Room IP & Licensing

Contribute under the AGPL, CLA, provenance, and dependency-review boundaries.

ISLAMU Event is publicly licensed under **GNU AGPL-3.0-or-later**. Non-bot contributors sign the project Contributor License Agreement (CLA), which grants the project steward rights to distribute and preserve the platform.

> \[!NOTE] This page summarizes engineering policy, not formal legal advice.

***

## Clean-Room Contribution Invariants

To safeguard the sovereign open-source nature of the project and protect outbound licensing paths:

* **No Ingestion of Copyleft / Proprietary Source**: Never copy code, SQL, migrations, tests, comments, documentation prose, or assets from third-party proprietary software or incompatible copyleft platforms.
* **Independent Creation**: When studying external features or public protocols:
  1. Record source URLs, access dates, and factual protocol behavior.
  2. Produce a source-free functional specification containing inputs, outputs, and wire contracts.
  3. Author the implementation independently using repository-native Clean Architecture conventions (see [Clean Architecture Conventions](/islamu-event/documentation/readme/contributing/clean-architecture.md)).
  4. Ensure all public standard identifiers (e.g. AT Protocol [Lexicons](/islamu-event/documentation/readme/federation-and-open-protocols/lexicons.md)) match wire requirements while surrounding expression remains original.

***

## Dependency & License Review

Before introducing a new NuGet package or external library:

* Verify the package uses an approved permissive open-source license (MIT, Apache 2.0, BSD).
* Incompatible licenses (GPLv2-only, SSPL, BSL) are strictly forbidden.

***

## Related Guides & Next Steps

* [**Contributing Overview**](/islamu-event/documentation/readme/contributing.md) — Community guidelines and contribution channels.
* [**Local Development Guide**](/islamu-event/documentation/readme/contributing/local-development.md) — Setting up your workstation with .NET 10.
* [**Clean Architecture Conventions**](/islamu-event/documentation/readme/contributing/clean-architecture.md) — Architectural patterns and code structure.
* [**Lexicons Reference**](/islamu-event/documentation/readme/federation-and-open-protocols/lexicons.md) — Open standard protocol schemas and identifiers.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://islamu.gitbook.io/islamu-event/documentation/readme/contributing/clean-room-ip-and-licensing.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.