# Business rules — baskit_webportal

Evidence date: 2026-10-19. Revision: `main` `ae9d75d`.

No business-rules document exists in the source repository. The application does not implement domain logic in git.

Every rule below is either **Unknown** or **Inferred** from repository metadata. Do not treat **Inferred** lines as approved business policy.

## Domain behaviour

**Unknown / Requires Confirmation.** No models, controllers, services, or validation code are committed.

## Validation rules

**Unknown.** No input handling code exists in the repository.

## Permissions and access

**Unknown.** No authentication or authorisation implementation exists in the repository.

## Workflows enforced by the application

None evidenced.

## Rules that can be stated from git alone

**BR-001 — The default branch is `main`.**  
**Implemented** — `origin/HEAD` points to `origin/main`.

**BR-002 — Only one commit exists on `main` at inspection.**  
**Implemented** — history is a single "Initial commit".

**BR-003 — No business data is stored in this repository.**  
**Inferred** — only `.gitignore` is tracked; no schema or data files.

## Inferred from `.gitignore` (not business rules)

The ignore file lists patterns for Node (`node_modules/`, `dist/`), Java (`*.class`, `target/`), Python (`*.py[cod]`), logs, IDE folders, and large media. That may guide future contributors but does **not** define product rules. Provenance: **Inferred** from file content only.

## Human confirmation needed

When application code is added or linked from another repository, this document should be replaced or extended with rules labelled **Documented Requirement** or **Implemented Behaviour** from code and approved requirements — not from repository naming alone.