Package, deploy, and health-check workplace services
| Feature | Parent Epic | Delivery status | Status source | Owner | Approved for Solution |
|---|---|---|---|---|---|
3DARCH-FT-8 | 3DARCH-EP-1 — Engineering Platform, Quality, and Operability | IN_BACKLOG | EXACT | 3D Architecture Wizzard team | No |
Description
Enable operators to build versionable frontend/backend images, package Kubernetes deployment configuration, and admit only healthy services to traffic.
User or operator problem
Operators need repeatable artifacts and health gates for deploying the workplace services safely.
Expected value
Creates versionable deployment inputs and prevents unhealthy services from receiving traffic.
Scope
Includes independent service images, repeatable tagging/publishing tasks, Helm configuration, probes, ingress, and dependency-aware readiness.
Exclusions
- End-user product behavior and solution or release authorization are outside these engineering Features.
Acceptance outcomes
- Frontend and backend images build independently for the declared platform.
- Images can be tagged and published through repeatable tasks.
- Helm charts configure deployments, services, ingress, runtime values, and health probes for both services.
- Process and dependency health distinguish a running backend from a usable backend.
- Database failure withholds readiness and returns a bounded unhealthy response.
Dependencies
- 3DARCH-FT-1 — Reproducible monorepo development workspace
- 3DARCH-FT-3 — Automated multi-layer quality verification
- 3DARCH-FT-6 — Repeatable database schema lifecycle
Risks
- Legacy packaging and deployment assumptions require validation against the target runtime before release.
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.
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
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. No canonical implementation Tasks have been defined.
Original source
- Discord – Scope – Linas: original Feature request
- Discord – Scope – Linas: proceed with documented mapping
Legacy implementation evidence
The Feature boundary was mined from legacy revision c0ced47ecaf4426f47e5c2e4868677f7144b951a.