Appearance
How it all fits together
This page is for: everyone.
DutyGraph gets what a team knows out of people's heads and into one map of who does what. The map is made of small records that people confirm. Everything else in the product reads from that map.
This page is the short version. Each part links to its own page.
The idea in five lines
- A company is mapped from the top down: vision and goals first, then departments, then roles, then the tasks each person does.
- The smallest unit is the Task Card: one task, written by the person who does it, with its trigger, inputs, steps, hand-offs and what "done" means.
- Every role gets a role profile: what the role owns, what it decides, what it does and who it works with.
- All of it is compiled into the Company Repo: a tree of Markdown files that people and AI can both read.
- Because the map is in files and records, AI can work with it: DutyGraph Agent™ for the advisor, a role AI for each person, MCP tools for any AI assistant and a CLI for the terminal.
Two sides, two readers
DutyGraph has two sides, and these docs keep them apart.
| Side | Who uses it | Where to read |
|---|---|---|
| Advisor dashboard | The advisor, forward-deployed engineer or consultant who runs DutyGraph for a client. They set up the company, send the questions and check the answers. | Advisor dashboard: the manual |
| Client app | The client's people. They answer questions, upload files and check what is written about their role. They never see the advisor dashboard. | Client app: guide for the team |
Each page says at the top who it is for.
Who uses it
| Person | What they do | Where |
|---|---|---|
| Advisor or forward-deployed engineer (FDE) | Sets up the company, runs the sessions, checks what the AI drafts, and delivers the Readout | The advisor dashboard, DutyGraph Agent, the CLI, MCP |
| Sponsor (CEO or owner) | Answers the North Star questions and approves the top of the map | A live session, a transcript, or their own app |
| Leaders and managers | Check the role profiles of the people who report to them | The client app |
| Employees | Answer questions about their role and write Task Cards for their own work | The client app on a phone or laptop, or their own AI chat over MCP |
| Partner firms | Coaching and AI firms that run DutyGraph for their own clients | Their own workspace, MCP and the CLI |
The flow of an engagement
| Step | What happens | Page |
|---|---|---|
| 1 | You research the company, plan the call, run it and send the onboarding package | Pitch to Package |
| 2 | The sponsor answers the top-level questions | North Star session |
| 3 | DutyGraph drafts a role profile for each person from the answers above them | Org chart and role profiles |
| 4 | People open the client app, check their profile and answer their questions | The client app |
| 5 | People write Task Cards for the work they do | Task Cards |
| 6 | You deliver the Readout | Readout |
| 7 | The map is kept current with new questions | Keep it current |
The records, from top to bottom
Every record traces up to the one above it. That chain is what makes the map useful: you can start at any Task Card and see which goal it serves.
| Level | Record | Example |
|---|---|---|
| Company | Vision, business model (Business Model Canvas), goals | "Double recurring revenue in 18 months" |
| Department | Charter, duties, how it serves the company | "Operations ships every order within 2 days" |
| Role | Role profile: owns, decides, does, works with | "Operations coordinator" |
| Responsibility | A result the role answers for, with its measure | "Orders are checked before release" |
| Duty | Recurring work that keeps a responsibility | "Check each morning's orders" |
| Task | One piece of that work, as a Task Card | "Check an order against the price list" |
Where the records live
- PostgreSQL is the source of truth. Every answer, profile and Task Card is a versioned record.
- The Company Repo is compiled from those records. It is a read view in Markdown. Nothing is stored twice. See Company Repo and DutyGraph Agent.
- Each company is isolated. A workspace sees only its own companies, and the database enforces this on every row.
Where AI fits
| Surface | Who it is for | What it does |
|---|---|---|
| DutyGraph Agent | The advisor, inside the app | Reads the page you are on and the company's files, writes drafts, proposes changes you apply |
| Role AI | Each person | A persona built from the approved role profile, with first questions and task starters. See Role AI |
| MCP server | Any AI assistant (Claude, ChatGPT, Cursor) | Advisor tools for running engagements, and employee tools for interviews and Task Cards. See Connect an AI assistant |
| CLI | Advisors and FDEs in a terminal | The same advisor tools as commands, plus pull and push of the Company Repo. See CLI |
| Autopilot | The advisor | DutyGraph Agent running on its own. It reads the map, finds gaps by rule, and proposes questions to send. See Keep it current |
Three rules hold on every AI surface:
- AI proposes, people confirm. A draft never becomes a fact until the person who owns it says so.
- AI runs as the person who asked. No tool or persona gets more access than that person has in the app.
- Nothing sent to DutyGraph is turned away. If an answer is raw or badly formed, it is saved first and tidied later.
What it is used for
- Getting ready for AI. An agent needs to know the task, the inputs and who approves. That is a Task Card.
- Key-person risk. The map shows work that only one person knows how to do.
- Buying or selling a company. See Knowledge transfer for M&A.
- Onboarding and cover. A new hire reads the role profile and Task Cards instead of shadowing someone for months.