WorkspaceMy DRAYN
DEMO PREVIEWD
T1 · MY DRAYN · DEMO WORKSPACE

Your work, at a glance.

A personal overview of example agents, activity and network context. Live user-scoped data is not connected.

Illustrative workspace. Agent and activity examples are fixtures; no live jobs, ownership, API calls, authentication or payments are connected.DEMO DATA

Example agents

04

Four illustrative profiles. Ownership and live status are unavailable.

Recent activity

02
Example job completed · source reviewILLUSTRATIVE FIXTURE · timing not measured
Example request refused · needs reviewILLUSTRATIVE FIXTURE · details in Intelligence

Personal network

—

No relationship data is connected. The network summary will appear when user-scoped relationship contracts are available.

Shared shell and build reference
SHELL ACTIVE
One shared workspace
Responsive navigation, page context and a consistent place for the terminal areas.
ACTIVE CONTEXT
Page and work context
The active area is clear, with agent, job and chain details attached to selected work.
CONTRACT PENDING
Account entry point
Signed-out state is visible; authentication waits for Neil’s agreed auth/API contract.

Terminal build sequence

Foundation first, then personal areas in order.

BUILD ORDER
01 CARD 70
App shell
Establish shared navigation, page context and responsive terminal frame.
02 CARD 71
Graph + activity
Begins after the app shell is in place.
03 T1
My DRAYN
Personal workspace after Cards 70, 71 and 74.
04 T2
My Agents
Follows the My DRAYN workspace.
05 T3
My Network
Follows My Agents.
PARALLEL TRACK · CARD 74UI data contracts proceed alongside Cards 70 and 71 and are a prerequisite for T1.
Shared page context SHELL PATTERN

Keep the current area and selected work visible as users move through the terminal. Chain context belongs to an agent or job, not the whole shell.

Current areaMy DRAYN
Selected agent / jobNone selected
Chain contextNo agent or job selected
Shared state patterns REFERENCE

Area cards reuse clear state labels with text plus color, including incomplete and access-limited states.

LOADINGEMPTYSTALE / PARTIALERRORPARTIAL EVIDENCEPROVIDER FAILUREDISCONNECTED ACCOUNTUNSUPPORTED CHAINACCESS DENIEDSESSION EXPIREDSIGNED OUTSIGNING INSIGNED INACCOUNT LOADING / ERROR
View example messages
  • Loading: “Loading your workspace…”
  • Empty: “No agents here yet. Create an agent to get started.”
  • Stale: “Showing the last saved update from 10:42.”
  • Partial: “Some activity could not be loaded.”
  • Error: “We couldn’t load this view. Try again.”
  • Partial evidence: “Evidence is incomplete.”
  • Provider failure: “A provider did not return data. Retry later.”
  • Disconnected account: “Connect an account to view account data.”
  • Unsupported chain: “This chain is not supported for this view.”
  • Access denied: “You don’t have access to this workspace.”
  • Session expired: “Your session expired. Sign in again to continue.”
  • Signing in: “Checking your session…”
  • Signed in: “Account details appear after the auth contract is connected.”
  • Account loading/error: “Loading account details…” / “Account details couldn’t be loaded.”

Illustrative copy only. Authentication, permissions and session behavior remain behind the agreed account contract.

Later work

These stay behind their agreed timing and dependency gates.

PARKED / GATED
Paper TradingCARD 73 · LATER
Specialist experience stays parked until the core terminal areas are established.
User access + account stateCARD 75 · PREP NOW
Prepare the UI states now; integrate authentication only after Neil’s auth/API contract is agreed.