# Project plan — formulys_api_nodejs

Evidence date: 2026-10-14.

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

Inspected revision: `master` at `9d191c4d2e344910abda7a10989a304d0988339c` (`9d191c4`, 2023-11-17 06:20:17 +0000, Jaco Brits `<jaco@overdrive.co.za>`, "Initial commit"). `origin/HEAD` points at `master`. No other remote branches. No tags.

The scan-host path `~/projects/sonar_scan/repos/formulys_api_nodejs` was not on this machine. The tree below was read from a clone of that git revision. The clone contains the only commit on `master`.

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

No `silicon_ark/formulys_api_nodejs/` directory existed before this file. A search of Silicon Ark Markdown for the slug `formulys_api_nodejs` found no earlier mention.

## Product

There is no README, product brief, API specification, or application source in the repository. The only tracked file is `.gitignore`.

The Bitbucket slug is `formulys_api_nodejs`. Nothing in the tree states what Formulys is, who the API would serve, or which problem it would solve. Reading "Node.js API for Formulys" out of the slug is **Inferred** from the name alone. No `package.json`, `node_modules` listing, server file, or route exists to confirm a Node.js runtime.

**Unknown / Requires Confirmation:** product owner, intended clients, whether any API was ever written outside this git history, and whether another repository replaced this one.

## Branch reality

| Line | Tip | Date | What it is |
|---|---|---|---|
| `master` (only branch; `origin/HEAD`) | `9d191c4` | 2023-11-17 | Bitbucket-style initial commit containing `.gitignore` only |

The commit has no parent. History is that one commit. Nothing has been committed since 2023-11-17.

**Discrepancy:** the onboarding scan (captured 2026-09-28 on the issue) listed `sonar-project.properties` and `sonarqube_scan.bat` at the repository root. Neither file is in `9d191c4`. `.gitignore` does not match those names, so they are not excluded by the ignore rules that are in git. Provenance: **Unknown** — they may have been untracked files on the scan host.

## Objectives (from the implementation, not from a written plan)

No milestone document, roadmap, or issue list is in the repository. The commit message is "Initial commit".

No objective is stated in the file. The ignore patterns include `node_modules/` and `dist/`, which is consistent with a Node project that was never added. That reading is **Inferred** from two lines in a stock ignore list. It is not a written goal.

## Scope

### In this repository

- One tracked file: `.gitignore` (50 lines in `9d191c4`).
- Comments in that file point at `https://www.atlassian.com/git/tutorials/saving-changes/gitignore` and say the list should be customised.
- Ignore patterns for Node artifacts (`node_modules/`, `dist/`), Java `*.class`, Python `*.py[cod]`, `*.log`, `*.jar`, Maven `target/`, JetBrains `.idea/`, `TEST*.xml`, `.DS_Store`, `Thumbs.db`, `*.app`, `*.exe`, `*.war`, and several video and TIFF extensions.

### Not in this repository

- Application source, tests, a README, `package.json`, a lockfile, or a `src` directory.
- HTTP routes, a database client, authentication, background jobs, queues, or storage.
- Bitbucket Pipelines, Docker, infrastructure-as-code, or environment files.
- `sonar-project.properties` and `sonarqube_scan.bat` (named by the onboarding scan, absent from git).
- Any link, import, or submodule pointing at another Formulys repository.

Silicon Ark documents other Bitbucket repositories whose slugs contain "formulys": `formulys-frontend`, `formulys_simpleflow`, `formulys_simpleflow_backend`, and `formulys-mobile-app`. This tree does not reference them. `formulys_simpleflow_backend` is itself a Node server scaffold. Whether `formulys_api_nodejs` was meant to be that API, an earlier attempt, or an unrelated placeholder is **Unknown / Requires Confirmation**.

## System shape

```text
git@bitbucket.org:overdrive/formulys_api_nodejs.git
  master @ 9d191c4
    .gitignore
```

There is no process to draw. No server starts from this tree.

## Current status

**Implemented:** a remote repository whose default branch holds a stock ignore file and nothing else.

**Not started inside git:** the API the slug names. There is no later commit, no feature branch, and no tag to show work in progress.

Last change in git: 2023-11-17. Status at inspection: dormant placeholder.

## Dependencies known from the repo

None. There is no manifest. The ignore file names ecosystems (Node, Java, Python, Maven) without pinning a version or a package.

## Human confirmation

1. Was `formulys_api_nodejs` intended to hold a Formulys Node.js API, and was that work done only outside git?
2. Do `sonar-project.properties` and `sonarqube_scan.bat` exist only as untracked files on the scan host, and should they be committed?
3. Is this repository obsolete, superseded by `formulys_simpleflow_backend` or another repo, or still a placeholder awaiting code?
4. Who owns the product, who would call the API, and what problem it is for.
5. Should the stock `.gitignore` be treated as intentional policy for this project?