# PRD — baskit_webportal

Evidence date: 2026-10-19.

Source: `git@bitbucket.org:overdrive/baskit_webportal.git`, `main` at `ae9d75d` (2026-07-03).

There is no PRD, README, or issue tracker export in the source repository or in Silicon Ark before this set. Requirements below are limited to what git proves. Anything about product behaviour is **Unknown / Requires Confirmation** unless labelled **Inferred** from the repository name only.

## Product purpose

**Unknown / Requires Confirmation.**

**Inferred (weak):** the slug `baskit_webportal` suggests a browser-based portal related to "Baskit". No code, copy, or configuration in git supports a stronger statement.

## Users and roles

| Actor | Evidence | Status |
|---|---|---|
| End user | — | **Unknown** |
| Staff / administrator | — | **Unknown** |
| Developer | Jaco Brits authored the initial commit | **Implemented** (git metadata only) |

No authentication, authorisation, or role model exists in the repository.

## Systems the product would talk to

**Unknown / Requires Confirmation.** No API clients, SDK usage, or integration config is committed.

## Major workflows

No workflows can be recovered from the repository.

| Workflow | Status |
|---|---|
| User registration / login | **Unknown** — no auth code |
| Core business transactions | **Unknown** — no domain code |
| Reporting or admin operations | **Unknown** — no UI or API |

## Functional requirements (from implementation)

None. The tracked tree contains no executable application.

## Non-functional requirements

None documented or implemented in git.

| Area | Status |
|---|---|
| Security (HTTPS, secrets, RLS) | **Unknown** |
| Performance / scaling | **Unknown** |
| Observability | **Unknown** |
| Testing | **Unknown** — no test tree |

## Integrations

**Unknown / Requires Confirmation.**

## Constraints stated in repository

The `.gitignore` lists patterns for common artefacts (for example `node_modules/`, `dist/`, `target/`, IDE folders). That implies future work may use Node, Java/Maven, or Python, but **Inferred** only — no lockfile or build file confirms a chosen stack.

## Assumptions (explicit)

These are **not** requirements; they are documentation assumptions until disproved:

1. The repository was created as a placeholder or early shell for a future Baskit web portal (**Inferred** from name and single initial commit).
2. Product requirements will need to be authored when code lands or linked from another source (**Inferred**).

## Open questions for product owners

1. What is Baskit in this context (product, client, internal codename)?
2. What must the web portal do on day one?
3. Is implementation expected in this repo or elsewhere?
4. Should SonarQube analysis apply once code exists (`sonar-project.properties` was seen on the scan host but not in git)?