---
url: /handbook/start-here.md
description: >-
  What the Start here section covers, and which pages to read first for your
  role.
---

# Start here

This section explains DutyGraph in plain terms. It says what the product does, where a company can start, how one company moves through it, who uses it and what is built today.

## Pages in this section

| Page | What it answers |
| --- | --- |
| [What is DutyGraph](what-is-dutygraph.md) | What the product does, end to end, and why mapping and governance share one data model |
| [Three ways in, one model](three-ways-in.md) | The three places a company can start (strategy, one department, one agent request) and which is built |
| [The DutyGraph loop](the-dutygraph-loop.md) | The six stages DutyGraph is designed around, and which stages are built today |
| [Run a company in 9 steps](run-a-company.md) | How an advisor takes one company from its website to a governed agent |
| [Who uses DutyGraph](who-uses-dutygraph.md) | Each role: what they see, what they do and how they get in |
| [Built and planned](built-and-planned.md) | The status of each capability: Built, Simulated or Planned |

## Reading order by role

Every reader should start with [What is DutyGraph](what-is-dutygraph.md), then [Three ways in, one model](three-ways-in.md). Then follow the path for your role.

**Advisor or FDE**

You run engagements. A forward-deployed engineer (FDE) uses the same app.

1. [Run a company in 9 steps](run-a-company.md)
2. [Who uses DutyGraph](who-uses-dutygraph.md)
3. [Built and planned](built-and-planned.md): know what you may show a client as available.
4. [Run engagements](../advisors/index.md) and [MCP for advisors](../connect/mcp.md)

**Client sponsor or executive**

You sponsor the work, or you join the executive kickoff.

1. [Who uses DutyGraph](who-uses-dutygraph.md): the sponsor and executive sections
2. [Sponsor packet](../discovery/sponsor-packet.md) and [Executive kickoff](../discovery/executive-kickoff.md)
3. [Opportunities](../opportunities/opportunities.md) and [Reports](../opportunities/reports.md)
4. [Built and planned](built-and-planned.md)

**Employee**

You answer questions about your own work. Later, you may own an agent.

1. [Team asks](../discovery/team-asks.md): what the private link asks you
2. [Task Cards](../discovery/task-cards.md): how your answer becomes a record of your work
3. [Share the agent plan](../agents/agent-plan.md): the plan page you may receive
4. [Request from your AI](../governance/request-from-your-ai.md)

**IAM and Internal Controls**

You approve access today. DutyGraph routes agent access to you. Your own IAM tools still provision it.

1. [Three ways in, one model](three-ways-in.md): the bottom-up entry point
2. [The key join](../governance/the-key-join.md)
3. [Why governed agents](../governance/why-governed-agents.md)
4. [Holdings](../governance/holdings.md), [System Catalog](../governance/system-catalog.md) and [Rule packs and SoD](../governance/rule-packs-and-sod.md)
5. [Approval chain](../governance/approval-chain.md) and [Set up governance](../governance/set-up-governance.md)

**Department head**

You lead one department and want to start there.

1. [Three ways in, one model](three-ways-in.md): pod-down discovery is **Planned**
2. [Map the company](../discovery/index.md): how discovery runs today
3. [Opportunities](../opportunities/opportunities.md)
4. [Built and planned](built-and-planned.md)

**Auditor**

You test whether agent access was justified and approved.

1. [The key join](../governance/the-key-join.md)
2. [Ledger](../governance/ledger.md)
3. [Audit evidence](../governance/audit-evidence.md)
4. [Evidence and provenance](../trust/evidence-and-provenance.md)

**Developer evaluating it**

You want to know what is real and how it fits your stack.

1. [Built and planned](built-and-planned.md)
2. [The DutyGraph loop](the-dutygraph-loop.md)
3. [Agent gateway](../governance/agent-gateway.md) and [Exports and runtimes](../agents/exports-and-runtimes.md)
4. [Security and data handling](../trust/security-and-data.md) and [Integrations](../connect/integrations.md)

## How to read the status labels

Each capability on these pages has one label:

* **Built:** in the code, with tests.
* **Partial:** some of it is Built and the rest is Planned. The page says which part.
* **Simulated:** the screen works, but no real outside system is connected.
* **Planned:** written down, not built.

::: info
**Status.** This section describes the product as built on October 15, 2026. Each page labels its own capabilities as Built, Partial, Simulated or Planned. [Built and planned](built-and-planned.md) is the full list and the reference when pages disagree.
:::
