Current State and Roadmap designed
This page is the product-owner summary. It is not the backlog system. It tells readers what they can rely on today, what is actively being closed, and which roadmap themes still define product maturity.
For the faster “what is real right now?” readback, pair this page with Platform Status.
Implemented Foundations
| Area | What is real now |
|---|---|
| Capacity control plane | Catalog, allocation lifecycle, node inventory, admin/operator surfaces |
| Access/runtime | Browser terminal path, SSH posture, session/token boundaries |
| Billing | Ledger-backed usage, balance posture, payment/top-up path |
| Storage | User storage operations with path-safety controls |
| App platform base | App catalog, manifest model, SDK direction, artifact trust/promotion direction |
| Documentation portal | Audience-first portal structure for product, architecture, security, operators, developers, and user-guide paths |
Active Closeout Themes
| Theme | Why it is active now |
|---|---|
| MFA product completion | The product flow must be coherent for user/admin/operator paths, not only technically implemented |
| Documentation portal completion | Teams need a stable portal for handoff, review, onboarding, and ARB/JAD use |
| CI/CD and deploy discipline | The same reviewed SHA should drive CI, deploy, and UAT evidence |
| Environment maturity | Kind/dev are active delivery environments; staging/demo are the next repeatable platform steps |
Near-Term Roadmap Pressure
| Roadmap area | What “done enough” looks like |
|---|---|
| Product flow coverage | Complete user/admin/operator flows exist, are documented, and are covered by UAT |
| Generated API/SDK reference | Developers and app builders can rely on rendered contracts and working onboarding docs |
| Observability and operator read models | Operators can verify runtime, release, and incident state without repeated direct inspection |
| Production-readiness controls | Security, release, rollback, and evidence posture are explicit and reviewable |
| Shared-platform reuse | IAM, policy, onboarding, evidence, and registry models are reused by future products rather than reimplemented |
What This Page Is Not
- not a replacement for Fairway task state;
- not a substitute for canonical product specs;
- not a release certificate.
Use this page to orient product and review conversations. Use Fairway and the canonical source docs for exact work state.