# Features — envolve-infra

Evidence date: 2026-10-15. Source: `https://bitbucket.org/overdrive/envolve-infra.git` (empty clone; no commit to pin).

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

No feature list existed in the repository or in `silicon_ark/envolve-infra/` before this file.

## Current

No product feature is implemented. The git tree is empty.

The repository itself exists on Bitbucket and can be cloned. That is hosting state, not a user-facing feature. Provenance: **Implemented** (clone on 2026-10-15).

## Completed

Nothing has been completed in git. There is no historical commit that later removed a feature.

## In development

Nothing. There is no branch with unmerged work. `git ls-remote` returned no heads.

## Planned

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

## Recently changed

No change can be named. The onboarding issue recorded "No commits found" on 2026-09-28. The clone on 2026-10-15 is still empty. Provenance: **Implemented** as remote state.

## Deprecated / removed

None found.

## Reported on the scan host, not in git

OVER-110 (2026-09-28) lists these paths at the top of `~/projects/sonar_scan/repos/envolve-infra`:

| Path | In git? | Read here? |
|---|---|---|
| `sonar-project.properties` | No | No. Scan-host path was not on this machine |
| `sonarqube_scan.bat` | No | No. Scan-host path was not on this machine |

They are not features of the Bitbucket tree. What they configure is **Unknown / Requires Confirmation**. The same two names are reported for other scan-host checkouts whose commits do not contain them. Treating them as untracked scan wrappers is **Inferred**, not a finding from file contents.

## Not in this repository

- A Docker Compose stack, nginx site, PHP image, phpMyAdmin service, or Magus submodule. Those are features of `overdrive/evolve-infra` at `35effc1`, documented in `silicon_ark/evolve-infra/features.md`. `git ls-remote` showed that head on `evolve-infra` and no heads on `envolve-infra`.
- Screens, APIs, jobs, or data stores.
- Tests, pipelines, or environment samples.

Whether the empty repository was intended to receive the Evolve infrastructure work is **Unknown / Requires Confirmation**.