​
The table

Search by name or domain filters as you type. Click a row to open the provider record.

​
New provider

Give it a name, its domains (comma separated; these match accounts from a client’s inventory), a category and optionally a website. Create draft makes the record and opens it. With Scan the domain now ticked (the default) the new-provider pipeline starts:
1

Scan

The crawler reads the provider’s own site (the homepage, help and support hosts, well-known paths and the sitemaps; about two dozen pages, same site only), scores each page on a deceased-account vocabulary, and proposes the policy page, the help page, source pages and any email address or request form it saw. No model is needed.
2

Analyse (with an LLM configured)

The model reads the pages the scan chose into the provider’s empty policy fields, with citations, a confidence and open questions. Supported outcomes are left for a person, with the model’s suggestion shown beside the checkboxes.
3

Draft playbooks

When outcomes are added (saving the Policy tab, or applying an analysis) a playbook is drafted for each new outcome that has none and saved as a draft if it validates.
Auto-apply only fills what is empty. A provider that already has a policy or a verification, an outcome that already has a playbook, or a draft that fails validation is left in the review queue for a person, with the reason in the audit log. The banner at the top of the provider record shows where the pipeline is.