# DIREKT MVP Scope

## MVP outcome

A real provider can be checked and published; a real customer can discover, evaluate and contact the provider; a real operations team can inspect the full lifecycle.

## In scope

### Android customer
- account and consent;
- area selection;
- category/text search;
- map and list;
- provider profile;
- check-specific trust details;
- saved provider;
- tracked enquiry;
- direct call/message handoff;
- enquiry history;
- eligible review;
- complaint/report;
- notifications and account controls.

### Android provider
- account/provider relationship;
- profile, services and operating model;
- service areas and consented public premises;
- local drafts;
- evidence upload;
- verification progress and remediation;
- availability;
- enquiries and response;
- reviews and responses;
- subscription/receipt basics.

### Backend
- identity and role enforcement;
- provider, category, location and verification domains;
- private evidence storage;
- geospatial search;
- enquiries/reviews/complaints;
- notifications;
- audit;
- subscription foundation;
- analytics and operations jobs.

### Admin/operations
- reviewer and field-agent workflows;
- evidence viewer;
- decisions/reasons;
- expiry/renewal;
- provider publication/suspension;
- complaints;
- support;
- financial exception visibility;
- configuration and audit.

## Pilot constraints

- one tightly controlled geography;
- limited provider categories;
- small verified supply cohort;
- staffed verification and support;
- no unattended national launch;
- approved payment/map/identity providers only.

## Out of scope

- native iOS;
- web customer marketplace as a production client;
- escrow and marketplace-held customer funds;
- credit, insurance or investment products;
- emergency dispatch;
- open bidding;
- anonymous public reviews;
- continuous location tracking;
- public certificates/IDs;
- automated final verification decisions;
- broad institutional procurement;
- international expansion.

## Scope change rule

A new feature may enter MVP only if it:

1. is supported by research;
2. is necessary to complete or protect the core loop;
3. has an owner, acceptance criteria and operational plan;
4. does not displace a higher-risk requirement;
5. is recorded in the decision log and roadmap.
