Appearance
Test flows
This page is for: new advisors and forward-deployed engineers, and the people who train them.
Use these flows to check that a new workspace works from first sign-in to a finished map. They are written for a developer or a new advisor who has never used this workspace.
Flows 2, 3 and 4 were walked on November 12, 2026 with CLI version 0.2.1 and a new company. The expected results come from that run.
Rules for a test run
- Use invented companies and people only. Put "Fictional" or "Test" in the company name.
- Do each flow in order. Later flows use what earlier flows made.
- When a step does not give the expected result, stop that flow. Write down the flow, the step, what you saw and a screenshot.
- Do not send email to real people. The flows below do not need email.
Replace <address> with the test address you were given: a preview deployment or a local run. Do not run these flows on https://dutygraph.com. That is the live product, and Flow 3 creates a company and people. If you were given no test address, ask for one before you start.
Flow 1. Start a blank workspace
Where: the advisor dashboard, in a browser. Time: 5 minutes.
| Step | Do this | Expected result |
|---|---|---|
| 1 | Open <address>/app and select Create an advisor workspace. Enter your name, email, a password, your firm and its address. If the address is invitation only, open your invitation link instead. | You land on Home. |
| 2 | Look at Home and the left rail. | Home has a New company button and no companies of your own. The rail shows Home, Inbox, Companies, Skills, Settings and Help. |
| 3 | Open the sample company (Cobalt Industrial Supply) from the sidebar. | The company opens on Overview with 12 people. Its pages are in the sidebar: Overview, Discovery, Repo, Work Map and more. |
| 4 | Sign out and sign in again. | You land on Home with the same workspace. |
Flow 2. Connect the CLI
Where: a terminal. Time: 5 minutes. Needs: Node 20 or later.
| Step | Do this | Expected result |
|---|---|---|
| 1 | npm install -g dutygraph then dutygraph --version | Prints 0.2.1 or later. |
| 2 | dutygraph --origin <address> login | The browser opens. After you approve, the terminal says you are signed in. |
| 3 | dutygraph --origin <address> whoami | Shows the address, the permissions read, write and a company count. |
| 4 | dutygraph --origin <address> companies | Lists the sample company with its id. |
If the browser sign-in does not finish, make a token in Settings › MCP access and run dutygraph --origin <address> login --token dgp_....
Flow 3. Set up a new company from the CLI
Where: a terminal. Time: 10 minutes. Add --origin <address> to each command.
Save this file as roster.csv first:
text
name,email,role,team,manager_email
Avery Stone,avery@harbor.example,CEO,Leadership,
Blake Reyes,blake@harbor.example,Operations manager,Operations,avery@harbor.example
Cam Ortiz,cam@harbor.example,Warehouse lead,Operations,blake@harbor.example| Step | Do this | Expected result |
|---|---|---|
| 1 | dutygraph client add --name "Fictional Harbor Tools" --method signed_sow --reference "SOW-001" --note "Test run" --website https://example.com | Shows what it will add and asks. After yes: "Added Fictional Harbor Tools", a company id, and "The engagement is active." |
| 2 | dutygraph use "Fictional Harbor Tools" | "Using Fictional Harbor Tools". |
| 3 | dutygraph roster import roster.csv | A preview: "3 people ready. 0 already present." Nothing is saved yet. |
| 4 | dutygraph roster import roster.csv --apply | "Added 3 people to Fictional Harbor Tools." |
| 5 | dutygraph team | Three rows. Invited is "No" for each. |
| 6 | Run step 4 again. | "0 people ready. 3 already present." and "No people to add." |
| 7 | dutygraph repo pull ./harbor-repo | A folder with about 80 files, including README.md, AGENTS.md, CLAUDE.md and a company folder. |
| 8 | Open the advisor dashboard and select the company switcher at the top of the sidebar. | Fictional Harbor Tools is in the list. Selecting it opens its Overview, marked Active. |
If step 1 answers that the tool is not found, the address runs an older server. See Which DutyGraph it talks to.
Flow 4. Run onboarding in the advisor dashboard
Where: the advisor dashboard, in Fictional Harbor Tools. Time: 20 minutes.
| Step | Do this | Expected result |
|---|---|---|
| 1 | Open the company, then Discovery, then Open Onboarding. | The Set up onboarding page shows a team list of 3 people. |
| 2 | Select Create onboarding session. | The Set up page shows the North Star session card and an org chart: Avery at the top, Blake under Avery, Cam under Blake. Everyone under the session is locked. |
| 3 | Pick a date, choose Avery in "Signed off by", and select Create. | The button changes to Run the session. |
| 4 | Select Run the session, then Run it live. | Question 1 of 15 shows, with the file it fills. |
| 5 | For three questions, select Type the answer, type two sentences, and go to the next question. | Each answer is kept when you go back. |
| 6 | Select Wrap-up. | "3 of 15 questions answered." Your answers show in the file tree below. |
| 6b | Select Save and send, then Go to departments and roles. | "Saved." The session card says "Done · locked in". Avery's card says "Ready to send". Blake is waiting for approval and Cam is locked after Blake. |
| 7 | Select Avery's card. | Avery's page shows their files on the left, the tabs Steps, Questions, Role profile and Stored, Send app link, and Avery's client app as a phone on the right. |
| 8 | In a terminal: dutygraph onboarding status | Lists the three people: Avery "session · 3/14 answered", Blake "open", Cam "locked", each with who they report to. |
| 9 | Open Readout. | "Mapping in progress", the company name, "Prepared for Avery Stone, CEO" and "Whole company · 3 people · 2 teams". |
A new company has no AI connection yet. This flow works without one. Where the app says it needs an AI key to write a draft, write down the place.
Flow 5. See the client app as a team member
Where: the advisor dashboard, in a browser. Time: 10 minutes.
| Step | Do this | Expected result |
|---|---|---|
| 1 | In Fictional Harbor Tools, select Client app in the header. | The client app viewer opens. It lists Avery, Blake and Cam. |
| 2 | Choose Avery. | Avery's client app shows as a desktop screen and as a phone screen, with what Avery can reach. |
| 3 | Choose Cam. | Cam's questions are not open yet. The screen says who Cam is waiting on. |
| 4 | Go back to Departments and roles and select Avery's card. | Avery's client app shows as a phone beside the Steps tab. Full page opens the same screen larger. |
Flow 6. Connect an AI assistant over MCP
Where: Claude Code, Claude.ai or another MCP client. Time: 10 minutes. See Connect an AI assistant.
| Step | Do this | Expected result |
|---|---|---|
| 1 | In Settings › MCP access, make a token with Read and Write. | A token that starts with dgp_ shows once. |
| 2 | Add the server to your client with the address <address>/api/mcp and the token. | The client lists DutyGraph's tools. |
| 3 | Ask: "List my DutyGraph companies." | The same companies as dutygraph companies, including Fictional Harbor Tools. |
| 4 | Ask: "Who is on the team at Fictional Harbor Tools, and who reports to whom?" | Avery, Blake and Cam with the right reporting lines. |
| 5 | In Settings, revoke the token. Ask the same question again. | The client reports that it is not signed in. |
Flow 7. Talk, the Work Map and the one-tap checks (sample company)
Where: the advisor dashboard, on the Cobalt sample company. Time: 15 minutes. This flow was not walked as a test run yet; the expected results come from the build notes of November 14 and 15, 2026.
| Step | Do this | Expected result |
|---|---|---|
| 1 | Open Client app, choose a team member, and open My work. | Talk about your work and Ask DutyGraph Agent are at the top. A person named on a teammate's card sees Mentioned you. |
| 2 | Select Talk about your work, type two sentences about a task, and select Done talking. | Without a speech key the screen opens in typing and says so. Found tasks lists what you said. In the preview, a save says "This is a preview. Nothing is saved or sent as this person." |
| 3 | On a Mentioned you check, select Sort of and type a few words. | The sample company's preview keeps the answer. |
| 4 | Open Work Map › Process map and click the Task Card on the other side of that hand-off. | Its lines show where the work arrives from and leaves to. The hand-off shows the person's "Sort of" and their words. |
| 5 | Open Work flows. | The tab shows how many workflows are suggested. The list has Confirmed, Suggested and Not workflows. |
| 6 | Pick a suggestion and select Confirm workflow, then Undo. | The workflow moves to Confirmed, then back to Suggested. |
| 7 | Ask DutyGraph Agent: "Where is the biggest constraint?" | With an AI connection, the answer names Task Cards by exact title and they ring green on the map. Without one, the Agent says no AI is connected. |
What to send back
For each flow: passed, or the step that failed with what you saw. Add anything that was slow, unclear or surprising, even when the step passed. A confusing screen is a finding.