# merchmix-beacon-fe

This repository is a small Next.js and TypeScript frontend for the Merchmix Beacon product. It contains a single application page, shared styling and assets, authentication-related code, and environment/deployment configuration. No backend implementation, domain workflows, database integration, or API routes are evidenced in the repository snapshot.

## Business Summary

Beacon provides the web entry point for a Merchmix application. This repository appears to cover the user-facing application shell and access setup rather than retail planning work such as assortment, buying, inventory, or markdown management. The available evidence is insufficient to identify a completed retailer-facing workflow.

## Capabilities

| Capability | Category | Status | Access | Exposure |
|---|---|---|---|---|
| Beacon Application Access | Authentication | `partial` | `execute` | user_facing |

**Beacon Application Access** — Provides the web entry point through which users can access the Beacon application.

## Workflows

**Open Beacon Web Application** — A user opens the Beacon frontend and reaches the application entry page.

1. Request the root web route `/`.
2. Next.js renders the application layout and root page.
3. Authentication-related middleware or helper code may participate in access handling.

## Architecture

A minimal Next.js App Router frontend written in TypeScript, packaged for deployment with Docker and CI configuration. The repository does not show a layered domain architecture or backend service implementation.

**Components:** Next.js application entry point in `app/page.tsx`, Application layout and global styles in `app/layout.tsx` and `app/globals.css`, Authentication-related implementation in `src/auth.ts` and `proxy.ts`, Static assets in `public/`, Deployment and environment tooling including `Dockerfile`, `next.config.ts`, and CI/environment scripts

**Patterns:** Next.js App Router, TypeScript frontend, Environment-based configuration, Containerized deployment configuration, Authentication middleware or helper pattern

## Interfaces

| Kind | Identifier | Description |
|---|---|---|
| `http` | `/` | Root web page served by the Next.js application. |

## Screens

| Route | Name | Purpose |
|---|---|---|
| `/` | Beacon Application Home | Frontend entry page for the Beacon application. |

## Dependencies

| Name | Kind | Relationship | Criticality |
|---|---|---|---|
| Microsoft Entra External ID | `external_service` | `authenticates_through` | `required` |
| Next.js | `library` | `uses` | `critical` |
| Node.js package ecosystem | `library` | `uses` | `required` |

## Technology

TypeScript, Next.js, React, Node.js package tooling, Docker, CSS, GitHub Actions, Bitbucket Pipelines

## Limitations

- The repository snapshot contains only one detected application page and no detected backend routes or API clients.
- No database, queue, internal service, or retail domain data model is evidenced.
- The implementation of `app/page.tsx`, `src/auth.ts`, and `proxy.ts` was not provided in the scanner output, so the precise UI behavior and authentication flow cannot be confirmed.
- No implemented evidence supports WSSI, OTB, range planning, size curves, markdown, allocation, replenishment, option planning, buying, or assortment planning capabilities.
- Documentation references backend requirements and Entra setup, but documentation alone is not treated as evidence of implemented functionality.
- The repository's production readiness and deployment environment could not be established from the available structural evidence.

## Agent Instructions

Treat this repository as the Beacon frontend entry point and authentication shell, not as a source of retail planning or backend business logic.

- Use the root HTTP route `/` when routing questions about the Beacon web entry page.
- For authentication or access issues, inspect `src/auth.ts`, `proxy.ts`, environment configuration, and the Entra setup documentation.
- Do not route requests for planning calculations, inventory data, product data, reporting, or other retail domain operations to this repository unless additional implementation evidence is found.
- Do not assume that documentation describing backend requirements represents an implemented backend.
- Check environment variables and deployment configuration before diagnosing authentication or runtime behavior.

## Source

| Field | Value |
|---|---|
| Repository | `merchmix-beacon-fe` |
| Branch | `master` |
| Commit | `085e0a5ae990` |
| Generated by | `gpt-5.6-luna` |

*Generated by the Merchmix Skills Platform from the current codebase.*