---
url: /handbook/discovery.md
description: >-
  How DutyGraph maps a company, the three ways capture can start, and what each
  step adds to the Company Repo.
---

# Map the company

Today DutyGraph maps a company from the top down. Research comes first, then the sponsor, then the executives, then the people who do the work. Each step fills part of the [Company Repo](company-repo.md), and each file in the Repo says how sure DutyGraph is of it.

The output is a set of [Task Cards](task-cards.md): one card for each piece of recurring work, with an owner, a performer, steps, systems and hours. Task Cards feed [Opportunities](../opportunities/opportunities.md) and, later, [governed agents](../governance/index.md).

## Three capture topologies, one engine

Capture can start from three places. They are not three engines. One discovery and evidence engine writes to one Company Repo, with one Task Card format. The starting point only changes the scope, the sponsor, who takes part, the evidence required, the questions, the coverage target and the approvals.

| Topology | Starts from | Who sponsors | Status |
| --- | --- | --- | --- |
| **Top-down** | Company strategy, then departments, managers and employees | The client sponsor | **Built**, for a functional organization. This page describes it. |
| **Pod-down** | One department or business unit; links to other units are recorded, not mapped | The department head | **Planned** |
| **Bottom-up task capture** | One agent request with no adequate Task Card; capture covers that one task | The employee's manager confirms the work | **Planned**. The request tools are Built. See [Just-in-time task capture](../roadmap/just-in-time-task-capture.md). |

See [Three ways in, one model](../start-here/three-ways-in.md) for who each one serves and what it produces.

## The Discovery Plan

In the app, open **Discovery › Plan**. The Plan shows 4 steps and the one step to do now.

| Step | What happens | Page |
| --- | --- | --- |
| 1. Company Research | Research builds a first picture from public sources. The sponsor packet asks the point of contact to correct it and to send the team list. | [Company research](company-research.md), [Sponsor packet](sponsor-packet.md) |
| 2. Executive Kickoff | Leadership confirms the strategy, the priorities, the departments, the owners and who decides. | [Executive kickoff](executive-kickoff.md) |
| 3. Team Discovery | The people who do the work answer short asks on their phone. Their answers become Task Cards. | [Team asks](team-asks.md) |
| 4. Solution Analysis | The advisor reviews opportunities against the recorded evidence. | [Opportunities](../opportunities/opportunities.md) |

Discovery opens when the engagement is active. A prospect's sidebar shows only Overview, Repo and Reports.

## The capture layers

The Repo records which layer of the company each source came from. A layer never invents content for a layer above it. It can only propose a change. Open a file's **History** in the Repo to see how it stood after each layer.

| Layer | Label in the Repo | Who fills it | What it adds to the Repo |
| --- | --- | --- | --- |
| 0 | Research + intake | Research runs and the team list | `company/`, `market/` and `systems/` files from public sources; `people/` and `roles/` from the team list |
| 1 | Executive kickoff | The sponsor, the CEO and direct reports | Confirmed company facts, the meeting account, people the advisor adds |
| 2 | Department heads | Heads and managers | Duties, leadership answers, facts a manager confirms |
| 3 | Managers | Managers and advisor drafts | Task Cards, workflows, handoffs and metrics |
| 4 | Employees | Team asks and confirmations | Answers stored as understood, the hours each person reports, confirmations of Task Cards |
| 5 | Agent drafts & exports | Draft agents and exports | Agent manifests and requests |

DutyGraph assigns the layer from the source and the role of the person behind it. Nobody types it.

::: info
Today the Plan has no separate step for department heads or managers. They answer the same [team asks](team-asks.md) as everyone else. Their answers and confirmations count at their own layer.
:::

## Evidence states

Every Repo file has one state. The state comes only from data that people and sources produced. DutyGraph does not invent a score.

| State | What it means |
| --- | --- |
| Confirmed | A person with authority confirmed it in DutyGraph. The confirmation is recorded. It is not a signature. |
| Observed | At least one client source backs it, but not every key field is confirmed. |
| Inferred | It rests only on research, a draft, a rule or an advisor entry. It needs a client source. |
| Disputed | Sources disagree. The best-supported value is shown. |
| Unknown | DutyGraph searched and found no usable evidence. |
| Proposed | A draft change or agent waits for review. |
| Slot | The file exists, but nothing has filled it yet. |
| Generated | DutyGraph built it from other files, for example an index. It is not a fact in itself. |

Research alone never makes a file Observed or Confirmed. An advisor's own note never confirms anything.

::: warning
DutyGraph's north-star model speaks of four evidence words: Observed, Inferred, Confirmed and Approved. The app uses the eight states above. "Approved" is not a separate state today. A Confirmed file carries `status: approved` and `approval: recorded` in its frontmatter.
:::

## What the advisor does

### Research the company

Add the company by its website and run research. See [Company research](company-research.md).

### Send the sponsor packet

The client contact corrects the facts and uploads the team list. See [Sponsor packet](sponsor-packet.md).

### Hold the executive kickoff

Approve the agenda, invite the executives and bring the notes in. See [Executive kickoff](executive-kickoff.md).

### Send team asks

Each person answers on a private link. See [Team asks](team-asks.md).

### Review and read the map

Accept answers in **Repo › To review**. Read the result in the [Company Repo](company-repo.md), the [Task Cards](task-cards.md) and the [Work Map](work-map.md).

## Which companies fit

Discovery is designed around a **functional organization**. Each person on the team list has one department and one manager. Departments come from that list, and the reporting chart follows the manager column.

A matrix organization, where a person reports to two managers, does not fit this model yet. Support for matrix and other organization shapes is **Planned**.

## In this section

* [Company research](company-research.md): add a company by its website and research it.
* [Sponsor packet](sponsor-packet.md): the first ask to the client contact.
* [Executive kickoff](executive-kickoff.md): the leadership meeting and what it produces.
* [Team asks](team-asks.md): short asks to each person, answered on a phone.
* [Company Repo](company-repo.md): the company as files, with a state on each file.
* [Task Cards](task-cards.md): one piece of recurring work, and the evidence that the work exists.
* [Work Map](work-map.md): how work moves through the business.

::: info
**Status.** **Built:** the 4-step Discovery Plan, company research, the sponsor packet, the executive kickoff, team asks, the Company Repo with its 8 states and capture layers, Task Cards and the Work Map, designed around a functional organization. **Simulated:** research on the sample companies uses fictional data labelled as simulated. **Planned:** pod-down discovery, bottom-up task capture ([Just-in-time task capture](../roadmap/just-in-time-task-capture.md)), matrix and other organization shapes, separate department-head and manager sessions, and fully AI-run capture sessions that write straight to Repo files.
:::
