Skip to content

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, and each file in the Repo says how sure DutyGraph is of it.

The output is a set of Task Cards: one card for each piece of recurring work, with an owner, a performer, steps, systems and hours. Task Cards feed Opportunities and, later, governed agents.

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.

TopologyStarts fromWho sponsorsStatus
Top-downCompany strategy, then departments, managers and employeesThe client sponsorBuilt, for a functional organization. This page describes it.
Pod-downOne department or business unit; links to other units are recorded, not mappedThe department headPlanned
Bottom-up task captureOne agent request with no adequate Task Card; capture covers that one taskThe employee's manager confirms the workPlanned. The request tools are Built. See Just-in-time task capture.

See Three ways in, one model 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.

StepWhat happensPage
1. Company ResearchResearch 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, Sponsor packet
2. Executive KickoffLeadership confirms the strategy, the priorities, the departments, the owners and who decides.Executive kickoff
3. Team DiscoveryThe people who do the work answer short asks on their phone. Their answers become Task Cards.Team asks
4. Solution AnalysisThe advisor reviews opportunities against the recorded evidence.Opportunities

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.

LayerLabel in the RepoWho fills itWhat it adds to the Repo
0Research + intakeResearch runs and the team listcompany/, market/ and systems/ files from public sources; people/ and roles/ from the team list
1Executive kickoffThe sponsor, the CEO and direct reportsConfirmed company facts, the meeting account, people the advisor adds
2Department headsHeads and managersDuties, leadership answers, facts a manager confirms
3ManagersManagers and advisor draftsTask Cards, workflows, handoffs and metrics
4EmployeesTeam asks and confirmationsAnswers stored as understood, the hours each person reports, confirmations of Task Cards
5Agent drafts & exportsDraft agents and exportsAgent 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 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.

StateWhat it means
ConfirmedA person with authority confirmed it in DutyGraph. The confirmation is recorded. It is not a signature.
ObservedAt least one client source backs it, but not every key field is confirmed.
InferredIt rests only on research, a draft, a rule or an advisor entry. It needs a client source.
DisputedSources disagree. The best-supported value is shown.
UnknownDutyGraph searched and found no usable evidence.
ProposedA draft change or agent waits for review.
SlotThe file exists, but nothing has filled it yet.
GeneratedDutyGraph 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 ​

Step 1

Research the company ​

Add the company by its website and run research. See Company research.

Step 2

Send the sponsor packet ​

The client contact corrects the facts and uploads the team list. See Sponsor packet.

Step 3

Hold the executive kickoff ​

Approve the agenda, invite the executives and bring the notes in. See Executive kickoff.

Step 4

Send team asks ​

Each person answers on a private link. See Team asks.

Step 5

Review and read the map ​

Accept answers in Repo › To review. Read the result in the Company Repo, the Task Cards and the Work Map.

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 ​

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), matrix and other organization shapes, separate department-head and manager sessions, and fully AI-run capture sessions that write straight to Repo files.

Source: gitbook/product/discovery/README.md in the DutyGraph repository.

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