Docs / Planning And Delivery

Planning And Delivery

Delivery Plan

This file turns the roadmap into a practical sequence of execution.

deliveryplan

Source: DELIVERY_PLAN.md

DELIVERY_PLAN.md

Purpose

This file turns the roadmap into a practical sequence of execution.

Use it to answer:

what gets built next
what each milestone must ship
which surfaces are touched
what is still intentionally delayed

docs/ROADMAP.md is the strategic view. This file is the tactical build order.

Delivery rules

Keep Harbor Node as the primary product surface.
Favor shipping a safe, supportable product over adding more breadth.
Harden and polish what already exists before adding many more integrations.
Treat cloud as additive and support-oriented, not the default trust boundary.
Every milestone should end in a user-visible improvement or a real launch-readiness gain.

Execution order

Milestone 1

Production hardening and release foundations.

Milestone 2

Finish the local operator product loop.

Milestone 3

Finish narrow integration maturity and design-partner beta readiness.

Milestone 4

Public v1 launch readiness and go-live.

Milestone 5

Post-launch premium expansion.

Milestone 6

Billing, self-serve operations, and deeper org/team controls.

Milestone 1: Production hardening and release foundations

Goal

Close the biggest gap between Harbor's current alpha quality and production expectations.

Primary surfaces

apps/cloud-api
apps/cloud-admin
apps/website
apps/harbor-node-api
infra/docker
.gitea/workflows
docs

Must ship

production-appropriate cloud/admin/browser session posture
CI aligned with the pinned Node version
CI that runs meaningful tests, not only typecheck/build
documented deployment, backup, restore, rollback, and upgrade expectations
stronger deployment security guidance and HTTP header guidance
written release checklist for public go-live

Suggested work breakdown

Security and auth

move cloud/admin auth toward HttpOnly cookie sessions
tighten browser session/storage assumptions where needed
finish remaining high-value SSRF/header/session follow-up items

CI and release engineering

update CI from Node 22 to the pinned Node 24 toolchain
run package tests in CI where available
add smoke/build verification for the full workspace
define branch-to-release expectations

Ops and deployment

document production reverse proxy / TLS expectations
document backup and restore for Node SQLite, Hub SQLite, and Cloud Postgres
document environment-variable requirements clearly

Exit criteria

Harbor can be deployed and updated with written instructions
the most important auth/session paths use production-grade patterns
CI catches the highest-value regressions before merge

Milestone 2: Finish the local operator product loop

Goal

Make Harbor feel obviously usable to a real operator without source-level knowledge.

Primary surfaces

apps/harbor-ui
apps/harbor-node-api
apps/hub
apps/docs-site
packages/shared

Must ship

stronger onboarding and first-run guidance
clearer settings and node-target ergonomics
clearer Harbor Guard policy visibility
clearer Harbor Hub import/update state
clearer port auth-readiness and troubleshooting cues
better manager and async execution visibility where confusion still exists

Suggested work breakdown

Harbor UI

tighten onboarding checklist into a stronger first-run flow
add or improve policy summary/inspection UX
improve settings clarity and help text
make Harbor Hub-backed state and local state easier to distinguish

Harbor Node API

expose missing metadata needed by Harbor UI
improve status, policy, and auth-readiness summaries
improve install/troubleshooting diagnostics

Hub and docs

make install/setup guidance and upgrade guidance clearer
keep Hub metadata high-quality and import-friendly

Exit criteria

an operator can install Harbor, import a Harbor Hub entry, configure auth, test and publish actions, and understand system state without reading source code

Milestone 3: Narrow integration maturity and design-partner beta readiness

Goal

Finish the first real integrations and prepare Harbor for supported real-world usage.

Primary surfaces

apps/harbor-node-api
apps/harbor-ui
apps/cloud-api
apps/cloud-admin
apps/website
apps/docs-site

Must ship

Gmail as a supportable production-grade Harbor Port
one additional high-value OAuth-backed integration only if justified
improved OAuth reconnect/refresh/failure/audit flows
design-partner support playbooks
broader regression coverage for real customer journeys
clean admin/support operations for real member, enrollment, and contact workflows

Suggested work breakdown

Integration maturity

finish Gmail operator UX and failure handling
add one second example only if it sharpens the product story
keep token custody local-first

Beta readiness

test real customer journeys end to end
document support steps for common failures
tighten member/account/license guidance

Exit criteria

Breakwater can support a small number of real customers without unsafe shortcuts or constant manual debugging

Milestone 4: Public v1 launch readiness and go-live

Goal

Launch Harbor publicly with a narrow, honest, supportable promise.

Primary surfaces

apps/website
apps/docs-site
apps/harbor-ui
apps/harbor-node-api
apps/cloud-api
apps/cloud-admin
docs

Must ship

website and docs aligned with the actual shipped product
website running as the intended under-construction landing page plus gated preview
clear Community, Pro, and Business story
stable install, upgrade, and troubleshooting path
documented premium/manual support operations where self-serve is not ready
go-live checklist completed and signed off