Workspace Control Deck

Workflow runs end to end

Milestone 2 is active. One required journey blocks delivery.

75%

Ready

Agents

Risk

Focus stack

Needs attention now

Recent signals

Agent resumed session cursor-design-1 resumed with current board context.

Evaluator blocked delivery Invite teammate failed at Send invitation.

Proposal moved to design input Focus mode now informs Activity design.

Board

Task list

M2 Phase: resume-ctx Priority P6+

Docs

Project context

Agents

Connected agents

Activity

Live timeline

Live

Task detail

Task

Ready phase P0

Acceptance

Risk

Assigned agent

Unassigned

Context summary

This task belongs to the current milestone and should stay inside its phase boundary. Agents should run a scope check before claiming adjacent work.

Assign agent

Dispatch ready work

Ready agents can receive this task now. Offline agents must resume first.

Confirm dispatch

Send task to cursor-apply-2

The agent will receive the task, acceptance, risk, phase boundary, and context snapshot.

Dispatch packet

Claim exactly one task. Stay inside the current phase. Run the scope check first. Use TDD for runnable behavior. Report criteria and residual risk when finished.

Will not send

This is not a casual chat message. It is an explicit Hub Apply dispatch.

Reader

M2 Overview Spec

.sinaris/milestones/m2-overview.md

Milestone 2 focuses on end to end workflow execution, including task status flow, resume context wiring, hub updates, and evaluator readiness.

Related actions

Agent detail

cursor-design-1

Wire snapshots into resume

Busy

Latest transcript

I am checking the resume packet boundary and verifying the current task before changing code.

Reading file: ApplyContextPacketBuilder.cs

Availability policy

Busy agents can receive chat, but new task assignment should wait until they are ready.

Agent session

cursor-apply-2

Ready. Send a task dispatch or a focused follow-up.

Continue after the scope check.

I will address the user message first and keep the task boundary intact.

Updating task status: In progress

Command

Search workspace

Evaluator

Acceptance journeys

Delivery is blocked because a required user journey failed.

Failed User can invite a teammate

Step 3 failed: Send invitation. POST /api/invitations returned 500.

Running User can finish onboarding

Currently running step 3: Create first project.

Create agent

Prepare a new session

Review the prompt before the agent is created.