---
id: "framework-workspace-builder"
type: "framework"
source_timestamps: ["§4.4"]
tags: ["meta-workspace", "bootstrapping", "adoption"]
related: ["concept-icm", "concept-portability", "claim-external-adoption"]
sources: ["paper"]
sourceVaultSlug: "icm-paper-folder-architecture-2026Jun02"
originDay: 2
---
# The Workspace-Builder (Self-Hosting Meta-Workspace)

## What it is

ICM includes a **workspace-builder**: a five-stage workspace whose **output is a new workspace**. It is itself built with ICM conventions ([[framework-icm-architecture]]), so the workspaces it produces are consistent because the builder enforces the same structural rules it was built with.

## The five stages

1. **Discovery** — identify the domain and the workflow.
2. **Stage mapping** — find the natural breakpoints between stages.
3. **Scaffolding** — create the folder structure.
4. **Questionnaire design** — decide what setup questions the workspace should ask.
5. **Validation** — confirm the pipeline runs end to end.

## Why self-hosting matters

Practitioners can create workspaces for their own domains **without understanding the conventions in detail** — the builder encodes them in its process. Examples:

- A marketing team builds a campaign-production workspace.
- A research group builds a literature-review workspace.
- A consultancy builds a client-deliverable pipeline.

## Adoption mechanism

The self-hosting property (a workspace that emits workspaces) is the **mechanism behind ICM's adoption beyond its author** — see [[claim-external-adoption]] and [[entity-external-adopters]]. Combined with [[concept-portability]] (a workspace is a folder you can hand off), it enables non-developer onboarding.


## Related across days
- [[framework-skill-creation]]
- [[entity-external-adopters]]
- [[claim-external-adoption]]
- [[synthesis-workspace-builder-is-the-meta-dialogue]]