# Business rules — im_flutter_app

Evidence date: 2026-10-12. Source: `git@bitbucket.org:overdrive/im_flutter_app.git` at `1b7bfe7682b7b85f5ee46a0c3fcd81bcec0dd40b` (`master`).

No business-rule document exists in the source repository. The only committed file is `.gitignore`. Rules below are limited to what that file and the Git history actually enforce. Nothing else was inferred into a domain rule.

## Domain

**Unknown / Requires Confirmation.** No domain (orders, users, billing, content, or otherwise) is named in the repository. The repository name does not establish a domain.

## Rules found

### BR-001 — Git ignores the example patterns

**Statement.** Paths matching the patterns in `.gitignore` are not added by a normal `git add` while this file is in effect.

**Provenance.** Implemented (the ignore file in `1b7bfe7`).

**Who.** Anyone committing to a clone of this repository.

**Trigger.** A path is created that matches a pattern, and Git is asked to stage it.

**This is version-control hygiene.** It is not a product or business rule. The file header says the list should be customized for the project. No customization beyond the example text is present.

### BR-002 — No application rule is enforced

**Statement.** The repository contains no validation, permission check, workflow gate, calculation, or constraint on business data.

**Provenance.** Implemented as an absence: the tree has no source file that could enforce a rule.

## Permissions and access

No application role, login, or access-control list is implemented.

Who may push to the Bitbucket repository is a host setting. It is not in this tree. **Unknown / Requires Confirmation.**

## Workflows

No business workflow is implemented. See `prd.md` (W0 is only "the clone contains `.gitignore`").

## Validation

No input validation exists.

## Rules explicitly not claimed

The following were considered and rejected as rules, because the evidence does not support them:

- A Flutter application, screen, or store rule. `flutter` appears in the repository name only.
- A technology choice (Node, Java, Python, Maven, JetBrains). Those words appear only as example ignore patterns.
- A SonarQube quality gate. The scan-host filenames in the OVER-153 snapshot are not in Git, and their contents were not read.
- A retention, privacy, pricing, or approval rule. None is written.

## Conflicts

None inside the repository. The discovery snapshot versus Git, and the repository name versus the empty tree, are recorded in `project-plan.md`. Those conflicts are about which files exist, not about two business rules disagreeing.

## Unknown / Requires Confirmation

- The business the repository was opened for.
- Any rule that operators follow outside this repository.