> 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/lexicons.md).

# Lexicons

Govern vendored AT Protocol schemas, exact identifiers, version changes, and privacy limits.

In the AT Protocol ecosystem, **Lexicons** are formal, versioned JSON schemas defining RPC methods and repository record formats. ISLAMU Event explicitly vendors and tests each supported lexicon schema, guaranteeing reliable type mapping and strict security boundaries.

***

## Supported Lexicon Collections

The platform limits ingestion and publication strictly to reviewed collections (see [AT Protocol & Bluesky Jetstream](/islamu-event/documentation/readme/federation-and-open-protocols/at-protocol-and-bluesky-jetstream.md)):

| Lexicon Identifier                 | Supported Operations                     | Local Entity Mapping                                                                                                       |
| ---------------------------------- | ---------------------------------------- | -------------------------------------------------------------------------------------------------------------------------- |
| `community.lexicon.calendar.event` | Inbound Ingestion & Outbound Publication | Core Event Aggregate & [Modular Aspects](/islamu-event/documentation/readme/events-and-ticketing/modular-event-aspects.md) |
| `community.lexicon.calendar.rsvp`  | Inbound Ingestion & Outbound (`#going`)  | Event RSVP & Attendance Intent                                                                                             |

> \[!IMPORTANT] Wildcard schema discovery is permanently disabled. Inbound records matching unvetted collections are silently ignored at the network layer.

***

## Fail-Closed Record Serialization

* If an event title, description, or venue location cannot be serialized without exceeding lexicon size limits or violating character formatting, outbound publication fails closed (the outbox job logs an error and aborts).
* The platform **never** silently truncates text or drops required fields to produce superficially valid records.
* Outbound fields strictly respect attendee privacy ceilings: private registration data and custom attendee answers are excluded from public lexicon records (see [Privacy Erasure & GDPR Compliance](/islamu-event/documentation/readme/security-and-identity/privacy-erasure.md)).

***

## Related Guides & Next Steps

* [**AT Protocol & Bluesky Jetstream**](/islamu-event/documentation/readme/federation-and-open-protocols/at-protocol-and-bluesky-jetstream.md) — Ingest firehose events and publish calendar records.
* [**Modular Event Aspects**](/islamu-event/documentation/readme/events-and-ticketing/modular-event-aspects.md) — Understand relational sector fields and how they map to lexicons.
* [**Privacy Erasure & GDPR**](/islamu-event/documentation/readme/security-and-identity/privacy-erasure.md) — Account deletion and federated record removal.
* [**Local Development**](/islamu-event/documentation/readme/contributing/local-development.md) — Work with CarpaNet source generators in .NET.


---

# 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/lexicons.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.