# Project plan — Footprint-Not-Used

Evidence date: 2026-10-14.

Source repository: `git@bitbucket.org:overdrive/footprint-not-used.git` (clone used `https://bitbucket.org/overdrive/footprint-not-used.git`).

Inspected revision: `master` at `76b2c93c37ace758f4a7370d56e90de51de81314` (2019-05-22, Jaco Brits, "Initial commit"). That commit is `origin/HEAD`. `git ls-remote` on 2026-10-14 printed the same SHA for `HEAD` and `refs/heads/master`, and no other refs.

The scan-host path `~/projects/sonar_scan/repos/Footprint-Not-Used` was not on this machine. The tree below was read from that git revision.

This plan describes what the repository contains. It does not decide what the product should become.

No `silicon_ark/Footprint-Not-Used/` directory existed before this file. A search of Silicon Ark Markdown for `Footprint-Not-Used` and `footprint-not-used` found no earlier mention of this slug.

## Product

The only tracked file is `README.md`. Its entire content is a Markdown heading, `Footprint`, followed by a blank line. There is no further sentence, no application, and no product statement.

The names in evidence are:

| Name | Where it appears | Provenance |
|---|---|---|
| `footprint-not-used` | Bitbucket slug and `origin` URL | **Implemented** as the remote |
| `Footprint-Not-Used` | Scan-host directory name recorded on OVER-128 (2026-09-28) | **Documented** in the onboarding issue, not in the repository |
| `Footprint` | The only line of `README.md` | **Documented** as a heading. It does not say what Footprint is |

A repository name is not a requirements statement. Whether "Not-Used" means the repository was retired, superseded, reserved, or never filled in is **Unknown / Requires Confirmation**.

What the product is, who it is for, and whether any code was meant to be pushed later are **Unknown / Requires Confirmation**.

## Branch reality

| Line | Tip | Date | What it is |
|---|---|---|---|
| `master` (default; `origin/HEAD`) | `76b2c93` | 2019-05-22 | Only branch. One commit |

`git rev-list --all --count` is 1. `git tag -l` printed nothing. `git ls-tree -r HEAD` lists `README.md` only (blob `de9e66f9842609a4e3f0166fa87149f6217d948d`).

The onboarding issue (OVER-128, captured 2026-09-28) recorded the same tip: `76b2c93`, 2019-05-22, "Initial commit", branch `master`. This clone agrees. Nothing has been committed since that date.

## Objectives

No project plan, issue list, or objective exists in the repository. The README heading does not state a goal. No objective can be inferred from application code, because there is no application code.

**Unknown / Requires Confirmation** whether this repository was created as a placeholder, as a retired name, or as a repository that was never filled in.

## Scope

### In scope of `master`

1. A Git repository on Bitbucket whose only tracked file is `README.md`.
2. The heading text `Footprint` in that file at `76b2c93`. The file is 15 bytes: `# Footprint` then CRLF, then a second CRLF. Provenance: **Implemented** (file bytes at that commit).

### Out of scope / not in this repository

- An application, website, API, database, test suite, or deployment manifest.
- Any file other than `README.md`.
- A description of what "Footprint" refers to.
- The contents of `sonar-project.properties` and `sonarqube_scan.bat`. Those names were reported by the 2026-09-28 scan. They are not in git, and the scan-host path could not be opened here.
- Product behaviour of other Silicon Ark directories whose names contain "footprint". See [Other footprint names in Silicon Ark](#other-footprint-names-in-silicon-ark).

## System shape

No system is implemented.

```text
bitbucket.org/overdrive/footprint-not-used
└── README.md    (15 bytes at 76b2c93; heading "Footprint" and a blank line)
```

There is no frontend, backend, database, API, worker, or deployment manifest in the remote.

## Major components

None. **Implemented** application-component count is zero.

`README.md` is a one-line title. It is not a product component.

## Milestones visible in git

| When | Commit | What landed |
|---|---|---|
| 2019-05-22 | `76b2c93` | Initial commit: `README.md` only |

No later milestone exists in git. The tip is unchanged from the date OVER-128 recorded.

## Implementation plan

There is no forward plan in the repository. Current status: **one commit, a heading-only README, no application**. The tip has been unchanged since 2019-05-22.

Whether anyone intends to push code here is **Unknown / Requires Confirmation**.

## Known dependencies

None declared. There is no `composer.json`, `package.json`, `requirements.txt`, `Dockerfile`, `bitbucket-pipelines.yml`, lockfile, or `.gitignore`.

## Other footprint names in Silicon Ark

On 2026-10-14 the Silicon Ark checkout contained two other top-level directories whose names include "footprint":

| Directory | What its own project plan says | Link from this repository |
|---|---|---|
| `matchcentre.footprintapp.net` | A public SA Rugby match centre (evidence date 2026-10-09, tip `3bd3534`) | None. This remote does not name that slug, that host, or SA Rugby |
| `tournaments.footprintapp.net` | A repository whose only tracked file is `.gitignore` (evidence date 2026-10-01, tip `cfbbf67`) | None |

Neither of those document sets names `footprint-not-used`. Sharing the word "footprint" is not a product relationship. Whether this slug was meant to hold any of that work, or to mark a name that should not be used, is **Unknown / Requires Confirmation**.

## Discrepancy with the onboarding scan

OVER-128 lists this top-level structure for the scan-host path:

```text
README.md
sonar-project.properties
sonarqube_scan.bat
```

`README.md` is the file git tracks. `sonar-project.properties` and `sonarqube_scan.bat` are not in the Bitbucket repository at `76b2c93`, and they are not in the commit's diff. There is no `.gitignore`, so Git would have shown them if they had been tracked. The same two filenames appear in the onboarding notes for other repositories whose git trees do not contain them (for example `wiki`, `website`, `storefront`, and `tournaments.footprintapp.net`). Whether they are untracked SonarQube wrapper files added on the scan host, rather than project source, is **Inferred** from that repeated pattern. It is **Unknown / Requires Confirmation** until someone opens the scan-host directory and reads the files.

## Human confirmation

- Is this repository supposed to hold a product, or should it stay as the May 2019 heading-only commit?
- What does the README heading "Footprint" refer to?
- Does the slug `footprint-not-used` mean the repository is retired, reserved, or unused, and if so, unused in favour of which other system?
- Whether any relationship to `matchcentre.footprintapp.net`, `tournaments.footprintapp.net`, or another Footprint system was intended.
- Whether the two Sonar filenames on the scan host are project files, and what they contain.