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

Next Spec Recommendation — Spec 345

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

Recommended next spec

• Recommended next spec: Governance Inbox Final Operator Workflow — a narrow follow-up over specs/327-governance-inbox-decision-first-workbench-productization/, specs/265-decision-register-approval/, specs/306-decision-register-reconciliation/, specs/307-decision-register-evidence-operationrun-link-polish/, and specs/308-decision-register-summary-review-pack/
• Reason: Repo truth shows that shell/scope, customer review, and evidence/review-pack foundations are already much stronger than the backlog wording suggests. The largest remaining operator-facing gap is the central decision queue itself: /admin/governance/inbox still needs one dominant queue-clearing posture, calmer evidence ordering, explicit next action, and stronger downstream customer-safe wording before the platform feels fully repeatable and sellable.
• Why not the alternatives:
  • Not Customer Review Workspace again: that lane is already materially closed by specs/312-*, specs/342-*, specs/343-*, and specs/344-*.
  • Not Evidence & Review Pack Output Contract first: core evidence/review-pack flow is already strong through specs/329-* and specs/337-*; the remaining evidence gap is mostly retained-artifact lifecycle clarity, not core output availability.
  • Not Provider Readiness first: provider surfaces still need calmer trust framing, but they are already scope-safe and usable after specs/339-* and specs/281-*; the governance queue is the more central daily-use blocker.
  • Not Localization & Customer-Safe Copy first: major localization/neutralization follow-through already exists in specs/275-* and specs/286-*; remaining work is QA/polish.
  • Not a new smoke-matrix-first spec: targeted Browser/Feature confidence is already strong through specs/340-* and recent strategic Browser suites; workflow clarity is the bigger current productization issue.
  • Not Customer Portal: repo history repeatedly rejects sneaking external-consumption work into Filament /platform, and the boundary still holds.
• Preconditions:
  • keep workspace/environment shell contracts from specs/338-* to specs/341-* untouched
  • treat Decision Register as the historical/proof ledger, not as the primary queue
  • reuse existing finding, evidence, review, accepted-risk, and OperationRun links rather than creating new truth
  • forbid new task-engine, Kanban, PSA, or customer-portal scope
• Risks:
  • scope creep into a generic workboard or approval engine
  • duplicating decision truth already present in Decision Register or finding/exception surfaces
  • adding workflow mutation scope that should remain in existing owner surfaces
• Acceptance target:
  • /admin/governance/inbox reads as the central operator queue
  • one dominant next action is visible per decision item or section
  • evidence basis, owner, age/SLA, and environment scope are explicit without overloading diagnostics
  • links into findings, reviews, proof, runs, and historical decisions reuse current truth instead of inventing new persistence
  • no portal, no new decision table, no new approval engine, and no shell rewrite are introduced
• Follow-up sequence (next 3–7 specs):
  1. Governance Inbox Final Operator Workflow (new follow-up over current governance runtime)
  2. specs/267-artifact-lifecycle-retention/ if retained-output trust remains the next strongest blocker after governance closure
  3. Provider Readiness / Onboarding Productization as a narrow follow-up over specs/339-* and specs/281-*
  4. runtime follow-through for specs/278-cross-domain-indicator-audit/ if indicator drift keeps reappearing on dashboards/ops/evidence surfaces
  5. retained-artifact browse/report polish only if StoredReportResource still feels insufficient after artifact-lifecycle work
  6. later strategic work such as a first governed AI runtime consumer only after the operator platform is calmer

Deferred Lines (explicit)

• Customer portal line:
  • defer external customer review history, evidence download center, branded document consumption, and any external portal guidance into a future /customerportal roadmap
  • do not pull these into Filament /platform as “just one more read-only page”
• Feature-expansion line:
  • broader PSA/ITSM sync, first governed AI runtime consumer, cross-tenant portfolio expansion, and customer self-serve commercial flows stay behind the operator-platform productization sequence above