---
title: "3DARCH-FT-1 — Reproducible monorepo development workspace"
description: "Enable contributors to install one pinned toolchain and run coordinated development, build, type-check, lint, test, documentation, and Storybook workflows across the platform."
---

# Reproducible monorepo development workspace

| Feature | Parent Epic | Delivery status | Status source | Owner | Approved for Solution |
|---|---|---|---|---|---|
| `3DARCH-FT-1` | [3DARCH-EP-1 — Engineering Platform, Quality, and Operability](../../3darch-ep-1.md) | `IN_BACKLOG` | `EXACT` | 3D Architecture Wizzard team | No |

## Description

Enable contributors to install one pinned toolchain and run coordinated development, build, type-check, lint, test, documentation, and Storybook workflows across the platform.

## User or operator problem

Contributors face onboarding delays and environment-specific failures when each package requires separately reconciled tools and commands.

## Expected value

Reduces contributor setup time and makes workspace checks repeatable across the monorepo.

## Scope

Includes the pinned Node/pnpm workspace baseline, root task orchestration, environment examples, and contributor setup path.

### Exclusions

- End-user product behavior and solution or release authorization are outside these engineering Features.

## Acceptance outcomes

- [ ] The workspace uses a declared Node and pnpm baseline.
- [ ] One root workflow can run each supported application/package task through the dependency graph.
- [ ] Local setup instructions and environment examples are available to contributors.

## Dependencies

- None recorded.

## Risks

- Tracked setup guidance and environment examples have legacy inconsistencies that can undermine repeatability.

## Human approval

Linas approved this Feature for documentation on 2026-09-02T10:40:43.220Z. It is **not Approved for Solution** and has no implementation approval.

- [Documentation decision](https://discord.com/channels/1518726359512387766/1543925247361814568/1544658325738885201)

## Delivery status evidence

The Feature was separately registered at `IN_BACKLOG` as an accepted catalogue boundary. This records backlog retention, not design or delivery progress.

- Event: Catalogue registration
- Actor and authority: Linas — Human project team member
- Reason: The Feature catalogue was accepted for governed documentation and retained in the backlog.
- [Status evidence](https://discord.com/channels/1518726359512387766/1543925247361814568/1544658325738885201)

## Architecture traceability

- Requirements: none derived.
- Readiness: Not started.

Architecture solution work must not begin until a separate human **Approved for Solution** decision is recorded.

## Tasks

[Review the Tasks group](./3darch-ft-1/tasks.md). No canonical implementation Tasks have been defined.

## Original source

- [Discord – Scope – Linas: original Feature request](https://discord.com/channels/1518726359512387766/1543925247361814568/1544647879111483562)
- [Discord – Scope – Linas: proceed with documented mapping](https://discord.com/channels/1518726359512387766/1543925247361814568/1544658325738885201)

### Legacy implementation evidence

The Feature boundary was mined from legacy revision `c0ced47ecaf4426f47e5c2e4868677f7144b951a`.

- [`package.json`](https://gitea.lego-cloud.eu/corp-v1-3darch-legacy/corp-v1-3darch-legacy/src/commit/c0ced47ecaf4426f47e5c2e4868677f7144b951a/package.json)
- [`pnpm-workspace.yaml`](https://gitea.lego-cloud.eu/corp-v1-3darch-legacy/corp-v1-3darch-legacy/src/commit/c0ced47ecaf4426f47e5c2e4868677f7144b951a/pnpm-workspace.yaml)
- [`turbo.json`](https://gitea.lego-cloud.eu/corp-v1-3darch-legacy/corp-v1-3darch-legacy/src/commit/c0ced47ecaf4426f47e5c2e4868677f7144b951a/turbo.json)
- [`devbox.json`](https://gitea.lego-cloud.eu/corp-v1-3darch-legacy/corp-v1-3darch-legacy/src/commit/c0ced47ecaf4426f47e5c2e4868677f7144b951a/devbox.json)
- [`README.md`](https://gitea.lego-cloud.eu/corp-v1-3darch-legacy/corp-v1-3darch-legacy/src/commit/c0ced47ecaf4426f47e5c2e4868677f7144b951a/README.md)