# Slice 7: MVP Scope Decision

## Status

Complete

## 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

- [x] Inventory ambiguous or conflicting MVP statements.
- [x] Define minimum release workflows.
- [x] Decide that AI is provider-neutral and post-MVP.
- [x] Decide that every modeled authentication type is release-blocking.
- [x] Confirm the six acceptance workflows in `MVP_SCOPE.md`.
- [x] Convert the decisions into measurable release criteria.
- [x] Update project state and dependent plans.

## 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

### 2026-07-18

- Removed IBM Bob/watsonx from MVP scope.
- Required all five modeled authentication modes.
- Approved six end-to-end acceptance workflows.
- Created `MVP_SCOPE.md`.

## Handoff

- Last completed: Product owner approved and documented the MVP scope.
- Next action: Use `MVP_SCOPE.md` to drive implementation and release acceptance.
- Known blockers: None.