# PRD — 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 formal PRD existed in the repository or in `silicon_ark/datafy_ios/` before this file. The only tracked file is `.gitignore`. The statements below record that absence. They are not a product decision.

## Product purpose

**Unknown / Requires Confirmation.**

The repository slug is `datafy_ios`. No README, page title, route, or comment defines a purpose. The `.gitignore` describes paths Git should skip. It does not describe users, workflows, or behaviour.

**Implemented:** a Bitbucket Git repository with one commit. `5e0218f` (2025-10-11, Jaco Brits, "Initial commit") adds a 50-line example `.gitignore`. The tip tree is that file only. `origin/HEAD` is `main`.

What a future product should do is out of scope for this document.

Other Silicon Ark sets describe Datafy clients that are not this repository. `flutter_app` is the Datafy Ai Flutter client and includes an iOS target. `datafy_web` is a Flutter web client and also contains an `ios/` directory. `datafy-supabase-functions` names a FlutterFlow mobile app `datafy_ai`. None of those documents names `datafy_ios`. Whether this slug was meant to be one of those clients is **Unknown / Requires Confirmation**.

## Users and roles

No user, role, permission, or account model is present.

| Role | Evidence | Provenance |
|---|---|---|
| Repository author | The only commit uses `jaco@overdrive.co.za`. The name on the commit is Jaco Brits | **Implemented** as git metadata, not an application role |
| Application user | No source file names a person, role, or login | **Unknown** |

Who would use a product in this repository, if one is added later, is **Unknown / Requires Confirmation**.

## Major workflows

No application workflow is implemented. There is no trigger, input, validation, output, or error path in product code.

The only observed repository operation, besides reading the tree, is the initial commit:

1. Trigger: initial commit on 2025-10-11 05:42:01 +0000.
   - Input: `.gitignore` (50 lines). The header says the patterns are examples and links to `https://www.atlassian.com/git/tutorials/saving-changes/gitignore`.
   - Behaviour: the file is the entire tree.
   - Output: `main` at `5e0218f`, which is also `origin/HEAD`.
   - Provenance: **Implemented** as git history. This is repository state, not application behaviour.

A clone of `git@bitbucket.org:overdrive/datafy_ios.git` on 2026-10-18 checked out `main` and matched that tip. `git ls-remote --heads` printed `5e0218f5ec43df7bb59a8d55f8b845682471d438` as `refs/heads/main`. Provenance: **Implemented** as remote state on that date.

## Integrations

No integration is declared or called from this repository.

| System | Evidence | Provenance |
|---|---|---|
| Bitbucket Git hosting | Remote URL on `origin`; one commit on `main` | **Implemented** |
| Atlassian gitignore tutorial | URL in the header comment of `.gitignore` | **Documented** as a comment. The file does not call that site |
| SonarQube | Filenames `sonar-project.properties` and `sonarqube_scan.bat` listed by OVER-80 for the scan-host path. Files not in git and not read. Those names are not ignore patterns | **Unknown** |
| Node, Java, Python, Maven, or a media pipeline | Patterns for those ecosystems appear together in the starter ignore file. No manifest or source file exists | **Unknown** whether any of them was intended |
| An iOS toolchain (Xcode, Swift, CocoaPods, TestFlight) | Not present. The slug contains `ios`. The ignore file does not mention Xcode or Swift | **Unknown** |
| Any API, database, mailer, queue, or storage service | Not present | **Unknown** |
| Other Datafy repositories (`flutter_app`, `datafy_web`, `datafy_lambda`, and the rest listed in `project-plan.md`) | Separate remotes documented elsewhere in Silicon Ark. This tree does not reference them | **Unknown** whether a product link was intended |

## Constraints

- This PRD must not treat the repository name as a specification of an iOS application.
- Ignore patterns must not be read as implemented features or as a chosen technology stack. Node, Java, Python, and Maven patterns appear in one starter file.
- Requirements cannot be tested against this repository until code or a written spec exists.
- The scan-host working tree was not available. Filenames reported there are not confirmed file contents.
- Behaviour documented for `flutter_app` and `datafy_web` belongs to those repositories. It is not a requirement of `datafy_ios`.

## Requirements discovered from the implementation

No functional requirements were discovered. There is no command, controller, route, screen, schema, test, or application config to cite.

| ID | Statement | Provenance |
|---|---|---|
| — | No requirement text exists in the repository | **Unknown** |

Nothing is marked **Planned**. A plan would need a document or an issue inside the repository, and there is neither.

## Data the repository manages

No product data. The only content is Git ignore patterns. See `technical-documentation.md` for the pattern list.

## Out of scope for this document

- Inventing an iOS product from the slug `datafy_ios`.
- Treating the starter ignore list as a stack decision.
- Copying screens, roles, or integrations from `flutter_app`, `datafy_web`, or any other Datafy set into this PRD.
- The unread contents of the two Sonar filenames reported on the scan host.

## Human confirmation

- What this repository is for, and who the users would be.
- Whether application code exists somewhere other than this remote.
- Whether this slug is related to the iOS target already present in `flutter_app` or `datafy_web`.
- Whether the Sonar filenames on the scan host belong to this project.