# Business rules — 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 business-rules document existed in the repository or in `silicon_ark/intersect_cloud_v2/` 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 (2024-09-27). 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-12. `HEAD` points at `refs/heads/main`.

## Domain behaviour

No domain object is defined. There is no account, tenant, subscription, message, queue, or document type in this repository.

Rules written for another repository are not rules of this one:

- `silicon_ark/intersect_lambda/business-rules.md` describes mail-send and queue behaviour, including SSM parameter names that use the prefix `intersectcloud`. That file does not name slug `intersect_cloud_v2`.
- This tree does not contain the string `intersectcloud`, and it does not reference that repository.

Whether any `intersect_lambda` rule was meant to apply to this repository is **Unknown / Requires Confirmation**.

## 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 Intersect Cloud, version 2." Only the slug says `intersect_cloud_v2`. **Not a rule.**
- "This repository replaces or extends `intersect_lambda`." No file here names that repository. The other slug's rules are documented separately. **Not a rule.**
- "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 rules already written for `intersect_lambda` should ever be attached to this repository.
- Whether the example ignore list was left unchanged on purpose.