docs: add promotable candidate backlog

docs/product/spec-candidates.md

@@ -53,6 +53,94 @@ ## Active Candidate Queue
 
 The historical record for `Workspace, Tenant & Managed Object Lifecycle Governance v1` remains below because it was promoted intentionally, not automatically, into Spec 262 and must not re-enter the active auto-prep queue.
 
+## Promotable Candidate Backlog
+
+**Boundary**: manual promotion only, not auto-prep. These items are intentionally outside `next-best-prep` and require an explicit product decision before any future spec refresh or follow-up work.
+
+### Auditor Pack Delivery & Executive Export v1
+
+- **Priority**: 1
+- **Repo truth**: review-pack export, evidence, tenant review, customer review productization, compliance mapping, and governance packaging foundations are already spec-backed.
+- **Why promotable now**: this is the clearest remaining step between repo-real governance truth and auditor-/executive-ready delivery.
+- **Why manual promotion only**: this is a bounded packaging and export decision, not an automatic next-best-prep foundation gap.
+- **Anchors**:
+  - `specs/109-review-pack-export/spec.md`
+  - `specs/153-evidence-domain-foundation/spec.md`
+  - `specs/155-tenant-review-layer/spec.md`
+  - `specs/258-customer-review-productization/spec.md`
+  - `specs/259-compliance-evidence-mapping/spec.md`
+  - `specs/260-governance-service-packaging/spec.md`
+
+### Cross-Tenant Promotion Execution v1
+
+- **Priority**: 2
+- **Repo truth**: cross-tenant compare preview and promotion preflight are already prepared, but execution is still the missing product action.
+- **Why promotable now**: this is the next MSP-multiplier after customer-safe review and packaging follow-through.
+- **Why manual promotion only**: the repo already has the compare/preflight preparation package, so only the narrower execution slice should be promoted deliberately.
+- **Anchors**:
+  - `specs/043-cross-tenant-compare-and-promotion/spec.md`
+
+### Governance Decision Pack & Approval Workflow v1
+
+- **Priority**: 3
+- **Repo truth**: governance convergence is spec-backed, but the bounded human-in-the-loop decision-pack workflow is still a distinct follow-up gap.
+- **Why promotable now**: it is the next decision-based operating slice after convergence, without expanding into autonomous remediation.
+- **Why manual promotion only**: this must stay an explicit product choice because the v1 scope is intentionally narrow: decision pack, reason, impact, evidence, recommended action, approve, reject, snooze, assign, audit trail, optional OperationRun link, no autonomous remediation in v1.
+- **Anchors**:
+  - `specs/257-governance-decision-convergence/spec.md`
+  - `docs/product/roadmap.md`
+
+### Customer-Facing Localization Adoption v1
+
+- **Priority**: 4
+- **Repo truth**: the localization foundation is already spec-backed; the open gap is customer-facing adoption, glossary completion, and productized surface coverage.
+- **Why promotable now**: localization is now a productization follow-through task, not a greenfield foundation.
+- **Why manual promotion only**: the broad foundation is already covered, so only a narrower adoption slice should be promoted deliberately.
+- **Anchors**:
+  - `specs/252-platform-localization-v1/spec.md`
+  - `specs/258-customer-review-productization/spec.md`
+  - `specs/260-governance-service-packaging/spec.md`
+
+### Billing & Subscription Truth Layer v1
+
+- **Priority**: 5
+- **Repo truth**: plans, entitlements, and commercial lifecycle maturity are already spec-backed, but the billing/subscription truth layer is still missing.
+- **Why promotable now**: this is the remaining commercial truth gap after entitlements and lifecycle groundwork.
+- **Why manual promotion only**: the broad readiness work is already covered, so this should not be reintroduced as an automatic foundation candidate.
+- **Anchors**:
+  - `specs/247-plans-entitlements-billing-readiness/spec.md`
+  - `specs/251-commercial-entitlements-billing-state/spec.md`
+
+### Stored Reports Surface v1
+
+- **Priority**: 6
+- **Repo truth**: the stored-reports substrate is already grounded by evidence and review foundations, but the product surface remains incomplete.
+- **Why promotable now**: this is the cleanest path from retained governance artifacts to a customer- and operator-usable surface.
+- **Why manual promotion only**: this is a focused product-surface follow-up, not an unprepared foundation gap.
+- **Anchors**:
+  - `specs/153-evidence-domain-foundation/spec.md`
+  - `specs/155-tenant-review-layer/spec.md`
+  - `specs/260-governance-service-packaging/spec.md`
+  - `docs/product/implementation-ledger.md`
+
+### Workspace & Tenant Closure Lifecycle v1
+
+- **Priority**: 7
+- **Repo truth**: lifecycle taxonomy is already explicitly captured as a spec-backed foundation, but closure/runtime follow-through is still open.
+- **Why promotable now**: it is the next bounded runtime slice after the taxonomy-first package.
+- **Why manual promotion only**: it must remain a deliberate follow-up and not collapse back into an automatic reopening of the broader taxonomy work.
+- **Anchors**:
+  - `specs/262-lifecycle-governance-taxonomy/spec.md`
+
+### First Governed AI Runtime Consumer v1
+
+- **Priority**: 8
+- **Repo truth**: the private AI governance foundation is already spec-backed, but there is still no first real governed runtime consumer.
+- **Why promotable now**: it is the clearest bounded follow-up once higher-priority sellability, promotion, and commercial-truth gaps are addressed.
+- **Why manual promotion only**: the foundation already exists, so the next move must be an explicit runtime-use-case decision rather than a repeated foundation-prep cycle.
+- **Anchors**:
+  - `specs/248-private-ai-policy-foundation/spec.md`
+
 ## Deferred / Existing Drafts Outside the Current Queue
 
 These items are still useful, but they are not the next best open specs from the current repo state.