# Project plan — magalies-pharma-heisenberg-frontend-new

Evidence date: 2026-10-09.

Source repository: `git@bitbucket.org:overdrive/magalies-pharma-heisenberg-frontend-new.git`.

Inspected revision: `main` at `a110255` (2024-11-20, Kevin James King, "Initial commit"). Full hash `a1102558add413d635de871b289ab1287eb47175`. That commit is `origin/HEAD`. The remote has no other branches and no tags.

The scan-host path `~/projects/sonar_scan/repos/magalies-pharma-heisenberg-frontend-new` was not on this machine. The tree below was read from that git revision.

This plan describes what the repository contains. It does not decide what the product should become.

No `silicon_ark/magalies-pharma-heisenberg-frontend-new/` directory existed before this file. A search of Silicon Ark Markdown for `magalies-pharma-heisenberg-frontend` found no earlier mention of this slug. Two other Heisenberg repositories are already documented. Neither of those document sets names this slug. See [Related names in other Silicon Ark projects](#related-names-in-other-silicon-ark-projects).

## Product

There is no application, README, or product statement in git. The only tracked file is `.gitignore`. Its own header says the patterns are examples to customize, and it links to Atlassian's gitignore tutorial. It is not a description of a Magalies Pharma or Heisenberg front end.

The names in evidence are the Bitbucket slug `magalies-pharma-heisenberg-frontend-new` and the scan-host directory of the same name. A slug that says "frontend" is not a requirements statement.

What the product is, who it is for, and whether any screen was ever deployed from this remote are **Unknown / Requires Confirmation**.

## Branch reality

| Line | Tip | Date | What it is |
|---|---|---|---|
| `main` (default; `origin/HEAD`) | `a110255` | 2024-11-20 | Only branch. One commit |

`git rev-list --all --count` is 1. `git tag -l` printed nothing.

The commit adds `.gitignore` only (50 lines). Author and committer are Kevin James King (`kevin@overdrive.co.za`). The message is `Initial commit`. The commit has no parent.

The onboarding issue (OVER-190, captured 2026-09-28) recorded the same tip: `a110255`, 2024-11-20, "Initial commit", branch `main`. This clone agrees.

## Objectives

No project plan, issue list, or README exists in the repository. No objective can be inferred from application code, because there is no application code.

**Unknown / Requires Confirmation** whether this repository was created as a placeholder for a new Heisenberg front end, a name reservation, or a project that was never pushed.

## Scope

### In scope of `main`

1. A Git repository on Bitbucket whose only tracked file is `.gitignore`.
2. The ignore patterns in that file, which the file itself labels as examples (Node artifacts, Java class files, Python bytecode, logs, jars, Maven `target/`, JetBrains `.idea/`, unit-test XML, macOS and Windows junk files, application binaries, and large media). Those patterns do not select a stack. See `technical-documentation.md`.

### Out of scope / not in this repository

- A front-end application, website, API client, database, or deployment.
- Any file other than `.gitignore`.
- The contents of `sonar-project.properties` and `sonarqube_scan.bat`. Those names were reported by the 2026-09-28 scan. They are not in git, and the scan-host path could not be opened here.
- The Heisenberg API and the print service documented under other Silicon Ark directories. Those trees are separate. See [Related names in other Silicon Ark projects](#related-names-in-other-silicon-ark-projects).

## System shape

No system is implemented.

```text
bitbucket.org/overdrive/magalies-pharma-heisenberg-frontend-new
└── .gitignore    (stock example ignore list; commit a110255)
```

There is no frontend, backend, database, API, worker, or deployment manifest in the remote.

## Major components

None. **Implemented** application-component count is zero.

The tracked `.gitignore` is repository metadata, not a product component.

## Milestones visible in git

| When | Commit | What landed |
|---|---|---|
| 2024-11-20 | `a110255` | Initial commit: `.gitignore` only |

No later milestone exists in git. The tip is unchanged from the date OVER-190 recorded.

## Implementation plan

There is no forward plan in the repository. Current status: **one starter commit, no application**.

Whether anyone intends to push code here is **Unknown / Requires Confirmation**.

## Known dependencies

None declared. There is no `package.json`, `composer.json`, `requirements.txt`, `go.mod`, `*.csproj`, `Dockerfile`, `Pipfile`, `bitbucket-pipelines.yml`, or lockfile.

The `.gitignore` names directories such as `node_modules/` and `target/`. Those directories are not in the tree. Listing them in an example ignore file is not a dependency declaration.

## Related names in other Silicon Ark projects

Two other documented repositories use the Heisenberg name. Neither document names this slug. This plan does not treat their behaviour as a component of this repository.

| Silicon Ark directory | What that other repository contains | Link to this slug |
|---|---|---|
| `magalies-pharma-heisenberg-serverless` | A Node.js Serverless API (`master` at `7d003d5`, 2023-05-03). Its project plan says a front end is not in that repository, and CloudFormation creates an S3 bucket `heisenberg-frontend-${EnvironmentName}` that the Lambdas do not use. Those documents ask where that front end lives | None. The serverless documents do not name `magalies-pharma-heisenberg-frontend-new`. This remote does not mention the bucket, the API, or that repository |
| `magalies-pharma-heisenberg-print-server` | A local Express service (`master` at `07aa3df`, 2022-10-19) that turns JSON into Zebra ZPL and prints it. Its documents do not name a front end | None. The print-server documents do not name this slug, and this remote does not mention that service |

The shared "Heisenberg" token in the three slugs is a naming fact. It is not evidence that this empty repository is the front end for the API, or the caller of the print server. Whether this slug was meant to hold that UI, to replace an unpublished front end, or to stay empty is **Unknown / Requires Confirmation**.

The serverless tip (2023-05-03) is earlier than this repository's only commit (2024-11-20). That order is a date comparison. It does not show that this commit continued the API.

## Discrepancy with the onboarding scan

OVER-190 lists this top-level structure for the scan-host path:

```text
sonar-project.properties
sonarqube_scan.bat
```

Those paths are not in the Bitbucket repository at `a110255`, and they are not in the single commit's diff. The same two filenames appear in the onboarding notes for other repositories whose git trees do not contain them. Whether they are untracked SonarQube wrapper files added on the scan host, rather than project source, is **Inferred** from that repeated pattern. It is **Unknown / Requires Confirmation** until someone opens the scan-host directory and reads the files.

The scan also did not list `.gitignore`, which is the only file in git.

## Human confirmation

- Is this repository supposed to hold a product, or should it stay as the 2024 starter commit?
- If a product was intended, what is its purpose, and where does the code live if not here?
- Is this slug the front end expected by the S3 bucket `heisenberg-frontend-${EnvironmentName}` in `magalies-pharma-heisenberg-serverless`?
- Any relationship to `magalies-pharma-heisenberg-print-server`.
- Whether the two Sonar filenames on the scan host are project files, and what they contain.