# PRD — footprint-lambda Evidence date: 2026-10-14. Source: `git@bitbucket.org:overdrive/footprint-lambda.git`, `master` at `351a5ca129d32c1a91550dbd2b7f3be8b7656b25`. Provenance labels: **Documented**, **Implemented**, **Inferred**, **Planned**, **Unknown**. No formal PRD existed in the repository or in `silicon_ark/footprint-lambda/` 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 `footprint-lambda`. No sentence, route, comment, or config defines a purpose, a user, or a workflow. `.gitignore` tells the reader to customize an example ignore list. It does not name a product. **Implemented:** a Bitbucket Git repository with one commit. `351a5ca` (2022-02-23, Jaco Brits, "Initial commit") adds `.gitignore` and nothing else. The blob is `b24d71e22373e5147f3c05c68a8742714a89b5d6` (624 bytes, 50 LF lines). **Documented:** the file header, which says the patterns are examples and links to `https://www.atlassian.com/git/tutorials/saving-changes/gitignore`. What a future product should do is out of scope for this document. ## Users and roles No user, role, permission, or account model is present. | Role | Evidence | Provenance | |---|---|---| | Repository author | The only commit uses `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 2022-02-23 04:29:38 +0000. - Input: `.gitignore` (624 bytes in git, LF). The header says the list is an example to customize. - Behaviour: the file is the entire tree. - Output: `master` at `351a5ca`. - Provenance: **Implemented** as git history. This is repository state, not application behaviour. A clone of `git@bitbucket.org:overdrive/footprint-lambda.git` on 2026-10-14 checked out `master` and matched that tip. `git ls-remote --heads --tags origin` printed `351a5ca129d32c1a91550dbd2b7f3be8b7656b25` as `refs/heads/master` only. 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 `master` | **Implemented** | | SonarQube | Filenames `sonar-project.properties` and `sonarqube_scan.bat` listed by OVER-126 for the scan-host path. Files not in git and not read | **Unknown** | | AWS Lambda or API Gateway | The slug contains "lambda". No `serverless.yml`, handler, or AWS template is in git | **Unknown** whether any Lambda was intended | | `FootPrintLive` | Separate Silicon Ark directory. Its plan describes a Zend Framework rugby operations application. This remote does not name it | **Unknown** whether any product link was intended | | `matchcentre.footprintapp.net` | Separate Silicon Ark directory. Its plan describes an SA Rugby match centre. This remote does not name it | **Unknown** whether any product link was intended | | `tournaments.footprintapp.net` | Separate Silicon Ark directory. Its plan describes a `.gitignore`-only repository. This remote does not name it | **Unknown** whether any product link was intended | | `Footprint-Not-Used` | Separate Silicon Ark directory. Its plan describes a heading-only README. This remote does not name it | **Unknown** whether any product link was intended | | Any mailer, queue, payment provider, or storage service | Not present | **Unknown** | ## Constraints - This PRD must not treat the repository name as a specification that an AWS Lambda, or a Footprint product, exists here. - This PRD must not treat the example ignore groups (Node, Java, Python, Maven) as a chosen stack. They appear together 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. `.gitignore` does not ignore `sonar-project.properties` or `sonarqube_scan.bat`. ## Requirements discovered from the implementation No functional product 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** | The ignore-file header is an instruction to customize examples. It is not a product requirement. Nothing is marked **Planned**. A plan would need a document or an issue inside the repository, and there is neither. Git's behaviour with this file, once other files exist, would be to skip the listed patterns. That behaviour is not observable here, because no other path is in the tree and no second commit exists. Provenance of the pattern text: **Implemented**. Provenance of any runtime effect on this repository's history: none observed. ## Data the repository manages None. There is no schema, fixture, sample record, or configuration value beyond the ignore patterns. ## Out of scope for this document - Deciding whether the repository should be archived, filled in, or left as the 2022 commit. - Behaviour documented for other Footprint or Lambda directories. Those trees were not this remote. - Contents of the two Sonar filenames reported on the scan host.