# PRD — intersect_cloud_v2

Evidence date: 2026-10-12. Source: `git@bitbucket.org:overdrive/intersect_cloud_v2.git`, `main` at `6dd7641d0690474633f3adda72d5572229dfa47a`.

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

No formal PRD existed in the repository or in `silicon_ark/intersect_cloud_v2/` 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 `intersect_cloud_v2`. No README, page title, route, or comment defines a purpose. The `.gitignore` describes paths Git should skip. It does not describe users, workflows, cloud resources, or behaviour.

**Implemented:** a Bitbucket Git repository with one commit. `6dd7641` (2024-09-27, Jaco Brits, "Initial commit") adds a 50-line example `.gitignore`. The tip tree is that file only. `HEAD` is `main`.

What a future product should do is out of scope for this document. The slug is not a specification of an Intersect Cloud product, and the `v2` suffix is not a specification of a second version. No file in this repository names a version 1.

## 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 2024-09-27 11:56:56 +0000.
   - Input: `.gitignore` (50 lines, 624 bytes). 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 `6dd7641`, which is also the `HEAD` symref.
   - Provenance: **Implemented** as git history. This is repository state, not application behaviour.

A mirror clone of `git@bitbucket.org:overdrive/intersect_cloud_v2.git` on 2026-10-12 matched that tip. `git ls-remote --symref` had already printed `6dd7641d0690474633f3adda72d5572229dfa47a` as `HEAD` and `refs/heads/main` as the symref. 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-162 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 |
| `intersect_lambda` (Simpleflow / SES / Supabase, as documented under `silicon_ark/intersect_lambda/`) | No remote URL, import, or API call in this tree. The other repository's SSM names use the prefix `intersectcloud`. This tree does not contain that string | **Unknown** whether the slugs were meant to share a product. See `project-plan.md` |
| Any API, database, mailer, queue, or storage service | Not present | **Unknown** |

## Constraints

- This PRD must not treat the repository name as a specification of Intersect Cloud, or of a version 2.
- 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.
- Behaviour documented for `intersect_lambda` must not be imported as requirements of this slug.
- 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.

## 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 Intersect Cloud product, or a version-2 migration, from the slug.
- Treating the starter ignore list as a stack decision.
- Importing mail, queue, Supabase, SES, or account behaviour from `silicon_ark/intersect_lambda/` as requirements of this slug.
- 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 it was meant to hold a cloud product, and what `v2` refers to.
- Whether it was meant to sit beside, replace, or stay separate from `intersect_lambda`.
- Whether application code exists somewhere other than this remote.
- Whether the Sonar filenames on the scan host belong to this project.