# Features — eit

Evidence date: 2026-10-15. Revision: `master` `91549dc` (2019-09-26, "First commit with pipeline").

The source repository has no feature list. Status below is from `README.md`, `bitbucket-pipelines.yml`, and `git log`. The only branch is `master`.

Planned features written as a roadmap: **none found**.

## Current features (master)

| Feature | What it does | Evidence | Status |
|---|---|---|---|
| Project heading | README title "Silicon Overdrive : EIT" | `README.md` | Documented. The heading does not describe a function |
| Database setup note | Tells the reader to update database details in a configure file | `README.md` | Documented. The file is not in the repository |
| Live FTP deploy | On `master`, installs `zip`, `git`, and `git-ftp`, then `git ftp push` to `ftp://$FTP_HOST_LIVE` | `bitbucket-pipelines.yml` | Implemented as a pipeline step |
| QA FTP deploy | On `development`, the same install, then `git ftp push` to `ftp://$FTP_HOST_QA/public_html/americanshutters.overdriveqa.co.za` | `bitbucket-pipelines.yml` | Implemented as YAML. Branch `development` is not on the remote. The step comment is "ftp example" |
| Commented first-time FTP init | `git ftp init` is present for both hosts and commented out | `bitbucket-pipelines.yml` | Present as comments. Not executed |

## Completed, from git history

These subjects are the whole history. They are not a separate product version.

| Date | Commit | Subject | What changed |
|---|---|---|---|
| 2019-09-26 | `000256f` | Initial commit | `README.md` with the single heading `# eit` |
| 2019-09-26 | `91549dc` | First commit with pipeline | README replaced. `bitbucket-pipelines.yml` added |

## In development

Nothing in the tree is marked in progress. There is no open branch besides `master`.

## Recently changed

No commit since 2019-09-26. "Recently" does not apply. The last change is the pipeline commit above.

## Planned

No issue tracker, TODO, or roadmap file is in the repository.

Comments that describe work the script does not do:

- "required for packaging up the application" on the `apt-get install` line. No package command follows.
- "init only use for the first time" on the commented `git ftp init` lines.
- The README's configure file.

These are comments and a sentence, not a committed plan. Provenance: **Inferred** that someone expected an application and a first-time FTP init. No specification of that application is in git.

## Deprecated or removed

| Item | Evidence | Status |
|---|---|---|
| README heading `# eit` | `000256f`, replaced in `91549dc` | Removed from the file. Still in git history |

No feature flag, retired module, or migration is present.

## Not in this repository

| Item | Why it is listed |
|---|---|
| Application code, tests, database, configure file | Named or implied by the README and by the packaging comment. Not committed |
| `sonar-project.properties`, `sonarqube_scan.bat` | Listed when this onboarding task was created. `git log --all` has no history for either name |
| eIT staff application | Documented from `overdrive/eitaws` in Silicon Ark `eitaws/`. Different repository |

## Source map

```text
README.md                  heading and setup sentence
bitbucket-pipelines.yml    image, master step, development step
```