# Business rules — frontend-angular

Evidence date: 2026-10-13. Source: `git@bitbucket.org:overdrive/frontend-angular.git`, `master` at `293b020`.

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

No business-rules document existed in the repository or in `silicon_ark/frontend-angular/` before this file.

## Rules found in the repository

None. The only tracked file is `.gitignore`. An ignore list does not enforce validation, permissions, calculations, 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: Jaco Brits (`jaco@overdrive.co.za`), 2023-08-24. 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. A clone of `master` succeeded on 2026-10-13.

## Domain behaviour

No domain object is defined. There is no screen, form, customer, order, session, or organisation entity in this repository.

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

- `silicon_ark/im_angular_app/business-rules.md` describes behaviour of the ImBank / I&M Angular client. That file does not name slug `frontend-angular`.
- Other frontend repositories under Silicon Ark document their own trees. None of those files 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 an Angular frontend." Only the slug says Angular. **Not a rule.**
- "The product shares rules with `im_angular_app`." Those rules live in another repository and are 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 `im_angular_app` or another frontend should ever be attached to this repository.