# PRD — envolve-infra

Evidence date: 2026-10-15. Source: `https://bitbucket.org/overdrive/envolve-infra.git` (clone of the SSH URL recorded on OVER-110, `git@bitbucket.org:overdrive/envolve-infra.git`).

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

No formal PRD existed in the repository or in `silicon_ark/envolve-infra/` before this file. The remote has no commits, so there is no implementation from which to recover requirements. The statements below record that absence. They are not a product decision.

## Product purpose

**Unknown / Requires Confirmation.**

The repository slug is `envolve-infra`. The scan-host directory name is `envolve-infra`. A name is not a requirements statement. No README, route, or comment defines a purpose, because none of those files exist.

**Implemented:** a Bitbucket Git repository that accepts a clone and contains no tree.

What a future product should do is out of scope for this document.

A different repository, `overdrive/evolve-infra`, has a README that calls itself the Evolve infrastructure repository and a Compose file for Magus. That behaviour is specified in `silicon_ark/evolve-infra/prd.md`. It is not behaviour of this remote. See [Integrations](#integrations).

## Users and roles

No user, role, permission, or account model is present.

| Role | Evidence | Provenance |
|---|---|---|
| — | No source file names a person, role, or login | **Unknown** |

Who would use a product in this repository, if one is added later, is **Unknown / Requires Confirmation**.

## Major workflows

No workflow is implemented. There is no trigger, input, validation, output, or error path to trace.

The only observed operation is a Git clone of an empty repository (2026-10-15):

- Trigger: `git clone` of `https://bitbucket.org/overdrive/envolve-infra.git`.
- Behaviour: Git created a local `.git` directory and reported an empty repository. The unborn local branch was named `master`. `git status` reported "No commits yet". `git status -sb` reported `origin/master [gone]`.
- Output: a working tree with no files besides `.git`.
- Provenance: **Implemented** as the state of the remote on that date. This is repository state, not application behaviour.

## Integrations

No integration is declared or called from this tree.

| System | Evidence | Provenance |
|---|---|---|
| Bitbucket Git hosting | Remote URL on `origin` after clone | **Implemented** |
| SonarQube | Filenames `sonar-project.properties` and `sonarqube_scan.bat` listed by OVER-110 for the scan-host path. Files not in git and not read | **Unknown** |
| `overdrive/evolve-infra` | Separate remote. `git ls-remote --heads` returned `35effc12722db94b315240b8b8f65e4d110a7738` on `refs/heads/master`. Documented in `silicon_ark/evolve-infra/`. No submodule, remote, or file in this repository points there | **Unknown** whether the two slugs were meant to be one product |
| `magus-core` | Named from `evolve-infra` and from `silicon_ark/magus-core/`, which links to `evolve-infra`. Not named by this empty remote | **Unknown** |
| Any shell, package registry, auth, or storage service | Not present | **Unknown** |

Copying Magus database settings, host ports, or the phpMyAdmin workflow from `evolve-infra` into requirements for `envolve-infra` would be an assumption. It is not done here.

## Constraints

- This PRD must not treat the repository name as a specification.
- This PRD must not treat `evolve-infra` as this repository. The slugs differ by one letter, and only one of them has commits.
- Requirements cannot be tested against this repository until code or a written spec exists.
- The scan-host working tree was not available. Filenames reported there are not confirmed file contents.

## Requirements discovered from the implementation

No functional requirements were discovered. There is no command, controller, route, screen, schema, test, or config to cite.

| ID | Statement | Provenance |
|---|---|---|
| — | No requirement text exists in the repository | **Unknown** |

Nothing is marked **Planned**. A plan would need a document or an issue inside the repository, and there is neither.

## Out of scope for this document

- Defining containers, images, or a Magus local stack because the slug contains "infra" and a similarly named repository has that stack.
- Importing functional requirements from `silicon_ark/evolve-infra/prd.md`.
- Contents of the two Sonar filenames on the scan host.

## Human confirmation

- Product purpose, users, and workflows, if this repository is meant to hold a product.
- Whether any requirement lives in another system (tracker, wiki, or `evolve-infra`) that was not linked from this remote.
- Whether this slug should be retired in favour of `evolve-infra`, or kept as a separate repository.