TenantAtlas/specs/345-platform-productization-readiness-roadmap-reconciliation-gate/roadmap-reconciliation.md

# Roadmap Reconciliation — Spec 345

**Branch**: `345-platform-productization-readiness-roadmap-reconciliation-gate`  
**Date**: 2026-06-02  

## Roadmap Theme Table

| Roadmap theme | Repo-real? | Productized? | Related specs | Related candidates | Gap | Recommended priority |
|---|---|---|---|---|---|---|
| Workspace/Environment shell and scope contract | yes | yes | `specs/338-*`; `specs/339-*`; `specs/340-*`; `specs/341-*` | stale queue items: `provider-connection-scope-hardening`, `canonical-link-query-cleanup`, `product-truth-docs-drift-cleanup` | Only minor wording follow-through remains; no structural shell blocker found. | Hold / protect |
| Customer Review Workspace / customer-safe consumption | yes | yes | `specs/312-*`; `specs/342-*`; `specs/343-*`; `specs/344-*` | stale candidate `customer-review-workspace-v1-completion`; UI lane `Customer Review Workspace productization` | Broad lane is effectively closed; only narrow polish should remain. | Hold / do not reopen as a broad next spec |
| Evidence / Review Packs / Audit disclosure | yes | partial | `specs/329-*`; `specs/337-*`; current runtime `EvidenceOverview`, `ReviewPackResource`, `StoredReportResource` | retained-artifact follow-through; stored-report/product-consumption follow-up | Core flow is strong, but retained-artifact state/lifecycle truth is still weaker than generation/download flow. | Next-later |
| Governance Inbox / Decision Register | yes | partial | `specs/327-*`; `specs/265-*`; `specs/306-*`; `specs/307-*`; `specs/308-*` | `decision-based-governance-inbox-v1`; UI lane `Governance Inbox decision experience` | Remaining operator workflow closure is the clearest central gap. | Now |
| Findings / Accepted Risks | yes | partial | `specs/343-*`; finding/finding-exception runtime and tests | no separate must-do candidate; tied to governance/artifact lanes | Lifecycle and customer-safe integration are solid; retained reporting/expiry clarity still depends on later work. | Next-later |
| Provider readiness / onboarding / permission posture | yes | partial | `specs/339-*`; `specs/281-*`; provider/onboarding runtime tests | UI lane `Provider onboarding/readiness UX cleanup` | Trust framing and dangerous-action guidance still need calmer productization. | Should-do-next |
| Localization / copy / neutral platform wording | yes | partial | `specs/275-*`; `specs/286-*` | stale candidates `Customer-Facing Localization v1` and `Customer-Facing Localization Adoption v1` | Foundation and major follow-through exist; remaining work is QA/polish or future external-surface wording. | Later guardrail |
| Commercial truth / billing-state maturity | yes | partial | `specs/247-*`; `specs/251-*`; `specs/274-*` | stale candidates `Commercial Entitlements & Billing-State Lifecycle v1`, `Billing & Subscription Truth Layer v1` | Internal truth layer exists; customer self-serve commercial portal remains separate and deferred. | Later / not next platform spec |
| Stored reports surface | yes | partial-to-yes | `specs/277-*`; `StoredReportResource` runtime | stale candidate `Stored Reports Surface v1` | Runtime exists, but retained-artifact lifecycle context still benefits from the broader artifact-lifecycle lane. | Later / merge with retained-artifact work if needed |
| Governance artifact lifecycle / retention | prepared package yes; runtime gap still open | no | `specs/267-artifact-lifecycle-retention/`; `specs/262-*` | `Governance Artifact Lifecycle & Retention v1` | Ready candidate with real value, but secondary to governance-inbox workflow closure. | Next-later |
| Workspace-first / ManagedEnvironment cutover pack | yes, as a concrete spec series | mixed | `specs/279-*` to `specs/287-*` | pack-level candidate is stale | Not a single open candidate anymore; use the existing spec-series truth instead of the old pack label. | Defer unless architecture work is deliberately resumed |
| Admin workspace navigation / tenant-owned surface repair | yes | mostly yes | `specs/301-*`; `specs/302-*`; `specs/303-*`; `specs/304-*` | conditional `navigation-contract-split` only | Historical migration group is mostly closed. | Only on fresh regression |
| Operations maturity / cross-domain indicators | yes | partial | `specs/328-*`; `specs/278-*`; `specs/268-*`; `specs/270-*`; `specs/271-*`; `specs/272-*` | `Cross-Domain Progress / Indicator Semantics` follow-through | Missing piece is not operations existence; it is semantics consistency and selective adoption. | Later |
| Cross-tenant compare / promotion | yes | partial | `specs/043-*`; `specs/264-*` | stale candidate `Cross-Tenant Compare & Promotion with Lineage v1` | Portfolio action exists as a spec lane already; not the most urgent platform productization blocker. | Later |
| Support access governance | yes | yes or functionally closed for current slice | `specs/276-support-access-governance/` | stale candidate `Enterprise Access Boundary & Support Access Governance v1` | Active candidate wording lags behind existing package reality. | Drop from active queue |
| Governed AI foundation / first runtime consumer | foundation yes; first consumer no | no | `specs/248-*` | `First Governed AI Runtime Consumer v1` | Foundation exists; visible runtime consumer is later strategic work, not a current platform sellability blocker. | Later |
| Customer portal / external consumption plane | no separate app/runtime in current product line | external/deferred | repeated non-goals across `specs/259-*`, `specs/260-*`, `specs/326-*`, `specs/342-*`, `specs/343-*`, `specs/344-*` | `291 Virtual Consultant / External Portal Guidance v1`; inferred customer portal slices | Current repo truth says `/platform` should prepare customer-safe outputs first, not become the portal itself. | Defer to `/customerportal` roadmap |
| Website / public marketing | separate app exists; not part of the platform lane | external | `apps/website`; website specs such as `specs/183-*`, `specs/213-*`, `specs/215-*` | public pricing/docs/lead-gen work | This belongs to `/website`, not the platform readiness queue. | Separate website roadmap |

## Reconciliation Notes

- The largest roadmap drift is not missing runtime; it is stale backlog wording that still treats several already-delivered or already-packaged lanes as open first-order candidates.
- The strongest repo-truth shift since older roadmap wording is the closure of the customer-review lane as a broad platform blocker. Recent Specs `342`-`344` materially changed that answer.
- The strongest remaining roadmap-to-repo gap is governance workflow closure, not a customer portal, not a shell rewrite, and not another broad review-workspace rewrite.