How Dwight works
Process depth for operators who want the full loop.
The landing page shows outcomes: clearer priorities, protected deep work, cleaner handoffs, fewer false fires. This page shows the machinery — how sources become judgment, how actions get staged, and where you stay in control.
Built for people managing humans and agents at once: multitasking, creative and strategic work, shifting stakeholders, and the need to stay excellent on execution without losing the big picture.
The loop
Connect the places work already lives
Calendar, mail, docs, Slack, meeting notes, time logs, and other connectors. Dwight does not start from a blank list you must fill by hand.
Score the day into a matrix
Each live signal becomes a card. Placement answers two trade-offs: how important is this, and how urgent is this. Position is the recommendation.
Correct in the open
Drag a card, ask why, edit details, or skip. Corrections are feedback to judgment — not just UI rearranging.
Stage the next move
For clear follow-through, Dwight prepares drafts, calendar blocks, source checks, research packets, or handoffs to operator runtimes.
You approve what leaves the building
Sensitive writes stay approval-first. Dwight shows evidence and the proposed action. You approve, edit, skip, or send to a trusted runner.
Learn from what actually happened
Approvals, skips, completed work, repeated avoidance, and protected time held or lost shape the next score — so the board gets closer to your real priorities.
Judgment model
Where a card lands is the verdict.
Dwight uses the Eisenhower Matrix because priority is a trade-off, not a sorted list. Two questions place every card: how urgent is it, and how important is it? You can accept the call, drag it, ask why, or turn it into an approved action.
Stephen Covey called the important-but-not-yet-urgent work “Quadrant II” — the work that compounds when protected and erodes when the day fills with other people's urgency. Getting more of your week into that quadrant is the point.
DO
Important and time-sensitive. Finish, decide, or unblock today.
PROTECT & BE HERE
Important before it gets loud. Defend time for the deep work that compounds.
DELEGATE + APPROVE
Loud or waiting on you. Batch, draft, delegate, or approve efficiently.
DELEGATE + AUTO
Low value or stale. Drop it, archive it, or let automation keep it quiet.
Memory, intelligence, judgment
The same product model runs across matrix, chat, cards, mobile, and operator handoffs.
Memory
Dwight remembers the shape of your work: clients, projects, commitments, goals, sources, drags, skips, approvals, and outcomes — only when that improves the next judgment or removes restart friction.
Intelligence
Signals are read together. Calendar pressure, email asks, documents, meetings, time spent, goals, people load, and past behavior become one view of the day — not isolated notifications.
Judgment
Judgment is the placement. A card is not merely ranked; it is given a stance: do it now, protect it, respond efficiently, or let machines and process handle the low-value remainder.
Surfaces
One judgment. Many doors.
The interface can change. The memory and judgment should not. Matrix, chat, cards, Agentic actions, review loops, and mobile capture all point at the same source-aware model of your work.
Matrix
See what matters now
A live Eisenhower board built from real work signals, not a static to-do list.
Ask Dwight
Reason across the day
Ask what to do, why something sits where it sits, what changed, or what still needs a human call.
Card workspace
Move one item forward
Evidence, source links, first steps, and staged actions for a single card.
Agentic queue
Clear drag without silent autonomy
Drafts, blocks, lookups, research, and operator handoffs wait for review where it matters.
Review loops
Teach judgment
Approve, skip, drag, finish, or mark stale. Outcomes become memory for the next day.
Mobile + companions
Capture and decide anywhere
Lightweight surfaces for quick capture, approvals, and source-aware follow-through when you are not at the desk.
Operating stack
You manage people and agents. Dwight keeps the shared picture honest.
Dwight is the judgment and memory layer. Operator runtimes can take scoped work. Connectors supply truth. You stay the final authority when something is irreversible or political.
Dwight
Cockpit, memory, judgment, approvals
Holds personal context, decides what matters, and stages what is safe or useful to prepare.
People you manage
Stakeholders and collaborators
Deadlines, asks, and commitments stay visible so human coordination does not fight the board.
Hermes / OpenClaw / operator runtimes
Hands and tools
Scoped execution for browse, code, research, or multi-step tool use — returning evidence for review.
Connectors
Source truth
Google, Slack, Gmail, Calendar, Drive, meeting notes, time trackers, chat, and other configured services supply live signals.
You
Final authority
Set goals, correct judgments, approve writes, and decide when Dwight should push versus wait.
Prefer a worked example first? Run the simulation.