shykes

ARCHIVE: Workspace Artifacts Tracking

Running tracking doc for the original workspace-artifacts design session. Superseded by the Modules v2 design docs.

See: https://github.com/dagger/dagger/tree/modules-v2/hack/designs/modules-v2

---

Workspace Artifacts Tracking

shykes

ARCHIVE: Do We Need Artifact Addresses?

Analysis concluding that typed collection filters collapse the need for a separate artifact address concept. The conclusion is incorporated into hack/designs/modules-v2/artifacts.md on the modules-v2 branch of dagger/dagger.

See: https://github.com/dagger/dagger/tree/modules-v2/hack/designs/modules-v2

---

shykes

ARCHIVE: Rebasing Artifacts onto Standalone Collections

Working notes from the design session that produced the Modules v2 split docs. Covers the Artifacts API schema evolution, Execution Plans, filter model, Action type, and staged changes to collections. Content has been absorbed into hack/designs/modules-v2/ on the modules-v2 branch of dagger/dagger.

See: https://github.com/dagger/dagger/tree/modules-v2/hack/designs/modules-v2

---

shykes

ARCHIVE: Workspace Artifacts Design (Pre-Modules v2)

This document is archived. It was the original integrated design covering collections, addresses, verbs, plans, and provenance as one system. It has since been superseded by the split design docs in hack/designs/modules-v2/ on the modules-v2 branch of dagger/dagger.

See: https://github.com/dagger/dagger/tree/modules-v2/hack/designs/modules-v2

---

shykes

Lockfile Session-State Proposal

This is a pure session-state design, not a hybrid DagQL/session design.

It intentionally picks one of the two mutually exclusive approaches:

1. do it through DagQL
2. do it through session state

This proposal picks session state.

shykes

Workspace design briefing: implementation vs. design discussion

Workspace Design Briefing: Implementation vs. Discussion

Companion to the ongoing Discord design thread. Based on a review of the implementation on the workspace branch against the points raised in discussion.

---

1. "Every client always has a workspace"

shykes

Part 3: Artifacts

Builds on Part 1: Module vs. Workspace and Part 2: Workspace API

Table of Contents

• Problem
• Solution
• What is an Artifact
• Operations

shykes

Dagger Design: Part 2 - Workspace API

Builds on Part 1: Workspaces and Modules

Table of Contents

• Problem
• Solution
• The Workspace Type
• Injection

shykes

Dagger Design: Part 1 - Workspaces and Modules

Dagger Design: Part 1 - Workspaces and Modules

This proposal is part 1 of an multi-part proposal to simplify the "design knot" - an interconnected set of design and ux problems blocking implementation of a wide range of features and improvements

Table of Contents

• Problem
• Core Concepts

shykes

CI/CD Stack (Dagger Cloud)

flowchart TB
    API[GitHub API]
    DaggerCloud[Dagger Cloud]
    Dev[Developer Machine]
    DaggerLocal[Dagger Engine]
    Pipeline[Portable Pipeline Logic]