# Project plan — eit

Evidence date: 2026-10-15.

Source repository: `git@bitbucket.org:overdrive/eit.git`.

The tree that was read is `master` at `91549dc` (2019-09-26, "First commit with pipeline", author name siliconoverdrive). `origin/HEAD` points at `master`. This plan describes what that tree contains. It does not decide what the product should become.

## Product

The README heading is "Silicon Overdrive : EIT". The only setup sentence is "go to configure file and update db details".

Provenance: **Documented** (`README.md`).

No application, database, configure file, or user interface is in the repository. What EIT is, who uses it, and whether a configure file exists only on a server are **Unknown / Requires Confirmation**.

Silicon Ark already documents a different repository, `overdrive/eitaws`, whose login page title is "eIT" and whose README calls that tree the working version on AWS. That application is not in this repository. Sharing the name does not make the two trees the same product. Whether `eit` was meant to hold, deploy, or replace `eitaws` is **Unknown / Requires Confirmation**.

## Branch reality

| Branch | Tip | Date | What it is |
|---|---|---|---|
| `master` (`origin/HEAD`) | `91549dc` | 2019-09-26 | README plus `bitbucket-pipelines.yml`. Two commits. No tags |

The pipeline file also names a `development` branch. That branch does not exist on the remote that was fetched. A push to `development` would be required before that step can run. Provenance: **Implemented** pipeline text; missing branch is **Implemented** as an absence.

The task-creation scan listed `sonar-project.properties` and `sonarqube_scan.bat` at the repository root. Neither name is in `git log --all`. Provenance: **Unknown** — they may have been untracked files on the scan host.

## Scope in the repository

In scope of what is committed on `master`:

- A one-line product heading and a setup sentence in `README.md`.
- A Bitbucket Pipelines definition that installs `zip`, `git`, and `git-ftp`, then pushes the repository over FTP.

Out of scope, because it is not in this tree:

- Application source, tests, a database schema, and the configure file named by the README.
- The eIT staff application documented under Silicon Ark `eitaws/`.
- SonarQube project files. They were named by the onboarding scan and are not in git.

## System architecture

```text
Bitbucket Pipelines (image python:3.5.7)
  branch master
    apt-get install zip git git-ftp
    git ftp push → ftp://$FTP_HOST_LIVE
  branch development (branch not present on the remote)
    apt-get install zip git git-ftp
    git ftp push → ftp://$FTP_HOST_QA/public_html/americanshutters.overdriveqa.co.za
```

There is no application process behind that diagram. `zip` is installed and never invoked. The pipeline image is Python 3.5.7 and the tree contains no Python file. Provenance: **Implemented** (`bitbucket-pipelines.yml`).

## Major components

| Component | Location | Role |
|---|---|---|
| README | `README.md` | Names the project and tells the reader to update database details in a configure file |
| Pipeline | `bitbucket-pipelines.yml` | FTP deploy steps for `master` and `development` |

## Milestones visible in git

These are history, not a forward plan. No future milestone document was found.

| When | Commit | Evidence |
|---|---|---|
| 2019-09-26 11:55 UTC | `000256f` | Initial commit by Jaco Brits. `README.md` contained only the heading `# eit` |
| 2019-09-26 14:02 +0200 | `91549dc` | "First commit with pipeline". README replaced with the Silicon Overdrive heading and the setup sentence. Pipeline file added |

No commit has landed since 2019-09-26.

## Implementation plan

There is no written plan in the repository. The README is the only setup instruction, and the file it names is not committed. The pipeline comments say `zip` is "required for packaging up the application" and that `git ftp init` is "only use for the first time". Both `git ftp init` lines are commented out. No packaging command follows the install.

## Known dependencies

- Bitbucket Pipelines.
- Pipeline image `python:3.5.7`, used to run `apt-get`. No Python application is committed.
- Packages installed at pipeline time: `zip`, `git`, `git-ftp`. `zip` is not called.
- FTP credentials and hosts supplied as pipeline variables: `FTP_USERNAME_LIVE`, `FTP_PASSWORD_LIVE`, `FTP_HOST_LIVE`, `FTP_USERNAME_QA`, `FTP_PASSWORD_QA`, `FTP_HOST_QA`. Values are not in the repository and are not copied here.
- A configure file and a database, named only by the README. Not in git.

## Current project status

`master` has had no commit since 2019-09-26. The repository is a pipeline definition and a short README. It does not contain a runnable application.

Silicon Ark had no `eit/` directory before this onboarding.

## Human confirmation

1. What does EIT stand for, and which product is this repository for?
2. Is this repository related to `overdrive/eitaws`, or only similarly named?
3. Where is the configure file the README tells the reader to edit, and which database does it point at?
4. Are `FTP_HOST_LIVE` and the American Shutters QA path still the intended deploy targets? The `development` step comment says "ftp example".
5. Was `development` ever created, and did either FTP step succeed?
6. Were `sonar-project.properties` and `sonarqube_scan.bat` ever part of this project?