My Work and Workrooms

Overview

My Work is the Workspace view of active company work available to you. Each item opens a Workroom: a focused place where authorized people and AI coworkers coordinate toward a named outcome.

A Workroom is not an unbounded chat channel. It has a work boundary: purpose, outcome, scope, accountability, authority, sensitivity, measures, timing, and a closure rule. The platform keeps the underlying governed Work Case and its evidence; the room presents that structure in language suited to doing the work.

What You See First

The top of a Workroom answers four questions:

1. What outcome does this room own?
2. What needs attention now?
3. Who is accountable and who is participating?
4. What is the next action?

Source identifiers, integration status, and projection confidence remain available under Room details. They do not displace the outcome or the people doing the work.

Activity and Participants

The Activity stream distinguishes messages, asks, coworker handoffs, work changes, decisions, artifacts, governed actions, verification, receipts, and cycle transitions. A message is an update; it is not proof that the outcome was achieved.

People and AI coworkers appear together as named participants. Their room role and current work state are separate:

• Accountable owns the room outcome.
• Coordinator keeps the room on-task to its outcome—curating who is in the room, sequencing turns, and driving to a decision, close, or escalation. A room has exactly one Coordinator; it may be the same person or coworker as the Accountable, or a different one. When no one is named, the Accountable coordinates by default.
• Contributor performs work in the room.
• Reviewer verifies work or an outcome.
• Observer follows the room without changing it.

AI coworkers remain governed participants. Joining a room does not expand their authority, and a visible presence signal does not grant permission.

An admitted coworker can read the room’s message feed and post into it, and appears as present while it works. Whether a coworker may read or post is decided per room, scoped to that room’s outcome and sensitivity—being admitted to one room grants nothing in another. A coworker working the room’s underlying task (for example an external CLI session on the room’s build) is admitted to that room as it joins.

A room can also call in new participants on demand: a member with action rights (typically the Coordinator) can invite another coworker or a person into the room, either to participate or read-only. The invitee is admitted only to that room, for that room’s outcome—never granted anything elsewhere.

Across rooms, you can see where each AI coworker is engaged—which active rooms it is in and its role in each (including where it coordinates). This 360 view helps manage how coworkers are used and recognise the routine patterns worth pre-positioning them for.

An authorized coworker can also open a relevant product surface from the room’s work type, resources, or task intent—even when no browser page is rendered. These silent/headless surfaces use the same semantic fields, validation, and governed actions as the human browser or mobile view. Room membership still does not expand authority: the surface catalog and every action apply the human role, coworker grants, room/work context, token scope, and approval rules together.

Open Participants to see why each person or coworker is in the room, what they are working on, their authority summary, and an AI coworker’s accountable sponsor. Coworkers created by the active thread’s governed lineage appear automatically; the room does not provide an unrestricted coworker picker.

Access and Other Channels

Room access has separate discovery, content, and action boundaries. Assignment or an explicit room policy admits a principal; a presence heartbeat never does. Sensitivity clearance is checked on the server before messages, participants, or context load. A person without content access receives the same not-found experience as an unknown room.

When an existing communication adapter attaches a Teams, Slack, email, or other external conversation to a Workroom, DPF remains the canonical context:

• concise notifications carry a link back to the internal room and its canonical Work Case reference;
• the channel binding resolves the external subject to one Principal before an inbound event can attach;
• a stable provider event identifier prevents duplicate room activity;
• sensitive actions pause for stronger authentication instead of completing in chat;
• sent or delivered status proves transport only, not that governed work completed;
• if an adapter cannot receive or interact, the channel reports a degraded state while the DPF room remains usable.

Unresolved external identities or room attachments are quarantined from room activity. Provider-specific setup and capabilities remain part of Employee Communication administration, not the Workroom itself.

Finite and Standing Rooms

• A finite room closes when its bounded outcome and closure rule are satisfied.
• A standing room supports recurring work. Each cycle still has its own objective, measures, stop conditions, and structured outcome.

Completion produces an Outcome Packet from governed decisions, artifacts, actions, receipts, evidence, and unresolved work. Conversation alone cannot complete a room.

In a standing room, the Current cycle panel shows the objective, trigger, review point, measure of done, and stop conditions before the general activity stream. When no cycle is active, the room says that it is healthy and idle rather than implying that recurring work is complete.

Completed cycles are ordered by completion time. Open a completed cycle to read its Outcome Packet, durable-record count, verification state, and unresolved work. Each unresolved item has an explicit disposition: carry it into the next cycle, open a separate case, defer it, or accept it. Retrying carry-over does not create duplicate work.

Pace and Priority

Every room shows the pace it is working at, in a Pace and priority section that stays closed until you open it. It answers one question: why is the coworker in this room behaving the way it is.

Inside, the room states:

• Pace — whether the coworker stays quiet, follows up, or pushes and escalates, and whether it advises, asks first, or acts alone.
• Where that came from — a policy floor, the room’s own choice, the shape of the work, the coworker’s own setting, or the platform default.
• Priority — whether this work leans toward quality, cost, or speed.
• Checking — whether work here is verified before it counts as done.
• Why — the specific reason for each change, in plain terms.

The pace is worked out from the room, not just from the coworker. Three things move it:

• The shape of the work. An escalation pushes harder because someone is waiting. Work that faces outward — anything leaving the business under its own name — is verified before it goes. Standing corpus curation stays in the background.
• What the business does. A business whose demand is emergency-driven, or whose capacity is lost rather than delayed when it goes unused, warrants earlier attention.
• The clock. When the business is closed, follow-up quietens down. When an obligation is due soon, it speeds up.

Two rules keep this safe.

Closing time changes how loudly a coworker follows up. It never changes what a coworker is allowed to do. An out-of-hours room is quieter; its approval requirements are exactly what they were during the day.

Some work is never quietened. Security incidents, platform and queue health, and a field appointment already running late keep their pace when the business is closed, because those problems get worse while nobody is looking.

If a room has nothing of its own to say about pace, it says so — “Running on defaults” — rather than implying a decision nobody made.

Giving a Room Its Shape

A room can be opened with a shape — a short statement of how decisions inside it are meant to route. The shape is what sets the room’s pace and priority, so it is the single most useful thing to get right when the room is created.

Setting the shape changes how the room behaves. An escalation room pushes harder, because someone is waiting. An outward review room verifies before anything leaves. A craft stewardship room stays quiet, because it is background work.

If a room is not given a shape, the platform will work one out where the room says enough about itself — a standing profession room is craft stewardship, a readiness check is an approval sign-off. Where the room does not say enough, it stays unshaped and simply runs on defaults. It will not invent a shape, because a made-up shape would change how the room behaves for reasons nobody chose.

Most rooms created before this existed are unshaped. Giving them a shape is worthwhile for any room where pace or verification actually matters.

Incomplete or Unavailable Rooms

If a room boundary is incomplete, the page identifies the missing elements instead of inventing them. If the source is unavailable, the last available projection is marked clearly and the page gives one recovery direction. If an AI coworker’s current status is unavailable, the participant panel says so and directs you back to the room’s next action instead of implying that the coworker is still working.

If you do not have access, the internal room title, participants, source references, and sensitivity details are not shown. External customer case pages remain customer-safe case summaries; they do not expose internal Workroom controls or participants.