---
id: "concept-portability"
type: "concept"
source_timestamps: ["§3.4"]
tags: ["portability", "git", "infrastructure-as-code", "handoff"]
related: ["concept-icm", "claim-external-adoption", "framework-workspace-builder"]
definition: "An ICM workspace is a self-contained folder: copy it, zip it, commit it to Git. No server, no environment to replicate, no deployment step — infrastructure as code for AI workflows."
sources: ["paper"]
sourceVaultSlug: "icm-paper-folder-architecture-2026Jun02"
originDay: 2
---
# Portability and Reproducibility (The Workspace Is a Folder)

## The proposition

A workspace is a folder. It can be:

- copied to another machine,
- committed to Git,
- emailed as a zip,
- synced through cloud storage.

It carries its own prompts, context structure, and stage definitions. **There is no server to configure or deployment artifact to build** — the workspace definition *is* the system. Infrastructure-as-code applied to AI workflows.

## Versioning benefits

- Every prompt change and stage edit is **diffable and reversible** via Git.
- Stage outputs can be committed after each run, creating a **version history of the pipeline's behaviour** over time.

## Handoff economics

Handing a workflow to a client means **copying a folder**. They can run and edit it without a developer — versus a framework solution that requires:

- documentation,
- environment setup,
- dependency management,
- ongoing support.

This is the mechanism behind the external adoption pattern in [[claim-external-adoption]] — and the structural reason a non-coder workspace builder ([[framework-workspace-builder]]) is even feasible.

## Counter-perspective

The enrichment overlay flags a real limitation: in enterprise contexts, portability requires more than file copying. Environment capture (library/model versions, API keys), access control and data governance, and reproducible runtimes (containers, IaC) sit on top of "workspace as a folder." Git-versioning files is necessary but not sufficient for reproducibility and compliance — ICM's portability story is strong for small teams and local workflows; larger orgs need to integrate it with environment management and governance tooling.


## Related across days
- [[framework-icm-architecture]]
- [[concept-icm-d2]]
- [[action-implement-folders]]