# Registry

This module discovers metadata providers and exposes them to the UI/API.

{% tabs %}
{% tab title="End users" %}

### What it does

* discovers `providers/metadata/_meta_*.py`
* exposes provider manifests for UI/diagnostics
* exposes provider HTML blocks for the UI

### When things break

**A provider doesn’t show up**

* import fails
* module doesn’t expose a provider instance/class
* manifest is invalid

**Provider shows up, but UI is weird**

* `html()` output is broken
* grouping rules changed
  {% endtab %}

{% tab title="Power users" %}

### Code map

* `providers/metadata/registry.py`

### Public API

* `metadata_providers_manifests()`
* `metadata_providers_html()`

### Discovery rules (high level)

* find `_meta_*.py`
* import the module
* look for:
  * module-level `PROVIDER`, or
  * a class with `manifest()` (instantiated with no args)

<details>

<summary>Discovery flow (diagram)</summary>

```mermaid
flowchart LR
  UI[UI/API] --> R[metadata.registry]
  R -->|discover _meta_*.py| M[import modules]
  M --> P[provider instance/PROVIDER]
  P --> MAN[manifest()/html()]
  MAN --> UI
```

</details>
{% endtab %}
{% endtabs %}


---

# Agent Instructions: 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:

```
GET https://wiki.crosswatch.app/blueprint-architecture/meta/registry.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.