# Project plan — unityCLI

Evidence date: 2026-09-30.

Source repository: `https://bitbucket.org/overdrive/unitycli.git` (SSH form recorded on the onboarding issue: `git@bitbucket.org:overdrive/unitycli.git`).

Inspected revision: none. A clone on this date printed `warning: You appear to have cloned an empty repository.` `git ls-remote` returned no refs. The scan-host path `~/projects/sonar_scan/repos/unityCLI` was not on this machine.

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

No `silicon_ark/unityCLI/` directory existed before this file. A search of Silicon Ark Markdown for `unitycli`, `unity-cli`, and `unityCLI` found no earlier mention of this repository. The wiki project documents a different file, `unity.py`, under the label "Unity CLI". That file is not in this remote. See [Related name in the wiki project](#related-name-in-the-wiki-project).

## Product

There is no application, README, or product statement in git. The names in evidence are the scan-host directory `unityCLI` and the Bitbucket slug `unitycli`.

What the product is, who it is for, and whether either string is a product name are **Unknown / Requires Confirmation**.

## Branch reality

| Line | Tip | Date | What it is |
|---|---|---|---|
| Remote | no refs | — | Empty repository. No branch, no tag, no commit |
| Local unborn branch after clone | none | 2026-09-30 | Git named the empty working branch `master`. `git status -sb` then reported `origin/master [gone]`. That name comes from the client default. It is not a remote branch |

`origin/HEAD` is absent because the remote has no commits. The Bitbucket default-branch setting for an empty repository was not readable from git. **Unknown / Requires Confirmation.**

Authors, history, and a last-commit date do not exist. The onboarding issue (OVER-318, captured 2026-09-28) already recorded "Last commit: No commits found" and "Current branch: HEAD / Unknown". This clone agrees.

## Objectives

No project plan, issue list, or README exists in the repository. No objective can be inferred from code, because there is no code.

**Unknown / Requires Confirmation** whether this repository was created as a placeholder, a failed push, or a project that was never started.

## Scope

In scope for this document: the Bitbucket repository as cloned on 2026-09-30, and the filenames the onboarding issue says were at the top of the scan-host working tree.

Out of scope:

- Inventing a command-line product from the repository name.
- Copying the behaviour of `unity.py` in the wiki repository into this plan.
- The contents of `sonar-project.properties` and `sonarqube_scan.bat`. Those names were reported by the 2026-09-28 scan. The files are not in git, and the scan-host path could not be opened here.

## System shape

No system is implemented.

```text
bitbucket.org/overdrive/unitycli
└── (no commits, no tree)
```

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

## Major components

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

## Milestones visible in git

None. There is no first commit.

## Implementation plan

There is no forward plan in the repository. Current status: **empty remote, no implementation**.

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

## Known dependencies

None declared. There is no `package.json`, `composer.json`, `requirements.txt`, `go.mod`, `*.csproj`, `Dockerfile`, `Pipfile`, or pipeline file.

## Related name in the wiki project

`silicon_ark/wiki/features.md` labels a stub feature "Unity CLI" and points at `unity.py` inside the wiki repository. `silicon_ark/wiki/technical-documentation.md` describes that file as a Python 2 argument parser. Those statements are about the wiki tree. They do not appear in `unitycli`, and the wiki documents do not name this Bitbucket slug.

Whether `unitycli` was meant to hold that script, replace it, or remain unrelated is **Unknown / Requires Confirmation**. This plan does not treat the wiki file as a component of this repository.

## Discrepancy with the onboarding scan

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

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

Those paths are not in the Bitbucket repository. The same two filenames appear in the onboarding notes for other repositories whose git trees do not contain them (for example `unity-skeleton` and the wiki project). 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 empty?
- If a product was intended, what is its purpose, and where does the code live if not here?
- Any relationship to `unity.py` in the wiki repository.
- Whether the two Sonar filenames on the scan host are project files, and what they contain.
- The Bitbucket default branch once a first commit exists.