# PRD — loginscreen-uriel

Evidence date: 2026-10-10.

Source repository: `git@bitbucket.org:overdrive/loginscreen-uriel.git`, `master` at `2ba8ff2` (2020-02-27).

Provenance labels used below: **Documented**, **Implemented**, **Inferred**, **Planned**, **Unknown / Requires Confirmation**.

This document records behaviour that can be traced to the repository. It does not add a product that the repository does not contain.

## Product purpose

**Unknown / Requires Confirmation.**

The tracked tree is Bitbucket's default README. It does not name a product, a user, a problem, or a workflow. The repository name is the only signal, and it is **Inferred**: `loginscreen-uriel` reads as a login screen associated with the Bitbucket user `uriel`. Nothing in `README.md` confirms that reading.

No prior Silicon Ark set existed for this directory.

## Users and roles

No user, role, or permission is defined in the repository.

| Candidate | Evidence | Status |
|---|---|---|
| A person who would use a login screen | Repository name only | **Inferred**. Not confirmed |
| "Repo owner or admin" | README heading "Who do I talk to?" | **Documented** as a blank template line. No name |
| "Other community or team contact" | Same heading | **Documented** as a blank template line |
| Author of the only commit | Git author `uriel <uriel@overdrive.co.za>` | **Implemented** as commit metadata. Not described as a product role |

## Systems the product talks to

None are present in the tree. No HTTP client, database driver, mailer, queue, or third-party SDK exists.

The README heading "Database configuration" is an empty bullet. It is not evidence that a database was chosen.

## Major workflows

No workflow is implemented. There is no screen, form, route, or script.

The README lists setup, test, and deployment headings with no steps under them. Those headings are **Documented** template text. They are not workflows.

## Functional requirements

No functional requirement can be written from this tree without inventing one. There is no controller, view, API, or test that states an expected behaviour.

The following were considered and rejected as requirements:

| Text | Why it is not a requirement |
|---|---|
| Repository name `loginscreen-uriel` | A name is not a specified behaviour. Login, credentials, sessions, and errors are all **Unknown** |
| README "What is this repository for?" | The bullets under it are "Quick summary", "Version", and a link to Bitbucket's Markdown tutorial. No summary or version is filled in |
| README "How do I get set up?" | Bullets name configuration, dependencies, database, tests, and deployment, and give no values |
| README "Contribution guidelines" | Bullets name tests, code review, and "other guidelines", and give no rules |

If a human later confirms that this repository was supposed to become a login screen, that confirmation is a new requirement. It is not in the current tree.

## Constraints

No validation rule, session rule, password rule, or access rule is implemented, because there is no application.

No dependency, runtime, or supported browser is declared.

## Integrations

None.

## Data

No entity, table, file format, or stored secret is defined. The README does not mention a field.

## Discrepancies

| Source | Says | Repository at `2ba8ff2` |
|---|---|---|
| Onboarding scan (2026-09-28) | Root contains `README.md`, `sonar-project.properties`, `sonarqube_scan.bat` | Only `README.md` is tracked. The two Sonar files are not in history |
| Repository name | Suggests a login screen | No login behaviour exists |
| README setup section | Implies configuration, dependencies, a database, tests, and deployment | No files for any of those |

## Out of scope in this tree

- Any login, registration, password reset, or session behaviour.
- A relationship to `logintuto`. That repository shares the author email `uriel@overdrive.co.za` and had commits on 2020-02-27, including one titled "reset repo". No file here links the two. Whether they are one effort is **Unknown / Requires Confirmation**. See `project-plan.md`.

## What a tester can take from this PRD

There is no behaviour to test. A meaningful test appears only after a human confirms a purpose and code exists. Until then, the checkable statements are:

1. `master` at `2ba8ff2` contains only `README.md`.
2. That file is the unfilled Bitbucket template.
3. `sonar-project.properties` and `sonarqube_scan.bat` are not in git.