Flow
From possibility to completed work
DX Complete keeps ideas, decisions, work, evidence, and completion connected while people retain authority over each meaningful transition.
Understand the matter
A possibility may begin as source evidence or conversation. Conversation is not automatically recorded. Discussion stays off the record until someone clearly asks to preserve an identified proposal or other durable context.
Define the Target and Direction
The Principal fixes the Target's bounded result, numbered completion checks, constraints, and exclusions. These do not change after work starts; a material change needs a new Target. The Direction defines the chosen course and governing decisions.
Authorize end-to-end delivery
Clear natural language is enough. The Principal engages Direct Delivery to reach the Target within the Direction. The current capable and authorized session then delivers that Target. This does not authorize unrelated work.
Use one capable session
The current capable session performs the accepted Target. It can use a bounded subagent when distinct capability, isolation, useful parallel work, or independent review provides a clear benefit. The subagent remains part of the same delivery and gains no authority.
DX Complete does not create a parallel delivery structure, backlog, polling loop, or automatic handoff. If the session cannot finish, it preserves the unchanged Target, records the exact stopping condition and next safe action, and returns control to the Principal.
Act, check, and report
The current session and any bounded subagents perform the work and report what they completed, what they checked, and any known limits. Independent review is tied to the Target and can give factual advice. It cannot add a completion check, approve the work, block it, or start a review loop.
Brief the Principal
The delivering session records closeout without an automatic review loop. Closeout states what changed, what was checked, and any genuine residual risk. The Executive restores the context the Principal needs to understand the result. Older governance records remain readable.
Use one name for each part of the work
The Principal starts it manually. Executive sessions can run side by side and retain long context.
The current capable and authorized session performs, checks, releases, and closes the accepted Target.
A subagent can add capability, isolation, parallel work, or independent review inside the same Direct Delivery engagement.
The Target states the result, numbered completion checks, constraints, and exclusions. A material change after engagement requires a new Target.
A decision, date, access grant, dependency, or required operational check stays a condition rather than becoming pretend agent work.
These records preserve history but cannot direct new work.
Keep unresolved source evidence visible
A candidate is source-backed evidence of a potentially important unresolved matter. It may be an idea or opportunity, a signal or anomaly, a dropped follow-up, or something that belongs in another workspace. Discovery does not make it true, urgent, assigned, accepted, or authorized.
Each candidate identifies its exact source and revision, preserves only the minimum safe evidence, and states confidence separately from possible impact.
A candidate is promoted, merged with existing work, dismissed, routed, deferred to an exact condition or date, or marked as not a candidate. It is never parked indefinitely.
Ideas can enter proposal work. Signals go to verification or triage. Missing follow-ups identify what is absent. Cross-workspace matters require separate authority before anything is written elsewhere.
Three ways to regain context
An on-demand briefing explains what each active matter is, why it exists, where it stands, what changed, and the next move or exact condition.
A current read-only analysis narrows the active portfolio to matters that need action, a decision, awareness, or an honestly unknown next relationship.
A scheduled report sends only meaningful record changes and near events. Silence is normal when nothing qualifies.
When a material gate needs your answer
When a real blocker, approval, load-bearing decision, material scope or risk choice, or authority boundary needs your input, the agent first restores the context: what the matter is, where it stands, what changed, why the answer matters now, and what the answer can affect.
The agent states its recommendation, the short reason, and the main tradeoff. It does not hide its view behind a neutral-sounding approval request.
When one message contains several atomic questions, label them Q1, Q2, and so on. A lone question may be unnumbered; numbering restarts in the next message.
A decision, an engagement, and a technical permission are shown separately. Silence is never treated as approval.
If you explicitly delegate one bounded decision, the agent's stated recommendation becomes the operative choice within that scope. Ordinary conversation remains ordinary conversation; this format is reserved for decisions that genuinely carry the work forward.
Personal Space is the default overview
Sign in without choosing a workspace and DX Complete opens your Personal Space: a compact Attention Queue and consolidated schedule across every workspace you can access. Human and domain matters remain distinct from automations, and every item links back to its source.
All accessible workspaces are included by default. You can mute one to remove it from your Personal Space and Daily Brief. Muting is your reversible setting; it does not change membership, records, workflows, or anyone else's view.
Personal Space is not the same as your personal workspace. Personal Space is an unshared overview. Your dxcuser- personal workspace is an ordinary workspace for personal records and can be shared without sharing your overview.
Catch up on shared working rules
A workspace catch-up also checks whether DX Complete’s shared working rules changed since that session last visited. When nothing changed, there is nothing extra to review. When they changed, the assistant receives a short current baseline or only the later relevant updates, with critical changes called out before affected action.
This check does not open another workspace or grant authority. It supplies shared context; the current workspace, the person’s direction, and the applicable current instructions still control the work.
Pause safely when sign-in needs a person
Authenticated testing follows three stages: prepare what can be prepared, pause at the human access checkpoint, then verify the signed-in state before resuming the approved test.
The assistant follows the agreed test plan and distinguishes a real sign-in need from a setup, membership, permission, or service defect.
The assistant uses the exact persistent in-app Browser tab only after it proves that the tab is visible and interactive. Passwords, verification codes, and other secrets stay in the sign-in page and out of the conversation.
Your confirmation is followed by an independent check that the signed-in state works. Only the already approved test resumes.
If the browser session is unavailable or access still fails, the assistant stops with a sanitized explanation of the exact blocker. It does not try alternate profiles, substitute callbacks, or improvise a bypass.
Before creating a sign-in attempt, the assistant proves five conditions together: the service and sign-in issuer match; one live callback listener is ready; the callback, return page, resource, and security bindings match; the exact in-app Browser tab is visible and interactive; and the continuation page is valid. Previews, screenshots, picture-in-picture windows, side panels, and another browser do not qualify.
The sequence is fixed: prepare one listener, verify one tab, verify live service metadata, create one fresh attempt, validate every binding and the continuation page, present it once, wait for you, receive the callback, verify the signed-in state, and finish. A failed check invalidates that attempt and it cannot resume.
A failure before creation makes no attempt. A later failure consumes the attempt. After the exact cause is repaired, the assistant restarts every check and may create at most one replacement. If that replacement fails, it stops; there is no third attempt.
Evidence contains only a separate reference, the failed stage and cause category, time, software build, the service address without its query, and the release identity. It never keeps sign-in state, verification values, codes, tokens, credentials, sign-in links, callback details, or provider content.
Plain words follow the current position
A bare “proceed” or “continue” advances one legitimate lifecycle step from where the matter stands. It does not silently run every remaining step. When two next steps are possible, or a condition prevents either, the agent presents the choice or exact condition instead of choosing for the principal.
“Memorialize” preserves identified context. “Propose” creates or continues an idea. A clear lifecycle direction to “Recommend” one identified durable idea prepares its decision case; asking what the agent recommends remains discussion and writes nothing. “Engage” directs the current capable session to carry an accepted Target through Direct Delivery.
Engage applies to a named Target or the single unambiguous matter immediately before it. A workspace-wide cycle must be explicit. If several Targets are plausible, the Executive asks. Delivery begins in the current capable session.
Write for the first careful reading
DX Complete uses a shared writing standard for assistant-authored responses, records, briefs, reports, documentation, and email. Technical instructions use Simplified Technical English when it fits. Other writing follows the same plain-language discipline.
In ordinary discussion, the assistant starts with the shortest useful plain-language answer. It does not volunteer technical or behind-the-scenes detail by default. It adds that detail when requested or when needed to explain a material blocker, risk, cost, tradeoff, evidence, authority boundary, or next step.
Prefer direct sentences and explain necessary specialist terms.
Remove repetition, but keep material facts, evidence, risks, boundaries, and next steps.
State the subject, action, uncertainty, and condition without avoidable ambiguity.
Use a respectful voice without invented familiarity or mechanical formality.
Exact quotations, code, identifiers, legal wording, and other source evidence stay exact. A writing standard improves expression; it does not grant permission to record, publish, communicate, or act.
Keep the current state visible
An accepted engaged Target is the current work contract. Job and task records are historical compatibility only.
Put the reminder on the record so the follow-up and its history remain visible.
Add a dated strike notice and the struck tag. The record and its history remain readable.
Use an ordinary record tagged event. State an exact date, a range, or honest wording such as late July, then add the outcome afterward.
DX Complete creates an ordinary workspace for records that belong to you rather than a project. Its stable address starts with dxcuser-.
The signed-in default combines an Attention Queue and schedule without moving source records or granting authority.
Genuine escalations appear under Important. Other material changes and near events appear as concise numbered updates.