# PRD — unity-salestracker

Evidence date: 2026-09-30. Source: `https://bitbucket.org/overdrive/unity-salestracker.git`.

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

No formal PRD existed in the repository or in `silicon_ark/unity-salestracker/` 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 `unity-salestracker`. A slug is not a requirements statement. No README, UI string, 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.

## 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-09-30):

- Trigger: `git clone` of `https://bitbucket.org/overdrive/unity-salestracker.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".
- 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.

| System | Evidence | Provenance |
|---|---|---|
| Bitbucket Git hosting | Remote URL on `origin` | **Implemented** |
| SonarQube | Filenames `sonar-project.properties` and `sonarqube_scan.bat` listed by OVER-326 for the scan-host path. Files not in git and not read | **Unknown** |
| Any sales, billing, auth, or storage service | Not present | **Unknown** |

The sales screens inside `unity-skeleton` talk to a browser mock, not to this repository. See `silicon_ark/unity-skeleton/prd.md`. Linking that behaviour to `unity-salestracker` would be an assumption. It is **Unknown / Requires Confirmation**.

## Constraints

- This PRD must not treat the repository name as a specification.
- 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 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 sales-tracking behaviour because the slug contains "salestracker".
- Importing functional requirements from `unity-skeleton` or `unity-soft-ui`.
- 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 another repo) that was not linked from this remote.