> 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/federation-and-open-protocols.md).

# Federation & Open Protocols

Selective AT Protocol publication and ingestion with explicit lexicon and privacy governance.

ISLAMU Event federates selected event data through explicit AT Protocol (Bluesky) contracts. Local domain capabilities, attendee consent, tenant policies, vendored lexicons, and lifecycle state remain the authoritative source of truth.

***

## In this Section

* [**AT Protocol & Bluesky Jetstream**](/islamu-event/documentation/readme/federation-and-open-protocols/at-protocol-and-bluesky-jetstream.md) — Linked-user OAuth, governed event publication, CarpaNet Jetstream firehose ingestion, cursor settlement, and tenant discovery.
* [**Lexicons**](/islamu-event/documentation/readme/federation-and-open-protocols/lexicons.md) — Vendored lexicon schemas (`community.lexicon.calendar.*`), exact collection mappings, and version governance.

***

## Explicit Architecture Boundaries

The platform intentionally does not implement:

* ActivityPub / ActivityStreams / WebFinger protocols.
* First-party Personal Data Server (PDS) or AppView hosting.
* Bidirectional relay bridges or unmoderated social post streams.
* Dynamic runtime lexicon discovery or wildcard ingestion.

***

## Related Guides & Next Steps

* [**AT Protocol Authentication**](/islamu-event/documentation/readme/security-and-identity/authentication.md#at-protocol-sign-in) — Choose primary passwordless login or optional exact-DID-linked sign-in.
* [**Multi-Tenancy Isolation**](/islamu-event/documentation/readme/security-and-identity/multi-tenancy.md) — Control which community tenants participate in open federation.
* [**Architecture & Outbox Workflows**](/islamu-event/documentation/readme/getting-started/architecture-and-request-flows.md) — Understand transactional outbox guarantees for federated records.
* [**Privacy Erasure & GDPR**](/islamu-event/documentation/readme/security-and-identity/privacy-erasure.md) — How federated posts and RSVPs are handled upon account erasure.


---

# 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/federation-and-open-protocols.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.