# Project plan — intersect_cloud_v2

Evidence date: 2026-10-12.

Source repository: `git@bitbucket.org:overdrive/intersect_cloud_v2.git`.

Inspected revision: `main` at `6dd7641d0690474633f3adda72d5572229dfa47a` (2024-09-27, Jaco Brits, "Initial commit"). That commit is `HEAD`. `git ls-remote --symref` reports `ref: refs/heads/main` for `HEAD`. The only ref on the remote is `refs/heads/main`. There are no tags.

The scan-host path `~/projects/sonar_scan/repos/intersect_cloud_v2` was not on this machine (`%USERPROFILE%\projects\sonar_scan\repos\intersect_cloud_v2` is absent). The tree below was read from that git revision.

This plan describes what the repository contains. It does not decide what the product should become.

No `silicon_ark/intersect_cloud_v2/` directory existed before this file. A search of Silicon Ark Markdown for `intersect_cloud` and `intersect_cloud_v2` found no earlier page for this slug. The only other top-level Silicon Ark directory whose name starts with `intersect` is `intersect_lambda/`. That is a different repository. See [Name overlap with intersect_lambda](#name-overlap-with-intersect_lambda).

## Product

There is no application, README, or product statement in git. The only tracked file is `.gitignore`. Its own header says the patterns are examples to customize, and it links to Atlassian's gitignore tutorial. It is not a description of a cloud product, an Intersect product, or a version 2 of anything.

History has one commit:

| Commit | Date | Author | What it did |
|---|---|---|---|
| `6dd7641` | 2024-09-27 11:56:56 +0000 | Jaco Brits (`jaco@overdrive.co.za`) | Initial commit. Added a 50-line `.gitignore` and nothing else |

The names in evidence are the Bitbucket slug `intersect_cloud_v2` and the scan-host directory of the same name. A slug is not a requirements statement. The suffix `v2` is part of that name. This repository does not contain a version-1 tree, a changelog, or a pointer to another repository.

What the product is, who it is for, and whether any code was meant to be pushed later are **Unknown / Requires Confirmation**.

## Branch reality

| Line | Tip | Date | What it is |
|---|---|---|---|
| `main` (default; `HEAD` symref) | `6dd7641` | 2024-09-27 | Only branch. One commit |

`git rev-list --all --count` is 1. `git tag -l` printed nothing. `git ls-tree -r --long HEAD` lists `.gitignore` only (624 bytes, blob `b24d71e22373e5147f3c05c68a8742714a89b5d6`). `git show-ref` listed `refs/heads/main` and no other ref.

The onboarding issue (OVER-162, captured 2026-09-28) recorded the same tip: `6dd7641`, 2024-09-27 11:56:56 +0000, "Initial commit", branch `main`. This clone agrees. `git ls-remote --symref` on 2026-10-12 printed `6dd7641d0690474633f3adda72d5572229dfa47a` as `HEAD`.

## Objectives

No project plan, issue list, or README exists in the repository. No objective can be inferred from application code, because there is no application code.

The only commit adds a starter ignore list. That is repository setup. It is not a written objective.

**Unknown / Requires Confirmation** whether this repository was created as a placeholder for a future product, as a second version of something else, or as a repository that was never filled in.

## Scope

### In scope of `main`

1. A Git repository on Bitbucket whose only tracked file is `.gitignore`.
2. The ignore patterns in that file at `6dd7641`. They are the example groups in the file's own comments: Node artifacts, Java class files, Python bytecode, logs, jar files, Maven output, JetBrains IDE files, unit-test XML, macOS and Windows junk, application binaries, and large media. Those paths are not present in the tree. See `technical-documentation.md`.

### Out of scope / not in this repository

- Any cloud service, API, screen, database, worker, or deployment.
- Any file other than `.gitignore`.
- A chosen language or framework. The ignore file lists several ecosystems in one template. See `technical-documentation.md`.
- The behaviour of `intersect_lambda`. That repository is separate. Its mail, Supabase, and SES rules are not rules of this slug. See [Name overlap with intersect_lambda](#name-overlap-with-intersect_lambda).
- The contents of `sonar-project.properties` and `sonarqube_scan.bat`. Those names were reported by the 2026-09-28 scan. They are not in git, `.gitignore` does not match those names, and the scan-host path could not be opened here.

## System shape

No system is implemented.

```text
bitbucket.org/overdrive/intersect_cloud_v2
└── .gitignore    (50 lines, 624 bytes, at 6dd7641)
```

There is no frontend, backend, database, API, worker, or deployment manifest in the remote.

## Major components

None. **Implemented** application-component count is zero.

The tracked `.gitignore` is repository metadata, not a product component.

## Milestones visible in git

| When | Commit | What landed |
|---|---|---|
| 2024-09-27 | `6dd7641` | Initial commit: example `.gitignore` only |

No later milestone exists in git. The tip is unchanged from the date OVER-162 recorded, and unchanged since 2024-09-27.

## Implementation plan

There is no forward plan in the repository. Current status: **one commit, ignore file only, no application**.

Whether anyone intends to push code here is **Unknown / Requires Confirmation**.

## Known dependencies

None declared. There is no `package.json`, `composer.json`, `requirements.txt`, `go.mod`, `*.csproj`, `template.yaml`, `Dockerfile`, `bitbucket-pipelines.yml`, or lockfile.

The ignore patterns name `node_modules/`, `*.class`, `*.py[cod]`, `*.jar`, and Maven `target/`. Those names are examples in a starter file. They are not declared dependencies.

## Name overlap with intersect_lambda

`silicon_ark/intersect_lambda/` documents a different Bitbucket repository, `git@bitbucket.org:overdrive/intersect_lambda.git`. That set (evidence date 2026-10-12) describes a serverless mail sender. Its project plan says the CloudFormation description on the `Lambda/` stack is `Simpleflow`, the direct-send function uses `no-reply@simpleflowhub.app`, and SSM parameter names use the prefix `intersectcloud`. The same plan says no product brief in that repository ties those three names together, and it records that repository's first commit as `57d0999` on 2024-09-30 ("Initial commit").

This repository does not mention `intersect_lambda`, Simpleflow, Supabase, SES, or those parameter names. Nothing in this tree imports, calls, or links that remote.

Chronology, using the date recorded in `silicon_ark/intersect_lambda/project-plan.md` and the date read from this remote: this slug's only commit (`6dd7641`, 2024-09-27) is three days earlier than the first commit recorded for `intersect_lambda` (2024-09-30). That order does not show that one repository replaced the other. Before this directory was added, a listing of Silicon Ark folders whose names start with `intersect` found `intersect_lambda` only. No `intersect_cloud` directory (without `_v2`) was present.

Whether `intersect_cloud_v2` was meant to be a version of the product inferred for `intersect_lambda`, a different product, or an unused repository is **Unknown / Requires Confirmation**. The mail, queue, and account behaviour written under `silicon_ark/intersect_lambda/` is not behaviour of this slug.

The shared author string is weak. Both histories include commits by Jaco Brits (`jaco@overdrive.co.za`). `intersect_lambda` also records commits by Dirk (`dirk@overdrive.co.za`). A shared author does not make the products one system.

## Discrepancy with the onboarding scan

OVER-162 lists this top-level structure for the scan-host path:

```text
sonar-project.properties
sonarqube_scan.bat
```

Those paths are not in the Bitbucket repository. `git ls-tree -r HEAD` lists `.gitignore` only. `.gitignore` does not ignore those filenames, so Git would have shown them if they had been tracked. The same two filenames appear in the onboarding notes for other repositories whose git trees do not contain them. Whether they are untracked SonarQube wrapper files added on the scan host, rather than project source, is **Inferred** from that repeated pattern. It is **Unknown / Requires Confirmation** until someone opens the scan-host directory and reads the files.

The scan also did not list `.gitignore`, which is the only file in git.

## Human confirmation

- Is this repository supposed to hold a product, or should it stay as the 2024-09-27 ignore-file commit?
- If a product was intended, what is its purpose, and where does the code live if not here?
- Does the `v2` in the slug refer to a prior system, and is that system `intersect_lambda` or something else?
- Whether the two Sonar filenames on the scan host are project files, and what they contain.
- Whether anyone is expected to push application code to `main`.