# Business rules — magalies-pharma-heisenberg-frontend-new

Evidence date: 2026-10-09. Source: `git@bitbucket.org:overdrive/magalies-pharma-heisenberg-frontend-new.git`, `main` at `a110255`. Full hash `a1102558add413d635de871b289ab1287eb47175`.

Provenance labels: **Documented**, **Implemented**, **Inferred**, **Planned**, **Unknown**.

No business-rules document existed in the repository or in `silicon_ark/magalies-pharma-heisenberg-frontend-new/` before this file.

## Rules found in the repository

None. The only tracked file is `.gitignore`. An ignore list does not enforce validation, permissions, calculations, pricing, stock, or workflow gates.

No rule below is inferred from the repository name. A name is not a domain rule.

## Identity and access

No login, role, or permission check exists in the tree.

The commit metadata records one author: Kevin James King (`kevin@overdrive.co.za`), 2024-11-20. That is history, not an access-control rule.

**Unknown / Requires Confirmation** who is allowed to push to the Bitbucket repository. Hosting permissions were not inspected (the Bitbucket API client returned HTTP 401). A clone of `main` succeeded on 2026-10-09.

## Domain behaviour

No domain object is defined. There is no prescription, patient, medicine, batch, barcode, order, or company entity in this repository.

Rules written for other repositories are not rules of this one:

- `silicon_ark/magalies-pharma-heisenberg-serverless/business-rules.md` describes the Heisenberg API (orders, batches, packaging scans, courier, Cognito groups). That file does not name slug `magalies-pharma-heisenberg-frontend-new`.
- `silicon_ark/magalies-pharma-heisenberg-print-server/business-rules.md` describes how that process turns a JSON body into a raw ZPL print job. That file does not name this slug.

Whether any of those rules were meant to apply to this repository is **Unknown / Requires Confirmation**.

## Validation

No validator, schema, form rule, or argument parser exists in this repository.

`.gitignore` causes Git to skip matching untracked paths. That is a version-control filter. The patterns are generic examples (see `technical-documentation.md`). They are not input validation for a product.

## Workflows

No status machine, approval step, retry, or scheduled job is defined.

## Explicit non-rules

The following were not adopted, because the evidence does not support them:

- "The product is a Heisenberg front end." Only the slug says frontend. No file in this repository names a screen, a route, or Heisenberg. **Not a rule.**
- "This repository is the application stored in S3 bucket `heisenberg-frontend-${EnvironmentName}`." That bucket name lives in `magalies-pharma-heisenberg-serverless`. This remote does not mention it. **Not a rule.**
- "Prescription, packaging, and courier rules from the serverless API apply here." Those rules live in another repository and are not referenced from this remote. **Not a rule.**
- "Print rules from `magalies-pharma-heisenberg-print-server` apply here." That service is a separate repository and is not referenced from this remote. **Not a rule.**
- "SonarQube quality gates apply." Two filenames were reported on a scan host and were not read. **Not a rule.**
- Any threshold, fee, eligibility check, or permission matrix. **Not present.**

## Human confirmation

- Whether any business rule for this slug is kept outside the repository.
- Whether rules already written for `magalies-pharma-heisenberg-serverless` or `magalies-pharma-heisenberg-print-server` should ever be attached to this repository.