╔═══════════════════════════════════════════════════════════════╗
║  ███████╗██████╗  ██████╗ ███╗   ██╗████████╗               ║
║  ██╔════╝██╔══██╗██╔═══██╗████╗  ██║╚══██╔══╝               ║
║  █████╗  ██████╔╝██║   ██║██╔██╗ ██║   ██║                  ║
║  ██╔══╝  ██╔══██╗██║   ██║██║╚██╗██║   ██║                  ║
║  ██║     ██║  ██║╚██████╔╝██║ ╚████║   ██║                  ║
║  ╚═╝     ╚═╝  ╚═╝ ╚═════╝ ╚═╝  ╚═══╝   ╚═╝                  ║
║                              ██████╗  █████╗ ████████╗ █████╗ ║
║  Auto-Generated Build Data   ██╔══██╗██╔══██╗╚══██╔══╝██╔══██╗║
║  Dependencies · Topology     ██║  ██║███████║   ██║   ███████║║
║                              ██████╔╝██║  ██║   ██║   ██║  ██║║
║                              ╚═════╝ ╚═╝  ╚═╝   ╚═╝   ╚═╝  ╚═╝║
╚═══════════════════════════════════════════════════════════════╝

Front Data

Auto-generated build data for the front-end monorepo. Dependency manifests and project topology.

---

Table of Contents

A) Documentation Overview

• A.1 Data Files
• A.2 How Data Is Generated

B) Architectural Design

• B.1 Repository Structure
• B.2 Generation Pipeline

---

A) Documentation Overview

A.1 Data Files

File	Content
front-deps.json	npm dependencies per project (merged + per-project breakdown)

A.2 How Data Is Generated

Generated by the C3 engine in the cloud repo:

cloud/a_solutions/bc-obs_c3-infra-mcp-api/src/engines/gen-deps.ts

The engine scans all package.json files across the front-end monorepo and produces a merged dependency manifest.

---

B) Architectural Design

B.1 Repository Structure

front-data/
├── front-deps.json    Merged npm dependencies (auto-generated)
└── manifest.json      Project manifest

B.2 Generation Pipeline

1. C3 engine scans ~/git/front/*/package.json
2. Extracts dependencies and devDependencies per project
3. Merges into a unified manifest
4. Writes to front-data/front-deps.json
5. Committed to this submodule repo

---

Last Updated: 2026-03-18