Create a New Store Opening Command Center in Enter for a U.S.-based multi-unit restaurant brand. Help the opening team move each new store from planned tasks to verified evidence, staffing and training readiness, an approved soft opening, and tracked opening-week results.

[TARGET USERS]
- New Store Opening Manager: Oversee all launches, assign owners, review evidence, and approve the soft opening for assigned stores.
- Franchisee / Store Owner: Update store tasks, upload evidence, and report blockers.
- HR / Training Manager: Track hiring stages, staffing targets, and training and certification.
- Administrator: Manage stores, workstream templates, task dependencies, users, and access scope.

[CORE WORKFLOW]
1. Create a launch for a store with address, format, timezone, target opening date, soft-opening date, and owner. Generate tasks by workstream: Hiring & Training, Store Setup, Permits / Admin, Vendor / Supply, Systems / POS, Local Marketing, and Opening Readiness.
2. Give each task an owner, due date, dependencies, status, notes, and an evidence requirement. Show blocked tasks, what they hold up, and the next actions on the store dashboard and timeline.
3. Track candidates from Applied to Hired, plus training and certification for every hire.
4. Lock soft-opening approval until all prerequisites are met, list every unmet prerequisite, and let only the assigned opening manager approve.
5. After approval, unlock Opening Week Day 1-7 daily reports for actual sales, orders, guest ratings, and issues.

[CORE PAGES]
- AI Launch Guide: Read-only answers about risks and next actions based on the current launch data.
- Launch Dashboard: Opening status, verified completion, blockers, soft-opening gate, workstream readiness, and next actions.
- All Launches, Launch Workflow, and Timeline: Portfolio status, the connected launch steps, and a dependency-aware plan.
- Workstreams: Task table with owner, due date, status, dependencies, and evidence.
- Hiring & Training, Opening Readiness, and Opening Week: Staffing pipeline, approval gate, and day-by-day reporting.
- Data Management: Imports, templates, users, and access.

[DATA AND BUSINESS RULES]
- Use stable IDs to link stores, launches, workstreams, tasks, dependencies, evidence files, candidates, training records, approvals, and daily reports.
- Count only verified tasks with required evidence in completion rates. A task that requires evidence cannot be completed without it.
- Soft-opening approval requires verified required tasks, staffing coverage, and at least 90% of hires trained and certified. Any later regression invalidates the approval but keeps its history.
- Treat AI guidance as read-only suggestions that separate verified facts from missing information; it must not change task status or approve gates.
- Use each store's local timezone for due dates and reports, and never accept future-dated actuals.
- Include a demo case: East Austin Drive-Thru, Austin, TX, target opening 09/20/2026, soft opening scheduled for 09/17/2026. Verified completion is 53% with 2 blockers; "Pass health inspection" (Alex Morgan, due 09/06/2026) is blocked and missing required evidence; 39 of 47 hires are recorded and 32 of 39 are trained; 8 prerequisites are unmet, so the soft opening stays locked and Opening Week reporting is unavailable.

[VISUAL DIRECTION AND DELIVERABLES]
- Use a focused operations workspace with clear status colors, compact cards, readable task tables, and visible locks on gated steps.
- Support desktop and mobile so store owners can update tasks and upload evidence on site.
- Use labelled demo data with consistent IDs and dates, USD amounts, and U.S. date conventions.
- Deliver a publishable demo with one traceable path from a blocked task to the locked soft-opening gate.

Before building, provide a requirements summary, missing information, page architecture, data model, readiness rules, role permissions, state transitions, and acceptance criteria. Do not begin generating pages yet.