# Features — russel-serverless-api

Evidence date: 2026-10-05. Source: `git@bitbucket.org:overdrive/russel-serverless-api.git`, `master` at `c6a6cd889f2da571fc0f10bb037041e5dfb65114`.

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

No feature list existed in the repository or in `silicon_ark/russel-serverless-api/` before this file.

## Current

No product feature is implemented. The git tree is `.gitignore` only.

The repository itself exists on Bitbucket and can be fetched. That is hosting state, not a user-facing feature. Provenance: **Implemented** (`git fetch` on 2026-10-05; `origin/master` at `c6a6cd8`).

## Completed

Nothing that a user could call has been completed. The only historical commit adds the Atlassian sample `.gitignore`. Provenance: **Implemented** (`git show c6a6cd8`).

That ignore file is repository boilerplate. It is not recorded here as a completed product feature. Its patterns are listed in `technical-documentation.md`.

## In development

Nothing. `git branch -a` shows `master` and `origin/master` only. There is no second branch with unmerged work. `git status` on the backup copy reports a clean tracked tree plus two untracked files (below). Those files are scan wrappers, not an API under construction.

## Planned

No planned feature is written down in this repository. **Unknown / Requires Confirmation** whether a backlog exists outside git.

## Recently changed

No product change can be named after 2020-12-01. `origin/master` on 2026-10-05 is still `c6a6cd8`. Provenance: **Implemented** as remote state.

The backup copy's untracked files have later filesystem dates (2026-01-07 and 2026-01-28). Those dates are not commits.

## Deprecated / removed

None found. There is no earlier commit that added a feature and a later commit that removed it.

## On the scan host, not in git

OVER-260 (captured 2026-09-28) lists these paths at the top of `~/projects/sonar_scan/repos/russel-serverless-api`. The issue path was not on this machine. The same names were opened on `E:\backup\sonar_scan\repos\russel-serverless-api`. `git status` reports both as untracked. They are not features of the Bitbucket tree.

| Path | In git? | What the file actually contains |
|---|---|---|
| `sonar-project.properties` | No | Sonar project key `overdrive_russel_serverless_api`, name `russel-serverless-api`, sources `.`, host `https://scan.appmonitor.co.za`, encoding UTF-8. Header says it was auto-generated |
| `sonarqube_scan.bat` | No | Pulls the repo, then runs a local `sonar-scanner.bat` with the same key, sources, and host. Token from `SONAR_TOKEN` or `SONARQUBE_TOKEN`. Header says it was auto-generated |

Provenance: **Implemented** as local files, **Documented** by their own headers. They are scan-host tooling. They do not add an API, a function, or a deployable service.

## Not in this repository

- A serverless function, HTTP route, API gateway, or OpenAPI document. The slug is the only "serverless" and "api" wording in git.
- A framework manifest (`serverless.yml`, SAM/CloudFormation template, `package.json`, or equivalent).
- Screens, jobs, queues, or data stores.
- Tests, Bitbucket Pipelines, or environment samples.
- Any file from `silicon_ark/website/` or from other projects that mention Russel Sauer. Those trees do not name this slug. Whether they were meant to share a product is **Unknown / Requires Confirmation**.