Skip to content

Three ways in, one model ​

A company can start DutyGraph from three places: its strategy, one department, or one agent request. These are not three products. They are three workflows that fill the same operating model through one discovery and evidence engine.

WARNING

DutyGraph is not meant to require a full company map before it can govern one agent. Today, though, the built path is top-down. Pod-down discovery is Planned. For bottom-up requests, the request tools are Built and the task capture behind them is Planned.

The picture ​

mermaid
flowchart TD
    A["A. Top-down<br/>start with company strategy<br/>Built"] --> E
    B["B. Pod-down<br/>start with one department<br/>Planned"] --> E
    C["C. Bottom-up<br/>start with one agent request<br/>request tools Built,<br/>capture Planned"] --> E
    E{"One discovery and evidence engine<br/>the entry point sets scope, sponsor,<br/>participants, evidence, questions,<br/>coverage and approvals"}
    E --> M["One operating model<br/>Company Repo, Task Cards,<br/>Work Map, governance records"]
    M --> O["Opportunities and Route"]
    M --> G["Governed agent requests"]
    classDef built fill:#d9f2e3,stroke:#2e7d4f,color:#123;
    classDef partial fill:#fff3cd,stroke:#a07800,color:#321;
    classDef planned fill:#eeeeee,stroke:#888,color:#333,stroke-dasharray: 4 3;
    class A,M,O,G built;
    class C,E partial;
    class B planned;

Green is Built. Yellow is Partial. Grey is Planned. The engine is yellow because today it has only one configuration: top-down, for a functional organization.

At a glance ​

Entry pointWho it servesStarts fromProducesStatus
A. Top-downPrivate equity (PE) firms, portfolio companies, roll-ups, mid-market CEOs and operating partnersThe sponsor's priorities and the executives' objectivesA company-wide map, opportunities and proposed agentsBuilt, for a functional organization
B. Pod-downEnterprise department heads, business-unit leaders, internal AI transformation teamsOne department's prioritiesA map of one unit, with its links to other units recordedPlanned
C. Bottom-upEnterprise IAM (identity and access management), Internal Controls, enterprise AI teamsOne employee's agent requestOne confirmed Task Card and one governed requestPartial: request tools Built; capture, manager confirmation and application-owner validation Planned

One engine, configured by the entry point ​

The three entry points share one engine. The entry point only changes its settings.

SettingA. Top-downB. Pod-down (Planned)C. Bottom-up (Planned)
Starting scopeThe whole companyOne department or unitOne task
Sponsor or accountable ownerThe client sponsorThe department headThe employee's manager
ParticipantsExecutives, then the team listThe unit's managers and employeesThe employee, the manager, an application or IAM owner
Required evidenceResearch, kickoff, team asks, confirmationsThe same, for one unitOne task description and its confirmations
Question sequenceCompany, then departments, then workUnit priorities, then workOne task: steps, systems, rules, exceptions
Coverage thresholdThe company's key work is mappedThe unit's key work is mappedThis one task is confirmed
Approval requirementsAdvisor review of each proposalThe sameManager confirmation, then the normal approval chain

There is one company database, one Task Card format and one evaluator. A task captured from a single request is the same kind of record as a task mapped top-down.

A. Top-down: start with company strategy ​

This is the path DutyGraph runs today. An advisor works down from the company's strategy to the work.

  1. Research and the sponsor packet set the sponsor's priorities.
  2. The executive kickoff records the executives' objectives and department responsibilities.
  3. Team asks capture manager workflows and employee tasks.
  4. The Company Repo, Task Cards and the Work Map record the work and its handoffs.
  5. Opportunities and Route turn the map into findings and proposed changes.

Status: Built, designed around a functional organization. Each person has one department and one manager. Matrix organizations are Planned. See Run a company in 9 steps.

B. Pod-down: start with one department ​

WARNING

Planned. This is a proposed extension of the functional-organization model. It is not built.

A department head sponsors discovery for one bounded unit.

  1. The department head names the unit and its priorities. These set the local strategic context.
  2. Discovery runs through the unit's teams, managers and employees.
  3. The unit's Task Cards and handoffs go into the same Company Repo.
  4. Where work crosses into another department, DutyGraph records the dependency. It does not need to map that department first.

Today the Discovery Plan starts from one company sponsor and the company's team list. It has no unit-level sponsor or unit coverage measure.

C. Bottom-up: start with one agent request ​

An employee asks for an agent. The request itself starts the capture of the one task it needs.

  1. The employee requests an agent in DutyGraph or from their own AI chat over the Model Context Protocol (MCP). Built.
  2. DutyGraph looks for a confirmed Task Card for that work. Today a request must name Task Cards that are already set up. Over MCP, if DutyGraph cannot choose one, it asks for the Task Card ids. Built.
  3. If there is no adequate Task Card, DutyGraph opens a short capture of that one task. Planned.
  4. The manager confirms the business work is real. Planned.
  5. An application or IAM owner validates the technical permissions the work needs. Planned.
  6. The evaluator proposes the agent's authority. Partial: see The key join.
  7. The request goes through the normal approval chain. Built.

Each request adds one confirmed Task Card to the operating model. Over time, the requests build up a map of the work that matters most to the company's agents. See Just-in-time task capture.

Why one model matters ​

  • A Task Card mapped top-down can back a later agent request without new capture.
  • A Task Card captured from one request can later appear in the department's map.
  • Governance and discovery use the same records, so neither keeps a second copy of the truth.

Only the top-down path fills the model today. The sharing across entry points is the design.

INFO

Status. Top-down discovery for a functional organization, the employee request tools and the approval chain are Built. The business and identity systems in the samples are Simulated. Pod-down discovery, bottom-up task capture, manager confirmation, application-owner validation and a configurable entry point are Planned. See Built and planned.

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

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