# Business rules — datafy_ios

Evidence date: 2026-10-18. Source: `git@bitbucket.org:overdrive/datafy_ios.git`, `main` at `5e0218f5ec43df7bb59a8d55f8b845682471d438`.

Provenance labels: **Documented**, **Implemented**, **Inferred**, **Planned**, **Unknown**.

No business-rules document existed in the repository or in `silicon_ark/datafy_ios/` before this file.

## Rules found in the repository

None that govern a product. The only tracked file is `.gitignore`. An ignore list does not enforce validation, permissions, or workflow gates.

No rule below is inferred from the repository name. A name is not a domain rule.

## Identity and access

No login, role, or permission check exists in the tree.

The only commit records `jaco@overdrive.co.za` with the display name Jaco Brits (2025-10-11). That is history, not an access-control rule.

**Unknown / Requires Confirmation** who is allowed to push to the Bitbucket repository. Hosting permissions were not inspected. The Bitbucket API client returned HTTP 401, so project settings were not read. A clone of `main` succeeded on 2026-10-18. `origin/HEAD` points at `origin/main`.

## Domain behaviour

No domain object is defined. There is no entity, status, price, account, store, task, or document type in this repository.

Retail store-execution rules documented for other Datafy repositories (`flutter_app`, `datafy_web`, `datafy_lambda`, `datafy-supabase-functions`) are rules of those repositories. They are not implemented here and are not adopted as rules of `datafy_ios`.

## Validation

No validator, schema, form rule, or argument parser exists in this repository.

`.gitignore` causes Git to skip matching untracked paths. That is a version-control filter. The patterns are listed in `technical-documentation.md`. They are not input validation for a product.

The header comments tell the reader to customize the examples. Provenance: **Documented** in `.gitignore`. That instruction is about the ignore file itself. It is not a product validation rule.

## Workflows

No status machine, approval step, retry, or scheduled job is defined.

## Explicit non-rules

The following were not adopted, because the evidence does not support them:

- "The product is an iOS application for Datafy." Only the slug says `datafy_ios`. **Not a rule.**
- "This repository is the Datafy Ai iOS client." That client is documented under `silicon_ark/flutter_app/` from a different remote. **Not a rule of this tree.**
- "The stack is Node, Java, Python, or Maven." Those words appear as section comments in a starter `.gitignore` that lists them together. No source file uses any of them. **Not a rule.**
- "SonarQube quality gates apply." Two filenames were reported on a scan host and were not read. **Not a rule.**
- Any threshold, eligibility check, or permission matrix. **Not present.**

## Human confirmation

- Whether any business rule for this slug is kept outside the repository.
- Whether the example ignore list was left unchanged on purpose.
- Whether rules already written for `flutter_app` or `datafy_web` were ever meant to apply here.