--- title: "3DARCH-FT-7 — Integrated local runtime with persistence and health checks" description: "Enable developers to start the browser workplace, real-time backend, and database as one local environment and determine whether each service is healthy." --- # Integrated local runtime with persistence and health checks | Feature | Parent Epic | Delivery status | Status source | Owner | Approved for Solution | |---|---|---|---|---|---| | `3DARCH-FT-7` | [3DARCH-EP-1 — Engineering Platform, Quality, and Operability](../../3darch-ep-1.md) | `IN_BACKLOG` | `EXACT` | 3D Architecture Wizzard team | No | ## Description Enable developers to start the browser workplace, real-time backend, and database as one local environment and determine whether each service is healthy. ## User or operator problem Developers need the browser client, backend, and database to start together with visible dependency health. ## Expected value Provides a repeatable integration environment and shortens diagnosis of startup or dependency failures. ## Scope Includes coordinated local startup for frontend, backend, and PostgreSQL plus storage, ordering, and health checks. ### Exclusions - End-user product behavior and solution or release authorization are outside these engineering Features. ## Acceptance outcomes - [ ] One local workflow starts the frontend, backend, and PostgreSQL dependencies. - [ ] Service ordering and persistent database storage are declared. - [ ] Frontend, backend, and database health checks expose startup failure. ## Dependencies - [3DARCH-FT-1 — Reproducible monorepo development workspace](./3darch-ft-1.md) - [3DARCH-FT-6 — Repeatable database schema lifecycle](./3darch-ft-6.md) ## Risks - Service health can appear green while a dependency or browser route remains unusable. ## 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-7/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`. - [`docker-compose.yml`](https://gitea.lego-cloud.eu/corp-v1-3darch-legacy/corp-v1-3darch-legacy/src/commit/c0ced47ecaf4426f47e5c2e4868677f7144b951a/docker-compose.yml) - [`apps/nebula/Dockerfile`](https://gitea.lego-cloud.eu/corp-v1-3darch-legacy/corp-v1-3darch-legacy/src/commit/c0ced47ecaf4426f47e5c2e4868677f7144b951a/apps/nebula/Dockerfile) - [`apps/singularity/Dockerfile`](https://gitea.lego-cloud.eu/corp-v1-3darch-legacy/corp-v1-3darch-legacy/src/commit/c0ced47ecaf4426f47e5c2e4868677f7144b951a/apps/singularity/Dockerfile) - [`apps/singularity/src/routes/health.routes.ts`](https://gitea.lego-cloud.eu/corp-v1-3darch-legacy/corp-v1-3darch-legacy/src/commit/c0ced47ecaf4426f47e5c2e4868677f7144b951a/apps/singularity/src/routes/health.routes.ts)