Working with actions
An action is a task extracted from your project’s communications — assigned to an owner, with a due date where one was stated. Actions fill the action register and surface in each person’s My work view. This page covers what you do with one day-to-day.
Where actions live
Section titled “Where actions live”The register page lists actions, with a My actions toggle, a Current / All switch (Current shows the live head of each thread; superseded and duplicate versions group underneath), and an Import button. Expand a row to assign or unassign an owner, see its relationships, or open its full detail page.
The detail page (Open detail (evidence, notes, history)) is where you work an action: its evidence chain back to source communications, audit history, relationships, notes, and a Draft email button.
Each action has a Notes box on its detail page for working context — what’s been tried, who said what. Type and Save; the note is saved on the action and the change is recorded in its audit history. Notes are also read by the auto-completion judge and the email drafter, so anything you record here informs both.
Email-driven completion
Section titled “Email-driven completion”When a reply lands in the project inbox, ddx PMO checks whether it completes any open action linked to that email thread (or owned by the sender). One of two things happens.
- Auto-close. The action is marked done automatically, recorded in the audit history as an automated change (attributed to the system) with the supporting quote. It then appears under Auto-completed recently in My work, each row with an Undo button.
- Suggestion. A done? chip appears on the action with ✓ to confirm (marks it done) or ✕ to dismiss. The chip’s tooltip shows the reasoning, the quote behind it, and the confidence. The chip shows on the register and in My work.
The chip and the Auto-completed recently row quote the email or Slack message they came from, so you only see them if you can open that message. It may not be the email the action came from: any later reply in the thread, or any message from the action’s owner, counts — including one in a private Slack channel or a supplier’s bid. If you can see the action but not that message, you see no chip, and you can’t confirm or dismiss it. The action stays open until someone who can see the message decides, or until it’s closed the usual way.
Auto-close only happens when all of these hold: the judge is highly confident, the sender passed email authentication (SPF, with the authenticated domain aligned to the From address) and is the action’s owner, the owner can open the message (so the close shows in their My work, with its Undo), the email carries no prompt-injection flags, and the action has had no prior Undo or dismissal. Otherwise you get the suggestion chip instead. (Slack messages count as authenticated by the workspace connection rather than by email checks.) An owner with no ddx PMO login, such as a client’s or a supplier’s contact, counts as able to open what anyone outside the workspace could: their ordinary email still closes their action, but a message from a private channel or a bid only raises a suggestion.
Draft a reply
Section titled “Draft a reply”Draft email on an action’s detail page generates an editable reply grounded in the project’s knowledge — the action’s evidence, your notes, and the stakeholder directory. It suggests recipient candidates (advisory — pick one or type your own), a subject, and a body, all editable, with a Check before sending list of caveats where relevant.
ddx PMO does not send mail. Copy to clipboard is the primary action;
Open in mail client opens the draft via a mailto: link (disabled for very
long drafts, where Copy is the reliable path). Review and send from your own
email.