> For the complete documentation index, see [llms.txt](https://help.delpha.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.delpha.io/use-cases/ultimate-parent/how-selection-works.md).

# How selection works

How Delpha selects the commercial Ultimate Parent: brand and operating structures over legal shells, ten ordered logic protocols, and the analysis pipeline behind each recommendation.

Delpha selects the **commercial** parent — the group an account operates and goes to market under — not simply the last legal owner in a corporate registry. The legal chain is retained as evidence; passive or non-operating owners can be bypassed for commercial selection.

Three pages cover the mechanics:

* [**Ultimate Parent Concepts: Brands vs. Operating Structures**](/use-cases/ultimate-parent/how-selection-works/ultimate-parent-concepts-brands-vs.-operating-structures.md) — why brands and operating structures beat strict legal entities.
* [**How Delpha Selects the Ultimate Parent: The 10 Logic Protocols**](/use-cases/ultimate-parent/how-selection-works/how-delpha-selects-the-ultimate-parent-the-10-logic-protocols.md) — the ten ordered rules, first match wins, with worked examples and resulting field values.
* [**Understanding the Ultimate Parent Analysis**](/use-cases/ultimate-parent/how-selection-works/understanding-the-ultimate-parent-analysis.md) — the step-by-step analysis and how confidence is calculated.


---

# 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://help.delpha.io/use-cases/ultimate-parent/how-selection-works.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.