Work Map

The Work Map shows how work moves through the business. It does not show who reports to whom. Open Work Map in the company sidebar. The page has 4 tabs: Value chain, Work flows, Task Cards and People. All 4 tabs read the same work as the Company Repo, in the same state.

Business stages are broader than duties. A stage groups work across roles. A duty is an ongoing responsibility. A Task Card is one specific task. There is no fixed number of stages. Templates are starting points, and a saved stream has 1 to 16 stages. Edit the stages and their descriptions in Discovery > Edit the profile and stages.

Value chain

The Value chain is a grid. The columns are the stages of the stream, from left to right. The rows are departments: the team of the person who owns each Task Card. Each cell holds the Task Cards of one stage and one department. If the company has more than 1 stream, choose the stream in the toolbar.

• Each Task Card is a chip with one line of text. The border shows the state of its file in the Company Repo. A solid border means Confirmed or Observed. A dashed border means Inferred or Proposed. An amber border with the word Disputed means that sources disagree.
• A dashed chip can also mean that AI proposed the stage. The inspector says Proposed stage.
• Each stage header gives its basis: "11 Task Cards · 0 confirmed · 10 people".
• A cell with more than 4 Task Cards shows 3 and "+N". Select "+N" to see all of them.
• "Hands off to" under a cell names the departments that receive work from it. Point at or select a Task Card to draw its handoffs as arrows.
• The Unassigned column at the right holds the Task Cards with no stage. It is always visible.
• The legend is one line above the grid. Select it to read more.

Select a stage header to open the stage on the right. The address changes to #graph/stage/<stream>/<stage>, so you can share the link. The panel lists the workflows (each opens in Work flows), the duties and the people of the stage. Select a Task Card to see its state, department, owner, the person who does the work, its stages, its proposed mode and its handoffs. Open Task Card opens the record. View in Company Repo opens its file.

Use Lens to mark one kind of signal at a time: Wait points, Automation candidates, Single holder or Gaps. The lens is off by default. A lens mark is a pointer to recorded work. It is not a finding. When the Company Repo has no signals yet, each lens shows 0. Use Find a Task Card to dim the chips that do not match.

The grid scrolls inside its frame and does not shrink the text. On a phone, the Value chain is a list of stages. Open a stage to see its departments and Task Cards.

Assign stages

Select the Unassigned header, or Assign stages in a Task Card panel. Choose the stages of each duty or Task Card. A duty can be in more than 1 stream or stage. The Task Cards of a duty follow its stages. A Task Card with its own stages keeps them. Clear the Task Card's stages to follow its duty again. A title, a duty name or a stage position never creates an assignment.

The Unassigned panel also lists links to removed stages, so you can choose a current stage. Saving an assignment creates a new record version and follows the usual review rules.

For older unassigned work, choose Connect existing work with AI in the Unassigned panel. Open a duty or Task Card to see the basis of an AI stage link. These links stay dashed until a person accepts them. They do not count as a confirmation.

People

People shows who holds which work. It has 2 views:

1. By stage (the default) is a matrix. The rows are people, grouped by department. The columns are the stages. A filled dot means that the person owns work in the stage. An open dot means that the person does the work of a Task Card there. On a phone, each department is a list.
2. Reporting lines shows the reporting chart of the Company Repo (the same chart as the Repo's Team layer). It is the only reporting chart in DutyGraph.

Select a person to open their panel: "Reports to", the duties and Task Cards they own, the Task Cards they do, and their open asks. The address changes to #graph/people/<person>. Owners and performers describe accountability and work. Neither role is an approval.

Work flows and Task Cards

Work flows follows one workflow, its tasks and its handoffs. Only a recorded handoff shows that work passes between tasks. A work flow opens as a process with Open as a process: Scope and Map are built, and the 4 later stages show as Planned. Task Cards shows the cards with their filters. Open the Client Brief on Reports to discuss priorities and prepare a report.

PostgreSQL is authoritative. Neo4j is a derived projection. The Cobalt sample has a saved, fictional business profile and stage assignments. You can edit them. An older sample with no profile shows an illustration that is labelled as such and that changes no record.

Ask about missing details

The section Work details to fill under the Value chain can flag an unexplained stage, a duty without Task Cards, missing details or people, and work whose sequence is not recorded. These are gaps in what DutyGraph knows. They are not proof that people work badly. A stage may not apply, and a Task Card may stand alone.

Choose a stage, then Ask about this work. Preview up to three questions and select the relevant people using their displayed, stored email addresses. Selection is deliberate: the whole roster is not enrolled. An unlinked person is not assigned questions just because of their job title. With continuing checks left on, this selection also authorizes later gap questions to those people. Turn it off for a single round.

Use Pause to stop queued automatic follow-ups and future checks; use Resume to continue for the saved selection. A send already in progress may finish. Only one work request stays open per person, new gap requests are spaced at least a week apart, and the same gap is not asked again automatically. An unanswered or unclear gap can still need advisor attention.

The private link lets the person speak or type, review the text, and submit. The answer is saved first. AI then proposes new work or fills missing details in eligible proposed records. Original evidence remains available; reviewed work, changed sources and conflicting accounts are held for advisor review. Delivery and processing status appear in the request history. A saved reply does not mean its AI update succeeded.

Sample workspaces allow question previews and send no emails. Real follow-ups need email and AI configured in Settings. Replies may describe actual task flows, but automatically captured flows are documentation only. They cannot start cases until an advisor configures and reviews them through the normal workflow controls.