Skip to content

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 ​

PageWhat it answers
What is DutyGraphWhat the product does, end to end, and why mapping and governance share one data model
Three ways in, one modelThe three places a company can start (strategy, one department, one agent request) and which is built
The DutyGraph loopThe six stages DutyGraph is designed around, and which stages are built today
Run a company in 9 stepsHow an advisor takes one company from its website to a governed agent
Who uses DutyGraphEach role: what they see, what they do and how they get in
Built and plannedThe status of each capability: Built, Simulated or Planned

Reading order by role ​

Every reader should start with What is DutyGraph, then Three ways in, one model. 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
  2. Who uses DutyGraph
  3. Built and planned: know what you may show a client as available.
  4. Run engagements and MCP for advisors

Client sponsor or executive

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

  1. Who uses DutyGraph: the sponsor and executive sections
  2. Sponsor packet and Executive kickoff
  3. Opportunities and Reports
  4. Built and planned

Employee

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

  1. Team asks: what the private link asks you
  2. Task Cards: how your answer becomes a record of your work
  3. Share the agent plan: the plan page you may receive
  4. Request from your AI

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: the bottom-up entry point
  2. The key join
  3. Why governed agents
  4. Holdings, System Catalog and Rule packs and SoD
  5. Approval chain and Set up governance

Department head

You lead one department and want to start there.

  1. Three ways in, one model: pod-down discovery is Planned
  2. Map the company: how discovery runs today
  3. Opportunities
  4. Built and planned

Auditor

You test whether agent access was justified and approved.

  1. The key join
  2. Ledger
  3. Audit evidence
  4. Evidence and provenance

Developer evaluating it

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

  1. Built and planned
  2. The DutyGraph loop
  3. Agent gateway and Exports and runtimes
  4. Security and data handling and Integrations

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 is the full list and the reference when pages disagree.

Source: gitbook/product/start-here/README.md in the DutyGraph repository.

DutyGraph. Pages label each feature Built, In review or Planned.