# RapidCloud Hub + Fleet redesign

This package turns the August 2026 Hub/Fleet MVP into a reviewable product
direction before production code is changed.

## Contents

- `prototype.html` — responsive, interactive prototype for six priority
  surfaces: Hub access states, Hub home, Hub app/update detail, Fleet access
  states, Fleet command center, and Fleet customer detail. The signed-in Hub and
  Fleet screens also contain interactive account menus.
- `screen-map.md` — information architecture, roles, states, and principal
  flows.
- `authentication-audit.md` — observed authentication modes, current gaps,
  ownership boundaries, and the release gate.
- `api-contract.md` — proposed customer-scoped application and deployment-run
  contracts needed by the redesigned experience.
- `implementation-plan.md` — production slices, file boundaries, tests, and
  acceptance criteria.

## Product stance

- **Hub is the customer's branded operational home.** Employees open their
  apps; customer administrators see availability, updates, documentation, and
  controlled deployment actions.
- **Fleet is RapidCloud's exception-driven control plane.** Operators start
  with unhealthy production, drift, failed releases, open requests, and
  expiring licenses instead of raw aggregate tables.
- **Presentation metadata has one source.** Logos, category, and customer-facing
  copy come from `rc-branding`; Fleet owns licenses, releases, requests, and
  health; customer/deployment configuration owns launch URLs.
- **The security boundary is unchanged.** Hub and the deployer remain in the
  customer's Azure tenant. Fleet stores operational metadata only and never
  needs Azure credentials or customer content.
- **Authentication is part of the product experience.** Hub owns branded entry,
  return, error, session, and account states around Microsoft Entra. Microsoft
  owns passwords, MFA, consent, and Conditional Access. Fleet uses RapidCloud
  SSO first and keeps password access as an audited emergency mechanism.

## Review order

1. Open `prototype.html` and review every state under `Hub · Access` and
   `Fleet · Access`.
2. Open Hub Home or Fleet Command Center and click the signed-in identity at the
   bottom of the sidebar to review the account menus.
3. Review the screen and flow decisions in `screen-map.md`.
4. Agree the identity boundaries and v2 read model in `api-contract.md`.
5. Implement the authentication foundation, then Hub home + `/v2/home`.