Opportunities: your team's hours and the proposed agents
Opportunities is in the main sidebar, after the Work Map. It says what to change. Each tab is a place where you act:
| Tab | What you do there |
|---|---|
| Your team (it opens first) | See each person's Task Cards in hours a week, switch to With proposed agents for the time back, and open an agent in the builder from its Task Card |
| Proposed agents | Open a proposed agent, or draft the ask that unblocks one that is not proposed (Agents guide) |
| Possible constraints | Accept or reject each possible constraint (C1, C2 …) with an owner or a reason. The Theory of Constraints exhibit opens from a constraint (Strategy guide) |
| Changes | Choose and record the change for each possible constraint, cheapest first, and draft the asks for missing numbers. A change's AI fit opens What AI can do today (Route guide) |
Status, October 13, 2026: built on matt/dev; the hours ranges and the AI-fit proposals were added on October 14. DutyGraph does not run or deploy agents. It builds them and exports them to the client's own AI tool.
Your team
The people are the page. One line at the top gives the numbers (the mapped hours, the people, how many Task Cards have their time, the proposed agents) and the toggle. Each bar is a Task Card, as long as the hours a week it takes, on 1 scale with the hours at the top. Each person has a row, grouped by team. The teams and people with a proposed agent come first.
- Current process. The agents' Task Cards are a light gray: today's process is not a warning. Other Task Cards are a darker gray.
- With proposed agents. Each agent's Task Card splits into the person's time with the agent (solid green) and the time back (a lighter green hatch, inside today's length). The right column adds "+… h back".
- The team's time back shows in the top line when the toggle is on With proposed agents (5.5–14.5 h a week on the sample).
- ✦1 Supplier record drafter → under a Task Card opens that agent in the builder, filled from that person and Task Card. The number is its rank: a link to a possible constraint first, then the time back.
- ⚑ C1, C2 mark a possible constraint (C for constraint; the keys were K1, K2 before October 13, 2026, and old K links still open). Select How is this worked out? for the arithmetic, and Show as a table for the numbers.
On a phone (760 px wide or less) the page puts the numbers first: 1 line (the mapped hours, the people, the proposed agents) with Details under it (how many Task Cards have their time, Reported, How?), then a 1-line Today | With agents switch. The legend and the scale notes sit under Key, closed. Each person is a card: name, role and total, 1 full-width bar on the team's scale, then each Task Card with its hours. The agent chip opens the builder and the C1, C2 chip opens Possible constraints with that constraint in focus; both have a 44 px tap target. On the other tabs, Proposed agents keeps the headline and puts the page sentence under How these are proposed, Possible constraints lists each flow on 1 compact row, and Changes gives each card the full width and leaves out Print.
Where the hours come from
- Each role template's team questions ask "About how many hours a week does this take?" (question 3, after the walk-through of the work). Discovery also asks the person who does a Task Card with no time: "How many hours a week do you spend on {task}, as a low and a high number?". On the answer page the person taps a range (Less than 1 hour, 1–2, 2–5, 5–10, 10–20 or More than 20 hours) or Not sure. Code reads the range, with no AI, and it reads Reported.
- An ask about 1 Task Card gives that card its hours when the person answers. A template answer is about work that has no Task Card yet: when 1 Task Card is drafted from the answer, the hours go to it; when several are drafted, Repo › To review asks which card they are for.
- With no answer, the time is runs a month × minutes per run, when Route has both numbers.
- A Task Card with neither shows time not captured, striped and off the scale. It is never 0.
- The hours with an agent are a prediction (Predicted). Only the sample companies have predictions. A real company has none until one is recorded, and the page says "Not predicted yet". After a pilot, Outcomes shows the measured hours.
- Capacity back = today's low − with-agent high, up to today's high − with-agent low. It is time for other work. It is not a saving, and DutyGraph shows no money.
The sample company's hours are fictional, authored answers. They read Reported · sample and Predicted · sample.
Known limit. This view shows time by a named person. The Route rule (no screen groups time by a named person) is not applied here yet. Use it with advisors, forward deployed engineers and investors on fictional or consented data until that is settled.
A real company's first proposed agent
On a real company the page starts empty: "No hours captured yet", and no proposed agent. Code proposes an agent only for a Task Card with an accountable owner and a proposed AI mode, or one that an accepted possible constraint cites.
The AI-fit pass (since October 14, 2026) fills most of this for you, by code and with no AI call. After Task Cards are drafted or changed, it reads each card and leaves proposals in Repo › To review, under AI modes, owners and hours for Task Cards:
- an AI mode for a card still on "People only", with a plain reason (for example, a step that moves money keeps a person deciding);
- the person who does the work: the person whose answer the card was drafted from;
- an owner: that person's manager in the roster;
- which Task Card a template hours answer is for, when several were drafted from it.
Select Accept the mode, Accept the owner, Accept or the Task Card, or Not now. Nothing changes until you accept. The pass does not run on the sample companies.
While proposals wait, Your team says what is missing (and Proposed agents says it when no agent is proposed), for example "2 Task Cards need an AI mode and 1 needs an owner — review the proposals in Repo › To review.", with Open To review.
To get the first proposal:
- Draft Task Cards from the team answers (Discovery › Draft task cards, which needs OpenAI, or write them yourself).
- Accept the proposals in Repo › To review.
- Where nothing is proposed, name an owner or set a proposed AI mode by hand: in Work Map › Task Cards, select the card, then Open Task Card and Edit record. Set Proposed operating mode. Or accept a possible constraint that cites the card. Not proposed says "No accountable owner" until there is one; select Draft the ask to ask who owns it.
- For a card with no time, ask the person who does the work (Open the asks).
See Run a company through DutyGraph, step 7.