How d5s fits together

d5s separates ownership, reusable context, work behavior, and individual executions. The separation is deliberate: a scheduled job can reuse the same approved context as a chat without turning every earlier conversation into a new instruction.

The hierarchy

1. An organization owns the broader member, group, billing, usage, and audit boundary. It can contain multiple workspaces.
2. A workspace is one day-to-day operating area. It contains projects and its own model, skill, connector, and API-key catalogs.
3. A project owns the reusable context and sharing policy for a body of work.
4. A chat, agent, automation, or dashboard determines how work is initiated and presented.
5. A session is the durable conversation or execution record.
6. A run is one active attempt inside that record.

Every runnable activity has a project. Starting a chat, automation, or dashboard without selecting one creates a hidden, unpromoted project for that activity. Explicitly creating a project makes it visible in Projects, and Save as project can promote the hidden project behind a standalone chat. Staffing an agent creates a dedicated home project that is managed through the agent and intentionally excluded from Projects and project search.

How the work modes use sessions

• A chat keeps one interactive session with multiple turns.
• An agent owns one continuing session for its entire lifetime. Manual messages, wakeups, heartbeats, and scheduled wakeups append to it.
• Each automation execution creates a new automation session, so run history stays independent.
• Each dashboard build or refresh creates a new dashboard session and can publish a new artifact version.

Context and capabilities

Context is what the agent can know: standing instructions, conversation history, project memory, and files. Capabilities are what it can do: follow a skill, call an activated connector, search the web, execute code, or create an artifact.

Workspace availability, project activation, and runtime approval are separate checks. For example, connecting GitHub makes a credential available in the workspace; activating it makes it available to one project; an Ask tool can still pause a run for a person to approve the exact action.

Execution remains visible

A message or trigger creates a turn. d5s records admission, queueing, execution events, tool calls, usage, and a terminal result. A sandbox is provisioned when a run needs one; it is an execution environment, not the source of project memory.

This model lets you stop a run without deleting its conversation, branch a completed response into a new chat, inspect an automation's past executions, or restore an earlier dashboard version without losing the resource that produced it.