# Current Personas and Fixture-backed Marketplace State

Last Updated: 2025-08-09

This document captures the canonical demo/test state of the Project Mycelium when running with fixtures.
It enables developers and reviewers to reproduce the exact marketplace state and verify the intended UX.

- Data Source: fixtures (filesystem)
- How to run:
  - APP_DATA_SOURCE=fixtures
  - APP_FIXTURES_PATH=./user_data
  - APP_DEMO_MODE=true (optional banner and safe guards)
  - APP_ENABLE_MOCKS=false (we do not rely on MockDataService)

## Snapshot

- Users: 10 (user1..user10)
- Providers: user1..user3
- Mixed (provider+buyer): user4..user6
- Buyers: user7..user10
- Products: 3 (seeded; will expand)
  - WireGuard VPN (category: applications) — provider: user1@example.com — featured
  - Public Gateway Bundle (category: gateways) — provider: user2@example.com
  - Object Storage (100GB) (category: applications) — provider: user3@example.com
- Services: TBD
- Orders: TBD

## Personas (credentials for demo)

These credentials are for demo/test environments only. Do not ship to production.

| Persona | Email               | Password | Roles               |
|---------|---------------------|----------|---------------------|
| user1   | user1@example.com   | password | ["provider"]        |
| user2   | user2@example.com   | password | ["provider"]        |
| user3   | user3@example.com   | password | ["provider"]        |
| user4   | user4@example.com   | password | ["provider","buyer"] |
| user5   | user5@example.com   | password | ["provider","buyer"] |
| user6   | user6@example.com   | password | ["provider","buyer"] |
| user7   | user7@example.com   | password | ["buyer"]           |
| user8   | user8@example.com   | password | ["buyer"]           |
| user9   | user9@example.com   | password | ["buyer"]           |
| user10  | user10@example.com  | password | ["buyer"]           |

## Ownership and Data Rules

- No orphan data: every product/service has an owner_user_id.
- Orders link buyer_user_id -> items -> product_id/service_id.
- Future payments will be linked via payment records.

## Known Scenarios to Verify

- Buyer journey (add to cart, buy-now, view invoice).
- Provider publishing a product/service and seeing it live.
- Insufficient balance UX contract where applicable.

## Reset and Updates

- Reset to seed (planned): cargo run -- seed --reset
- Fixtures path: ./user_data
- Versioning: see ./user_data/version.json

## Change Log

- 2025-08-09: Initial scaffold with 10 demo users, pending product/service/order seeds.