# Developer Workflow Runbook

This runbook defines the safe working process for the JARVIS Command Dashboard repository.

## 1. Before work

```bash
git status --short --branch
git rev-parse HEAD
```

Then:

- Confirm the current phase.
- Check which files are allowed to change.
- Do not copy runtime data into the repo.
- Do not open Health DB or Finance runtime unless the current phase explicitly allows it.
- Do not call real domain endpoints unless the current phase explicitly allows it.

## 2. During work

- Touch only files in scope.
- Use synthetic examples only.
- Keep contracts and docs aligned.
- No UI/gateway/adapter work during docs-only phases.
- No npm install or Python dependency install unless explicitly approved.
- No generated reports, screenshots or media without allowlist.

## 3. Before commit

Run:

```bash
make verify
git status --short
```

Review:

```bash
git diff --stat
git diff
```

Confirm:

- no forbidden file types
- no real `.env`
- no credentials
- no runtime folders
- no Health/Finance raw data
- contract JSON examples are valid

## 4. Commit

Use a clear commit message, for example:

```bash
git add <files>
git commit -m "chore: add repository safety bootstrap"
```

## 5. Push

Push with the configured GitHub credential path. Do not print tokens.

After push, verify remote SHA:

```bash
git ls-remote origin refs/heads/main
```

## 6. Abschlussmeldung

Report:

1. Commit SHA
2. changed files
3. tests/checks run
4. security scan result
5. what remained intentionally disabled
6. open points
7. recommendation for next phase

## Phase discipline

Do not proceed to the next phase until Sir has reviewed and approved the result.