
# Start Here — Respiratory Care Professional BREATHE Mission Control

This download gives Hermes the complete materials needed to build `My BREATHE`. It is not yet the finished application.

## Five-minute start

1. Save the original ZIP unchanged.
2. Do not add patient information, patient-linked narratives, credential secrets, restricted employer records or other sensitive content.
3. Extract a working copy and verify it with `python3 tools/verify-build-kit.py --package .`.
4. Open a private, isolated Hermes implementation workspace.
5. Give Hermes the complete package and paste the instruction from `README-FIRST.md`.
6. Review the Implementation Activation Card. Choose **Approve**, **Revise** or **Cancel**.
7. Keep every checkpoint receipt. The build may require several visible turns.
8. Accept the application only when the final report says what was actually built, tested, blocked and supported.

## What the finished product is intended to contain

- one RT-owned My BREATHE Command Center;
- the exact Core Four and an empty optional fifth launcher;
- five protected foundation workspaces and explicit personal/employer/academic/business/community context;
- twenty-four BREATHE powers installed inactive;
- twenty-four runnable workflow cards in Preview;
- thirty canonical BREATHE templates;
- the Assess → Diagnose/Define → Plan → Implement → Evaluate loop;
- Guide, capability, evidence, agent, privacy, memory, diagnostics and recovery pages.

## Honest completion states

- **Operational** — all applicable records passed, including a genuine configured streamed response and cancellation through the packaged UI.
- **Core operational; AI setup pending** — every offline/core criterion passed, but a live backend was unavailable for the genuine-stream test.
- **Not operational** — one or more core criteria failed or remain blocked.

Until Hermes produces that report, readiness remains `not_operational_build_required`.
