# PRD — ohlief

Evidence date: 2026-10-08.

Source: `git@bitbucket.org:overdrive/ohlief.git`, `master` at `a85c889` (2020-02-10, Jaco Brits, "Initial commit").

There is no prior PRD in the source repository or in Silicon Ark. The only committed file is Bitbucket's default `README.md`. No functional requirement can be recovered from code, tests, or a filled-in document. Nothing below is a product decision.

## Product purpose

**Unknown.** The README heading "What is this repository for?" is followed by the placeholders "Quick summary" and "Version", plus a link to Bitbucket's Markdown tutorial. No purpose is stated.

The repository name `ohlief` matches the word used by two other Silicon Ark sets (`ohlief-app-client`, `ohlief-app-api`). Those sets describe an EDI order and invoice application. This repository does not contain that application and does not refer to those repositories. Treating this repository as that product would be an invention. The relationship is **Unknown / Requires Confirmation**.

## Users and roles

| Actor | Evidence | Status |
|---|---|---|
| "Repo owner or admin" | README bullet under "Who do I talk to?" | **Documented** as template text. No person, role, or permission is named |
| "Other community or team contact" | Same section | **Documented** as template text. No contact is named |
| Commit author | Git author of `a85c889`: Jaco Brits | **Implemented** as history metadata. Not a product role |

No login, session, permission, or user record exists in the tree.

## Systems the product talks to

None. The tree has no HTTP client, SDK, webhook, database driver, or configuration that names an external system. The Markdown tutorial URL in the README is a documentation link, not an integration.

## Major workflows

None. There is no screen, route, command, job, or script in git.

The README lists setup, configuration, dependencies, database configuration, tests, and deployment as empty bullets. Those are the Bitbucket template. They are not workflows.

## Functional requirements

No requirement in this repository describes an action a user can take. The statements below record that absence so a later reader does not treat silence as an unspecified feature.

### FR-001 — Repository holds a starter README

A checkout of `master` at `a85c889` contains `README.md` and no other tracked file. The file is the Bitbucket starter. It does not instruct a reader how to build, run, or deploy an application.

Evidence: `git ls-tree -r HEAD`, `README.md`. Implementation: Implemented. Confidence: High.

### FR-002 — No product behaviour is specified

The repository does not define users, inputs, outputs, validation, or error behaviour for a product.

Evidence: the same tree. Implementation: absent. Confidence: High that the absence is real at `a85c889`. Confidence: none about intent.

## Constraints

None stated. There is no validation, permission model, retention rule, or environment constraint in the tree.

## Integrations

None in this repository.

Calls made by the Oh-lief EDI client and API are specified in `silicon_ark/ohlief-app-client/` and `silicon_ark/ohlief-app-api/`. They are not requirements of `ohlief`.

## Edge cases

There is no input path to fail. Empty state of the product is the repository itself: one placeholder README, last changed 2020-02-10.

## Non-goals confirmed by absence

No API, no user interface, no database, no authentication, no background job, no test, no pipeline, no deployment manifest.

## Requires confirmation

- Whether a product was ever meant to live in this repository.
- Whether the Oh-lief EDI requirements in the sibling Silicon Ark directories should be linked to this slug, or kept separate.
- Whether any behaviour existed only as untracked files on the scan host (see `project-plan.md`).