# Business rules — eit

Evidence date: 2026-10-15. Revision: `master` `91549dc`.

Rules below are taken from `README.md` or `bitbucket-pipelines.yml`. Each rule is marked **Documented** or **Inferred**. An inferred rule is what the file does. It is not a confirmed business decision.

No separate business-rules document existed in the source repository or in Silicon Ark. The tree has no application code, so there are no validation rules, permission checks, or domain calculations to recover.

## Identity

| ID | Rule | Source | Label |
|---|---|---|---|
| BR-001 | The README presents the project as "Silicon Overdrive : EIT" | `README.md` | Documented |
| BR-002 | The expansion of EIT, the users, and the business the system serves are not stated | Absence in both files | Unknown / Requires Confirmation |

## Setup

| ID | Rule | Source | Label |
|---|---|---|---|
| BR-003 | Setup is described as editing a configure file and updating database details | `README.md` | Documented |
| BR-004 | That configure file is not part of the committed tree, so the written setup cannot be completed from git | `README.md` compared with `git ls-tree` | Inferred |

## Deployment

| ID | Rule | Source | Label |
|---|---|---|---|
| BR-005 | Pushes to `master` are deployed with `git ftp push` to `ftp://$FTP_HOST_LIVE` | `bitbucket-pipelines.yml` | Inferred from the pipeline. No prose says this host is production |
| BR-006 | The live FTP username, password, and host come from `FTP_USERNAME_LIVE`, `FTP_PASSWORD_LIVE`, and `FTP_HOST_LIVE` | `bitbucket-pipelines.yml` | Inferred |
| BR-007 | Pushes to `development` are deployed with `git ftp push` to `ftp://$FTP_HOST_QA/public_html/americanshutters.overdriveqa.co.za` | `bitbucket-pipelines.yml` | Inferred from the pipeline |
| BR-008 | The QA FTP username, password, and host come from `FTP_USERNAME_QA`, `FTP_PASSWORD_QA`, and `FTP_HOST_QA` | `bitbucket-pipelines.yml` | Inferred |
| BR-009 | The `development` key is commented "ftp example" | `bitbucket-pipelines.yml` | Documented as a YAML comment. Whether the URL is an example or a real target is Unknown / Requires Confirmation |
| BR-010 | `git ftp init` is not run by either step. Both init lines are comments | `bitbucket-pipelines.yml` | Inferred. A remote that was never initialised will not be initialised by this file |
| BR-011 | The script installs `zip` and does not call it. The install comment says zip is for packaging the application | `bitbucket-pipelines.yml` | Inferred. No packaging rule is actually applied |
| BR-012 | The pipeline does not build, test, or exclude files before the FTP push | `bitbucket-pipelines.yml` | Inferred. git-ftp's own ignore rules are not configured in this repo |

## What was not found

No rule was found for:

- Who may change database details.
- Which database, which fields, or which values are valid.
- Who may deploy, or a difference in access between live and QA beyond the two variable sets.
- Retention, billing, privacy, or audit.

Do not treat that absence as a decision that those rules are unwanted. It is an absence of evidence.