Product Team Handoff in-progress
Use this page when the question is not "how is the system built?" but
"what can we ship, what still needs work, and what should product look at
first?"
Reading Order
- Product Strategy
- User Interactions
- Journeys and v3 IA
- Launch, Allocation, and Runtime Flow
- Competitive Context
- Portal Execution Roadmap
Product Decision Route
Product Triage Flow
What Is Implemented Now
| Area | Current state |
|---|
| Core platform shell | Product shell, role-aware navigation, account/access/admin surfaces are present and under active v3 refinement |
| Compute lifecycle | Catalog, launch, allocation state, release, terminal/SSH, and storage paths exist |
| Billing | Usage accrual, ledger, checkout/top-up, warnings, and payment evidence are implemented |
| Admin and ops | Node, allocation, audit, release, and evidence surfaces exist, with some production-readiness gaps still explicit |
| App platform direction | App catalog, SDK, manifest, promotion, and artifact/runtime direction exist, but full app lifecycle maturity is still incomplete |
| Documentation portal | Persona-first portal baseline is live; this follow-up batch is improving product handoff, user guide quality, and audience completeness |
Current Product-Critical Work
| Theme | Why product should care | Current status source |
|---|
| MFA journey completion | User/account MFA flows must be coherent before the feature can be called product-complete | Fairway MFA tasks and program memory |
| Demo readiness | Demo must reflect canonical routes plus retained fixtures/apps, not only deploy success | Fairway demo tasks and demo UAT evidence |
| Docs portal audience completion | Product, IAM, infra, operators, and end users need clearer handoff paths | This docs follow-up epic |
| Staging and demo environment repeatability | External review and validation quality depend on repeatable env setup | Staging/demo task groups |
Product Queue View
The portal should summarize product pressure, not replace Fairway as the live
work queue.
| Queue bucket | What belongs here |
|---|
| Shipping now | User-visible flows, UAT blockers, deploy-readiness issues, and exact acceptance gaps |
| Hardening next | Sensitive operations, superadmin posture, env parity, rollout safety, and operator visibility |
| Platform leverage | Docs portal, SDK/dev experience, environment automation, and release/runtime evidence |
| Future roadmap | Multi-provider edge, staging/demo scale-out, stronger app lifecycle, sovereignty/air-gapped models |
For exact live task state, use Fairway. For product interpretation, use the
roadmap and source docs linked from this page.
Product Owner Checklist
Product Review Rule
A feature is not product-complete because a backend path or admin proof exists.
The user, admin, operator, and recovery journeys must all be coherent enough to
test and explain without sending the reader into source docs or provider
internals.
Product Decision Boundaries
| Decision area | Product stance |
|---|
| Current vs future | Mark future-state clearly; do not present roadmap items as deployed behavior |
| User flow quality | A feature is not complete because the backend path exists; the user/admin/operator journey must be coherent |
| Queue ownership | Fairway owns live task state; portal pages summarize themes and decisions |
| Audience split | Internal-only strategy, queue, and readiness detail stay internal even when public/customer tracks exist later |
| Follow-up | Outcome |
|---|
| User guide flow pack | Primary user/admin flows become screenshot-ready and easier to test in UAT |
| Audience handbooks | IAM, infra, token-factory/shared-platform builders, and operators get clearer direct paths |
| Publish path | Portal hosting path becomes explicit for this iteration instead of implicit in historical docs |