# Slice 7: MVP Scope Decision

## Status

Not started

## Objective

Define one testable MVP release boundary, especially whether IBM Bob/watsonx integration is required for the initial release.

## Dependencies

- Product-owner decisions
- Existing requirements, architecture, and task inventory

## In Scope

- AI-in-MVP decision
- Required personas, workflows, deployment model, inclusions, exclusions, and acceptance criteria
- Reconciliation of conflicting requirement statements

## Out of Scope

- Feature implementation and detailed post-MVP roadmap planning

## Tasks

- [ ] Inventory ambiguous or conflicting MVP statements.
- [ ] Define minimum release personas and workflows.
- [ ] Decide whether AI is required, optional, or post-MVP.
- [ ] If required, define the smallest acceptable AI capability and provider boundary.
- [ ] Decide whether every modeled authentication type is release-blocking.
- [ ] Confirm component, lifecycle, persistence, export, observability, and deployment expectations.
- [ ] Define explicit non-goals and accepted limitations.
- [ ] Convert the scope into measurable release criteria.
- [ ] Update `TASKS.md`, `CODEX.md`, requirements, architecture, and dependent slices.

## Acceptance Criteria

- [ ] One authoritative MVP definition exists without contradictory release requirements.
- [ ] AI has an explicit status and, if included, a bounded acceptance test.
- [ ] Every requirement maps to a slice and validation criterion.
- [ ] Deferred features are clearly labeled post-MVP.
- [ ] Slice 6 has a definitive release checklist.

## Validation

- [ ] Requirements, architecture, tasks, and slices use consistent language.
- [ ] No open question can materially change MVP completion.
- [ ] The product owner approves the release boundary.

## Risks and Open Questions

- AI ambiguity can invalidate estimates and acceptance late in development.
- Aspirational requirements can make the MVP impractically large.
- Scope reduction must not discard required security controls.

## Progress Log

No work recorded yet.

## Handoff

- Last completed: Slice plan created.
- Next action: Present conflicting statements and obtain product-owner decisions.
- Known blockers: Requires user approval and should be resolved early despite its number.